As shown on this map, there is a road called NE Elam Young Parkway which meets NE Cornell Road twice. On the westside intersection, it is labelled as “NE Elam Young Pkwy West”, and on the eastside it is labelled as “NE Elam Young Pkwy East”. However, on other street signs, it simply says “NE Elam Young Pkwy”, with no indication of east or west. I don’t want people using routing apps to be confused by this and turn onto the wrong road. How should I tag the road? Should I use a node at the intersection saying whether it’s East or West?
Best to use good name keys:
• name for on the ground name
• official_name for official names
• loc_name for local names
…
@R0bst3r Did you mean something like this?
Oh hey, I got my diploma on that street, and worked across the street from there!
The address numbers have Elam Young running east-west parallel to Cornell Road, not perpendicular to it, so there’s no ambiguous addresses that would necessitate disambiguation. Furthermore, the parkway’s only six blocks long with its ends only two traffic lights apart. Any reasonable router’s going to see that and pick the best route regardless of name, and any reasonable driver’s going to consider missing one end of the loop a second chance junction anyway (no u-turns at controlled intersections in Oregon).
My vote is for no change in this instance.
In that neighborhood, it seems unlikely that only the first 200 feet or so of the street would have an “East” or “West” in the name, only for that word to disappear as soon as the little entrance median disappears. If no signs or addresses include this directional suffix, I guess you were hoping to disambiguate the intersections manually. But turn-by-turn navigation applications could disambiguate it anyways by telling the user the distance to the next turn or, better yet, the number of blocks or traffic lights to the next turn.