This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fenix 3 GPX Exports from Connect give nonsense zero island results in Google Earth

Former Member over 8 years ago

I recently spent a month in England where I uploaded each days activities into Garmin Connect. In Connect the tracks show correctly on a map. When I export them however all I get is a vertical line from England down to zero island - 0,0 longitude latitude:

I see that each gpx file starts with at least one 0,0 track point:

<name>2016.07.27 Castle Great Coxwell Cross Country Skiing</name>
<type>cross_country_skiing</type>
<trkseg>
<trkpt lat="0" lon="0">
<ele>0</ele>
<time>2016-07-27T13:19:08.000Z</time>
<extensions>
<ns3:TrackPointExtension>
<ns3:atemp>31.0</ns3:atemp>
</ns3:TrackPointExtension>
</extensions>
</trkpt>

I have tried removing these 0,0 points but the track still display as above in Google Earth and GPX Viewer (Mac).

0 Former Member over 8 years ago

There is a problem with GPX and TCX exports from Garmin Connect Online which I have reported to Garmin and they have confirmed and are investigating. If I were to guess the problem occurs when the watch can't get a good enough location lock and is perhaps recording <null> (ie, a blank) for the lat/lon. This can happen if you start the track before the watch gets a good location lock (wait a few seconds past when it says it has a lock just to be safe). The map display in Garmin Connect Online correctly ignores these points, but when you export to GPX/TCX it converts the <null> to a 0...thus you end up in the Atlantic Ocean off the coast of Africa!

I have been successful in manually removing these 0,0 data points out of my GPX export to get the track to display correctly in my photo geotagging software. They can occur anywhere in your track that the watch doesn't have a location lock so you'll want to make sure you get them all. Another option is to open the activity in Garmin's Basecamp software. At least in the Mac version it does not have this same problem and should export a clean GPX file.

0 haraldbootz over 8 years ago

same here, probs with the exports

not nice when I want to use the gpx files for other stuff (like importing to Runtastic, where I track other sports, too)