On Wed, Dec 05, GerdP wrote: > Thorsten Kukuk wrote
> > Yes, I think the problem is if you cross 180. Maybe if the data is > > going from ~-180 to ~180, we should check what the latest node from > > the right is, and what the latest node from the left is, and exclude > > the empty middle? > > I thought the same and coded that before, but the problem would be the > same if you use a polygon containing e.g. all countries using french as the > national language. > I think it is not good enough to creae two distinct areas if the original > polygon > contained more than two, and guessing the original polygon is not trivial, > esp. not > if it contains small areas around islands. Ok, but I can create the problem with only _one_ polygone, which contains only Alaska, too. The problem is if a polygone has to cross -180/180 longitude. Ok, due to the design, it will always be two polygons ... Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
