Using a bot for specific well know Suffix abbreviations only should be reasonably safe. IE never change ST to street if it is a prefix sort of rules.
Dale On Thu, Apr 8, 2010 at 12:23 PM, Richard Welty <rwe...@averillpark.net>wrote: > On 4/8/10 9:48 AM, Lord-Castillo, Brett wrote: > > One issue with using unabbreviated names, is sometimes the abbreviations > are part of the official name. > > Examples here: > > 1st Community CU Dr (First Community Credit Union goes to a -different- > address) > > River City Blvd/River City Casino Blvd; many people think the first is an > abbreviation of the former. It isn't, two different streets that will route > mail (and traffic) to two different sets of addresses > > St Louis Street, which is different from Rue St Louis, which is different > from Saint Louis Street and Saint Louis Boulevard, which is still different > from The Boulevard St Louis. In each of those cases, the non-type > abbreviations are part of the name and expanding the abbreviations can turn > them into different streets. > > > i don't think anyone would argue with this. it's why having a bot > rampage through > "fixing" things is probably a Real Bad Idea unless it's extremely well > thought out > and comprehensively tested beforehand. > > the thing i think most of us are arguing for is in cases where we know that > ST == Street, Rd == Road, Blvd == Boulevard, we should be storing the > full string, and treating abbreviations as a rendering problem. how we get > there is an implementation issue to be resolved. right now, i fix them > by hand > when editing in josm because the josm validator whines about it. > > richard > > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us >
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
