Problem importing gpx file to My Collection

It may be a problem with the file that was originally uploaded to the OS site. You can often resolve problems with BC failing to import downloaded GPX tracks by uploading the problematic file to the webapp GPS Visualizer and converting it to a second GPX file, downloading the converted version and importing that into BC.

Having exactly the same problem as 7649582.  Manually created a test route using OS Mapping but that doesn't clear the problem. Tried GPS Visualizer and it works. Thanks :-)  However.....having paid a subscription to OSMaps and for a new GPSMAP 66i I would hope for seamless compatibility. Any other advice please?

Hi, Had the same problem and it appears to be at the OS end. Have found that switching "Back to OS Maps Classic" at the top of the new OS Maps website and then exporting exactly the same routes works in Basecamp.

I have just checked and agree with you that the GPXs created by the original OS site https://osmaps.ordnancesurvey.co.uk/ import into BC without any issue, but the same route exported as a GPX from the new OS website https://explore.osmaps.com fails to import.

If you plot a simple test route, export the route GPX from each OS site, then compare the two files in a text editor you will see that the two files are very different. In the GPX from the explore.osmaps site, OS seem to have added in a pile of new new 'OS' extensions which aren't readable by BaseCamp. When you use GPS Visualizer to convert this file, it strips out all these OS extensions and restores it to a clean GPX file which will then import, like the one produced by the original OS site.

So it looks like you will need to use the original OS site for exporting GPXs. However I suggest you make two GPXs as above and send them to OS Customer Support and ask them what's happening and why. 

That's very useful, thanks :-)  I have written to Ordnance Survey and will let you know if their reply sheds any more light. They sell the GPMAP 66 on their web site so it's not good marketing on their part if their new OS Maps site is incompatible. Will keep you posted.

This solved it for me, thank you!!

5162707 said:

However.....having paid a subscription to OSMaps and for a new GPSMAP 66i I would hope for seamless compatibility.

Do the new OS files work on the GPS MAP?

Even if I copy the new site GPX below into the \Garmin\GPX folder on my GPSMAP 66st, the device won't read it.

These are the test downloaded GPX files of the same route as I mentioned above.

OS enquiries.zip

The new site file has a spurious unmatched <rte/> tag in line 33, which was not present in the file of the same route downloaded from the original site, so it just may be a bug in writing the GPX? A few people have confirmed this behaviour with different devices and have reported it to OS, so I presume it is the same for the GPSMAP 66i?

Hi, This just in from Ordnance Survey cc'd below. It's a known problem which they hope to resolve in the next version of OS Explore due out on the 14th Feb. 

"Thank you for your contact reporting what is a 'known issue' for GPX files.

If you wish to export from Explore then please note the files from Explore contain wptType, rteType and trkType formatting. If you are trying to import onto the app please can you try using the web version (classic) if you are experiencing issue with importing to web then please can you try importing to the app? These are the 'workarounds' currently provided by the Tech team. So the team are aware and a new version of Explore is set to release on 14 February which we expect to return all the features working as first hoped."