Tagging with abbreviated names is tagging for the renderer. The database should be as unambiguous as possible, and the renderer should apply local abbreviation conventions.
This is "not the way anyone ever writes street names here in DC", you say. But it's the way people in DC pronounce it, which is what a navigation system or an audio map for blind users would do. Our database isn't just used to render images. "The renderer can use rules to de-abbreviate", you will say. It gets complicated for ambiguous abbreviations — is St Saint or Street? On 23 Mar 2012, at 13:47, Lynn W. Deffenbaugh (Mr) wrote: > IMHO, here in the US we have the USPS which has published standardized street > naming conventions specifically using the abbreviations. It would seem to me > that these "official" street names are what should stick and the expansions > of them should not be happening. Not to mention how much more crowded the > map labels would become. > > Lynn (D) - KJ4ERJ > > On 3/23/2012 8:36 AM, Mikel Maron wrote: >> Hi >> >> User chdr (http://www.openstreetmap.org/user/chdr) seems to be running a >> script to automatically replace street name abbreviations with the full word. >> so 1600 Pennsylvania Ave NW becomes 1600 Pennsylvania Avenue Northwest. >> Which is not the way anyone ever writes street names here in DC. >> >> Anyone else aware of this? Opinions? Should this be stopped? >> >> -Mikel >> >> * Mikel Maron * +14152835207 @mikel s:mikelmaron >> >> >> _______________________________________________ >> talk mailing list >> >> talk@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/talk > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
