Several navigation issues (feedback)
-
One thing that is not actual navigation but very much related: In yesterday’s Race I loaded the course and started navigation without TbT just to be able to see where the route would be just in case. As I run through the finish point, I got a full screen notification that I reached the end of the course and had to dismiss this notification to be able to actually stop my activity tracking.
I think the upper button should have paused regardless…
-
Edit. I just realized joaquin’s photo I was referencing is comparing a Coros with Garmin, and that Coros does also have an offset, which seems even bigger than what is seen in Suunto.
Removed bad photo (of my post)
In those photos you see only a 3 meter offset with Garmin, but I’m finding many turns with much more distance offset with Komoot’s algorythms, as explained. Even something like 15 meters several times.
-
@dreamer_ I didn’t remove any photo or modify the post, so I’m not sure what you’re referring to.
As I mentioned before, turn notifications depend on the vector map data that generated that turn. Even when using the same map provider, you can still have different turn thresholds depending on the algorithm or routing engine used, as well as the map update frequency of each platform.
That’s why sometimes Garmin is more reactive, other times Suunto, and other times COROS. In any case, navigation remains perfectly usable on all of them.
These are simply normal differences and limitations across platforms.
-
@Joaquin said in Several navigation issues (feedback):
@dreamer_ I didn’t remove any photo or modify the post, so I’m not sure what you’re referring to.
As I mentioned before, turn notifications depend on the vector map data that generated that turn. Even when using the same map provider, you can still have different turn thresholds depending on the algorithm or routing engine used, as well as the map update frequency of each platform.
That’s why sometimes Garmin is more reactive, other times Suunto, and other times COROS. In any case, navigation remains perfectly usable on all of them.
These are simply normal differences and limitations across platforms.
The photo was removed by me, not you @joaquin . I misunderstood one of the photos and that’s why I corrected the post
-
@dreamer_ all clear
️ I didn’t understand what you meant.
By the way, it would be great if you were in Zegama, Val de Aran, Mallorca, or Andorra UTMB. It would be nice to meet you, and I’m sure we’d have a nice chat about GPS gadgets. -
@dreamer_ I did a quick test route in Madrid, in an area where I don’t usually run, created natively in each platform (Suunto App, COROS App, Garmin Connect, and Amazfit App) to avoid any inconsistencies coming from GPX imports.
For clarity, I’ll only show the first three turns. For example, COROS only generates one turn here (the third one).
As you can see, each platform interprets turns differently depending on their routing engine, vector map data, and turn detection thresholds.
Garmin & Suunto
Very close overall. In the first two turns, a slight advantage for Suunto in terms of reactivity, and on the last one, Garmin was slightly ahead.
-
COROS & Suunto
On the third turn, which is the only one COROS detected among the first three, it clearly triggers earlier. The turn is indicated when I’m still around 15–20 m away, as you can see in the track displayed on the map.
Amazfit & Suunto
Amazfit consistently triggers earlier on each turn. As shown in the images, the turn notification appears significantly before reaching the actual turning point.
Final conclusion
That said, YOU CAN PERFECTLY FOLLOW TURN-BY-TURN NAVIGATION WITH ANY OF THE FOUR WATCHES.
From my experience, Garmin and Suunto are quite similar in terms of turn reactivity and distance to turn when routes are created manually in their respective apps.
As mentioned, this will depend on the platform where the route is created, and of course your experience may vary. I’m simply sharing my tests across different locations.
We will of course continue working to improve this for all users, which is why this kind of feedback is very valuable. Thank you very much!
-
@Joaquin Looking at the watch photos - why does Suunto not pointing to the left next to the distance remaining in the 2nd and 3rd photo? It’s counter intuitive, isn’t it?
Race S
-
@2b2bff said in Several navigation issues (feedback):
@Joaquin Looking at the watch photos - why does Suunto not pointing to the left next to the distance remaining in the 2nd and 3rd photo? It’s counter intuitive, isn’t it?
This is the display, when the next turn is not within notification distance. Then it is basically a generic icon for this data field how far the next turn is.
I also think the actual direction could be shown in this state. No idea if this will come later. -
@2b2bff We don’t have a dynamic icon in the data field that shows the turning direction; we’re working on it, and it’s something I’d love to have. The correct turn signal appears after 20 meters.
