Re-tested latest Run and Recorder apps today over a 1.03mile loop.
Had recorder set to record every second.
Distances recorded:
Run showed 1mi (needs 2 decimal places when in mile or km mode)
When the track is viewed in recorder it shows as 1m (no decimal fraction).
Amizfit Bip showed 1.03mile (I have verfied through a Garmin eTrex this is correct)
Downloaded the GPX file and loaded into Viewranger and it said 0.97 miles.
HOWEVER when the file is imported into viewranger there is a tolerance of 30m and it throws points away if it thinks it can make a simpler polygon.
CONCLUSION: I am satisfied that with the recorder set to 1s intervals that the distance calculations by Run and Recorder come out the same. Any discrepancies will be down to not setting the recorder to match the same GPS fix frequency as Run OR down to import issues when the downloaded GPX file is imported into some mapping software.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Re-tested latest Run and Recorder apps today over a 1.03mile loop.
Had recorder set to record every second.
Distances recorded:
HOWEVER when the file is imported into viewranger there is a tolerance of 30m and it throws points away if it thinks it can make a simpler polygon.
CONCLUSION: I am satisfied that with the recorder set to 1s intervals that the distance calculations by Run and Recorder come out the same. Any discrepancies will be down to not setting the recorder to match the same GPS fix frequency as Run OR down to import issues when the downloaded GPX file is imported into some mapping software.
2 Attachments