<div dir="ltr"><div>When mapping things, I have typically been putting name or alt_name on numbered roads to match what is in addr:street. I look at businesses along the road to see how they refer to their address and also the USPS zip code lookup tool to see the USPS standard format for the address. The value that goes in addr:street has abbreviations expanded, converts from upper case to title case, and may include directional prefixes and/or suffixes.</div><div><br></div><div>So, you have something like "Route 6" in addr:street, but it could have
easily been something else like "Highway 6", "State Road 6", "State
Route 6", "Massachusetts Route 6" "South Highway 6 Northwest". Only one of these forms is the standard form for that particular address.<br></div><div><br></div><div>The USPS has a page listing standard variations on numbered routes as part of addresses:</div><div><br></div><div><a href="https://pe.usps.com/text/pub28/28apf.htm">https://pe.usps.com/text/pub28/28apf.htm</a></div><div>(Interesting that USPS prefers to sometimes abbreviate ROAD as RD and sometimes prefers unabbreviated)</div><div><br></div><div>For me, the different ways of naming the numbered route is significant enough to warrant adding it as a name or alt_name to the Way for the road itself.</div><div><br></div><div>Peter<br></div><div><br><div class="gmail_quote"><div dir="ltr">On Sun, Aug 19, 2018 at 5:29 PM Greg Troxel <<a href="mailto:gdt@lexort.com">gdt@lexort.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
[Alan and I have had a big conversation off list; following up a bit here]<br>
<br>
"Alan & Ruth Bragg" <<a href="mailto:alan.ruth.bragg@gmail.com" target="_blank">alan.ruth.bragg@gmail.com</a>> writes:<br>
<br>
> "The Great Road" is the official name of the main drag in Bedford. Street<br>
> signs are inconsistent, some say "Great Road" others say "The Great Road".<br>
> The MAD street addresses are "Great Road"<br>
> I have set OSM name="The Great Road" and alt_name="Great Road"<br>
><br>
> I'm hoping the GIS data manipulation software could be set to look at both<br>
> name= and alt_name=?<br>
<br>
Certainly, if we have a import processing requirement that the<br>
addr:street field in an address much match a nearby road, then we should<br>
probably consider it a match if it matches one of the alt_names.<br>
<br>
However, the point of matching is to look for things that are perhaps<br>
wrong, as part of our duty to ensure that the import is very high<br>
quality. addr:street matching an alt_name is at least somewhat<br>
irregular, so we probably should be looking at those cases and asking<br>
"is this actually right?".<br>
<br>
In this case, your explanation is quite convincing, and I believe this<br>
is a case where the official street name and the addr:street in<br>
addresses are not the same. And alt_name is appropriate because the<br>
variants are 1) actually names and 2) used to name the road in a<br>
semi-formal or better sort of way, separately from talking about<br>
addresses.<br>
<br>
> alt_name is explained here <a href="https://wiki.openstreetmap.org/wiki/Names" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Names</a><br>
><br>
> Alternative name by which the feature is known. If there is a name that<br>
> does not fit in any of the above keys, alt_name can be used, e.g.,<br>
> name=Field Fare Road and alt_name=Fieldfare Road, or name=University Centre<br>
> and alt_name=Grad Pad. In rare cases, the key is used for multiple<br>
> semicolon-separated names, e.g. alt_name=name1;name2;name3, but this usage<br>
> is not preferred.<br>
<br>
If the *road itself* is actually known by an alternative *name*, then<br>
alt_name makes sense. That leaves out two cases where I think alt_name<br>
is inappropriate:<br>
<br>
road is not known by the name, but addresses use it. (I think "State<br>
Highway" for US 6 is one of those cases.)<br>
<br>
The alternative reference is not actually a name, such as "Route 6",<br>
which is a way to represent the information stored in a ref tag.<br>
<br>
In the second case, if we can validate that "3850 Route 6" is a<br>
legitimate address as recognized by the local people, local government,<br>
USPS, etc., then I think it's fine to consider that a match for QA<br>
purposes. But we should not put "Route 6" in an alt_name tag; that's<br>
just spamming the database with something that's already there as<br>
"ref=US 6".<br>
<br>
Plus, adding an alt_name of Route 6 fails the OSM general test of "would<br>
we do this for correctness, if we weren't thinking about an import". So<br>
adding things that don't belong in the name of the import breaches our<br>
duty of import quality.<br>
<br>
> On the Cape hundreds of MAD addresses use the route number for sections of<br>
> MA and US highways.<br>
> Route 6 for OSM "Grand Army of the Republic Highway",<br>
> Route 6A for OSM "Cranberry Highway",<br>
> Route 130 for OSM "Forestdale Road",<br>
> Route 28 for OSM "Main Street"<br>
<br>
These are all in ref tags. (Interesting that two are US and two state,<br>
and they are written the same way -- but addressing authorities do what<br>
they do and ours is to record not challenge.) I think we can deal with<br>
this by having a table of pairs of addr:street and ref that are<br>
considered matching (and thus evidence of non-broken addrs) for QA<br>
purposes. That is the purpose of the matching -- to guard against bad<br>
data, not because there is some rule that addr:name and the way name tag<br>
have to be the same.<br>
<br>
<br>
<br>
Finally, there was some earlier notion that some navigation program does<br>
not find addresses if addr:street and a way's name tag don't match. Two<br>
thoughts:<br>
<br>
we should (and I will) dismiss this as speculation until we have real<br>
data<br>
<br>
programs that behave this way are broken, because there's nothing in<br>
the real world stopping street naming authorities and address<br>
authorities from being inconsistent. And we have ample evidence<br>
already of actual inconsistencies (the Route 6 cases, (The) Great<br>
Road, and the north/west woodlawn(?) case).<br>
<br>
which means I think it's ok to import data when addr:name and a way's<br>
name tag don't match -- as long as we have examined it and believe both<br>
to be correct.<br>
_______________________________________________<br>
Talk-us-massachusetts mailing list<br>
<a href="mailto:Talk-us-massachusetts@openstreetmap.org" target="_blank">Talk-us-massachusetts@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-us-massachusetts" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk-us-massachusetts</a><br>
</blockquote></div></div></div>