
Hello Thorsten, thanks, I think this is a problem that can be solved in splitter. It seems that r247 works fine if you use --polygon-file=usa.poly r248 and above will refuce the polygon because it contains long diagonal lines. See also http://gis.19327.n5.nabble.com/splitter-r250-and-open-questions-reg-bounding... Gerd
Date: Fri, 30 Nov 2012 22:04:32 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] splitter maximum tile size
On Fri, Nov 30, GerdP wrote:
Thorsten Kukuk wrote
No, there is no limit for the maximum tiles size for now. Thanks for the hint. What is the limit? I guess it is not a constant, but depends on resolution and other values? Unfortunately the test data is gone and I didn't download it.
If you want to look at the problem, I can try to regenerate the data again.
I am not sure if the problem has to be solved in splitter or in mkgmap. Anyway, please try to reproduce it.
Ok, here is the data:
http://osm.thkukuk.de/tmp/usa.tar.bz2
It contains the tile 71500722.osm.pbf, the splitter data (areas.list, template.args, densities-out.txt) and the usa.poly with which you can cut out the input data from a planet file.
The problem is the 180 longitude. The few data on the left on it should be added to the tiles on the right, not the very, very far away data on the left. I don't know if this is something we can solve better with splitter, but I doubt it's solveable with mkgmap.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev