62 Transfer from Basecamp to Explore

  Contents First Previous Next

Import GPX files into EXPLORE

Most mapping software will allow you to export a gpx file of tracks, routes and saved waypoints. Basecamp makes this process particularly easy, and that is what I have used for this experiment. I created a 200 mile route In northern England and created a gpx file of the route and of the track.

These gpx files can be imported into the Garmin Explore website - either as a route or as a track. So that makes four different possible outcomes. I’ve taken each of these 4 situations and produced a screenshot of the result on the Explore website. Comments describe how the result appears in the XT.

In case you have missed a previous section, once a route or track is in your account on the Explore website, it automatically appears on your XT - synchronising through the Garmin Drive App on your phone.

In a few examples I have mentioned 'Track-Trip' routes. These are the routes that are created when the Zumo is asked to convert a track to a trip, and are described in more detail at the bottom of this page.

Importing a GPX Track to Garmin Explore



Basecamp GPX Track -> EXPLORE Track - (Pic 1)

Explore accepts the entire track, point by point, (many hundreds of them) and displays it on the Explore Map. No Waypoints are transferred or displayed.

When the XT Synchs with Explore, the identical track is displayed. There is no indication from Explore that the number of points has been reduced. Tracks have no route points of any kind, so none of the saved Waypoints are transferred to the Explore site. The hundreds of track points are represented on the Explore map as small blue triangles - and as you zoom in, more become visible.

The Zumo XT is able to use a track for navigation, as described earlier. The course is plotted faithfully, it can never be altered by the XT and if you wander off route, a dotted line is drawn on the screen indicating the direction to the closes point of the track. The lower right data ‘button’ on the XT indicates how far it is to get back to the track.






BaseCamp GPX Track -> EXPLORE Route - (Pic 2).

The Explore site receives the entire track, but the XT has to calculate a route between every pair of adjacent points - so it limits the number of points to 200. If the route is 200 miles long, this will average out to about 1 point every mile, but it does this intelligently, it removes more points from long straight sections and keeps more points on the twisty roads.

This should generate a pretty accurate route, but it is important to have the Zumo settings of eg Faster Time, No Avoidances to be set the same as the program that created the route and track in the first place. In theory the XT could create a slightly different route - motorway slip roads spring to mind.

The route on the Explore map looks perfect - but it consists of 199 straight lines. The Zumo XT will have the job of plotting a route between each pair of the 200 points.

The XT creates a route that can be navigated, giving turn by turn directions. It has no intermediate routing points, but behaves like the ‘Track-Trip’ route - the route doesn’t alter, but if you deviate, it calculates a way to rejoin the track at the closest navigable point.




Importing a GPX Route to Garmin Explore


Basecamp GPX Route to Explore Track - (Pic 3)

Explore takes any Waypoints and plots them on the map as triangles. If there are no Waypoints (ie created and saved in Basecamp with the flag tool), then there will be no Waypoints on Explore's map.

The track is drawn independently on the Explore map, as a series of dashed straight lines.

When it appears in the XT after pressing Go! , this displays as a normal track, with a dotted magenta line indicating the straight line route to the start of the track, or back to the track if you wander away from it.

Any Waypoints that formed part of the original route are also transferred with the track and are displayed on the screen as blue flags. They appear in the XT’s list of favourites under the Explore banner. If the link to Explore is removed, the favourites from Explore are no longer available.






Send a BaseCamp Route to Explore Route - (Pic 4)

Surprisingly, Explore displays the route in the same way that it displays the track in Pic 3 - A series of straight lines which appear to join together the original route points. Again, if there were no saved waypoints in the route, then no triangles are shown on the map.

The original curvy route is abandoned - only straight lines are shown.

On sync with the XT, any Waypoints are added as Explore’s Favourites.

This Route is not transferred from Explore to the XT. Explore on a PC does not cater for sending routes to the XT. Only tracks.



Using Straight Line Tracks on the XT.

For both of the scenarios above, where Explore is presented with a straight line joining together the original route points, the track (not the route) can be synched with the XT and it can be converted to a trip. It will create a magenta line which follows roads, passes through the original route points, and issues instructions.



'Track-Trip' is a term that I introduced into these notes to distinguish between a 'Trip' which is created with the XT's Trip Planner App, and the term that the XT uses when it converts a Track into a 'Trip'.

A 'Trip' is a sequence of route points and information which defines how a route should be calculated by the Zumo. The Zumo is able to calculate a new route from the parameters in the Trip, should the rider deviate from the original.

A Track-Trip is a navigable magenta line created from a track and has no visible intermediate points.

Like a Track, it remains fixed. but it is able to plot a new section of route to the closest point of the original, should the rider deviate from the magenta line.


  Contents First Previous Next

The information on these pages has been acquired from personal experience of using and testing the behaviour of Basecamp and my Zumo XT. I have no links with Garmin, and these pages should not be regarded as instructions. They are presented for interest only. The contents of these pages must not be shared, copied, transmitted, redistributed or re-published in any form without my permission. (C) JHeath 2021.