GPX files compatibility with Garmin MapSource

[RogerC]

I have been trying to load a GPX file generated by Osmand+ into Garmin MapSource. I get the message "(filename) could not be imported".

The file loads into JOSM without problem.

Looking at the file and comparing it with a Garmin generated GPX file, the principle difference seems to be that the later contains a <metadata> tag including a <bounds> tag. Also, it names tracks, which the Osmand+ version does not.

Can anyone confirm if these differences are what causes the problem? Or if not, can anyone suggest other causes?

Many thanks,

Roger

[Harry van der Wolf]

You have to check whether the extension is .GPX or .gpx.

It makes a difference for some applications whether the extension is in uppercase or lowercase.

That might be the problem.

Harry

2014/1/11 RogerC <ro...@rogercalvert.me.uk>

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

[RogerC]

That's not it I'm afraid. Both files are .gpx.

Roger

[Greg Troxel]

RogerC <ro...@rogercalvert.me.uk> writes:

> I have been trying to load a GPX file generated by Osmand+ into Garmin
> MapSource. I get the message "(filename) could not be imported".
>
> The file loads into JOSM without problem.
>
> Looking at the file and comparing it with a Garmin generated GPX file, the
> principle difference seems to be that the later contains a <metadata> tag
> including a <bounds> tag. Also, it names tracks, which the Osmand+ version
> does not.

So there are two questions lurking in your mail:

does the osmand-generated GPX comply with standards (I would expect
so, but if you can explain why not I'm sure that would be of interest)

what non-standard things does mapsource insist on


I would recommend taking a single-track file from osmand, and one from
mapsource, and compare the usage of tags, and then hand-edit the osmand
one to be structurally like the mapsource one, and see if that works,
and then search to find out what's really necessary.

[fx99]

Garmin MapSource is really picky about tags that it accepts.
I tried some OSMAnd tracks and had to remove all <hdop> and         <extensions>           <speed> tags from the file in order to
be able to read it with MapSource .

[RogerC]

Thanks Greg and fx99. I will have to do some experimentation. I was hoping there might be a simple answer, but it seems not. I will post anything I discover.

Roger

[RonalT]

Op maandag 13 januari 2014 10:35:18 UTC+1 schreef RogerC:

I was hoping there might be a simple answer, but it seems not. I will post anything I discover.

Roger

I use JavawaRTWtool to do this. It is a simpel free program written by Javawa.
Download it from: http://www.javawa.nl/rtwtool.html
The language is Dutch or English 

It read all kinds of files, GPX, GDB, TCX, FIT, GPI, KML, KMZ, ITN, OV2, HTML, CSV, TXT, SHP, DXF.

It is not so picky, but makes a good file for Mapsource.

[meneer zwijn]

Same problems for BaseCamp, same solution (JavawaRTWtool).

[RogerC]

Thank you RonalT and meneer zwijn. I have downloaded JavawaRTWtool. I have not managed to get back to this problem yet (it is not critical for me), but hope to soon.

Roger

[Wouter Portegijs]

I noticed the same problem
And used sed to delete the speed and hdop information from the gpx file, works after that in basecamp.
The extensions header is also in garmin gpx files so it does not need to be removed.

sed -i bak -e '/speed/d' -e '/hdop/d'