Rider 550 re routeing

[motorick]

I use myroutapp to plan routes which i then send to MyDrive as gpx files in track format to ensure the route stays as planned. But in the field if I have a road closure the unit will not re calculate around. This has given me grief several times. Anyone have a fix?

 

[Willy875]

If it is a GPX, it is not possible to ignore it
if it is a route created on Mydrive
To cancel the point that has not been seen.

Click on the … then delete the next waypoint and it recalculates the route for the next point very quickly.

 

[raesewell]

If you use GPX track files it cannot deviate from the route, to cope with road closures you need to use a Tomtom Route itn. file which calculates a route from point to point dependant on your settings.

 

[motorick]

If you use GPX track files it cannot deviate from the route, to cope with road closures you need to use a Tomtom Route itn. file which calculates a route from point to point dependant on your settings.

Thanks, will give the itn file a go. Tried gpx route files but Mydrive converts to straight lines between waypoints

 

[canderson]

I use myroutapp to plan routes which i then send to MyDrive as gpx files in track format to ensure the route stays as planned. But in the field if I have a road closure the unit will not re calculate around. This has given me grief several times. Anyone have a fix?

And there's my complaint with software that uses the *.gpx <trkpt> method for putting together an itinerary. It's a brain-dead approach that allows for no real intelligence to be applied to a route.

There are THREE different styles of *.gpx. One is <trkpt> (track point), and all it is is series of breadcrumbs that have been taken/created at a regular interval of distance or time. As a result, the files can also be HUGE. While some prefer it for group rides, the fact that with this style *.gpx, the TomTom forces the route down specific roads can be a real issue, as you have discovered. It is my least favorite *.gpx format. It does not allow the routing engine of the TomTom to operate at all, and so makes no provisions whatsoever for traffic, blocked roads, whatever.

A more sensible style of *.gpx for many users would be the <rtept> (route point) style. This provides a series of points that are to be achieved in sequence. The routing engine is left to figure out how to achieve each of those points based upon current conditions. This is similar to the old TomTom *.itn file in practice/function.

The third style of *.gpx is the <wpt> (waypoint) style files. This is very similar to the TomTom custom POI *.ov2 file in use. It is just a list of potential points to visit with no particular order implied. One makes their own routing to achieve whichever of the points in whatever order is preferred for a given run.