[mkgmap-dev] splitter maximum tile size
From GerdP gpetermann_muenchen at hotmail.com on Wed Dec 5 09:52:58 GMT 2012
Hi all, I am trying to find a decision what splitter should do in the following case: Assume you have created an extract from planet using the usa.poly from Thorsten. usa.poly <http://gis.19327.n5.nabble.com/file/n5739131/usa.poly> http://gis.19327.n5.nabble.com/splitter-maximum-tile-size-tp5738382p5738533.html This polygon file contains 10 distinct areas. The resulting osm dump contains a huge bounding box covering almost 50 % of planet, but it also contains huge areas without any nodes (e.g. the european and asian area) Without the parameter --polygon-file=usa.poly splitter will try to create tiles that cover the bounding box of the file, which results in huge tile(s) covering europe and russia. This is obviously not what the user wants. What should splitter do in such a case? I see two solutions: 1) stop with a message that the tiles are too big and ask for a polygon-file 2) guess what polygon was used. I'd say 1) is good enough. In other words: If splitter is not able to split a file without creating huge (almost empty) tiles, it will ask for a bounding-polygon. Is that okay? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-maximum-tile-size-tp5738382p5739131.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
- Previous message: [mkgmap-dev] splitter maximum tile size
- Next message: [mkgmap-dev] splitter maximum tile size
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list