Address tags will be used to build up the address of an object.
`set_address_tags()` takes a table with arbitrary fields pointing to
-_key match lists_. To fields have a special meaning:
+_key match lists_. Two fields have a special meaning:
* __main__: defines
the tags that make a full address object out of the OSM object. This
main = {'addr:housenumber'},
extra = {'addr:*'},
postcode = {'postal_code', 'postcode', 'addr:postcode'},
- country = {'country-code', 'ISO3166-1'}
+ country = {'country_code', 'ISO3166-1'}
}
```
object will fall back to be entered as a `place=house` in the database
unless there is another interested main tag to be found.
- Tags with keys `country-code` and `ISO3166-1` are saved with their
+ Tags with keys `country_code` and `ISO3166-1` are saved with their
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_multiline__ creates a (Mutli)LineString from the ways in
+* __relation_as_multiline__ creates a (Multi)LineString from the ways in
the relations. Ways are combined as much as possible without any regards
to their order in the relation.