[mkgmap-dev] [locator] Country specific rules

From WanMil wmgcnfg at web.de on Sat May 7 12:45:18 BST 2011

Can you please send your areas.list from the splitter? Then I can test 
and debug myself.

The place-tag is evaluated only by the old locator. Which value do you 
use for the parameter location-autofill? Please send also your complete 
mkgmap commandlines with parameters.

WanMil



> Hello,
>
> Horb isn't complete in the tile. I created the tile also with osmosis with the same boundaries (top=48.735352 left=8.129883 bottom=48.295898 right=8.657227). Same behaviour.
> But, I've created a place tag named Horb and now I can find all streets within this tile. So the question is, is it needed that also the place-tag is within the tile or maybe the boundfile? I've made 2 screenshots, I hope it works and helps to understand and fix this problem.
> Without the place-tag in the tile:
> http://snailrun.de/images/MapSearch/Ohne.png
> With the place-tag in the tile:
> http://snailrun.de/images/MapSearch/Mit.png
>
> If you need further informations/tests just write me an email.
> I'm german, sorry for my poor english, I try my best :)
>
> Cheers
> Martin
>
> P.S.: Isn't it possible to attach pictures to the maillist?!
>
>
>
>
>
>
> Am 06.05.2011 um 18:00 schrieb WanMil:
>
>> Based on the logging and the current default style I would expect that
>> you get a street with
>> name = Schafblumenhalde
>> country = Deutschland
>> region = Landkreis Freudenstadt
>> city = Horb am Neckar
>>
>> Can you please check if Horb is completely contained in one tile (63240403)?
>>
>> In that case I would assume that maybe this is an index problem. Maybe
>> Steve is able to check that?!
>>
>> I will continue to add some more useful debug statements to the locator
>> branch so that it is easier to track such things.
>>
>> WanMil
>>
>>> Sorry, me again.
>>>
>>> I used now the tile produced the splitter, which contains the the not found streets of Horb. For e.g. I could find the Schafblumenhalde. With the debug-logging (LocationHook = FINE) I find this in the logfile:
>>>
>>> 2011/05/06 09:55:17 FEIN (LocationHook): ./tiles_germany/63240403.osm.gz: Added tag mkgmap:admin_level5 = Regierungsbezirk Karlsruhe to [motorcycle=destination,access=destination,mkgmap:admin_level2=DEU,mkgmap:admin_level4=Baden-W�rttemberg,mkgmap:admin_level5=Regierungsbezirk Karlsruhe,mkgmap:admin_level6=Landkreis Freudenstadt,name=Schafblumenhalde,mkgmap:admin_level8=Horb am Neckar,highway=residential,motorcar=destination]
>>>
>>>
>>> Where is the problem?!
>>> Are in the logfile are only not assignable streets logged?!
>>>
>>> Cheers
>>> Martin
>>>
>>> Am 06.05.2011 um 09:44 schrieb Martin:
>>>
>>>> Good morning :)
>>>>
>>>> Both problems didn't come up, when I cut a small bounding box out of the main pbf-file with osmosis and create a map with just this one tile.
>>>> Is it possible, that this problem comes from the splitter?!
>>>>
>>>> Cheers
>>>> Martin
>>>>
>>>>
>>>> Am 05.05.2011 um 17:44 schrieb Martin:
>>>>
>>>>> Hello,
>>>>>
>>>>> this rules works very good.  2 strange things:
>>>>> Sometimes Basecamp and the Oregon 450 has problems to find Streets starting with 2 letters, space, more letters (Am Anger, Am Lusbühl, Am Hägle (http://osm.org/go/0DKQ69he@-?way=22999129)), but  "Auf der Bleiche" (http://osm.org/go/0DKQ43mIw--?way=22999129) works. It's not a problem with the Umlaute (äöü).
>>>>> And the second thing:
>>>>> I've created a german-map (http://snailrun.de/gmapsupp.img.zip), splitted into tiles with a 1200000 nodes. In Horb for example I can find the "Am Lochbrunnenstraße" (2 letters, space, more letters works here ?!?) but not the Lichtenbergstraße, Kirchstraße, Schafblumenhalde (http://osm.org/go/0DhcL1dyJ-?way=22999129)
>>>>> But when I cut out a bounding-box from the Germany.osm.pfb-file in the size of Horb, I can find the all streets....
>>>>> Strange things...
>>>>>
>>>>> Cheers
>>>>> Martin
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Am 04.05.2011 um 21:03 schrieb WanMil:
>>>>>
>>>>>> I think only the city rules need to be tweaked in Germany:
>>>>>>
>>>>>> # Germany = DEU cities
>>>>>> mkgmap:country=DEU&   mkgmap:city!=*&   mkgmap:admin_level8=* { set
>>>>>> mkgmap:city='${mkgmap:admin_level8}' }
>>>>>> mkgmap:country=DEU&   mkgmap:city!=*&   mkgmap:admin_level7=* { set
>>>>>> mkgmap:city='${mkgmap:admin_level7}' }
>>>>>> mkgmap:country=DEU&   mkgmap:city!=*&   mkgmap:admin_level6=* { set
>>>>>> mkgmap:city='${mkgmap:admin_level6}' }
>>>>>> mkgmap:country=DEU&   mkgmap:city!=*&   mkgmap:admin_level9=* { set
>>>>>> mkgmap:city='${mkgmap:admin_level9}' }
>>>>>> mkgmap:country=DEU&   mkgmap:city!=*&   mkgmap:admin_level10=* { set
>>>>>> mkgmap:city='${mkgmap:admin_level10}' }
>>>>>>
>>>>>> First use admin_level=8 for city names. This covers all cities with a
>>>>>> size up to 300000. Bigger cities don't use admin_level=8 but
>>>>>> admin_level=9 and 10 (and 11) for suburbs. The appropriate name of the
>>>>>> bigger city should be contained then in the admin_level 7 or 6.
>>>>>>
>>>>>> Please try it and give a feedback if that's ok. The upper rules are
>>>>>> committed in r1937.
>>>>>>
>>>>>> Later on I will try your region settings.
>>>>>>
>>>>>> WanMil
>>>>>>
>>>>>>> In Germany we have the same mess...
>>>>>>>
>>>>>>> Actually I'm using this rules:
>>>>>>>
>>>>>>> mkgmap:country!=*&   mkgmap:admin_level2=* { set
>>>>>>> mkgmap:country='${mkgmap:admin_level2}' }
>>>>>>>
>>>>>>> mkgmap:region!=*&   mkgmap:admin_level3=* { set
>>>>>>> mkgmap:region='${mkgmap:admin_level3}' }
>>>>>>> mkgmap:region!=*&   mkgmap:admin_level4=* { set
>>>>>>> mkgmap:region='${mkgmap:admin_level4}' }
>>>>>>> mkgmap:region!=*&   mkgmap:admin_level5=* { set
>>>>>>> mkgmap:region='${mkgmap:admin_level5}' }
>>>>>>>
>>>>>>>
>>>>>>> mkgmap:city!=*&   mkgmap:admin_level10=* { set
>>>>>>> mkgmap:city='${mkgmap:admin_level10}' }
>>>>>>> mkgmap:city!=*&   mkgmap:admin_level8=* { set
>>>>>>> mkgmap:city='${mkgmap:admin_level8}' }
>>>>>>> mkgmap:city!=*&   mkgmap:admin_level7=* { set
>>>>>>> mkgmap:city='${mkgmap:admin_level7}' }
>>>>>>> mkgmap:city!=*&   mkgmap:admin_level6=* { set
>>>>>>> mkgmap:city='${mkgmap:admin_level6}' }
>>>>>>>
>>>>>>>
>>>>>>> I don't know if this makes sense, but referring to this page:
>>>>>>> http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative
>>>>>>> <http://wiki.openstreetmap.org/wiki/Tag:boundary=administrative>
>>>>>>> there are 2 options for the admin-boundaries:
>>>>>>> 10 and 11 admin levels :(
>>>>>>> So actually I still playing with this setting, maybe somebody has better
>>>>>>> rules for Germany.
>>>>>>>
>>>>>>>
>>>>>>> Thanks and regards
>>>>>>> Martin
>>>>>>>
>>>>>>>
>>>>>>> Am 04.05.2011 um 19:38 schrieb Minko:
>>>>>>>
>>>>>>>>
>>>>>>>> Netherlands:
>>>>>>>>
>>>>>>>> mkgmap:region!=*&   mkgmap:admin_level4=* { set
>>>>>>>> mkgmap:region='${mkgmap:admin_level4}' }
>>>>>>>> mkgmap:city!=*&   mkgmap:admin_level10=* { set
>>>>>>>> mkgmap:city='${mkgmap:admin_level10}' }
>>>>>>>> mkgmap:city!=*&   mkgmap:admin_level8=* { set
>>>>>>>> mkgmap:city='${mkgmap:admin_level8}' }
>>>>>>>>
>>>>>>>> For Belgium I'm not sure, seems a big mess there ;-)
>>>>>>>>
>>>>>>>> Provinces are found in level 5 or 6, level 4 is for Flandres and Wallonie
>>>>>>>> But in level 5 you have something like the 'Flemish Community' too:
>>>>>>>> http://www.openstreetmap.org/browse/relation/53136
>>>>>>>> There is also the Flemish region (level 4), don't have any clue what
>>>>>>>> the difference is between those two:
>>>>>>>> http://www.openstreetmap.org/browse/relation/53134
>>>>>>>>
>>>>>>>> Cities:
>>>>>>>> mkgmap:city!=*&   mkgmap:admin_level9=* { set
>>>>>>>> mkgmap:city='${mkgmap:admin_level9}' }
>>>>>>>> mkgmap:city!=*&   mkgmap:admin_level8=* { set
>>>>>>>> mkgmap:city='${mkgmap:admin_level8}' }
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> mkgmap-dev mailing list
>>>>>>>> mkgmap-dev at lists.mkgmap.org.uk
>>>>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> mkgmap-dev mailing list
>>>>>>> mkgmap-dev at lists.mkgmap.org.uk
>>>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>>>
>>>>>> _______________________________________________
>>>>>> mkgmap-dev mailing list
>>>>>> mkgmap-dev at lists.mkgmap.org.uk
>>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> mkgmap-dev mailing list
>>>>> mkgmap-dev at lists.mkgmap.org.uk
>>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> mkgmap-dev mailing list
>>>> mkgmap-dev at lists.mkgmap.org.uk
>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>>
>>>
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>> mkgmap-dev at lists.mkgmap.org.uk
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at lists.mkgmap.org.uk
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

---

• Previous message: [mkgmap-dev] [locator] Country specific rules
• Next message: [mkgmap-dev] [locator] Country specific rules
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the mkgmap-dev mailing list