Run.GPS Online Shop

• Einloggen | Registrieren

• Apps
  • Run.GPS Trainer UV PRO
  • Tägliche Kalorienbilanz
• Downloads
  • Run.GPS Atlas Karten
  • Run.GPS Skins
• Community
  • Ruhmeshalle
  • Top 100 Aktivitätslevel
  • Neueste öffentliche >
    • Trainingseinheiten
    • Routen
    • Benutzer
    • Fotos
    • Trainingspläne
  • Stats >
    • Länder
    • Sportarten
    • Clubs
    • Smartphones
  • Foren
• Routenplaner
• Mein Run.GPS
• Support
  • Foren
  • FAQ
  • Partner

GPS-Sport ForenRun.GPS SoftwareHilly tracks, loose distance?

Bitte einloggen, um neue Kommentare zu erstellen

Foren durchsuchen

Erste Seite<Seite1von1>Letzte Seite admin 06.04.2010 15:57:52 UTC Dima is right. The altitude is not taken into account because it's not accurate enough. mdscott 01.04.2010 20:17:23 UTC same experience I lost 0,2 miles out of 5,8 or about 3,5% on a hilly course. Dima 31.07.2009 11:00:56 UTC There are some problems with GPS attidute accuracy, so I think run.gps do not use it for calculations and actually shortens distance. SteffenK 24.07.2009 20:15:08 UTC same experience I've measured out several tracks by bike and run.gps is always several hundred metres behind the "real" distance. I think measured out the real distance correctly because i measured out the wheel length of my bike very exactly and I'm using a Vdo bikecomputer... and there was the half marathon witch was about 21,1km and rund.gps lost 700 metres although the Dop was always below 3. Guess there are still some problems in calculating out the huge amount of measuring points. Vladlen_Popov 24.07.2009 09:35:25 UTC geändert am 24.07.2009 09:53:52 UTC I have same comment. The lenght of track (it is too hilly) which is I used for running is 14.5 km it was calculated on Nokia Sports Tracker, but RunGPS shows 13.6 km. clarre 20.07.2009 13:29:26 UTC I am an experienced runner (have been running long istance for 28 years) and believe I have a decent perception of time and distance when I run. I ahve used RunGPS on a HTC Touch HD when running on fairly flat ground for a couple of months. It has been working great! When on vacation in my summer house I have a couple of tracks I run which are very hilly. The tracks are roughly 15 km. I believe I loose something like 7-900 meters on the software compared to what I have always believed they are. I can of course not be sure but I can usually estimate distances very well from my own tempo and the time I run. So my question is: Does the algorithm really take the alititude into acount when it calculates the distance??? The distance between A and B is of course longer if you have to climb also. All the best C-H Erste Seite<Seite1von1>Letzte Seite