[mkgmap-dev] [PATCH v2] Precompiled seaFrom WanMil wmgcnfg at web.de on Sat May 12 18:30:11 BST 2012
> >Once the new precompiled coastline code goes in, I guess my service > will become obsolete and can go away again. >But until then, feel free > use the coastlines from there to work around flooding issues. > > Is that really the case? Using precompiled sea for the whole world seems > overkill - there are something like 56500 files in sea_20120331.zip > file. All I need is the Great Britain coastline to guard against flooding. Does it matter how many files there are? Anyhow it would be easily possible to use a subset of the files. When I post the next patch of the precompiled sea the input files have osm of pbf format. Using osm format it is possible to correct floodings manually with JOSM. So from my point of view the only reason to use the present coastline processing is that the precomiled sea uses not the very latest data and is compiled only from time to time. Ok, maybe a second one: Precompiled sea uses the multipolygon algorithm. But it would be quite easy to add the polygon variant if required. WanMil > > Or have I misunderstood something? > > Roger Calvert (Rogerc on OSM) > > > > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] [PATCH v2] Precompiled sea
- Next message: [mkgmap-dev] Resolution range for POIs ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list