Proposal talk:House numbers/UnitedStates

Two things: the description of "Street type" is unclear (it seems to include some full street names as well as types), and the location of the street type is ambiguous; in the Southwestern US and Quebec, you'd find streets where the street type precedes the name (e.g. Calle Del Norte or Rue Ste. Marie).

Suffixes are also sometimes found in pairs or more; for example, Marion County Florida has many diagonal streets named with patterns like "X Place/Street/Avenue/Court Road" and an entire development is full of streets named "X Trace/Course/Trail Circle/Way/Court," where X is a name of a tree (see zip 34472 for the latter form). Another example: alleys in downtown Macon, GA are named things like "X Street/Avenue Lane." --Lordsutch 01:43, 18 November 2012 (UTC)

• I don't see what this proposal is trying to achieve. Why break up the street name into sections? Why do you need to know it is an avenue rather than a street? The street name is the name. "Dansom Lane South" is just the name of a street, being a lane or the southern part makes no difference and is not worth recording separately. Making the addr:street tag NOT use the displayed name of the road is a terrible idea since that is not what is used in most of the rest of the world. One thing this proposal does very well in increase the complexity. That will put off newcomers and thus harm OSM - we need all the mappers we can get. Chillly 18:30, 19 November 2012 (UTC)

include it in the street name

Street types are very common as part of the street names and splitting this in different tags would be a major change to the current scheme, for what benefit? The same also applies to prefixes like "old" or "new" which are usually considered to be part of the name (at least in here). I can't see a really good reason to change things now by splitting the street component into several semantic parts. --Dieterdreist 09:51, 19 November 2012 (UTC)