Scenic GPX Export to Garmin Basecamp Import
Quote from Rbmjr on 22.10.2024, 10:56I was planning a route with a friend over lunch and later wanted to export the route from Scenic 4.x so I could import the route into Basecamp. I tried multiple exports and imports, exporting to iCloud, attaching the route to an email, etc. and every time I receive the same error. Any ideas as to what I am doing wrong?
[caption id="attachment_8331" align="alignnone" width="800"]
Error importing GPX file exported from Scenic 4.x[/caption]
I was planning a route with a friend over lunch and later wanted to export the route from Scenic 4.x so I could import the route into Basecamp. I tried multiple exports and imports, exporting to iCloud, attaching the route to an email, etc. and every time I receive the same error. Any ideas as to what I am doing wrong?
[caption id="attachment_8331" align="alignnone" width="800"]
Error importing GPX file exported from Scenic 4.x[/caption]
Quote from Guido on 22.10.2024, 11:11Basecamp doesn't support CDATA in a GPX file.Scenic 4 uses the CDATA tag to save the route mode in the GPX. CDATA is an official way to store text in XML files (GPX is an XML file).So, this is a Basecamp bug, but I don't expect Garmin to fix this. You can try to send an email to them, but a google search indicates that this problem has existed since 2012. Here for example: https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows/59049/waypoints-description-problemI plan to expand GPX export in the future, allowing you to choose the elements you include in the export. As soon as I start working on it, I will also take this into account (so that you can optionally choose to include the routing mode in the GPX). In Basecamp it is not used anyway.Until then, unfortunately, there is no other choice but to open the GPX in a text file and then delete the selected text between and including the <cmt> tags (see attached photo)

