I basically agree with Mike<br><br>A couple of links for reading relating to this discussion. (Several are PDF's)<br><br><a href="http://www.co.larimer.co.us/streets/rules.htm">http://www.co.larimer.co.us/streets/rules.htm</a><br>
<a href="http://www.ltg.gov.vi/GIS_2010/usvi_street_naming_project_guidelines.pdf">http://www.ltg.gov.vi/GIS_2010/usvi_street_naming_project_guidelines.pdf</a><br><a href="http://flathead.mt.gov/gis/documents/Conventions.pdf">http://flathead.mt.gov/gis/documents/Conventions.pdf</a><br>
<a href="http://www.mlgw.com/images/StreetNamingGuidelines.pdf">http://www.mlgw.com/images/StreetNamingGuidelines.pdf</a><br><a href="http://libraries.maine.edu/Spatial/gisweb/spatdb/gis-lis/gi94040.html">http://libraries.maine.edu/Spatial/gisweb/spatdb/gis-lis/gi94040.html</a><br>
<a href="http://www.cravencounty.com/documents/RoadNamingOrdinance.PDF">http://www.cravencounty.com/documents/RoadNamingOrdinance.PDF</a><br><br>Reading a few of these...<br>These are guidelines for NEW names, and old existing names can be and are a mess in some places.<br>
I do not think there is any sure fire way to deal with the names due to the older ones that did not follow such conventions. Because of this any thing presented must be guidelines, and clearly state that not all roads will clearly fit them. They should probably be based on the newer naming conventions, and anything that does not fit should all be left in the base name.<br>
It seems clear that directions do convey meaning such as which part of a long road, and that they are part of the name as much as road or street is.<br>The full name should be broken up into components. Applications using the databse can decide how much and how they will make use of that information. Such as abbreviate, or drop directionals.<br>
<br>What locals use can be placed in another tag if it differs from the official name, but should not be the primary name in the database. Local governmental standars do affect how we try to break up the names, but not how locals (as in along that street) use the names.<br>
<br><br><br><div class="gmail_quote">On Mon, Aug 23, 2010 at 3:59 PM, Mike Thompson <span dir="ltr"><<a href="mailto:miketho16@gmail.com">miketho16@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
You have caused me to do some real thinking and digging on this<br>
subject. I think this debate is good, and will lead to better OSM<br>
data in the long run.<br>
<br>
I think the "rules" should be replaced with the following "guidelines".<br>
<br>
If the directional is on the street sign, this is a strong indication<br>
that it should be part of the name. Pre-directionals are included in<br>
at least some street signs in Columbus Ohio, but not in SLC. Note,<br>
the size of the font does not mitigate the fact that they are on the<br>
signs.<br>
<br>
If official local government sources use pre-directionals, this is<br>
very strong indication that they should be part of the name. The<br>
Franklin County Ohio (where Columbus is located) Highway engineer<br>
includes directions in some cases on their maps. Note "E. North<br>
Broadway" and "W. North Broadway" on the following map:<br>
<a href="http://www.fceo.co.franklin.oh.us/Map-Atlas%20Pages/map_19.PDF" target="_blank">http://www.fceo.co.franklin.oh.us/Map-Atlas%20Pages/map_19.PDF</a>, but<br>
not all. Note "W Broad St" in this map from the same source:<br>
<a href="http://www.fceo.co.franklin.oh.us/Map-Atlas%20Pages/map_27.PDF" target="_blank">http://www.fceo.co.franklin.oh.us/Map-Atlas%20Pages/map_27.PDF</a>. Also,<br>
the Franklin County Auditor often uses directionals in their property<br>
database, although not consistently.<br>
<br>
If local residents and businesses _ever_ use directionals when talking<br>
about a street, this is an indication that it should be part of the<br>
name (I think we agree on this one).<br>
<div class="im"><br>
>> A test that I have not heard mentioned here is whether the directional<br>
>> appears as part of the building/house number on the sides of buildings<br>
>> (e.g 1705 W). If it does, we know for sure that it is part of the<br>
>> building number, and not the street name and it can safely be removed<br>
>> from the street name.<br>
> That will hardly every apply.<br>
</div>A very good indication that pre-directionals should not be removed<br>
from the name tag outside of Utah. A city style address consists of a<br>
building number, and a street name (we are not concerned here with<br>
city state or zip). If the directional is part of the complete<br>
address, it must be either part of the building number, or the street<br>
name. If is not on the front of the building with the building<br>
number, then it must be part of the street name.<br>
<div class="im"><br>
<br>
> Again you are taking that test too literally.<br>
</div>"Tests" are to be taken fairly literally. With these "tests" in the<br>
proposal, a new mapper may easily get the impression that in OSM<br>
pre-directionals are almost always to be removed from the name tag.<br>
<div class="im"><br>
> This test will fail in Washington DC and other places where the<br>
> directionals are really needed.<br>
</div>The point should not be just whether directionals are needed, but<br>
whether they are regarded by local residents, businesses, and<br>
government officials as a part of the name. This should be evidenced<br>
by signage, official local government documents, and local usage<br>
(again, I think we agree on this final guideline).<br>
<div><div></div><div class="h5"><br>
_______________________________________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Dale Puch<br>