[mkgmap-dev] issues with tile boundaries

Sun Mar 17 07:34:33 GMT 2013

Hi Minko,

Minko-2 wrote
> Last try was to feed the splitter N1.poly and M1.poly, those polygons were
> aligned
> at the Garmin grid (dividable by 2048) but the splitter rounded the
> polygons differently, so the ressulting tiles of N1 and M1 didnt quite
> match (and their borders were not a multiple of 2048).
> 
>> I see these options to help in your case:
>> 1) Complex: Implement an algorithm in splitter which does something
>> similar to your approach: Partition the input file into a few large
>> areas
>> and calculate each partition seperately.
> 
> Maybe you can use N1 and M1 poly's as example?

the polygons in N1 and M1 are not aligned, but with the new parameter
--no-trim-to-polygon
splitter writes the area.poly with the aligned coordinates.

Reg. the complex algo : I think it will not help in your case, but it might
be a solution for those
that are running out of memory. I will not code that unless there is a real
need, because the solution that I have in mind would add a lot of
complexity.
OK?

Gerd

--
View this message in context: http://gis.19327.n5.nabble.com/issues-with-tile-boundaries-tp5753275p5753477.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.