Elevation profile of routes created in Suunto App
-
Hi,
I have issue with the quality of the elevation profile in routes created in Suunto App (and Route planner). When using Suunto App, I use iOS.The most obvious situation to observe the issue is when creating a manual route without following any roads or trails. The elevation profile is completely off and unusable.
Attached is a few examples where I created snippets of a route in Suunto App and in Strava. First I thought it might be due to regional bad quality of the underlying map data. But the error is consistent both in northen Norway, mid of Sweden and in the region of Chamonix (France).
The strange thing is that if I exit the route creator mode of SA and long press anywhere on the map, so that I get info regarding the coordinates of the point I pressed, it gives me correct elevation. So there seem to be a difference between the map data and the elevation for each point in a created route.
Also, when creating a manual route (without following a trail), SA only looks at the delta between point to point. When creating same thing in Strava, it seems to iterate the elevation all along the line between point to point. This becomes painfully obvious if you create a manual route from one peak to another peak. Elevation profile in Suunto App is just a straight line between the elevation of peak 1 to peak 2, and Strava gives you a much more correct profile, showing the valley between the peaks.
I love creating routes in SA an actually hate Strava interface, but when it come to elevation profile, SA is unusable for me. I’m surprised that nobody else seems to have this isAt least from what I see in this forum?
-
Hi again,
Here’s another example. Two first screenshots are from creating the same route. The only difference is that in The second picture I added the last route point at the peak, and in the first picture the last route point is slightly before the peak.
And here’s a screenshot from doing that ski tour last year.
-
And here’s and example of creating a route only consisting of point A to point B in Suunto App and in Strava. Point A is Brevant and Point B is Aguille du midi in Chamonix (France).
-
@Tomas-Vujic-Schelin said in Elevation profile of routes created in Suunto App:
I’m surprised that nobody else seems to have this isAt least from what I see in this forum?
I made several posts and comments about the low quality of elevation data in Suunto App. Even even following trails, the elevation data is often off and the estimated ascent for the route is routinely 15-30% too low.
Suunto: Ambit, Ambit 3 Peak, 9 Baro, Race S, Race Ti
Garmin: Forerunner 210, Forerunner 610, Fenix 6X, Fenix 7X Ti -
I noticed the Problem on some Route creation too. Not on all routes, but on some Parts. Improving this Part of the Route creation would be pleasant.
-
@sky-runner said in Elevation profile of routes created in Suunto App:
Even even following trails, the elevation data is often off and the estimated ascent for the route is routinely 15-30% too low.
This have just become better, test again. Though ofc depends on the location
-
@Tomas-Vujic-Schelin said in Elevation profile of routes created in Suunto App:
The most obvious situation to observe the issue is when creating a manual route without following any roads or trails. The elevation profile is completely off and unusable.
When building a route in “free draw” mode the elevation is off. This is a known problem. Hopefully will be addressed one day.
-
@pavel.samokha Minimal route changes, with essentially no change in elevation, result in something like this:
-
@maszop I can’t infer the full meaning from your post. What route changes?
-
@pavel.samokha Minimal route editing
-
@maszop as I said above - yes, it’s a known issue
-
@pavel.samokha Well, certain problems shouldn’t arise in tools whose primary purpose is navigation. And they’ve existed for so many years.
It’s a real shame, because I think SuuntoApp has the best route editing mechanism on the market.
-
@pavel.samokha said in Elevation profile of routes created in Suunto App:
When building a route in “free draw” mode the elevation is off.
Is there a reason behind this?
-
@2b2bff if you’re asking why SA doesn’t provide a correct elevation profile between two arbitrary points on the map then it’s because it has never been developed. This is a separate task, not the same as provide an elevation profile for a route along path network
-
@maszop said in Elevation profile of routes created in Suunto App:
Well, certain problems shouldn’t arise in tools whose primary purpose is navigation. And they’ve existed for so many years.
I’m not arguing that this is important issue to solve, but there are (and always will be) many things which someone can claim are essential.
We will soon have another big and important thing released related to navigation.
