Trip Window

Trip Window (Bottom Left)

Whenever you select a trip file, from the Device file list, or Windows file list, it is automatically loaded in the trip info.

The file name and trip name is shown in a Green bar if it was loaded from the device, in Aqua if loaded from Windows.

If you make modifications and press Save Trip File the trip file is saved from where it was loaded.

On the left you see a Tree view of all the data items in the trip.

Selecting a node filters the grid.

In the grid you can modify all basic data types. The button Save Trip File is only enabled when changes were made. If you click on it you will get a prompt ‘Saving the trip file will force recalculation. OK?’

Selecting a Node, or a line in the grid, will also update the Hexadecimal view and the Map view on the Bottom Right.

Items can be shown in a different color to mark turnarounds, or differences found by the compare. Use Alt+Down/Up to navigate to marked lines.

Right clicking on the grid will display a context menu.

Depending on the type of item shown in the grid a dropdown, or dropdown menu can be selected.

Buttons

Save trip File (From Values)	Save the modifications in the grid to the trip file.
Trip Editor	Opens the trip in the Trip Editor. See 12. Using Trip Editor
Explore info	Shows detailed info on items in Explore.db

The button Explore info is enabled for applicable models when the explore functions are enabled.

Context menu

DropDown menu's

Boolean type

Transportmode

Route point (Via, or Shape)

Route preference (for complete trip)

Route preference per segment (not for XT)

Some info on the items:

mImported

Set it to False to prevent RUT. This can also be done with the Trip function. (Top Left view)

mPreserveTrackToRoute

This is true for a trip created from a track.

mParentTripId/mParentTripname

All trips having the same values are shown grouped on the Trip planner. (Only for XT)

mRoutePreference

mTransportationMode: Corresponds with what you see on the device when you open a trip.

mLocations

Corresponds to Via and Shaping points used. The item mAttr defines Via or Shaping.

mAllRoutes:

Contains the result of the calculation. TripManager is not able to display all info, because not all data has been decoded. However all basic info, like road names and gps coordinates are shown. It can even create nodes that are accepted by the zūmo without recalculation, if the GPX is calculated by BaseCamp. If the GPX lacks this info it can create a dummy node. This first time a trip with a dummy node is opened on the zūmo the trip is recalculated. Note that this recalculation appears to be relatively fast.

Links to more detailed information:

Subclass field

Trip file (.trip)

Example of a turnaround

When the device filelist shows a turnaround symbol, you will find marked lines in mAllRoutes causing the turnaround.

This route point is placed on a parallel road, causing a turnaround. These turnarounds are mostly unintentional, and can cause routing errors, and are a known cause why starting routes with Closest Entry Point (CEP) fail.

(Use Alt+Down/Up to select the next/previous line.