Hi, I tried to align the polygon files along a Garmin raster with units divisable by 2048. Howver, the splitter still does another sort of rounding and draws a different polygon, sometimes it is only one garmin unit difference, but this causes that the polygons doesn't touch each other, and also are not a multiple of 2048 which I think can cause those gaps and artefacts along the borders.
Am I correct? I can manually edit the areas.lists file to make the tiles one garmin unit bigger to see if this will improve the map, but I think the splitter could be improved here? In the archives I found this rule: #The numbers used in areas.list are in Garmin units. To get from #latitude and longitude in degrees to Garmin units multiply by 46603 #which, incidentally, is (2^24)/360. #To avoid overlap you have to make sure that the Garmin units are exactly #divisable by 2048. Gerd wrote: > If you use a simple polygon with spitter (e.g. a rectangle), it will > fit the > tiles > into the polygon. If I got that right you use multiple splitter > passes, each > with > a single polygon area. Later you try to combines the tiles to one map. > You should instead run splitter with a polygon that contains the > complete > area. > If that doesn't help, please post the polygon files and the splitter > parms > that you use. > > Gerd > > > > > -- > View this message in context: > http://gis.19327.n5.nabble.com/issues-with-tile-boundaries-tp5753275p5753289.html > Sent from the Mkgmap Development mailing list archive at Nabble.com. > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
