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

GPX Activities uploaded no longer have length/distance

Since the Garmin Connect website downtime yesterday (12/19/14), GPX file uploaded as activities no longer interpret the correct mileage length, or associated calculations. Time and elevation appear to be known, but not distance.

Anyone else see this?

Thanks
  • My Connect is showing details without a problem, so not sure it's Connect.


    When you upload a GPX file as an activity, you have no distance issues?
  • I guess it's better if users with distance issue will also declare which gps appareil they are using.

    I suspect that some specific bike computers like Edge family are not affected by the problem.
    Please let me know if I'm right or wrong.
  • I guess it's better if users with distance issue will also declare which gps appareil they are using.

    I suspect that some specific bike computers like Edge family are not affected by the problem.
    Please let me know if I'm right or wrong.


    Same problem with distances here (Dakota 20 & Oregon 450)
  • I tried this several different ways.....

    1) Uploaded an activity using Garmin Basecamp from my eTrex Venture HC handheld unit - distance in Garmin Connect 0.0; Basecamp has the correct distance
    2) Uploaded directly from my Edge 500 to Garmin Connect using Garmin Express - distance in Garmin Connect was correct.
    3) Uploaded directly from a Forerunner 15 watch to Garmin Connect using Garmin Express - distance in Garmin Connect was correct.
    4) Exported an activity (gpx format) with correct distance from Garmin Connect and then imported the file back into Garmin Connect - distance was 0.0
  • Thanx for sharing. Good clues to think about :)
  • I've explained that I'm uploading a GPX from an Oregon 550 as an activity. It worked before 12/18, distance has been 0.00 after. The distance before and after shows correctly in Mapsource. There is nothing different except the Connect website upgrade on 12/18. I further explained that when I look at my green elevation plot and select 'over distance', the mileage shows up incorrectly at the bottom of the graphic. What should be 1 mile shows as 0.001 miles. That's why my 3.8 mile hike shows as 0.00 miles, it's being interpreted as 0.0038 miles. I also added that this is confirmed by uploading a nuvi GPX track of 26.1 miles, which shows as 0.03 miles. They're somehow 3 decimal places off on the distance.

    If Garmin isn't reading this, and I keep having to repost what I've already said, this appears pointless.

    If it's working for you, you aren't uploading a GPX file from a standard GPS device, you're syncing a fitness device.
  • One may also think that G applied a bug to cut out all not compatible devices with GC.

    G already declared that not all devices are compatible with GC. For example, Etrex, when connected to GC via cable, is shown as 'unknown device'.

    To make a long story short, G may have changed their policy. They may have done it simply showing correct data in a wrong way.
    This will keep good data on dbase anyway, just to maintain their possibility to make a step back if users make a revolution :-/
  • Please note that I hope being WRONG

    It would be a real delusion buying a Garmin device but having to manage data with third parties sw :-(
  • Having the same problem - Forerunner 210 battery was running a little low and didn't have my charger handy, so recorded two runs via Strava, with a view to exporting the GPX file and upload to Garmin Connect.

    Other users are spot on - the distance is 3 decimal places off. For example, ran 21km on Christmas Day, Garmin Connect Mobile app displays the run as being 21m. Another run of 6km shows as 6m.

    A run uploaded from the Forerunner 210 via Garmin Express works fine - it's just the other, uploaded GPX files that are giving an issue.

    Should be a simple enough bug to fix from Garmin's end, one would think?