[EN] I think I have found an issue with the route calculated by Kurviger
[EN] I read the corresponding [documentation]
[EN] Here is a url to a short example (<10km) that shows the issue:
[EN] Description of the issue and how it should work instead:
The route should go directly as it does when routed on OSM: OpenStreetMap
What else can I look at to make sure this routing is allowed in Kurviger?
Your edit is just 15h ago. Wait until Kurviger updates its database.
Just a quick info for everyone waiting on daily routing updates, the update cycle can be delayed over the next days / weeks as we are updating a few things. Routing data should not get older than a week, if everything works as expected.
We will be returning to continuous daily updates ASAP.
Kurze Info, die Routing-Daten können über die nächsten Tage und Wochen immer mal wieder ein paar Tage hinterher hinken. Die Daten sollte aber eigentlich nie älter als eine Woche werden.
Wir werden so schn…
You can check the date of the routing table in the menu. Date is than displayed at the bottom.
Thank you! I didn’t know I can check the time. I’ll wait and see if it updates.
However, the only change I made was add the specific tags (foot, motor vehicle, etc.); the “Allow Access: All” was already set to yes, that’s why I posted.
I will wait a few days and hopefully it’ll change.
If in the middle of planning and not able to wait few days I in such case take the new “beeline”-function and can go on with my route …
In parallel, I can correct the OSM data and check the action a few days later.
Thanks! I didn’t know that existed, but I think it’s only for “Tourer” level sub. I have the “Pro” and don’t see that option anywhere in the interface.
No, it wasn’t.
The display in OSM-editor is a bit misleading here.
If nothing is set, it shows “yes”, which is true for public roads as “yes” is the default here.
But not for barriers like gates. There access must be explicitly set, otherwise Kurviger won’t route.
Aha! Thank you so much! learned something new. We have lots of these here, so definitely good to know!
Unfortunately, I don’t know if your “Pro” refers to Kurviger Pro (version 1.x) or Kurviger (version 2.x) with subscription.
You can see what is possible with the different versions in the features comparison. May help you in some situations.
I have the Kurviger Pro android app version that was purchased with a one-time payment, but without the subscription. And since I don’t see a “beeline” option when building routes, I am guessing that option requires a sub.
The straight line route profile with many other
is available in Kurviger 2 with a subscription:
There you are right (as you can see in the linked Features comparison).
Kurviger Pro 1.x and Kurviger 2.x (pro with subscription) can coexist on the same device without interference.
Subscription is free for the first week.
Android 12 introduces some difficulties:
“… if the apps can resolve the exact same domain host and path, as might be the case with lite and full versions of an app, only the app that was
installed most recently can resolve web intents for that domain.”
Thanks for the hint. Is added in the Features comparison now.