There is a similar setting option for Navigation: route indicator improvements (Pro)
Is it really useful, to have separate settings for rerouting and for route indicator?
Is there any use case where the route indicator should have a different setting than the rerouting option?
I am afraid, that this would confuse novice users.
Why not simply inherit the route indicator setting from the rerouting option setting?
Just tested with a few “fake blocks” : the routing seems to be very reasonable. Helpful new function!
Tested using the “next unvisited waypoint” option with a few special scenarios to see what the behaviour will be. And I was really happy with it: I think now it’s unlikely that rerouting will mess up your route. Very good: if missing a waypoint due to a detour Kurviger still automatically omits it if getting near the next one. It’s just the behaviour I’d expect if being rerouted (and very convenient if being used together with the “skip next waypoint” function, like Tom already mentioned). Perfect!
But I’ve the same opinion like linux-user: maybe it would make sense to combine this option with the “route indicator” setting to keep things easy.
I would really appreciate if this feature will nevertheless be implemented in the future. Still would offer additional functionality.
I really like this new look. Especially the fact that the distance to the indicated point is shown. This helps to estimate your way even if not seeing the route at the moment.
Helpful. But I would really appreciate if this layer would also be available on Kurviger’s website. Gastronomy locations are also important while planning a rotue, not only for spontaneous stops during your roadtrip.
Hmmm - I don’t understand how to use that function. I looked up a location in Google Maps, copied the Plus Code and pasted it in the search field in the Kurviger app. Nothing happened. Also tried to use the “share” function but this also didn’t work. I think I’m doing something wrong. What would be the best way to import a looked up location from Google Maps directly into Kurviger?
I also had the feeling that the display refresh rate is a little bit slower than it was before (even on a Huawei P20 Pro). Maybe because I had actived the gastronomy layer?
All in all this a very valuable update. Thumbs up!
It works in search, write a (global) plus code, e.g. 7HQQ57WG+66.
Or if long press a point on map and in Share.
Share contains: OSM link, Plus code, what3words.
As mentioned in feature topic, Google Maps produce (local) plus codes (area name + local code), not the offline specification, it’s something different (see their documentation).
Local plus codes need extra work with online search for the area name.
It’s their own online implementation, usable inside their online ecosystem.
Third party apps need extra work just to be compatible with Google Maps.
Gastronomy layer contains too much content, that’s why all maps show such POI from a sufficient zoom (e.g. 17) to avoid hurting map performance. Currently we show it from zoom 15, cannot do it earlier and probably need to do it in larger zoom.
It’s like house numbers or vegetation layers, too much data needs large min zoom.
Short distances in avoid road block are usually more dependent on route geometry.
In example the 100 m are just after 1st turn, so routing may cannot use it for calculation.
Also important role plays the user direction, as cannot (re)route on a street backwards.
To demonstrate, I’ve stopped shortly before “Führholzerstraße”.
In the left (first) screenshot the next turn instruction is 160m away.
Kurviger could have used a route like e.g. in right (second) screenshot, but roadblock 100m doesn’t change route.
I can see if 100 m case can be improved. Though since all that depend on route geometry, cannot expect wonders for such short distances.
Current values came from forum discussion here, not sure if they’re the best.
500 m and more are far more reliable options in routing for avoid road blocks.