[mkgmap-dev] [Patch V1]Re: Still problems with lakes

2012-10-17 Thread GerdP
Hi, here is a first try to fix this issue. splitter_problem_list.patch http://gis.19327.n5.nabble.com/file/n5731258/splitter_problem_list.patch A sample list of problem polygons: problem_polygons.txt http://gis.19327.n5.nabble.com/file/n5731258/problem_polygons.txt Specify it in the new

Re: [mkgmap-dev] mkgmap splitter or mkgmap leave out information on luxembourg.osm.pbf from geofabrik

2012-10-17 Thread n Willink
Hi Felix I have encountered similar problems when splitter only produces one pbf file - see previous posting about tdb mdr issues Have you tried reducing the max-nodes to obtain 2 pbfs - that seems to do the trick with me /nick -- View this message in context:

Re: [mkgmap-dev] mkgmap splitter or mkgmap leave out information on luxembourg.osm.pbf from geofabrik

2012-10-17 Thread Felix Hartmann
On 17.10.2012 17:10, n Willink wrote: Hi Felix I have encountered similar problems when splitter only produces one pbf file - see previous posting about tdb mdr issues Have you tried reducing the max-nodes to obtain 2 pbfs - that seems to do the trick with me /nick yes doesn't change

Re: [mkgmap-dev] It's clearly a bug in the splitter

2012-10-17 Thread GerdP
Hi Felix, Exact map coverage is (49.44551467895508,5.733017921447754) to (50.184946060180664,6.532230377197266) Trimmed and rounded map coverage is (49.482421875,5.712890625) to (50.185546875,6.50390625) I think the reason is that splitter writes a different bounding box to the file. I am

Re: [mkgmap-dev] [Patch V1]Re: Still problems with lakes

2012-10-17 Thread Jaromír Mikeš
Od: GerdP gpetermann_muenc...@hotmail.com Hi Gerd, here is a first try to fix this issue. splitter_problem_list.patch http://gis.19327.n5.nabble.com/file/n5731258/splitter_problem_list.patch I would like to try your patch as I have problem with glacier polygon when I build map of

Re: [mkgmap-dev] It's clearly a bug in the splitter

2012-10-17 Thread WanMil
I think this was discussed some time ago: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012193.html WanMil Hi Felix, Exact map coverage is (49.44551467895508,5.733017921447754) to (50.184946060180664,6.532230377197266) Trimmed and rounded map coverage is (49.482421875,5.712890625)

Re: [mkgmap-dev] It's clearly a bug in the splitter

2012-10-17 Thread Felix Hartmann
Actually the way I put the rounding now (to include everything) - is the way it has been up to rev 104, then came rev105 and the change (28.1.2010) - the patch did the same thing as I did. However actually now that I think about it - I can only come up with one explication why rev 105 on

Re: [mkgmap-dev] [Patch V1]Re: Still problems with lakes

2012-10-17 Thread Jaromír Mikeš
Od: Gerd Petermann gpetermann_muenc...@hotmail.com Hi Gerd, why o5m: o5m is much faster to read compared to pbf, and the new algorithm requires a few more reads As Greenland map hasn't too much data I stayed with pbf ... not really longer splitting. Specify it in the new parameter

Re: [mkgmap-dev] [Patch V1]Re: Still problems with lakes

2012-10-17 Thread Henning Scholland
Hi Gerd, is it possible to use a normal splitter r200 with o5m input-data? What about mkgmap? Henning Am 17.10.2012 16:36, schrieb GerdP: Hi, here is a first try to fix this issue. splitter_problem_list.patch http://gis.19327.n5.nabble.com/file/n5731258/splitter_problem_list.patch A

Re: [mkgmap-dev] It's clearly a bug in the splitter

2012-10-17 Thread Steve Ratcliffe
On 17/10/12 19:44, Felix Hartmann wrote: However actually now that I think about it - I can only come up with one explication why rev 105 on splitter was done - that is so that tiles don't overlap. Because the current hack means all tiles will be expanded. Yes, that is exactly right, the tiles