Indeed, if the problem is in map data, then the solution is to update the map.
Anyone can learn to do it, see for example https://learnosm.org
If you go that route, feel free to ask for help when you get stuck. Or you can leave a Note when you notice situation on the ground is not correctly represented on the map, and hopefully someone will fix it.

I see several possible causes:

  • data in OSM might be mapped incorrectly, e.g. routers will behave differently if it is mapped as one road with another forking from it, or if they are mapped as two different roads. In this case it some volunteer to fix it;

  • the map that OsmAnd shows, and the map OsmAnd uses for routing are different (OsmAnd is very powerful, but also very complex. E.g. you can use online maps for display which are very fresh, but it will use downloaded offline map for routing, which generally only updates once a month and requires you to remember to update it manually. Or it can use external routers with their own freshness policy, etc. If you’d like to try something simpler than OsmAnd, or want to check how alternatives behave, I’d recommend Organic Maps)

  • everything is mapped correctly and up-to-date, but OsmAnd app itself is not recognizing it should give a warning at that specific point. Then it is an OsmAnd issue, which can only be fixed there.

As far as I remember, OsmAnd uses that wording only when entering and exiting a roundabout, not on regular road splits. Can you give us exact point on the osm.org map where it happens (use share button with include marker enabled)? Along with instructions from which point to which point are you going when it doesn’t warn you? That way, we might be able to say which of the 3 possible causes above is the culprit.

6 Likes