jfheath wrote: ↑Wed Apr 24, 2024 3:11 pm
The mArrival bytes in the .trip file may be a red herring as far as this is concerned.
John, I may not have explained it quite correctly.
The mArrival field is stored for every Begin/Via/Shaping and End point. The sorting of the trips, routes, rowts or whatever you pronounce them, is done on the
mArrival field of the
Begin point. This point can be set from BC by setting the departure time of the Begin point. It is then copied to 'trp:DepartureTime' in the GPX.
The other points are not relevant for sorting.
Digging deeper, the field is the nbr of seconds since 1989/12/31 00:00:00 stored in presumably UTC/GMT.
I tested it with 6 routes in BC with a departure date starting from 1990/1/1 00:00:00 to 1990/1/1 02:00:00. I used those dates, so the values in the file would be near to zero. They showed up in the XT in that order.
Then I modified the last route and set the field to '00 00 00 10' (16 seconds after midnight 1989/12/31). After restarting the XT it was the first.
Edit: This would explain why trips that have no departure date set always appear on top. They have a value of '00 00 00 00' in mArrival, so that's the lowest value possible.
The field is stored like a Unix Epoch, except that it does not start from 1970/1/1 but from 1989/12/31.
https://www.epochconverter.com/
I agree that this info is not very useful.