[mkgmap-dev] Coastline issues - analysis and possible solution
From michael lohr micha.lohr at web.de on Mon Aug 29 08:27:05 BST 2011
fixed tiles may produce better coastlines, but you'll get "map too big" at some point as the map grows. so you could either set a large safety margin and get a lot more tiles or you'd have to fix the tiles anew more often. Am 29.08.2011 09:08, schrieb Bartosz Fabianowski: >> It still takes a little tweaking to get the coastlines right. I have >> manually chosen the tile borders so that the coastline will end outside >> the tile border. Only in the Swedish/Finnish border I am using >> extend-sea-sectors to make up some coastline in Sweden. > This is why I collected the coastlines for all of Europe in a single > file. When all European coastlines are available, you no longer have to > tweak tile boundaries. > >> I think that it could be useful to have the tile-splitter support a set >> of fixed tiles that it would split itself further as needed. > I presume you would then use this so that you extract a larger region > and then let the splitter generate tiles for a subset of this region? > With a sufficient margin of safety between the two regions, this should > work by providing the splitter with coastline data even when tiles grow > due to rounding. > > - Bartosz > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20110829/9ae45e44/attachment.html
- Previous message: [mkgmap-dev] Coastline issues - analysis and possible solution
- Next message: [mkgmap-dev] Coastline issues - analysis and possible solution
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list