Features

· Enhanced file management with bi-directional file transfer between zumo and PC, multi-select support, logical file naming, organization, and grouping.

· Automatic or easy setting of routes to “saved” rather than “imported” which prevents “RUT” behavior.

· Detailed viewing and editing of .trip file content including an overview on an Open Street Maps (OSM) map and a detailed hexadecimal view.

· Creation of .trip files on the zumo directly from .gpx files on the computer, including those created by Basecamp or other route planning software, eliminating the need to import and save routes and other data.

· Creation of .gpi (point of interest) files from .gpx files and display of .gpi file information.

· Post-processing of .gpx files including optional prefixing of shaping point names with route information.

· Automatic comparison and visual presentation, on an OSM map, of .trip file content on the zumo with .gpx file content on the computer. This allows a user to check that a route calculated by the zumo matches the route specified by the .gpx file. Any desired adjustments can be made while sitting at a computer before beginning to travel rather than on the roadside when a problem arises.

· Routes can be shared with others using identical zumo models by directly sharing .trip files.

· Trips can be Imported and Exported to and from CSV, or to Excel via the clipboard.

· Experimental support has been added to calculate a route in the Trip Editor using GeoApify,

· It can show detailed data that is stored in the Explore.db on your device, including a visualization on the map, and exporting to GPX. Ideally it should be the same as in the cloud.

Trip Manager is a Windows based program developed by FrankB of this forum as an alternative way of sending routes, tracks and waypoints to the Zumos XT1 and XT2.

You still connect your XT1/XT2 to your PC with a USB cable, but TripManager then takes care of creating the necessary route files in the Zumo. It is a smooth and easy to follow operation which by-passes the normal import process. In doing so it avoids all of the little quirks that the Zumo's internal import process seems to create.

This process undertaken by TripManager happens so quickly that really I wonder why the Zumo makes so much fuss about importing routes !

The map can be panned, zoomed in and out, and the precise location of route points can be verified at street level.

TripManager (TM) is (in short) a powerful (if not the most powerful) Windows program for transferring routes to Garmin navigation devices (In particular the Zumo XT, XT2, XT3 and Tread 2 series) and for analyzing the *.trip files used internally by these devices, which are crucial for their operation.

Since the Garmin navigation devices supported by TripManager (TM) do not internally use routes from GPX files or from BaseCamp (contrary to what is likely a widespread assumption), but instead use the *.trip files generated from them, TripManager (TM) essentially serves to “manage” these *.trip files.

With TripManager (TM), you can transfer routes from GPX files (including via drag-and-drop) directly into the navigation device in such a way that further editing within the device itself is (in principle) no longer necessary.

When using TripManager (TM), there is no need for an additional import process in the navigation device itself, since TripManager (TM) directly uses the device’s internal route format (*.trip files). For example, a GPX import that can sometimes take several minutes on the GPS unit itself can be completed in just a few seconds using TM.

In addition to the advantage of directly using Garmin’s internal trip format for routes, TripManager (TM) can also effectively prevent the (all- too-common and “unpopular”) RUT behaviour that occurs when there are deviations in the route.

Furthermore, TripManager (TM) is also ideal for listing the navigation system’s internal trips (imported routes).

This is a huge help for anyone experiencing Tread App synchronization issues or “orphaned routes”, because TM makes it very easy—and, above all, quite reliable—to identify duplicate trips (routes) that are causing problems.

With TM, the “Import” flag for existing routes—which is one of the causes of the RUT problem—can also be corrected directly (just as it is when transferring data using TM itself).

The routes listed in the navigation content can also be displayed directly on a selection of maps using TM for verification (or comparison with the original GPX file).

For (more experienced) users, detailed trip information—including otherwise hidden route details—is also available.

Among other things, the app offers several additional features, such as route comparison, sharing/exporting to Kurviger, viewing Explore content, settings, and the Vehicle Profile database. Another feature that should not be underestimated for all zumo XT3 or Tread 2 users is the ability to specify the vehicle profile to be used for the route directly within the TM.

I also don’t want to forget to mention the option to transfer routes in such a way that the navigation system always requires a recalculation, or that recalculation may not be necessary for routes from BaseCamp sources, or even that routes can be transferred directly in a single segment (like Track2Routes).

Another useful feature is the ability to transfer, besides the trips, also routes, tracks, and waypoints as GPX files (for import or as a backup) directly to the navigation device. There’s also an interesting feature here that allows you to create POIs directly from a GPX route.

Unfortunately, tracks and waypoints cannot be transferred directly, but require a manual import, to the zumo XT2, zumo XT3, or Tread 2. Partly because the data is stored in hidden directories, or the structures required to display them on the device (still) involve too many unknown characteristics.