DriveSmart 61 Saved Trips Sort Order

[Bernie_Kamerman]

I create trip files for each day there are about 100 days in a long trip. I import these but can not figure out a way to affect the order in which they are presented on the device.
I have tried the date is the rte line (<name>TR7-5</name>) but that have no effect.
I have tried incrementing the number in the ret line (<number>1</number>) also no effect.

The software in the device must use something to create the order does anyone which field effect effects the presentation order?
Thanks,
Bernie

 

[Nuvi-Nebie]

I would guess that each file created on the 61 is initially displayed in date order, are you copying files from the 61 to a computer renaming them and then copying them back to the 61?

 

[Bernie_Kamerman]

I create them on my computer and copy them to them drivesmart 61.

 

[Nuvi-Nebie]

Are you creating Routes or Tracks on your computer?, either way the files may be being sorted by the date the file was generated, rather than reading a field in the file or using the file name

 

[Bernie_Kamerman]

Route File <rte> and <rtept> types.
Not the Date generated because when I change a file, delete the one from the device and upload the new version it does not sort either first or last.
I'd love to be able to see the code, it should not be too difficult the figure out if the order is determine on the display or the insertion and how they decide the order.

 

[Nuvi-Nebie]

OK so you are creating Routes on a computer and copying them to the 61, which computer program are you using to generate the Routes?, I am familiar with creating Routes using Garmin Basecamp but I am guessing you are not using that, what file type is the Route (or Routes) contained in?, e.g. gpx, rte etc

There are some file structures detsiled here that might help :-
https://www.topografix.com/GPX/1/1/#SchemaProperties

 

[Bernie_Kamerman]

I've written my own code. I create my routes in Streets and Trips and Export the GPX file and import it into excel and do some manipulation with excel then from and an excel VB procedure create the GPX files for the Drive Smart 61. This has worked great for me. Last year we had 96 driving days on the trip so 96 files. It is a pain it the neck going through the non-order list to find a file. Gets easier toward the end of the trip.
I'm trying every optional GPX format field to see if I can figure out what the Garmin uses to establish the order, No lick so far.

 

[Nuvi-Nebie]

I created 3 Routes using Garmin Basecamp e.g.:-

file 1111.gpx containing route Name AAAA
file 2222.gpx containing route Name BBBB
file 3333.gpx containing route Name CCCC

I sent these 3 Routes to Nuvi56 in the order 1111.gpx, then 3333.gpx and then 2222.gpx and the 3 Routes were displayed in AAAA then BBBB then CCCC order, using :- Main Menu >> Apps >> Trip Planner, so my Nuvi56 is displaying Routes in alphabetical Route Name order, the 1111.gpx file has Route Name AAAA recorded like this :-

 <rte>
    <name>AAAA</name>
    <extensions>

Here is an edited 1111.gpx file :-

<?xml version="1.0" encoding="utf-8"?><gpx creator="Garmin Desktop App" version="1.1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/WaypointExtension/v1 http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www8.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/ActivityExtension/v1 http://www8.garmin.com/xmlschemas/ActivityExtensionv1.xsd http://www.garmin.com/xmlschemas/AdventuresExtensions/v1 http://www8.garmin.com/xmlschemas/AdventuresExtensionv1.xsd http://www.garmin.com/xmlschemas/PressureExtension/v1 http://www.garmin.com/xmlschemas/PressureExtensionv1.xsd http://www.garmin.com/xmlschemas/TripExtensions/v1 http://www.garmin.com/xmlschemas/TripExtensionsv1.xsd http://www.garmin.com/xmlschemas/TripMetaDataExtensions/v1 http://www.garmin.com/xmlschemas/TripMetaDataExtensionsv1.xsd http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensions/v1 http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensionsv1.xsd http://www.garmin.com/xmlschemas/CreationTimeExtension/v1 http://www.garmin.com/xmlschemas/CreationTimeExtensionsv1.xsd http://www.garmin.com/xmlschemas/AccelerationExtension/v1 http://www.garmin.com/xmlschemas/AccelerationExtensionv1.xsd http://www.garmin.com/xmlschemas/PowerExtension/v1 http://www.garmin.com/xmlschemas/PowerExtensionv1.xsd http://www.garmin.com/xmlschemas/VideoExtension/v1 http://www.garmin.com/xmlschemas/VideoExtensionv1.xsd" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wptx1="http://www.garmin.com/xmlschemas/WaypointExtension/v1" xmlns:gpxtrx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3" xmlns:trp="http://www.garmin.com/xmlschemas/TripExtensions/v1" xmlns:adv="http://www.garmin.com/xmlschemas/AdventuresExtensions/v1" xmlns:prs="http://www.garmin.com/xmlschemas/PressureExtension/v1" xmlns:tmd="http://www.garmin.com/xmlschemas/TripMetaDataExtensions/v1" xmlns:vptm="http://www.garmin.com/xmlschemas/ViaPointTransportationModeExtensions/v1" xmlns:ctx="http://www.garmin.com/xmlschemas/CreationTimeExtension/v1" xmlns:gpxacc="http://www.garmin.com/xmlschemas/AccelerationExtension/v1" xmlns:gpxpx="http://www.garmin.com/xmlschemas/PowerExtension/v1" xmlns:vidx1="http://www.garmin.com/xmlschemas/VideoExtension/v1">

  <metadata>
    <link href="http://www.garmin.com">
      <text>Garmin International</text>
    </link>
    <time>2021-03-02T16:40:56Z</time>
    <bounds maxlat="51.577355861663818" maxlon="0.070102214813232" minlat="51.54510498046875" minlon="-0.102267265319824" />
  </metadata>

  <rte>
    <name>AAAA</name>
    <extensions>
      <gpxx:RouteExtension>
        <gpxx:IsAutoNamed>false</gpxx:IsAutoNamed>
        <gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
      </gpxx:RouteExtension>
      <trp:Trip>
        <trp:TransportationMode>Automotive</trp:TransportationMode>
      </trp:Trip>
    </extensions>
    <rtept lat="51.54611349105835" lon="-0.102267265319824">
      <time>2021-03-02T16:19:32Z</time>
      <name>Highbury Corner and St Paul's Road</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>
        <gpxx:RoutePointExtension>
          <gpxx:Subclass>00009A9AAA01522063060F24FF00AFA762ED</gpxx:Subclass>
          <gpxx:rpt lat="51.54611349105835" lon="-0.102267265319824">
            <gpxx:Subclass>03009A9AAA01B22D0E002116000000000000</gpxx:Subclass>
          </gpxx:rpt>
          <gpxx:rpt lat="51.54611349105835" lon="-0.102267265319824" />
          <gpxx:rpt lat="51.54611349105835" lon="-0.102267265319824" />
          <gpxx:rpt lat="51.54611349105835" lon="-0.102267265319824" />
          <gpxx:rpt lat="51.54611349105835" lon="-0.102267265319824">
            <gpxx:Subclass>03009A9AAA013D2B0E001F0058001B2E7000</gpxx:Subclass>
          </gpxx:rpt>

