Recently I made changes to a road trying to prevent OsmAnd from saying “keep left” where I believed it was confusing.
Was hoping turn:lanes and some more accurate turn restrictions on parts of the road would clear this up. But as of now OsmAnd says to turn left to stay on the current road when east bound and the original reason I made the changes is still there.
All the info I’ve looked up doesn’t indicate to me anything I’ve done wrong and is leaving me confused. Does anyone have any insight into how I can correct this?
Don’t map for the renderer. If OsmAnd doesn’t handle it correctly, complain on their issue tracker.
Are you able to confirm that my changes were correct and that OsmAnd is at fault here? I don’t think complaining to OsmAnd devs is the correct move here, at least not until I have determined my changes were not erroneous.
I have no clue about the whole problem, but I looked at what I think is the first issue where it looks like it tells you to turn left where the sliplane splits to go right into the shred right parking lot.
My guess is that turn:lanes is supposed to be tagged immediately before the intersection it applies to, and since the turn:lanes are tagged on the way before the sliplane attaches, it’s applying left|none|none to the sliplane junction, where it sees 2 outgoing ways and applies “left” to old Shakopee (going straight) and probably “none” to the sliplane. I would try removing the turn:lanes from the old Shakopee section before the sliplane but keep it on the way that is actually connected to the main intersection there.
I also noticed that there is a turn restriction for coming out of the shred right sliplane entrance and then turning 180° to go eastbound on Shakopee. Since that sliplane entrance is one way, I don’t think that turn restriction is necessary or really helps, and it might be confusing to osmand. Without that turn restriction, I don’t think it would be necessary to have the old Shakopee split into 2 ways before the sliplane and after up until the intersection, so merging those 2 segments of old Shakopee (immediately before the sliplane entrance to shred right and up until the intersection itself) might simplify things.
So I guess that’s 2 ideas that I think might fix the issue. Hopefully that works and can be applied to some of the other issues, I’m not sure about the intersection itself, I’ll have to look at it closer later.
Edit: on second thought, I think the convention is to have turn:lanes marked whenever there are turn markings on the asphalt, so I would suggest removing the turn restriction on the sliplane and merging the 2 ways on either side of where the sliplane connects - I think that way it maybe won’t try to apply the turn:lanes to the sliplane since it won’t be attached to the end of a way with turn:lanes but in the middle (I’m guessing that’s how it works). Removing the turn:lanes on the west section I think would go against the wiki guidelines. If it was necessary to have 2 segments for shakopee then a hack would be to attach the sliplane a few feet before or after where the 2 segments of shakopee join, but that shouldn’t be necessary here.
I will try these changes. Thank you for your time and advice. :)
No problem! I don’t really do much road mapping so I’m still figuring it out, I do mostly just sidewalks and parking lots, but I’m noticing some intersections near me also have some messed up lane configurations.
Another thing that might help is ab-street, if you download the desktop version you can import an area using an overpass query and view it using the viewer program bundled with ab-street, and it lets you click on segments and view where the turns connect from and to. It might not be 100% accurate but it’s another thing that helps to debug. I found that a road near me shows up in ab-street with the wrong number of lanes which pointed me to an issue.
I had the same issue, I assumed it was a topography error.
I dont have this issue with Organic Maps
