Suunto Routeplanner
-
@kemetter
Sounds Great! -
@kemetter said in Suunto Routeplanner:
This should match Suunto app quite well, but some GPX files have quite odd content. I would need the original GPX file in question to be able to resolve this.
Waypoints should load if GPX is exported from Suunto app, but from other sites it’s not a standard how they mark user named waypoints.
Here is one example, which I think I created this in Strava:
Issy Alps 50k.gpxWhen I load this in Suunto App it shows all waypoints and the distance is 50 km:
When I load the same GPX file in the routeplanner, no waypoints are shown and the distance is 42 km:
It may not be obvious by looking at the screenshots but the missing parts are from the start to the first waypoint and from the last waypoint to the finish. Basically, the route now starts at the top of the first mountain and ends at the top of the last mountain.
I’ve had similar issues with a few more GPX routes.Also, I should mention that on-route waypoints can also be present in routes that are saved as FIT files. Those can be generated by some route planners such as PlotARoute and are natively supported by Garmin. It would be great if the route planner could load routes in the FIT format too. Also, routes in FIT format can embed turn directions, and some route editors (e.g. PlotARoute) can create those too. It would be awesome is Suunto followed the same standard.
-
P pavel.samokha referenced this topic
-
@sky-runner said in Suunto Routeplanner:
@kemetter said in Suunto Routeplanner:
This should match Suunto app quite well, but some GPX files have quite odd content. I would need the original GPX file in question to be able to resolve this.
Waypoints should load if GPX is exported from Suunto app, but from other sites it’s not a standard how they mark user named waypoints.
Here is one example, which I think I created this in Strava:
Issy Alps 50k.gpxWhen I load this in Suunto App it shows all waypoints and the distance is 50 km:
When I load the same GPX file in the routeplanner, no waypoints are shown and the distance is 42 km:
It may not be obvious by looking at the screenshots but the missing parts are from the start to the first waypoint and from the last waypoint to the finish. Basically, the route now starts at the top of the first mountain and ends at the top of the last mountain.
I’ve had similar issues with a few more GPX routes.Also, I should mention that on-route waypoints can also be present in routes that are saved as FIT files. Those can be generated by some route planners such as PlotARoute and are natively supported by Garmin. It would be great if the route planner could load routes in the FIT format too. Also, routes in FIT format can embed turn directions, and some route editors (e.g. PlotARoute) can create those too. It would be awesome is Suunto followed the same standard.
I fixed a bug with GPX loading and that file should load better now. Still some uncertainty about the user waypoints, it seems to load two of them but there apparently should exist four. I will look into that.
Regarding FIT files Routeplanner supports loading them but as they are usually made from exercise logs, there is no turn-by-turn or waypoint support when loading FIT files.
-
@kemetter many thanks for maintaining and developing this great tool.
Sadly, the area I frequent the most (Dolomites, Italy) have a poor rendering quality, frequently distorted by artefacts that cause the maps to be sometimes completely unreliable
(e.g. https://forum.suunto.com/topic/10992/artefacts-on-maps?_=1770025858529) -
@kemetter
I am very happy with the new Route Planner. It’s much more comfortable to plan routes on a PC compared to using the app, and the direct upload to Suunto is really useful. Thanks Suunto for that WebApp!I have a few feature requests that would be great to see:
Reset Button: An option to clear the currently planned route and start fresh on an empty map.
Estimated Time of Arrival (ETA) based on Pace: The ability to input a target pace to get a time estimation for the planned route. It would be great to see how long a route will take based on my expected speed directly in the planner. This is crucial for planning nutrition and logistics for long trail runs.
Turn-by-Turn (TbT) Navigation Toggle: Currently, I can’t enable or disable TbT navigation in the Suunto App for routes imported via the Web Route Planner (though it works for Komoot imports). It would be great if Suunto supported this option natively within their own ecosystem.
Colored Map Layers (Ascents/Descents): It would be helpful to have a toggle in the Web App to show colored segments for ascents/descents on the route and elevation profile, just like in the mobile app.
-
@tuxbuster TbT:
I just tested this. When I open the route that was synced to my Suunto account in the app, I can then toggle TbT on or off. I am on iOS.
So this one works well. -
@Egika You’re right. I tested it again: If I draw a route from scratch in the Web Route Planner and upload it to Suunto, I can enable TbT. BUT: If I open an existing GPX file in the Route Planner and then upload it to Suunto, the option for TbT in the Suunto App is missing.
-
@tuxbuster I think the reason is, that existing GPX files do not necessarily match to existing paths or roads. There is just no data basis on which any tool can decide where a turn is a turn.
To introduce turns, the app need to know if a road forks or has an intersection - this information cannot be applied to external gpx tracks that probably don’t stick to roads in the first place.I hope you can understand what I mean…
-
@Egika I see what you mean. The imported GPX is treated more like a static overlay rather than a natively planned route. For TbT to work, the Route Planner would need to ‘snap’ the GPX to the map and recalculate the path based on the map data upon saving. This is the only way the system can generate the necessary turn instructions.
-
The turn-by-turn guidance is not a standard in GPX files and Suunto uses a specific way of storing “turn-by-turn guidance waypoints” into the file. Other route planners may use a different way to store them. Thus it’s working between Routeplanner and Suunto app as they are using same way to mark them, but third party GPX files use different syntax or none. Recreating tbt into a GPX file that does not have it is not trivial as it requires rerouting the complete route. It can be done, but getting good quality tbt is really challenging.
