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
  • Yep, GPX uploads from my Dakota 10 are showing track but not distance. My guess is that they've shut down the distance calculations to facilitate processing bandwidth for all of the Vivofit users, of which I'm one ;-). Well, if they're considering GPX files from older Garmins as third party products, then it's time for me to find a new ecosystem. And I was liking Garmin too....
  • Is it free? As someone else mentioned, the availability of Garmin Connect and facilities to sync my data with it is something that encouraged me to buy Garmin products (Edge 500, VIRB Elite, HRM etc). If it hadn't been available I may have bought those items from elsewhere. Yes, you can sync the data with other websites (automatically in a lot of cases, including Strava) but I still expect Garmin to continue to provide Connect with a reasonable level of service. What they could consider is looking at a standard/premium model where purchase of a device gives you access to certain functionality and you can get extras by paying but they've chosen not to do that yet (as far as I can see) so I don't think it's unreasonable to expect Connect to just work!


    Exactly true. This web site is part of the service we pay for when we buy our devices.
  • I'm the only one bothering with this thread these days, LOL. Apparently, according to tech support, uploads to Garmin connect from hiking-specific devices are no longer supported. Here's a quote of the tech support reply:

    "Thank you for contacting Garmin International. I will be happy to assist you with the Dakota 10 and the Garmin Connect inquiry.

    Do you have BaseCamp on your computer? Please, advise.

    BaseCamp was developed for outdoor units using GPX files.

    Garmin Connect was developed for fitness products using FIT files.

    The files on the Dakota are stored as a GPX files and it does not work well with Garmin Connect. The GPX files do work well in BaseCamp.

    Here is a link for BaseCamp: http://www8.garmin.com/support/mappingsw.jsp

    Please, use BaseCamp for the GPX files recorded by the Dakota.

    If you have any other questions, please reply to this email or contact us at 1-800-800-1020 Monday through Thursday from 8:00AM Central to 6:00PM and between 8:00AM and 5:00PM on Fridays. We are closed most major holidays and weekends."




    I think I'm returning the Garmin Forerunner 210 and Vivofit I just bought and going the Fitbit route. I stayed with Garmin because of the other devices I had. If they won't integrate my devices anymore, I see no reason for any loyalty to their products.
  • WOW, if GPX no longer supported... too late for returning my 62s. No Garmin again.
  • Here is a free temporary fix until Garmin fixes Connect.

    Install Garmin Training Center. Use the Import function to import your GPX file. Use the Export function and select TCX.

    That new TCX will upload to Connect. I just did exactly that and it worked. :o
  • Oh - it (the GPX upload) used to work perfectly until the GC update in Dec. Now that they can't fix what they messed up it the easy way out is to say GC doesn't support it anymore?

    .....'stored as a GPX files and it does not work well with Garmin Connect.'[/COLOR] --->>>>> Just scan through many threads here, and see how well it DID work with GC!

    Bizarre, actually, total BS :mad:
  • As I metioned a few days ago I dumped my forerunner 210 an bought a Polar m400. Very nice device, but also some flaws, nothing serious. It's new and new features are coming by time. And it's much cheaper than a forerunner 210, has more functions AND a nice WORKING web interface called Polar Flow.

    Garmin Connect still doesn't get it. Even a TCX I exported from Polar Flow cannot be uploaded (don't know why). But the SAME FILE works on Strava without any problem. Can't Garmin read their own file formats anymore?

    Now waiting for the announced bike computer from Polar. So a long relationship (to Garmin) is passing ...

    And, BTW, I don't want to install any software to fix Garmins errors. I am (ie was) expecting that garmin fixes the wrong distance in my uploaded tracks automatically. I don't want(ed) to upload anything again.
  • 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 :-/


    That's what I suspected time ago... and now things appear to confirm my worries :mad:

    Discovering it analizing clues and un-official private answers from Garmin is very irritating. More than else because it seems that Garmin deliberately introduced an fake bug to cut out "unwanted Garmin customers" from Garmin Connect.

    <polemic mode: on>
    My question now is: what could be the most reasonable behaviour for a customer "unwanted" by a supplier ?
    <polemic mode: off>

    I think it's time to look around for a worthy heir of my Etrex30 !
  • Specs of GPSMAP 62s:

    Garmin ConnectTm compatible (online community where you analyze, categorize and share data)

    And yet it's a unknowm device.....
  • It is compatible ... but it won't automatically sync, handhelds never have. You need to manually import gpx files.

    Unknown device could also be due to a corrupt GarminDevice.xml file. You could try deleting it from the Garmin folder on your 62, then reboot the 62 which will recreate the file then try again. It may at that point be recognised. My Montana and Etrex are.