<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi all,<br><br>it seems that I have to explain a few more details.<br><br>The inc/address file contains rules which set the tags<br>like mkgmap:country, mkgmap:region, mkgmap:city and <br>so on. <br>These tags are used in two different ways:<br>1) for housenumber processing<br>2) to fill the corresponding fields of POIs <br><br>With my initial post I just wanted to point out that we have a lot<br>of redundant rules, and the patch posted here<br><a href="http://gis.19327.n5.nabble.com/Patch-v1-simplify-address-rules-tp5847326.html" target="_blank">http://gis.19327.n5.nabble.com/Patch-v1-simplify-address-rules-tp5847326.html</a><br>shows which rules I mean.<br><br>In the meantime Minko suggested to modify the rule for BEL instead of removing it.<br><br>The general rules implemented in the file are:<br>mkgmap:admin_level2 : mkgmap:country (this is the 3 character ISO code, e.g. GER for Germany)<br>mkgmap:admin_level6,5,4,3 : mkgmap:region (meaning depends on country)<br>mkgmap:admin_level8,7,9,10 : mkgmap:city<br><br>A rather simple test to find out if the implemented rules are good is<br>to compare addr:city with mkgmap:city.<br>Add a line like this at the end of inc/address:<br>mkgmap:city!=* & addr:city!=* & addr:city != ${mkgmap:city} { echotags "city name?" }<br> <br>and check the messages. When all rules are OK and the boundary file is up to date<br>(and also OK) only a few messages should be printed, most of them showing different spelling<br>of the same name.<br><br>If you see many lines where the names in mkgmap:city and addr:city are totally different <br>this is a hint that either the rules are not OK or that boundaries are missing/wrong.<br><br>Gerd<br><br><br><div>From: gdt@ir.bbn.com<br>To: steve.sgalowski@gmail.com<br>Date: Sat, 6 Jun 2015 20:21:05 -0400<br>CC: mkgmap-dev@lists.mkgmap.org.uk<br>Subject: Re: [mkgmap-dev] superfluous country specific rules in inc/address?<br><br><pre> <br>Steve Sgalowski <steve.sgalowski@gmail.com> writes:<br> <br>> mkgmap:country admin level 5<br>><br>> then mkgmap:state admin level 6<br>> mkgmap:region admin level 7<br>> postcode sdmin level 8<br>> suburb level 9, 10<br> <br>My quick reaction is that which admin_level corresponds to which parts<br>of an address varies by region. In my part of the US, state is level4,<br>city/town is level8, and that's really all there is in address.<br>Whether a (legal) city/town is "suburb", "city", "town", "village",<br>etc. is based on size and relationship to larger entities.<br> <br>Around me only two cities have admin_level 10 boundaries. One calls<br>them neighborhoods or villages, not suburbs. Sometimes they show up in<br>postal addresses.<br> <br>So really I wonder if this means that the address component rules should<br>be encoded on the boundary, something like "addresses within this<br>polygon inherit name_component_foo=bar".<br> <br>I am leaning to having addresses have everything (in the US) below state<br>explicit, to avoid this.<br> <br> <br></pre><br>_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</div> </div></body>
</html>