I fully agree to the idea of @zaphod_42.
As far as I understand this concerns “Garmin ShapingPoint GPX” format - correct?
Just a hint: In former Kurviger export in “Garmin ShapingPoint GPX” format only start and destination were ViaPoints. If using further ViaPoints, according to manual at least on some devices the number of consecutive ShapingPoints is limited (e.g. BMW Navigator 5: 50, Navigator 6: 125). This might lead to conflicts when exporting long routes, especially on devices with a small number of allowed ShapingPoints in a row .
I do not know details about Zumo 590/595/3xxx or the newer Zumo XT.
On my BMW N5 sometimes route import failed due to too many ShapingPoints in a row, but it did not give clear feedback about the reason (or even no feedback about the reason) .
Now and then import with more than 50 ShapingPoints in a row is possible - I still do not fully understand that
I have to admit that I have no simple idea to solve that problem - a solution would be a setting “maximum number of ShapingPoints in a row” for Kurviger export, but this makes the user interface more complex and also will increase implementation effort
You are right - I just checked on Website, there are different ‘symbol’ tags (‘Flag, Blue’ / ‘Waypoint’ ) and different ‘type’ tags (‘via’, ‘shaping’ ) for via points and shaping points.
But as far as I know this will have no impact on import on Garmin devices, because they do not use those differences do distinguish between ViaPoints and ShapingPoints, they import all points as ViaPoints.
So the problem “max. number of consecutive ShapingPoints” will not occur.
Sorry - it’s me again …
Thanks for the solution regarding the additional waypoints while exporting a gpx file.
But: woundn’t it be great to have all generated waypoints while importing a gpx file set as shaping points either? None of these generated waypoints are set intentionally, therefore should be shaping points. You may take the example from start of this thread.
Thanks in advance, Robin.
My question is: Is that rule valid also outside GPX import? E.g. will adding/changing/removing a waypoint name switch ViaPoint / ShapingPoint automatically? (I would not like that, but I think during GPX import it is a good idea to use it for initial value).