[mkgmap-dev] Coastline issues - analysis and possible solution

Mon Aug 29 08:40:44 BST 2011

> fixed tiles may produce better coastlines, but you'll get "map too big"
> at some point as the map grows.

The way I understand Marko's suggestion, you would give the splitter an 
initial list of tiles (or just a region) and it would then subdivide 
that into smaller tiles as it does today. The difference would be that 
you could provide the splitter with a large dataset (say all of Europe) 
while telling it to cut out tiles for a small region (say the 
Netherlands) only. This would essentially integrate the osmosis cutting 
step into the splitter. The advantage of this is that the splitter has 
data for the tiles it cuts out, including ones that expand when 
rounding. The disadvantages are a need to push around larger datasets, 
to need to specify tile boundaries each time the splitter is invoked and 
a loss of the UNIX principle that each tool handles one small thing and 
handles it well.

- Bartosz