[mkgmap-dev] splitter: option for maximum tile area?From Thorsten Kukuk kukuk at suse.de on Thu Nov 1 11:38:08 GMT 2018
On Thu, Nov 01, Gerd Petermann wrote: > Hi Bernhard, > > my understanding is that you should never see broken precompiled sea data, because the data source is not directly OSM > but http://openstreetmapdata.com/data/land-polygons where Jochen Topf invests time to check that the data is OK before updating it. > So, sea.zip might not be up to date but should always be OK. Not really, as he writes on his web page, his tools tries to repair the coastlines. And as I use them, too, I know that this automatic "repair" can break the result even more. I have added some additional post-precessing checks and patched osmcoastline to bail out on more errors to make sure that the result is for me really useable. Currently the coastlines are so heavy broken, that osmcoastline only seg.faults. So there will be no update with the broken costlines. I assume that why geofabrik does not report coastlines errors anymore, too. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
- Previous message: [mkgmap-dev] splitter: option for maximum tile area?
- Next message: [mkgmap-dev] splitter: option for maximum tile area?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list