Maps app: route exported as GPX does not open correctly with Garmin Connect

Hi,
The routes that I save from the Maps app as GPX fail to open correctly with the Garmin Connect app. This app is needed to load the route on a Garmin navigator device.
When I upload the same file to the online BRouter tool, that does work. So, I have a workaround because I can export the route from BRouter and transfer that file to the phone, it opens fine with Garmin Connect - but that is quite a detour.

/e/OS version v3.5

Maps version 7.1.24.44.112F2A33.FF608AF0 com.generalmagic.magicearth
Garmin Connect version 5.22.1

In case someone wants to investigate it:

Here is an example route exported from Maps.
Here is the route after import/export with BRouter.

I was using OSMAnd+ before on Google Android, but because of problems with the app on /e/os I tried the Maps app and liked it. It also supports dowloading maps; I still should try offline navigation.

I have experienced GPX compatibility issues, but have not used Garmin. I understand that Garmin use (their own, idk) ExpertGPS. This link https://www.topografix.com contains more links than anyone could want, the top right menu may be the place to start, perhaps
GPX: the GPS Exchange Format for a less proprietary angle.

(Legacy /e/) Maps (general magic) is likely to soon be replaced by Cardinal, a link to test version is found on the forum for instance Cardinal / Maps apk links broken since renaming.

1 Like

Garmin Connect will take the Magic Earth gpx export if it has a xml namespace, replace (add xmlns=..) in the gpx node in the the second line after the <xml> root

- <gpx version="1.1">
+ <gpx xmlns="http://www.topografix.com/GPX/1/1" version="1.1" >

maybe worth a bugreport to magicearth

An on-device fix can be: open the magicearth gpx with CoMaps/Organicmaps and export again, this would add any namespaces and allow it to be opened by Garmin Connect.

(mostly unrelated, advertisement: I wrote a small export script for Magic Earth favourites to other formats)

2 Likes

@tcecyk Cool, that works. It never occurred to me to open the files with a text editor. They’re almost readable. This feels better as a workaround than import/export with BRouter-web, because that changes more than just the namespace. I will figure out how to file a bug for MagicEarth anyway, because this workaround will not do while I am on the road.
Thank you!

I filed a bug with Magic Earth and received a quick response. In short: the version of Magic Earth in /e/os is too old, this problem is likely fixed in a new version. Please upgrade.

```
Hi Tony,

Thank you for your message and for the detailed explanation.

It appears that you are using a very old version of the Magic Earth app (version 7.1.24). Since that release, we have introduced many updates and improvements to the application, including a complete redesign of the app in December 2025. The latest update was released in February 2026.

In the newer versions of Magic Earth, GPX export has been improved and the exported GPX files are compatible with Garmin Connect without requiring manual modifications such as adding the GPX namespace.

Also, please note that you are using /e/OS. While Magic Earth may run on alternative Android-based operating systems, we cannot fully guarantee stability or compatibility on these platforms, and some unexpected issues may occur.

We also recently introduced a new freemium model as part of the updated application experience.

Please let us know if the issue persists after updating.

Best regards,
Alex
```