Lines between waypoints

[Cabati]

Hi, when I import a GPX file into my Garmin XT, it creates connecting lines in between the waypoints.
Can someone tell me what I do wrong?
/Matthias

[Breezly]

That file is not a list of waypoints. It's a track. What is it that you're trying to do?

[Cabati]

I found a GPX file of a nice tour in Denmark and simply want to upload it to my Garmin XT. But it is connecting some of the "points" and this gives thousands of kilometers, instead the 2-300 km the track is in real.

[Breezly]

Well that file is a track with 1,834 pints in it. Some of the points are out of order and that is why there are odd lines connecting different parts of the route. I would guess that either the file is corrupted or was put together incorrectly.

[raza]

I delved into the attached fail and tried to extract the problem of straight lines.
I discovered an error on the map. The two roads along which the trail runs are not connected and consequently the calculation of the planned route from the trail fails.
Nevertheless, I managed to somehow extract the planned route from the trail. Where a straight line remained in the trail, I adjusted using nearby local roads.
I hope I helped with that.

[jfheath]

The attached GPX file contains 3 routes, two tracks and 4 stored waypoints.

Routes:
kml_122 has just two waypoints - the satrt and finish kml_122 and kml_1221 - set for motorcycle, faster time. It has no intermediate points defined, but the route has been calculated on Basecamp and saves a whole lot of 'ghost points' - the gpxx route point extensions which keep the route in place when it is loaded to the XT.

sled_004 has plenty of intermediate Via and shaping points - one of which is a waypoint - Sled 004. These appear to have been dropped in place using Basecamp tools - judging by the name given to the points.

Tårsvej 151 to Sled 0041 - has just 3 points - Tårsvej 151, Tårs and Sled 0041. Only oneof these is a waypoint (Sled 0041). The route description alos shows it has been calculated by garmin (or similar) - with a small number of ghost points - but it is a short route and many of the roads it goes along are straight so the number of points required to represent a straight line is much smaller than the number required to draw a curve.


There are two tracks in the file.

kml_122 and Sled 004

kml_122 follows the route kml_122 precisely.

Sled 004 track does not follow the kml_122 route.

image2.png (651.22 KiB) Viewed 1992 times

The blue line represents the track, the magenta line shows the route.

When I use basecamp to convert the kml_122 route to a track, the track follws the route precisely - as you would expect.

I don't think that Basecamp was used to convert the Sled_004 route to the sled_004 track. Or if it was - something went very wrong with the conversion. The lat/lon points do not match up, and they would do if they came from the same place. Perhaps the map on your XT is not the same as the map in Basecamp - or the routes originated from somewhere else and you did not recalculate the routes before trasnferring them.

The kml_122 track and route also have different lat/lon values for each of the points - even though they plot precisely on the map.

I'll explain what I mean. In the gpx file, if they were obtained fromt he same route using the same map the 'ghost' route point

<gpxx:rpt lat="54.913079738616943" lon="12.053461074829102" /> would be converted to a track point
<trkpt lat="54.913079738616943" lon="12.053461074829102" />

ie the lat / lon doesn't change at all - only the tag at the start.

In fact, the equivalent point as far as I can tell (6th one down) in your track shows as as this -

<trkpt lat="54.913168251514435" lon="12.054146379232407" /> None of the track points match any of the route points ! The track must have come from a different source or a different map.

There are about 1280 of these. Only the genuine waypoints which have defined coordinates are the same. The rest do not match up at all.

When I transferred them to my XT, I got the same results as the Basecamp map shows.

After recalculating the routes and creating new tracks in Basecamp there were no issues.