Import of GPX files created by OSMAND into Garmin BaseCamp or Garmin Devices

496 views
Skip to first unread message

Wim Linden, van der

unread,
Mar 3, 2019, 9:22:25 AM3/3/19
to Osmand
Since sometime it is no longer possible to import gpx files created by osmand into Garmin BaseCamp.
Import of these files results in the error message 'unknown error opening import file'.

Further, importing osmand created gpx files into a Garmin Edge Touring navigation system leads to useless tracks.

Please advise how to solve this.

Metaluc

unread,
Mar 3, 2019, 1:06:33 PM3/3/19
to Osmand

They open fine with JOSM and GPStrackmaker pro. And if you output them from these programs they can then be imported into BaseCamp.

GPSbabel does not seem to correct them.

Each program that reads and writes them changes the tags a bit from Osmand's output. Them seem to place waypoints and routes before tracks, but manually moving them with an editor does not to fix anything.

I suspect BaseCamp is doing something wrong, like bad implementation of the spec. Garmin is known for creating some pretty bad software.

David Martin

unread,
Mar 4, 2019, 5:34:43 AM3/4/19
to Osmand
Agree.  I have been looking for somewhere to ask OSMAND to look at the export of GPX files. I *always* import GPX to Basecamp or to the (older) Mapsource and neither can handle the GPS files that OSMAND produces.  So this 'feature' completely breaks my workflow.  And by the sound of it, for quite a few other people too.  I am not knowledgeable enough to determine what's broken, but presumably OSMAND developers do know.  Presumably some (new) GPX data is being output that older progs cannot handle.  Please give us an app option, or remove that data ?

Metaluc

unread,
Mar 4, 2019, 7:02:29 AM3/4/19
to Osmand
It might be more productive to provide an osmand generated gpx file to Garmin and ask them why it doesn't import. Their "unknown error occurred" message is lame.

Mapsource us no longer supported.

Several other programs import the files, Josm, GPStrackmaker, Babel. That points the finger at Garmin more than osmand.

bughunter

unread,
Mar 4, 2019, 7:14:42 AM3/4/19
to Osmand

Here is a relatively cheap workaround. Get the free GPSbabel program here...


Use GPS Babel to translate .GPX from from OsmAnd to Garmin .GDB format.

The .GDB format file can then be imported into Garmin BaseCamp or the obsolete MapSource program.

If you want a Garmin compatible .GPX file, you can export from BaseCamp to a .GPX file.

This appear to work for Waypoints Routes and Tracks although enhanced information from OsmAnd such as elevation, and turn directions text, angle of turn are filtered out.


Wim Linden, van der

unread,
Mar 4, 2019, 10:41:52 AM3/4/19
to Osmand
Op zondag 3 maart 2019 15:22:25 UTC+1 schreef Wim Linden, van der:
=======================================
Thanks for the answers.
Import the gpx into OpenStreetMaps also results in an error message.

I discovered that the error is caused by the second part of the gpx file where the route instructions are given linked to the locations.
After removal of this part, the adapted gpx file can be imported into BaseCamp and can be used in a Garmin device (Edge Touring).

To remove this part open the gpx file with a text editor (like Notepad) and remove all lines at the end after (including) <rte> up to incl </wpt>.
The very last line </gpx> has to remain.

.....                      
<rte>                ^
.....                   | remove
.....                   |
</wpt>              v
</gpx>

The part to be removed contains locations and all kind of instructions like 'go right', street names etc.

I hope that OSMAND corrects this gpx export feature!

Andy Townsend

unread,
Mar 4, 2019, 11:05:33 AM3/4/19
to osm...@googlegroups.com

On 04/03/2019 15:41, Wim Linden, van der wrote:
>
> To remove this part open the gpx file with a text editor (like
> Notepad) and remove all lines at the end after (including) <rte> up to
> incl </wpt>.
> The very last line </gpx> has to remain.
>
Guessing a bit, but I bet you could leave the route points and waypoints
in if you removed the actual problematic elements from each object.

For example, I occasionally need to load an OsmTracker file into
MapSource, and you need to remove the "Speed" XML elements (search and
replace in a text editor) in order to do so.

Best Regards,

Andy

PS: I'm tempted to point the finger at Garmin rather than OsmAnd for
this one - I've written some things that target Garmin GPSs and their
file format is _very_ fussy.  Lots of things that "should be perfectly
valid XML" just won't work.



Wim Linden, van der

unread,
Mar 4, 2019, 1:54:29 PM3/4/19
to osm...@googlegroups.com
Andy, thanks for your answer, but I have no idea which the problematic elements are.
I did some trial and error but without success.
At the other hand, removing the entire last part is not much work and easy to do.
After doing the file works fine in my Garmin Edge and with BaseCamp.

The deleted file part is only useful in a device with Osmand  or other with a partial window for route instructions. Garmin has a different system for this.

Regards,
Wim

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/a4qHhUjkcKE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Message has been deleted

Christoph Rüegg

unread,
May 12, 2019, 5:16:11 PM5/12/19
to Osmand
I have the same problem and I use the following solution:
  • copy the Osmand-gpx file as kmz (not kml) into GoogleEarthPro. This creates several folders (see att. meineOrte)
  • save the file of the line  indicated with the red arrow (see attachment) as a kmz-file (not kml) on the desktop or somewhere else
  • import the kmz-file into BaseCamp and rename it at your convenience (it will contain all information like coordinates, time, elevation, velocity)
  • use it in BaseCamp or export it to any device as required
meineOrte_LI.jpg

Paul Tolhuis

unread,
May 12, 2019, 5:41:38 PM5/12/19
to osm...@googlegroups.com
Why not use Routeconverter.de?

Op zo 12 mei 2019 23:09 schreef Christoph Rüegg <chrir...@gmail.com>:
I have the same problem and I use the following solution:
  • copy the Osmand-gpx file as kmz (not kml) into GoogleEarthPro. This creates several folders (see att. meineOrte)
  • save the file of the line  indicated with the red arrow (see attachment) as a kmz-file (not kml) on the desktop or somewhere else
  • import the kmz-file into BaseCamp and rename it at your convenience (it will contain all information like coordinates, time, elevation, velocity)
  • use it in BaseCamp or export it to any device as required


--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/562e9f92-3b9f-4a13-8371-f898927eee1e%40googlegroups.com.

Christoph Rüegg

unread,
May 12, 2019, 6:32:01 PM5/12/19
to osm...@googlegroups.com
You are right. Or with gps-visualizer as I learned from another entry in the blog.

Herzliche Grüsse
Christoph

You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/a4qHhUjkcKE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/osmand/CAA%3Dxz1s0UU4ujv1D8s9GE157Jx87V2kBA_WO6wR1%2BpbhY_9AiQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages