Hi all,<br><br>Two things:<br><br>First, thanks Mark, for a very useful suggestion. I need to think about it, but I think it has merit from the standpoint of streamlining the address assignment process, as well as keeping address points in sync with their associated streets.<br>
<br>Second, Richard, please see Carl's post which talks about the proposal from the standpoint of emergency services. Carl could likely say what the pros & cons are of splitting the tags vs loading everything in the addr:street tag.<br>
<br>Happy Thanksgiving, everyone,<br><br clear="all">-- SEJ<br>-- twitter: @geomantic<br>-- skype: sejohnson8<br><br>"Common sense is the collection of prejudices acquired by age eighteen." -- Einstein<br><br>
<br><br><div class="gmail_quote">On Wed, Nov 21, 2012 at 3:19 PM, Richard Welty <span dir="ltr"><<a href="mailto:rwelty@averillpark.net" target="_blank">rwelty@averillpark.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
ok, thanks, carl. this helps. i'm working on an emergency services related project<br>
right now and it's helpful to learn about these things.<br>
<br>
the next question is this. supposing we implement Steven's proposal, how does<br>
this help in emergency services mapping projects, that is, what does this breakout<br>
facilitate for us?<span class="HOEnZb"><font color="#888888"><br>
<br>
richard</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 11/20/12 10:05 PM, Carl Anderson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br>
<br>
This proposal is a good thing, provided that it does not deprecate current<br>
tagging uses.<br>
<br>
>From my experiences in emergency services (911), emergency management (FEMA<br>
and State/County EMA), and location finding I find that it is often very<br>
important to know what the colloquial core phrase of an address is.<br>
<br>
A "Colloquial core phrase" is something we all use everyday. We shorten<br>
names down to a useful, but still meaningful, core.<br>
If I were to say that I was at 14th and K, many of my DC friends would know<br>
that I was at the intersection of 14 St NW and K St NW.<br>
My friends who are not familiar with DC could guess the location given a<br>
bit of prompting.<br>
<br>
In easy cases it is easy to determine the "colloquial core phrase" of an<br>
address.<br>
Sometimes however, it is not easy to guess the correct local use for a<br>
street name or address.<br>
<br>
For instance my friends in Alpharetta, GA all know that North Point Mall<br>
Blvd is not the North version of Point Mall Blvd, but instead is the Blvd<br>
at North Point Mall. My friends farther away from Alpharetta, GA probably<br>
don't know this.<br>
<br>
Additionally, many times I have seen St. Lo Dr. mangled by well intentioned<br>
people into Street Lo Drive or once and a while into Street Lo Doctor. Of<br>
course Saint-Lô is is a well known place in France with a name derived from<br>
Saint Laud.<br>
Consider how often people mangle the intersection roads "Boulevard" and<br>
"Boulevard Drive" in Atlanta, GA. It is about even how well intentioned<br>
people convert both names into one of the two valid choices.<br>
<br>
Steven's proposal creates a mechanism for local knowledge and local<br>
colloquial use to be added into OSM. In turn this data, when present, will<br>
allow people who interact with the public to better understand the intent<br>
of the public in a more precise fashion.<br>
<br>
The parsing steps move the bits that are not part of the core into well<br>
known tags that can be unambiguously dealt with.<br>
The unambiguous aspect is equally important as abbreviation usage is often<br>
lossy. For instance some US jurisdictions use BL as an abbreviation for<br>
Boulevard and others use BL for Bluff. (In the emergency services world<br>
hilarity does not ensue). If OSM had such names as "Braided Blanket Bluff"<br>
in the proposed tagging scheme<br>
<br>
<br>
If we were to use the proposal as additional tags to the current existing<br>
tags people could add to OSM data to the limit of their local knowledge and<br>
when they knew the common local usage could, correctly, completely and<br>
unambiguously fill out the parsed tags that Steven has proposed.<br>
<br>
C.<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
<br></div></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Talk-us mailing list<br>
<a href="mailto:Talk-us@openstreetmap.org" target="_blank">Talk-us@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk-us" target="_blank">http://lists.openstreetmap.<u></u>org/listinfo/talk-us</a><br>
</div></div></blockquote></div><br>