-
-
Notifications
You must be signed in to change notification settings - Fork 996
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display C (Straight) instead of KL (if it's uniquely determined) #15559
Comments
IF we reproduce we need to make small map example to test and fix it later |
I can't see any live updates within the app... |
Please also see #13383 (comment) |
thank you for working on this! If you need more test cases, here are the ones I came across. Let me know if I can help with 🛰️GPX tracks, 📱screenshots, 📷mapillary images etc. I have checked the underlying osm data in these locations and it seems correct. 1. Tübingen Reutlinger Straße 2. Autobahn A3 Limburg Süd 3. Köln Aachener Straße I think this is a rather significant issue, because the prompts are not just a bit ambiguous but factually incorrect and will lead to users making incorrect turns even though the calculated route was correct. As I said, please let me know I can help you resolve this, I'd be more than happy to assist! |
🐞 routing report
Routing engine
Routing Profile
CAR
Start and end points
Schweizerhof, Abzweigung Jostal
https://www.openstreetmap.org/#map=17/47.98066/8.14132
Following street direction from west to east
Actual and expected routes
This is a real screen shot!
The voice announcement is misleading "links einordnen" ("get left") like shown in the top left of the screenshot, but should be like it is at the exact same time(!) correctly shown in the top center. So there should be no announcement at all as it's just following the normal road in the normal direction straight forward. So the screen-navigation (top center) looks correct but the voice navigation says at the same time misleading things (top left).
Is this a regression?
No, it's the same problem for months as it was(?) an error in the map data on openstreetmap.org. I (tried to?) fix it there around July/August(!). It does work with all the navigations on openstreetmap.org for months, but the misleading voice announcement keeps persisting even with the September and current October update of the map data. And even by showing it correct in small in the top center of the screen.
🌍 Your Environment
OsmAnd Version:
Device and Android/iOS version:
Google Pixel 4a, Android 13
Maps used (online or offline):
Deutschland Baden-Württemberg 01.10.2022
Anything else relevant?
It happened on numerous other places before, that I changed an error or even couldn't find any error in the openstreetmap.org data. The navigation on openstreetmap.org even worked correctly and as expected, but the OsmAnd voice routing kept even after monthly updates saying the wrong misleading things.
In the OsmAnd descriptions I found so far only the hint, it's using openstreetmap data for navigation, but obviously it doesn't (at least not the current downloaded one).
So how to get OsmAnd using the current downloaded offline data for voice navigation?
And if this on purpose, couldn't at least somewhere easier to find be a hint what data is used for voice navigation and when and how it gets updated?
The text was updated successfully, but these errors were encountered: