Several navigation issues (feedback)
-
@elbee yes, as explained above, it is not possible to obtain accurate turns with GPX, therefore the operation is exactly the same as SA.
-
@Joaquin said in Several navigation issues (feedback):
@elbee yes, as explained above, it is not possible to obtain accurate turns with GPX, therefore the operation is exactly the same as SA.
I understand. But importing a gps into komoot (or Garmin connect) can produce a fit file for the watch that contain TBT notifications, in opposite to Suunto app/website where importing a GPX cannot produce a fit file with TBT notifications.
It’s not a ‘not possible’, it’s a ‘not implemented’ (and I understand resources are limited, feature requests are plenty and choices have to be made)
-
@elbee These are different topics.
Komoot generates turn-by-turn instructions because it has its own routing engine and is a platform fully dedicated to route planning. In fact, its core value proposition from the beginning has been precisely to create reliable turn indications, so all its development is optimized around that.
In the case of sports watches, the approach is different. It’s not just about navigation, but a much broader ecosystem including performance metrics, battery optimization, sensors, etc. Replicating that level of accurate turn generation without a full routing engine behind is not trivial.
Garmin, for example, does not rely on pre-generated turns embedded in the route file. The watch itself generates turn instructions in real time based on its onboard maps. That’s why you don’t see turns included in the route itself, as they are calculated directly on the device during navigation.
Additionally, what you’re showing in the screenshot is exactly that behavior.
The “turn notifications” toggle does not mean the turns are embedded in the file itself. It simply enables the device to generate turn alerts during navigation based on its internal maps and routing logic.
In other words, the turns are not coming from the GPX/FIT file as predefined instructions. They are being calculated on the watch side, in real time, using the available cartography.
This is fundamentally different from platforms like Komoot, where the turns are precomputed by a routing engine and exported as part of the route.
With Suunto, when working with GPX files, you are limited to the track geometry, which does not contain reliable turn information. That’s why, to have accurate turn-by-turn guidance, the route needs to be created or edited directly in the Suunto App, where that navigation layer can be properly generated
BTW, IG that GPX route has turn-by-turn directions—Wikiloc, for example, has some routes with turns, Suunto app will show those turns or information waypoints.
-
@Joaquin said in Several navigation issues (feedback):
No brand, except Garmin, is truly providing reliable turn-by-turn navigation directly from a GPX file. Garmin can do this because it vectorizes the map data on-device and matches the track against a real path network.
In my experience of using Fenix 6 and Fenix 7 it is not how it works. What you describe might work if on device routing mode is used, but in reality nobody that I know ever uses it because it is super slow, glitchy, and half of the time can’t start a route, especially if the route is long.
The vast majority of people use the “Follow the course” mode which isn’t that different from how Suunto follows a GPX route - the map isn’t used for the most part for the navigation and exists there only for the context. The way Garmin does turn directions in this mode is y detecting sharp changes in the route direction. As of a couple years ago Garmin also cross references that against trail or road junctions on the map to avoid turn notifications at every zigzag of a trail, but they used to do that in the past. Still Garmin implementation often misses turn notifications if the turn isn’t sharp enough, for example of there is a Y shaped trail fork. Also, by the way, these turn directions are included in the map as special waypoints (Garmin calls them course points), but it seems that skipping of erroneous turn directions that are not at trail junctions is done on the watch.
-
@Joaquin I did not pretend a comparison but to expone some points (starting with the user experience, and that is very important) and explained why the Komoot workaround needs a very serious rework. The notifications while better than in Coros or Amazfit, are not accurate enough. This is like in the previous generation and it is very clear that work and investigation needs to be done.
Keep also in mind that I throughly tested all brands but Polar in very long trail runs.
Said this, the fork shot you post is a very nice example, since:
- It’s true Amazfit does not notify some forks
- It’s true Coros notifies forks as right-left turn. While Coros’ approach is not perfect, is somehow valid since keeps you in the path.
- It’s also true that the Komoot approach is not accurate enough, and this applies to all notifications of the whole track (not just and only the forks)
-And it’s also true that the Komoot workaround means the complicated user experience and that users are even forced to use a third party social network.
Even if some forks are left (in Amazfit but not Coros), what it happens in a very long trail run is that most notifications are just turns. Since with the Komoot algorythms It seems there’s an offset being the notifications not good enough, the feeling (for the whole trail run) while better with all the notifications, is less accurate. And this is important to note and should not happen.
But there’s something that has changed in Amazfit in the very last month (I don’t think they have still fixed those forks thought). The thing is I tested very recently the T-Rex Ultra 2 (not the T-Rex 3 Pro) and the navigation is incredible improved this very last month (as said, there don’t notify forks or roundabouts yet and there were some few forks left, like the one you show but with the T-Rex 3 Pro).
In my opinion they have rewritten everything. And the explanation is that they finally managed to add the routeable thing I was explaining. Have a look at this : https://youtube.com/shorts/jGDmJTFyGwk (there’s an english audio track) . This is the very last month, and there’s even a new update improving that.
I’m posting this, not to explain the routeable thing but to say they finally found a way to make everything A LOT more clever. So yes, in my opinion, this means they changed completely their turn-by-turn implementation (or my impression is that is greately improved). Now they are here, they are very likely fixing the remaining things very soon.
Again, this is not a comparison at all (personally, I don’t have now that Ultra 2 watch and I don’t recomend their watches at all because the so many bugs and issues), but what I mean is that their navigation at this moment, is a lot better that we could think just looking at those shots in a very concrete scenario.
I also had tested the Coros Nomad 2 months ago, and while I don’t like Coros navigation, their turn-by-turn are working perfectly fine, even if you change your direction (they only notify left and right turns)
As said, I’m here because Suunto is superior in many things. Triathlon now excels and navigation, while not perfect, I feel like maps are super fast and very good. But Komoot’s algorythms are not good enough (and the user experience is not either the best) and this should be noted because the Komoot approach is convoluted and is not good enough.
-
@dreamer_ I’m simply trying to explain why Suunto does it this way, I think it’s good to understand why things are done this way.
And super thanks for the feedback
-
@Joaquin said in Several navigation issues (feedback):
Garmin, for example, does not rely on pre-generated turns embedded in the route file. The watch itself generates turn instructions in real time based on its onboard maps.
That is not my experience. My forerunner 935 didn’t have maps only breadcrumb, but I do get TBT notifications if I imported a route via Garmin connect. Some goes for the forerunner 965 I had before my current watch. If I selected a route I did get TBT, but if I selected “follow the route in opposite direction” I didn’t get TBT notifications.
Also, I once didn’t load a map for an area on my forerunner 965 but still got TBT notifications (althought the screen only showed a black background and a breadcrumb to follow)Maybe that changed in the last year.
-
In my opinion, on‑watch routing is highly overrated. And sometimes it can be really dangerous – in higher mountains, for example. It’s slow, unreliable, and on a tiny watch screen, you can easily miss potential errors in an automatically generated route.
SuuntoApp is missing one pretty obvious feature. When you import a GPX file, it should ask – the way Komoot does – whether you want it to redraw and analyse the route (adding missing elevation, turn‑by‑turn directions, etc.), or just import the original GPX file without any changes, like it does now.
-
@maszop this is good improvement/feature
I’ll pass this on to the team in case we can do something about it in the future.Super thanks!!
-
@Joaquin Thanks. Komoot does that mainly for staying on roads and trails, whereas with Suunto it would be more about adding missing elevation and TBT.
From what I’ve seen, only Komoot (online) – using the phone’s computing power – can generate a logical route.
Garmin is just okay at best. The Hammerhead Karoo is pretty weak. Google Maps, apart from driving, is rubbish. Mapy . com is okay at best. And I’m mostly talking about using the phone’s processing power and usually having an internet connection.So I don’t know if it’s worth putting so much effort and resources into adding routing to Suunto watches, knowing it’s going to be very unreliable, except maybe in cities.
-
@dreamer_ I think there might have been a small misunderstanding, so just to clarify my point.
I was simply referring to the brands you mentioned as examples, not trying to say one approach is better or worse. Each brand has its own philosophy, and this is just ours.
Of course, we are actively working towards improving things like GPX-based turn guidance or routing directly on the watch, but we want to do it in a way that we believe is robust and reliable for the user. That’s why, for example, offline maps in the app combined with routing to the watch is part of what I’d call the “Suunto way” of building a routable map experience.
I really appreciate your feedback and the level of detail you’re bringing to the discussion. It’s genuinely valuable for us
️
