Hi, some weeks ago WanMil wrote
> ... > All in all: Please keep the format of the bnd files as simple as > possible and think about using it for other purposes. e.g. the current > format could easily be used for coastline processing - one can > precompile the coastlines and mgkmap could load the sea areas from the > precompiled sea file. This would be great to have (a big!! performance > and quality improvement). But someone needs to implement that. > I looked at the sources now and see two ways how to do that: 1) We can write the result of SeaGenerator.joinWays() or 2) We can write the result of SeaGenerator.end() pro 1): this will produce files that are usable for all, no matter what optionsthe user wants to use in generate-sea parm, so it can be downloaded like the precompiled boundaries. pro 2): this should reduce the CPU time even more, but every user has to create his own file(s) Any ideas what will be better? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Precompiled-coastlines-tp5507867p5507867.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