******

[NOTE :- Further gpxx:rpt lines have been omitted because the file was too big to post]

******

          <gpxx:rpt lat="51.556863784790039" lon="0.068321228027344" />
          <gpxx:rpt lat="51.556863784790039" lon="0.068321228027344" />
          <gpxx:rpt lat="51.556863784790039" lon="0.068321228027344" />
          <gpxx:rpt lat="51.55657066963613" lon="0.067873802036047">
            <gpxx:Subclass>0600B79AAA0166AB08002117000021001300</gpxx:Subclass>
          </gpxx:rpt>
        </gpxx:RoutePointExtension>
      </extensions>
    </rtept>
    <rtept lat="51.556519959121943" lon="0.06795996800065">
      <time>2021-03-02T16:19:34Z</time>
      <name>Ilford</name>
      <sym>Waypoint</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>
        <gpxx:RoutePointExtension>
          <gpxx:Subclass>000000000000FFFFFFFFFFFFFFFFFFFFFFFF</gpxx:Subclass>
        </gpxx:RoutePointExtension>
      </extensions>
    </rtept>
  </rte>

</gpx>

I suggest you experiment with Garmin Basecamp (free to download), so you can see how it constructs an Route

Here is a full downloadable 1111.gpx zip file :-

 

[Bernie_Kamerman]

Thank You,
This is very revealing.
I copied your gpx code and made made 1111-5555 with name AAAAA-EEEE and mine are displayed CCCC, BBBB, AAAA,EEEE, and dddd (I made dddd lowercase).
So it is apparently something about my DriveSmart 61.
My software Version: 6.30
GPS Firmware: 9.00.00
FMI: 3.6

 

[Nuvi-Nebie]

Take a look at this thread :-
http://forums.gpsreview.net/discussion/31307/sorting-imported-trips-on-a-drivesmart-51
It's probably worth reading all the posts but the last two refers to sorting by "trip departure time in Basecamp"

I set the Route departure time to 12:34:56 in Basecamp

  <trp:ViaPoint>
          <trp:DepartureTime>2021-03-03T12:34:56Z</trp:DepartureTime>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>

Full GPX below :-

 

[Bernie_Kamerman]

I put 4 routes in the same gpx file alphabetically in order so that they would have to stored in order and they still display out of order. So I suspect it is a display side problem in the Drive Smart 61/51 devices.
Definitely not a show stopped but I am curios about it.

 

[Nuvi-Nebie]

Did you see my post #10?, I think the problem has been identified

 

[Bernie_Kamerman]

Yes I put in <trip:departuretimes> and I still see the files in the incorrect order. I made the departure dates and times both ascending. That is why I suspect display side.
Also, incidentally, i testing with the same five fields with various combination of options those always display in the same incorrect order. Even when I put five <rte> structures in a single gpx file.

 

[Motorcoach Driver Steve]

EUREKA, Nuvi-Nebie, YOU DA MAN!

I am a tour bus driver who has used BaseCamp and my Zumo 550 (also motorcycled) for 13 years to create and navigate trip routes for tours of a day to 3 weeks, from two to 70 routes per trip. Both BaseCamp and the Zumo displayed routes sorted alpha-numerically, so by naming them in the format “MMDD Seq# Desc”, like “1106 1 B from A”, “1106 2 C from B’, etc., all routes were sorted in the sequence I will do them in BaseCamp and in the Zumo after being sent from BaseCamp. Perfect.

