Erreur de Calcul des KM dans Land ?

Segui

jacques emile

• 10 maggio 2018 12:12

Je reviens de la traversée du Drakensberg Afrique du Sud - au passage je salue la qualité de la carte Raster de TwoNav qui est en gros la copie du set des excellentes cartes papier de l'escarpement bien qu'il y ait des erreurs dans quelques noms et leur situation géographique - j'ai enregistré quotidiennement mes traces avec ma montre Amazfit XIAOMI puisque je ne voulais pas courir le risque d'avoir mon Twonav bloqué dans mon smartphone.

Ces traces lues dans LAND ont un kilométrage notablement supérieur a celui qui est donné par ma montre ou par BaseCamp. Les kilométrages de ma montre et de Basecamp sont quasi identiques et reflètent la réalité. Soit 220km pour presque 300 donnés par Land. 

Quel est le problème, un mauvais paramétrage de mon Land ?

(Nota je viens d'installer la dernière MAJ)

Merci de pouvoir me répondre

 

0

• 

  Uwe B.

  • 10 maggio 2018 14:08

  I guess it is the same problem I allready stated in this thread:
  https://support.twonav.com/hc/en-us/community/posts/360007377911
  I started recording my tracks with a Xiaomi Amazfit Pace watch. Sometimes the altitude is not added to the track and if this happens, Land is giving it a value of "-1" instead of igrnoring it. This leads to a lot of pseudo vertical movement. You can either use Land to correct the altitude like stated in the mentioned thread or hope for a fix.

  0

  Azioni per commenti Permalink
• 

  jacques emile

  • 10 maggio 2018 18:24

  Thanks UWE for your comment, but in my instance I fear this is with the milage that may appears buggy ...

  0

  Azioni per commenti Permalink
• 

  Uwe B.

  • 10 maggio 2018 19:25
  • Modificato

  Yes but if you calculate mileage in a 3 dimensional setting (CGPSL can do it in a 2dimensional too) and one dimension just jumps from -1 to I don't know which altitude your mountains had, I guess the 3 dimensional mileage gets just wrong.

  0

  Azioni per commenti Permalink
• 

  jacques emile

  • 10 maggio 2018 19:30

  OK, I understand ... That may be why the gap between the 2 figures : Land calculating the milage in 3D and Amazefit/BaseCamp only in 2D. 

  Thks Uwe

  0

  Azioni per commenti Permalink
• 

  Uwe B.

  • 10 maggio 2018 21:06
  • Modificato

  Not exactly. I can't be sure without seeing the trackfile but I guess Basecamp/Amazfit is calculating in 3D too, but are ignoring the missing altitude points, while Land is using them for calculation with the value -1m, which was done so in my case and which did distorted the mileage value massively (just imagine adding one deep valley descent and steep mountain ascent for each missing altitude in a trackpoint). For now just try to use the solutions which have been suggested in the linked thread, I guess that will result in comparable mileage.

  0

  Azioni per commenti Permalink
• 

  www.twolandnaviste .fr

  • 11 maggio 2018 07:15

  Hi,

  Didn't you try asking Land to recalculate your track ?

  Clic right on a track, Tools, Assign time and Speed

  Best regards

  0

  Azioni per commenti Permalink
• 

  jacques emile

  • 14 maggio 2018 15:18

  Thanks, I'll try like that.

  0

  Azioni per commenti Permalink

Accedi per aggiungere un commento.