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
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:
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
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
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
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)
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
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
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
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
10 matches
Mail list logo