|
Where should addr:city, addr:postcode, addr:country, ... be set, when using associatedStreet relations instead of addr:street tags? It doesn't make much sense to set them on the nodes, as on of the primary benefits from using relations - not repeating the same addr:street over and over again - would be busted... But as far as I read the wiki, the associatedStreet relation itself is also not meant to hold address information. |
|
In theory addr:* tags shouldn't be needed on associatedStreet relations; the associatedStreet has a name (the addr:street equivalent) and is in a geographical database where city, country, country, etc should be possible to work out from the location (though see comments about postcodes below). Having said that, I can see no harm in adding addr:* tags to the relation. The addr:city one in particular might be useful for a road somewhere roughly equidistant between two cities; though it depends on each data user whether they check for and use any such tags. addr:postcode probably requires a country specific answer, as in many parts of the UK for example there are often more than one postcodes for a single street (such as one for one side of the road and one the other, and sometimes even another for new houses slotted in amongst older ones), so in the UK the addr:postcode tag would go on the individual addresses. 1
If houses on the same street have different postcodes, one could also use more associatedStreet-Relations, where the street is member in both.
(06 Oct '12, 15:56)
Alexander Ro...
|
