Problem importing gpx file to My Collection

Further to that yes, the data in the modified file is duplicated so the whole route is first saved in the format </wpt><wpt lat="50.367194" lon="-4.158171">
<name></name>
</wpt>

and then in the format <trkpt lat="50.367194" lon="-4.158171"><time>1970-01-01T00:00:01.000Z</time></trkpt>

Tried stripping out the first lot of data in the <wpt> format and it still uploaded perfectly OK so Garmin must only read the <trkpt> data.

When the OS GPXfile is imported into BaseCamp, BC reads both the waypoints and the track points in the file. There are 879 individual waypoints and 1439 track points. As dpawlyk said, these are different. Only the track points are needed by BaseCamp or your device to create the track.

The GPX file exported from Nakarte also has both waypoints and trackpoints.

Yes I discovered that. Removing the Waypoints, which seem to have exactly the same co-ordinates as the track points, the file still loaded and displayed OK in Garmin Connect. I used to use Basecamp all the time with my eTrex Legend but with this new machine I am only using Garmin Connect although I think both Basecamp and my eTrex were a better set up than my current one. I unfortunately lost my eTrex. It might not have had all the bells and whistles of the Edge Connect but I really just want it for navigation, not to tell me how many calories I've burned or how many litres of sweat I've lost! Anyway I digress.

There are fewer waypoints than track points. That the waypoints have the same coordinates makes sense.

Waypoints are coordinates your route "must" pass through. In between the waypoints, the path can follow whatever path is selected by the routing calculator.

Track points were originally coordinates that were recorded on an actual trip. These will trace your actual path.

Track points are now also used to accurately show where your path will go.

Thus, the standard way to plan a route is to pick your waypoints and have the routing calculator choose the path between the waypoints. The routing calculator can also generate track points that trace the path it chose.

Many GPS devices can use tracks to base navigation on. Some of them (like the Edges for cycling) can only use tracks.

Since, historically, tracks were part of a record, the points always had timestamps.

The route calculator needs to know the direction of the track to be able to use it for navigation. It knows the direction from the timestamps.

This normally isn't as hard to deal with. Part of the issue was the lack of timestamps (most sources include them).

Hi - thank you for that, very interesting. I must admit I have learned a lot today from being on this forum. That was a thing with my eTrex Legend - when programming a route you had to make sure it would calculate the same route as you had drawn on Basecamp. As the device had a much smaller and slower computer in those days, it often came up with some bizarre twists and turns so you had to be quite canny and 'trick' it into sticking to the route you had in mind. I get what you're saying about the difference between waypoints and trackpoints and the necessity for timestamps to define the direction with trackpoints. If you didn't get the waypoints in the right position for the eTrex it would often try to take you off down some un-navigable path, a bit like Google maps sometimes tries to do with it's current navigation facility - we've often ended up on tricky little single track roads when a perfectly acceptable but slightly longer route is available on a less remote route.

I'm very familiar with how the Edge devices work. Not so much for the others.

Part of the confusion is the meaning of "route". That sometimes means a list of waypoints (that the path needs to be calculated between). Some devices can uses these "route" files and some (like the Edges) cannot.

"Track" tends to be used more consistently (it's a list of timestamped coordinates that traces the path accurately).

Same problem for me Exporting a GPX file from explore.osmaps and then trying to import into Garmin Connect.

I opened the OSmaps gpx file in a text editor, deleted all of the <wpt> data lines, leaving just the <trk> data and then it successfully uploaded into Garmin Connect.

Thanks for the help of the forum, let's hope OSMaps and Garmin can collaborate here, although not holding my breath.