Agreed, these databases all have different rules for their own purposes. The USPS prefers spaces but allows hyphens. The MUTCD prohibits signposting the “Lp” abbreviation that TIGER insists on. If it’s still a tossup even after considering the underlying reasons for a discrepancy, such as a blatant mistake, then pick one spelling to go in name=* and the other to go in alt_name=*.
In general, I prefer to put the less austere spelling in name=*, since it communicates information that a user or data consumer might miss otherwise. For example, TIGER lists this street’s name as “E BUSINESS WAY”, with “E” as the directional prefix. Many maps and navigation systems therefore expand it to “East Business Way”, but in fact the street’s name is supposed to be “E-Business Way”, as in electronic commerce. Similar confusion can arise due to a missing period after the middle initial of a personal name. (Let’s go to Chuck East Cheese’s today!)
The stakes are considerably lower for alt_name=*, which can hold multiple values separated by semicolons. I wouldn’t flinch at seeing alt_name=Bob O Link Drive;Bobolink Drive, though if one feels strongly enough about it, there’s always not:name=Bobolink Drive.
Wherever the signs on the ground are inconsistent, I also map the signs themselves as street name sign nodes. This explains my tagging choice to mappers who come along later, discouraging them from naïvely undoing my work based on one source or another. In the past, I’ve even been able to stop slow-motion edit wars by mapping these signs.
I’ve mapped one of the stop sign assemblies at the intersection with Sperry Street so you can see what this might look like in your case. There’s still ongoing debate about some aspects of traffic sign tagging, but the point of this exercise is simply to show your work, so it doesn’t have to be perfect.
2 Likes
