
Steve Sgalowski <steve.sgalowski@gmail.com> writes:
mkgmap:country admin level 5
then mkgmap:state admin level 6 mkgmap:region admin level 7 postcode sdmin level 8 suburb level 9, 10
My quick reaction is that which admin_level corresponds to which parts of an address varies by region. In my part of the US, state is level4, city/town is level8, and that's really all there is in address. Whether a (legal) city/town is "suburb", "city", "town", "village", etc. is based on size and relationship to larger entities. Around me only two cities have admin_level 10 boundaries. One calls them neighborhoods or villages, not suburbs. Sometimes they show up in postal addresses. So really I wonder if this means that the address component rules should be encoded on the boundary, something like "addresses within this polygon inherit name_component_foo=bar". I am leaning to having addresses have everything (in the US) below state explicit, to avoid this.