RS - Reported track data differences

[WVMike]

I have noticed the voice reported data when finishing a track is different than what is reported once it is uploaded to RE.
Today I recorded a track that was voice reported as 1002' of AEG at the end of the track.

When I uploaded it to RE it is showing 839' AEG.

The mileage is usually off as well but I cannot remember the specifics.

Comments?

WV-Mike

[joebartels]

@WVMike
When you save or post from Route Scout to HAZ it auto syncs elevation to 1/3 arc National Elevation Data which is typically more accurate. Mileage shouldn't change much if any from RS to HAZ.

[WVMike]

When you save or post from Route Scout to HAZ it auto syncs elevation to 1/3 arc National Elevation Data which is typically more accurate. Mileage shouldn't change much if any from RS to HAZ.

Thanks Joe.
I am diggin' RS and RE!

[rcorfman]

When you save or post from Route Scout to HAZ it auto syncs elevation to 1/3 arc National Elevation Data which is typically more accurate. Mileage shouldn't change much if any from RS to HAZ.

If I felt up to it, I would argue that that probably isn't the case as far as AEG goes. It will be more accurate for the current elevation since that is based off a mathematical model, but for calculating how much a person goes up and down, I have my doubts.

[joebartels]

Elevation Sync from RS to HAZ is now off. Five or so years ago, elevation on smartphones was horrible. Now seems better than NED coordinate models, especially near cliffs and in canyons. Unlikely needed but you can still manually sync on HAZ if desired.

Note, AEG won't be an exact match. There will be a slight difference in AEG on RS vs HAZ. Either a floating point difference or coding variance limits.

Tested RS +Add Route & RS +Add triplog
RS save to RC seemed fine in one test but I didn't dig into it