Quote from open1mind on 24.01.2025, 16:35So, what are you using to open the gpx file to make that edit? I have tried it, and it wants to open with basecamp which gets me nowhere.... This is all really unfortunate because before the update my quick workflow was---- just moving the Google Maps into Scenic and then emailing it to myself, followed by a download onto my computer, and then dragging it over into my Basecamp before sending to Zumo.
Now I need to try to edit the GPX file - cant say that I have ever tried that before and I am not sure what tool to do that with????
thanks
So, what are you using to open the gpx file to make that edit? I have tried it, and it wants to open with basecamp which gets me nowhere.... This is all really unfortunate because before the update my quick workflow was---- just moving the Google Maps into Scenic and then emailing it to myself, followed by a download onto my computer, and then dragging it over into my Basecamp before sending to Zumo.
Now I need to try to edit the GPX file - cant say that I have ever tried that before and I am not sure what tool to do that with????
thanks
Quote from Guido on 25.01.2025, 00:11A simple plain text editor is sufficient. If you have a Mac there comes one pre-installed called "TextEdit"
If you have windows it's called Notepad if I remember correctly.Do you have to go through Basecamp to get the route in your Zumo? The newer Zumo models (at least the XT2) also work with the Garmin Threads app that can import the new Scenic GPX files. Here's a forum topic on that: https://scenic.app/forum/topic/export-gps-files-from-scenic-4-wireless-and-with-sd-to-garmin-xt2/
A simple plain text editor is sufficient. If you have a Mac there comes one pre-installed called "TextEdit"
If you have windows it's called Notepad if I remember correctly.
Do you have to go through Basecamp to get the route in your Zumo? The newer Zumo models (at least the XT2) also work with the Garmin Threads app that can import the new Scenic GPX files. Here's a forum topic on that: https://scenic.app/forum/topic/export-gps-files-from-scenic-4-wireless-and-with-sd-to-garmin-xt2/
Quote from open1mind on 28.01.2025, 14:08Thanks... TextEdit partially worked as you describe.
I did succeed in moving a few into base camp as mentioin. In other cases, the text did not include the specific language that showed in your post.
I have a Zumo 1, and I dont know of any way to use Garmin Threads to get it there. Unfortunate that my long standing workflow (Google - Scenic- Basecamp- Zumo) got more complicated.
Thanks... TextEdit partially worked as you describe.
I did succeed in moving a few into base camp as mentioin. In other cases, the text did not include the specific language that showed in your post.
I have a Zumo 1, and I dont know of any way to use Garmin Threads to get it there. Unfortunate that my long standing workflow (Google - Scenic- Basecamp- Zumo) got more complicated.
Quote from svoscom on 06.04.2025, 04:36Quote from Guido on 22.10.2024, 11:11Basecamp doesn't support CDATA in a GPX file.Scenic 4 uses the CDATA tag to save the route mode in the GPX. CDATA is an official way to store text in XML files (GPX is an XML file).So, this is a Basecamp bug, but I don't expect Garmin to fix this. You can try to send an email to them, but a google search indicates that this problem has existed since 2012. Here for example: https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows/59049/waypoints-description-problemI plan to expand GPX export in the future, allowing you to choose the elements you include in the export. As soon as I start working on it, I will also take this into account (so that you can optionally choose to include the routing mode in the GPX). In Basecamp it is not used anyway.Until then, unfortunately, there is no other choice but to open the GPX in a text file and then delete the selected text between and including the <cmt> tags (see attached photo)Hello Guido,
The current version of the Scenic app no longer includes the link <cmt> to </cmt>. That's okay. This saves me the trouble of editing the GPX file. Thanks. But Relive no longer accepts the scenic.gpx file. Any ideas?
Best regards,
Sven
Quote from Guido on 22.10.2024, 11:11Basecamp doesn't support CDATA in a GPX file.Scenic 4 uses the CDATA tag to save the route mode in the GPX. CDATA is an official way to store text in XML files (GPX is an XML file).So, this is a Basecamp bug, but I don't expect Garmin to fix this. You can try to send an email to them, but a google search indicates that this problem has existed since 2012. Here for example: https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows/59049/waypoints-description-problemI plan to expand GPX export in the future, allowing you to choose the elements you include in the export. As soon as I start working on it, I will also take this into account (so that you can optionally choose to include the routing mode in the GPX). In Basecamp it is not used anyway.Until then, unfortunately, there is no other choice but to open the GPX in a text file and then delete the selected text between and including the <cmt> tags (see attached photo)
Hello Guido,
The current version of the Scenic app no longer includes the link <cmt> to </cmt>. That's okay. This saves me the trouble of editing the GPX file. Thanks. But Relive no longer accepts the scenic.gpx file. Any ideas?
Best regards,
Sven
Quote from Guido on 06.04.2025, 06:41I did not remove the <cmt> tag. It will still be in the GPX if you export a route. (If you export a recorded ride it will not be there). I did not change anything else compared to GPX export in Scenic 3.
I know that Relive used to accept Recorded Ride GPX exports from Scenic. I’m not sure about route exports though.
I did not remove the <cmt> tag. It will still be in the GPX if you export a route. (If you export a recorded ride it will not be there). I did not change anything else compared to GPX export in Scenic 3.
I know that Relive used to accept Recorded Ride GPX exports from Scenic. I’m not sure about route exports though.
Quote from pe112 on 23.04.2025, 06:06Quote from Guido on 22.10.2024, 11:11Basecamp doesn't support CDATA in a GPX file.Scenic 4 uses the CDATA tag to save the route mode in the GPX. CDATA is an official way to store text in XML files (GPX is an XML file).So, this is a Basecamp bug, but I don't expect Garmin to fix this. You can try to send an email to them, but a google search indicates that this problem has existed since 2012. Here for example: https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows/59049/waypoints-description-problemI plan to expand GPX export in the future, allowing you to choose the elements you include in the export. As soon as I start working on it, I will also take this into account (so that you can optionally choose to include the routing mode in the GPX). In Basecamp it is not used anyway.Until then, unfortunately, there is no other choice but to open the GPX in a text file and then delete the selected text between and including the <cmt> tags (see attached photo)Hi Guido,
I found that the cause of the import problem into Basecamp is a different one.
It is the order of the <desc> and the <cmt> element within the <rte>.
According to the XSD it must be
- <name>
- <cmt>
- <desc>
If I swap the <desc> and <cmt> elements in a route generate by Scenic then Basecamp reads it without any complaint. (Even with CDATA in the <cmt>.)
Hope this helps.
Best, Martin
Quote from Guido on 22.10.2024, 11:11Basecamp doesn't support CDATA in a GPX file.Scenic 4 uses the CDATA tag to save the route mode in the GPX. CDATA is an official way to store text in XML files (GPX is an XML file).So, this is a Basecamp bug, but I don't expect Garmin to fix this. You can try to send an email to them, but a google search indicates that this problem has existed since 2012. Here for example: https://forums.garmin.com/apps-software/mac-windows-software/f/basecamp-windows/59049/waypoints-description-problemI plan to expand GPX export in the future, allowing you to choose the elements you include in the export. As soon as I start working on it, I will also take this into account (so that you can optionally choose to include the routing mode in the GPX). In Basecamp it is not used anyway.Until then, unfortunately, there is no other choice but to open the GPX in a text file and then delete the selected text between and including the <cmt> tags (see attached photo)
Hi Guido,
I found that the cause of the import problem into Basecamp is a different one.
It is the order of the <desc> and the <cmt> element within the <rte>.
According to the XSD it must be
- <name>
- <cmt>
- <desc>
If I swap the <desc> and <cmt> elements in a route generate by Scenic then Basecamp reads it without any complaint. (Even with CDATA in the <cmt>.)
Hope this helps.
Best, Martin
Quote from Guido on 23.04.2025, 06:49This definitely helps Martin. THANK YOU! I wasn’t aware that the order mattered. This should make this a lot easier to fix.
This definitely helps Martin. THANK YOU! I wasn’t aware that the order mattered. This should make this a lot easier to fix.
Quote from pe112 on 23.04.2025, 07:43You are welcome.
Basecamp is the only GPS tool I know about that correctly validates GPX files against the XSD when reading them. Other tools may be using other parsers and be more forgiving for that reason. This may make Basecamp look stubborn, but in the end it is the correct way to work with XML.
You are welcome.
Basecamp is the only GPS tool I know about that correctly validates GPX files against the XSD when reading them. Other tools may be using other parsers and be more forgiving for that reason. This may make Basecamp look stubborn, but in the end it is the correct way to work with XML.
Quote from ogroggo on 03.05.2025, 05:09Quote from open1mind on 24.01.2025, 16:35So, what are you using to open the gpx file to make that edit? I have tried it, and it wants to open with basecamp which gets me nowhere.... This is all really unfortunate because before the update my quick workflow was---- just moving the Google Maps into Scenic and then emailing it to myself, followed by a download onto my computer, and then dragging it over into my Basecamp before sending to Zumo.
Now I need to try to edit the GPX file - cant say that I have ever tried that before and I am not sure what tool to do that with????
thanks
If you need to make the edit on the iPhone, for that I use the GPX viewer 2 app.
This is a small edit, close to the top of the gpx file, relaively easy in GPX viewer 2.
Other edits - like removing gpx points at end of longer files - are more tedious.
But I like the app for changing stuff when I am on-route with only the phone available.
Quote from open1mind on 24.01.2025, 16:35So, what are you using to open the gpx file to make that edit? I have tried it, and it wants to open with basecamp which gets me nowhere.... This is all really unfortunate because before the update my quick workflow was---- just moving the Google Maps into Scenic and then emailing it to myself, followed by a download onto my computer, and then dragging it over into my Basecamp before sending to Zumo.
Now I need to try to edit the GPX file - cant say that I have ever tried that before and I am not sure what tool to do that with????
thanks
If you need to make the edit on the iPhone, for that I use the GPX viewer 2 app.
This is a small edit, close to the top of the gpx file, relaively easy in GPX viewer 2.
Other edits - like removing gpx points at end of longer files - are more tedious.
But I like the app for changing stuff when I am on-route with only the phone available.
Quote from pe112 on 03.05.2025, 07:05Guido has fixed the issue with the latest Scenic version (4.18).
So there is no need to edit GPX files anymore 🙂
Best, Martin
Guido has fixed the issue with the latest Scenic version (4.18).
So there is no need to edit GPX files anymore 🙂
Best, Martin
Quote from Guido on 03.05.2025, 07:06Martin’s genius remark above has been implemented in Scenic v4.18 (released yesterday). No need to edit the exported GPX (or at least not for this reason) anymore.
Martin’s genius remark above has been implemented in Scenic v4.18 (released yesterday). No need to edit the exported GPX (or at least not for this reason) anymore.



