TripManager support GPX Files from Tyre2Navigate also

[proofresistant]

It looks like routes and GPX files from Tyre2Navigate can also be transferred with TripManager

At least in principle; I have currently tested it with my Tread 2 device.

But i noticed that only the option with recalculation actually makes sense.
The other options also work, but the ghost points are lost and are therefore meaningless and require recalculation as well.
In my opinion, it probably also makes sense to have routes from other sources recalculated in the device

Here is an example of what a GPX file looks like when saved from Tyre2Navigate.

tMo1(actDef) WK 3B TYRosm Shp 4tMo1 4Trd2.gpx

(6.7 KiB) Downloaded 38 times

[FrankB]

My first impression:

The GPX has subclasses, but what is normal for BC created GPX files is this sequence:

rtept 1
2116 Leave route point
1fxx Intermediate
...
1fxx
2117 Approach route point
rtept 2

etc.

The GPX from tyre only has 2116 = Leave route point. So you're correct the trip can be created by TM, but will be recalculated by the unit.
Note that in TM you see 'BaseCamp calculated GPX only' in the trip options! The same for MyRouteAPP, Kurviger etc.

Question: Can Tyre create a track? If yes, you could use the compare function of TM after recalculation by the unit.

added spaces for readability

Code: Select all

<gpxx:RoutePointExtension>                                                                                                    
  <gpxx:Subclass>0600D88F0C0249D70B00211600001F001F00</gpxx:Subclass>                                                         
  <gpxx:rpt lat="51.15663" lon="7.22413"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.15320" lon="7.22728"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.15040" lon="7.23121"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.14892" lon="7.23409"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.14841" lon="7.23849"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.14788" lon="7.24196"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.14708" lon="7.23805"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     
  <gpxx:rpt lat="51.14438" lon="7.23556"><gpxx:Subclass>0600D88F0C0249D70B00 2116 00001F001F00</gpxx:Subclass></gpxx:rpt>     

[proofresistant]

Of course, Tyre2Navigate can also create tracks for the routes.
You can set whether or not the track should be saved for each route.

It's good that you found the cause of the missing ghost points.
However, I wouldn't recommend a solution here, as there are countless other planning tools with different features each.

TM has a note that for the “without calculation” options, only (BaseCamp calculated GPX only) should be used, which should be sufficient

PS
By the way, one of the biggest advantages for me is that TripManager makes it super easy to compare routes calculated by the device with the tracks.
The visual comparison with the map alone is worth its weight in gold for me.

[FrankB]

Of course, Tyre2Navigate can also create tracks for the routes.
You can set whether or not the track should be saved for each route.

Additionally. The Trk2RT (from @smfollen) that is integrated in TM V1.7 will allow you to create a route from a track.

It's good that you found the cause of the missing ghost points.
However, I wouldn't recommend a solution here, as there are countless other planning tools with different features each.

What I found to be a pleasant surprise is that they DO have a subclass with a MapSegment and RoadId. I dont know if they are correct.