House number improvements
08
Jun
House numbers have been part of mkgmap for a couple of years now, but as more and more housenumbers are added to OSM, Gerd undertook a project to update the code to deal with many more cases of real world OSM tagging.
The main changes are:
- mkgmap tries to identify unnamed roads which lead to houses and can be named (assuming they are service roads)
- mkgmap tries to find a plausible road when no street is given.
addr:interpolation
ways are used to find the most plausible road and the interpolated addresses are found- improved evaluation of
addr:*
tags, esp. the support foraddr:place
and the support foraddr:housenumber
withoutaddr:street
, img data is optimized to make sure that address search finds a place close (< 40m) to the address. - special cases regarding addresses in different cities or zip codes along the same road are handled. This is important when a road starts in city A and has some numbers 1..20 there and later crosses city B with numbers 1..5 and finally ends in city C with numbers 1..50.
- the found addresses are typically closer to the house
Using in your own style
If you want to test with your own style: Please note the new special tags
mkgmap:numbers=false
and mkgmap:execute_finalize_rules=true
- a road with
mkgmap:numbers=false
is ignored in house number processing. The default style uses this for ferries and motorways and for bicycle-only roads. - The
mkgmap:execute_finalize_rules=true
tag will cause the finalize rules to be run, even if no object is created in the map for that element. So to set the city, region and country values for all elements with house numbers, useas a first rule in points, lines and polygons and addaddr:housenumber=* {set mkgmap:execute_finalize_rules=true}
to the finalize sections.include 'inc/address';
Use version r3612 or above to get these upgrades.
Posted by steve on 8 Jun 2015