|
If a state highway has no street signs, does the 'on the ground rule' dictate that it has no name? What if official government data lists the name on both the road itself and all of the addresses along it as "Highway XYZ"? This makes sense, but I don't know if this is something that was decided by the community or if someone just made this up and added it to the wiki. Whoever added this must not have noticed that the entire Interstate system and most US/state highways do not follow this rule. I'd imagine that to data consumers, consistency is more important than technicalities like what constitutes a name. What if the software doesn't read the network/ref tags? The road would just be called 'unnamed road'? One could argue this is a software bug and not a data issue, but I don't see any harm in adding a name to avoid it. Should the route relation and/or road segments be tagged with a name? |
|
You should only ask one question at a time, thanks. The on the ground rule just requires something to be reasonably verifiable for an OSM contributor, on the ground at the location. That could easily be by determining the name of a road by asking locals, or deriving it from an address on the road, a street sign is simply the easiest way of determining a name. It is not clear what your other questions are, but yes simply duplicating the ref to the name field is not really necessary and all reasonable applications will check both, particularly for major roads that might not have a "name". |
