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
Currently we scale the y-axis of the elevation widget depending on the incoming data and so even small changes between e.g. 110m and 130m look huge despite being distributed over a few kilometers. Should we use e.g. "min elevation + 500m" as maximum value? Or e.g. use 0m as min elevation? And somehow consider the length of the route when picking the (min and) max elevation of the widget?
The text was updated successfully, but these errors were encountered:
Currently we scale the y-axis of the elevation widget depending on the incoming data and so even small changes between e.g. 110m and 130m look huge despite being distributed over a few kilometers. Should we use e.g. "min elevation + 500m" as maximum value? Or e.g. use 0m as min elevation? And somehow consider the length of the route when picking the (min and) max elevation of the widget?
The text was updated successfully, but these errors were encountered: