|used to connect streets with houses, for addressing purposes.|
|Status: in use|
|Tools for this tag|
associatedStreet relations have been used by some mappers as an alternative to addr:*-Tags.
Using relations to associate addresses and streets
|type||associatedStreet|| use |
|name||streetname||optional but recommended|
|name:xx||streetname in xx language||optional|
|addr:suburb||suburb name||should be used only in case if there 2 or more streets with the same name in the same city/town/village/etc. Otherwise, don't use this tag|
According to Taginfo, as of 26th January 2015 there are 3 567 496 "house" members of type=associatedStreet relations, and 44 330 243 uses of addr:street=*. This means that 7.4% of address objects are included in an associatedStreet relation.
This is 5th most used type of relations .
The community is divided over the future of this relation. An informal vote in 2015 yielded a 49/50 for/against deprecation.
Incomplete/wrong data due to JOSM's Terracer Plug-In
There are probably thousands of associatedStreet relations without a street member due to a previous default setting in JOSM's Terracer plugin: Each time a new relation was created with the newly separated parts of the original building as members, but NO street is added automatically as member to that relation. The setting was fixed in August 2014.
Pros and Cons compared to addr:street
Reading information from a tag instead of a relation may be more straightforward for certain consumers, leading to better performance.
associatedStreet relations can be created before the street name is known (for example during armchair mapping before a survey)
Using associatedStreet relations may help routers direct users through the correct street segment (for example when a row of houses sits between two parallel street sections)
It allows adding information which concerns the whole street, like a name:etymology:wikidata=* tag, only once, instead of needing to repeat it on each nodes/ways, reducing chances of typos.