Yes, that was exactly my idea. I use MS Visual Studio Code, which has a good compare feature.
There are a few differences between the MRA and the BC version and I'm trying to figure out which one is crucial. Unfortunately, the gpxx extensions are probably responsible for that, but they are a proprietary Garmin development and not publicly known. Most of the time you can only get to the bottom of these effects by trial and error...
@Hans-van-de-Ven-MR-MRA said in Add option for stripping shaping points in gpx export:
The developers should dive into that as soon as they have time
Of course! But perhaps we can try out a few things in advance to make it easier for the developer to analyse the problem.
This topic is a broad field and you can invest quite a lot of time in it.
@Martin-Wilcke Thank you for your help. I am interested in further testing 
Your number 3 test works, that all VIA points are now being shown. But the whole route is gone. The route is now point to point shown.
Unfortunately, the Montana route planer does not show the VIA points in a list as your Zumo does. This is a sutpid Garmin software decision, as the GPSMap 276Cx could do this and was based on Montana software.. the only option, where is does show VIA points like Zumo in a list, if I do transfer a route from Basecamp with "Direct Navigation". Thats the only case, where this works. You can find such example route here: clickme (This means only straight lines, no routing)
This is can example, what I mean. It only works with my uploaded direct Route from Basecamp. Your "MRA Route Version 3", despide being direct, does not show its points, so it's apprently not detected as direct route?
@Hans-van-de-Ven-MR-MRA Great, many thanks. Do you want to open for that a support ticket?
Thanks for the link, I‘ll check it out!
OK - here comes the next and hopefully final attempt (Version 4):
https://hidrive.ionos.com/share/pquvtok.yw
This version contains all the additional information from the BC file, which either has static values or can be derived relatively easily.
I'm curious to see if it works!
ooops, little bug in version 4, please use version 5.
@Peter-Schiefer Thanks, I will have a look.
@Martin-Wilcke Thank you. I tried V5 and Unfortunately no change. Still missing VIA points.
Shiny!
@ConiKost
Too bad. Then the gpxx:subclasses must probably also be included, but I have no idea how the content can be determined or derived. Maybe someone else has an idea...
@ConiKost
I use outdoor Garmins since decades for my Moto bike Tours. Having ViaPoints part of the route is one of the most important things for my routing. With export/import of the GPX 1.2 files and recalculation set to off in the Montana 700i, the Routing works fine but the ViaPoints are missing.
It surely seems to have something to do with the GPXX : Subclass Tags. It would be great, if ViaPoint support for Garmin Outdoor Devices could be implemented in MRA. Until then, I will stick with Basecamp, possibly running on a virtual machine with Windows 10 or 11 in the future.
@Canario said in Add option for stripping shaping points in gpx export:
@ConiKost
I use outdoor Garmins since decades for my Moto bike Tours. Having ViaPoints part of the route is one of the most important things for my routing. With export/import of the GPX 1.2 files and recalculation set to off in the Montana 700i, the Routing works fine but the ViaPoints are missing.
It surely seems to have something to do with the GPXX : Subclass Tags. It would be great, if ViaPoint support for Garmin Outdoor Devices could be implemented in MRA. Until then, I will stick with Basecamp, possibly running on a virtual machine with Windows 10 or 11 in the future.
To be honest, I don't have high hopes, that this will be proper supported in future, as most of the users here uses automotive devices like Zumo/Tread. And the roadmap seems to have more important features on it's list (which I can even understand..)
Yes, that was exactly my idea. I use MS Visual Studio Code, which has a good compare feature.
There are a few differences between the MRA and the BC version and I'm trying to figure out which one is crucial. Unfortunately, the gpxx extensions are probably responsible for that, but they are a proprietary Garmin development and not publicly known. Most of the time you can only get to the bottom of these effects by trial and error...
