You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue started appearing 1-2 weeks ago
but like a month ago i had such a case too but by far not that extreme (50 km ~300m elevation diff vs actual)
here in that example, you can see that there are at least 2 places that are at 0 elevation, thus here the calculation appears to be correct but the underlying data is not? on bigger routes you won't be able to spot that ....
makes this feature unfortunately useless at the moment :(