Address tags will be used to build up the address of an object.
`set_address_tags()` takes a table with arbitrary fields pointing to
Address tags will be used to build up the address of an object.
`set_address_tags()` takes a table with arbitrary fields pointing to
main = {'addr:housenumber'},
extra = {'addr:*'},
postcode = {'postal_code', 'postcode', 'addr:postcode'},
main = {'addr:housenumber'},
extra = {'addr:*'},
postcode = {'postal_code', 'postcode', 'addr:postcode'},
object will fall back to be entered as a `place=house` in the database
unless there is another interested main tag to be found.
object will fall back to be entered as a `place=house` in the database
unless there is another interested main tag to be found.
value under `country` in the address tag list. The same thing happens
to postcodes, they will always be saved under the key `postcode` thus
normalizing the multitude of keys that are used in the OSM database.
value under `country` in the address tag list. The same thing happens
to postcodes, they will always be saved under the key `postcode` thus
normalizing the multitude of keys that are used in the OSM database.
* __relation_as_multipolygon__ creates a (Multi)Polygon from the ways in
the relation. If the ways do not form a valid area, then the object is
silently discarded.
* __relation_as_multipolygon__ creates a (Multi)Polygon from the ways in
the relation. If the ways do not form a valid area, then the object is
silently discarded.
the relations. Ways are combined as much as possible without any regards
to their order in the relation.
the relations. Ways are combined as much as possible without any regards
to their order in the relation.