The Zumo is starting to go, so I recently bought a DriveSmart 66 (I no longer motorcycle). When I tested sending routes from BaseCamp, all was great except in the Route Planner App they are sorted in some seemingly random undecipherable way! What a PAIN when out there trying to find and select one of 75 routes from a randomly ordered list!

I called Garmin, no help, they weren’t able to tell me the sorting logic, only that it was no longer alpha-numeric and it had been that way for a while, perhaps for all Drive and DriveSmart devices, and it wasn’t likely to change, but of course I was free to submit a request.

Before doing that I searched and found nothing until I hit on this forum. I had never had to set a firm departure date/time (never used Trip Planner), so my saved routes until now all defaulted to the same date/time I suppose, or maybe blank. After seeing this thread, I tested it, and sure enough, if you select the first departure waypoint and set a firm departure date/time on it, and do similar to the other routes, using your trip itinerary as a rough guide, BINGO, they are now sorted in perfect execution order after sending to the 66 and bringing them up in the Route Planner! Problem solved! It is an extra step, but not a big one (as long as I remember this extra step) and I can certainly live with it, as it’s unlikely I could convince Garmin to change it. (BTW, any routes without firm departure times set are shown first in that undecipherable order, then the ones with firm departures in the order of departure. So if there are any I forgot to set, they’ll be at the top of the list and I can easily correct them and re-send.)

THANK YOU!!!

 

[Motorcoach Driver Steve]

As a small addition to the above, if when you are on a trip using imported routes, you have a need to add a side trip and want to plan a route, without access to BaseCamp, these new devices are quite good at allowing you to create and save a route, including adding shaping points to customize the routes, in fact it works quite like BaseCamp. When you save one or more such device-created routes, in Route Planner there will now be two sections, one called "Saved Routes" and one "Imported Routes". Since when you create a route on the device, there is not an opportunity to set a departure date/time, that "Saved Routes" list IS sorted alphanumerically, so you can still use a smart naming scheme to display them in your desired order within that list.

I'm not certain what all devices these observations apply to, but I'm guessing most devices available in the last couple of years may be the same.

 

[Bernie_Kamerman]

Steve, what is the syntax to the Way Port departure date/time.
I used:
<wpt> lat="38.556835" lon="-109.541101"><name>TR7-20</name><time>2022-07-20T07:20:06.015Z</time></wpt>
Then made the date/time higher for each wpt, however they still display randomly in Trip Planner imported trips.

 

[Motorcoach Driver Steve]

Bernie -- I have never edited GPX files directly, so I'm no expert at that. I do all my route planning in BaseCamp, and there it is trivially easy to set a departure date/time for the first via point in any route by double clicking on that point, checking the "Departure Time" box, then selecting the date from a calendar and filling in the time.

However, having done that for a short trip with two routes in BaseCamp, I exported that list to a GPX file and this is what I see for the first route, where I set the departure time to 1/21/2022, 2 pm CST:

<rte>
    <name>0121 1 CR Bowling Ctr from East HS</name>
    <extensions>
      <gpxx:RouteExtension>
        <gpxx:IsAutoNamed>false</gpxx:IsAutoNamed>
        <gpxx:DisplayColor>Magenta</gpxx:DisplayColor>
      </gpxx:RouteExtension>
      <trp:Trip>
        <trp:TransportationMode>Automotive</trp:TransportationMode>
      </trp:Trip>
    </extensions>
    <rtept lat="42.502037705853581" lon="-92.327814102172852">
      <time>2010-06-11T16:14:07Z</time>
      <name>Wloo East HS Ath Pickup</name>
      <cmt>354 Barclay St</cmt>
      <desc>354 Barclay St</desc>
      <sym>School</sym>
      <extensions>
        <trp:ViaPoint>
          <trp:DepartureTime>2022-01-21T20:00:00Z</trp:DepartureTime>
          <trp:CalculationMode>FasterTime</trp:CalculationMode>
          <trp:ElevationMode>Standard</trp:ElevationMode>
        </trp:ViaPoint>

So it seems it's the "DepartureTime" variable that the sorting pays attention to. This only needs to be set for the first point in the route. I believe the "Time" variable on a waypoint has to do with the date it was created, so has no effect on the sorting of routes.

Hope this helps.

 

[Motorcoach Driver Steve]

...The capital "D"s in what I pasted seem converted to green smiley faces, not sure what that's about. I tried to edit it but it wouldn't accept my changes.

 

[Motorcoach Driver Steve]

I see what I pasted lost the indents as well, so I'll just upload the GPX.

 

[Nuvi-Nebie]

...The capital "D"s in what I pasted seem converted to green smiley faces, not sure what that's about. I tried to edit it but it wouldn't accept my changes.

I fixed the 'green smiley faces' and the indents by putting the text inside a CODE box in your post #17

With this :-

You get this :-

:D

Without CODE . . . /CODE you get :-