[mkgmap-dev] boundary France broken?

Thu Jan 23 21:18:50 GMT 2014

No Problem, Gerd.

BTW: looks like Norway has the same problem... didn't check deeper for 
others, but those too (France and Norway) were quite promient.

Just to confirm: it doesn't matter that the command is still running ? 
it did already create the level 2 files, seems to run through the levels 
by admin level.... I assume it doesn't 'revisit' admin level 2

Patrik
On 23.01.2014 22:11, GerdP wrote:
> Hi Patrik,
>
> it's bad. A good picture would not show any line between France and its
> neighbours
> on the continent.
>
> Sorry for the typo, I use some more options for debugging and removed them
> after copy+paste.
>
> Gerd
>
> Patrik Brunner wrote
>> Is that now good or bad ?
>>
>>
>> It's still running on admin_level 5 but I assume that level 2 is finished.
>>
>> BTW: my Windows Java did complain about the option --Xmx6800m
>> I assume it should be a single dash, not doubledash... therefore -Xmx6800m
>> I've just ran it without...
>>
>> Patrik
>>
>> On 23.01.2014 20:23, Gerd Petermann wrote:
>>> Hi Minko,
>>>
>>> the boundary relation 2202162 was changed 5 or more times since
>>> 2014-01-01.
>>>
>>> You can check yourself using a command like this:
>>> java --Xmx6800m -cp d:\mkgmap\dist\mkgmap.jar
>>> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryCoverageUtil
>>> bounds_20140101.zip > log
>>>
>>> This will take a while and produce a directory gpx in the current
>>> directory.
>>> If you load all the files in
>>> gpx\summary\covered\admin_level=2
>>> into e.g. JOSM you should not find holes in France. If you do,
>>> something was broken when the bnd files were generated.
>>>
>>> Gerd
>>>
>>>> Date: Thu, 23 Jan 2014 17:55:35 +0100
>>>> From:
>> ligfietser@
>>>> To:
>> mkgmap-dev at .org
>>>> Subject: [mkgmap-dev] boundary France broken?
>>>>
>>>> Hi,
>>>> I found out that the boundary of France in bounds_20140101.zip
>>> (http://www.navmaps.eu/boundaries) might be broken. Places in France
>>> are not assigned to France anymore. If I use the previous bounds file
>>> (bounds_20131101.zip) it works as expected. Can anyone check where the
>>> cause is?
>>>> _______________________________________________
>>>> mkgmap-dev mailing list
>>>>
>> mkgmap-dev at .org
>>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>>
>>> _______________________________________________
>>> mkgmap-dev mailing list
>>>
>> mkgmap-dev at .org
>>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> mkgmap-dev at .org
>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>> part1.04040003.04080301@
>>   (150K)
>> &lt;http://gis.19327.n5.nabble.com/attachment/5794147/0/part1.04040003.04080301%40gmx.net&gt;
>
>
>
>
> --
> View this message in context: http://gis.19327.n5.nabble.com/boundary-France-broken-tp5794112p5794150.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev