[mkgmap-dev] How to debug: IE instead of IRL

Tue Dec 6 16:04:45 GMT 2011

> On Mon, Nov 28, WanMil wrote:
>
>>> On Mon, Nov 28, WanMil wrote:
>>>
>>>> Hi Thorsten,
>>>>
>>>> I've observed such a problem once although I cannot fully adapt it to
>>>> your problem. Anyhow I'll describe what happens in mkgmap so you might
>>>> have an idea yourself?!
>>>
>>>> What might have happened in your case is:
>>>> 1. You have used different name-tag-list values for different tiles (is
>>>> that possible? I should know but I am unsure...). Anyhow the country
>>>> abbreviation should be the same because it is always taken from the
>>>> LocatorConfig.xml.
>>>
>>> No, I don't use different name-tag-list values for different tiles.
>>> And meanwhile I found out that the country abbreviation is always
>>> the one from "--country-abbr=XYZ", independent of which value is
>>> specified here. Since the island Ireland consists of two countrys,
>>> the value is always wrong for both states. Between, only the
>>> country Ireland is wrong, North-Irland is always correct.
>>
>> I am not sure if I understand you correct: Northern Ireland is always
>> correct (which means abbrevation is GBR) whereas Republic of Ireland is
>> always incorrect (which means abbreveation is the value of
>> --country-abbr). Did you mean that?
>>
>> Anyhow you provided two error messages as examples. Both are located in
>> the country Republic of Ireland.
>> http://www.openstreetmap.org/browse/way/46605658
>> [...,mkgmap:admin_level2=IE,mkgmap:country=IE]
>> http://www.openstreetmap.org/browse/way/106590397
>> [...,mkgmap:admin_level2=IRL,mkgmap:country=IRL]
>>
>> The first way shows the problem very good. The mkgmap:admin_level2 tag
>> is set to IE, so there must be a precompiled boundary with the tags
>> admin_level=2 and nameXXX=IE where nameXXX is one of the tags set by
>> name-tag-list. I have searched the precompiled bounds of Oct 16th (you
>> are using them?) but I couldn't find such a boundary so far. So at the
>> moment I have no idea about the problem...
>
> Was revision 2133 to be supposed to fix this? Anyhow, with r2133 it is
> now working fine for me.
>
>    Thanks,
>      Thorsten
>

When having a look at your problem I observed this problem although I 
don't think that it fixes it.

Anyhow I am glad that it's working now :-)

WanMil