Suunto Routeplanner
-
@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…
t6, S6, Elementum Terra, Ambit 3 Sapphire, Spartan Ultra Copper, Traverse Alpha, S7 Graphite LE, S9B Ambassador, S9P Granite Blue Titanium, S9PP Titanium Sand, Vertical All Black, Race Titanium Charcoal, Race S All Black / Titanium Courtney, Run Lime
-
@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.
-
@kemetter said in Suunto Routeplanner:
The turn-by-turn guidance is not a standard in GPX files
Not standard in GPX files but there is a Garmin standard for route FIT files. Perhaps Suunto could adopt that.
Basically, turn directions are stored as route waypoints with special waypoint codes.
Some route editors like PlotARoute are capable of inserting turn direction and saving the route as a FIT file, and that works correctly with Garmin watches.Suunto: Ambit, Ambit 3 Peak, 9 Baro, Race S, Race Ti
Garmin: Forerunner 210, Forerunner 610, Fenix 6X, Fenix 7X Ti -
@sky-runner The problem is that GPX is an open standard. FIT is a proprietary format that Garmin currently allows others to use.
-
@Egika said in Suunto Routeplanner:
@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.
Komoot kan add tbt notifications if you upload a gpx to their app (and sync it to suunto). The garmin connect can also do it. But you cannot sync that to suunto (nor does garmin a particular good job. You get tbt alerts that are just bends in the road)
-
@elbee said in Suunto Routeplanner:
@Egika said in Suunto Routeplanner:
@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.
Komoot kan add tbt notifications if you upload a gpx to their app (and sync it to suunto). The garmin connect can also do it. But you cannot sync that to suunto (nor does garmin a particular good job. You get tbt alerts that are just bends in the road)
Like said, it can be done but quality will most likely be bad, meaning you will get either too many or too few turn instructions.
-
@sky-runner said in Suunto Routeplanner:
@kemetter said in Suunto Routeplanner:
The turn-by-turn guidance is not a standard in GPX files
Not standard in GPX files but there is a Garmin standard for route FIT files. Perhaps Suunto could adopt that.
Basically, turn directions are stored as route waypoints with special waypoint codes.
Some route editors like PlotARoute are capable of inserting turn direction and saving the route as a FIT file, and that works correctly with Garmin watches.So does Garmin use FIT to store routes? But they don’t store their TbT into GPX files?
