Well I tried out 264 without a polygon, and it's fixed and the empty area in the west is taken out. But Mapsource still cuts the map when zooming in at around 142 East. Is this the same when using a polygon? On 19.12.2012 09:57, GerdP wrote:
Felix Hartmann-2 wrote
yep. I think the actual data is no more than 150° (east 31 to 180)- but the sea info around adds more to it so it starts already at W2°) On 18.12.2012 22:46, Gerd Petermann wrote: The error was in the new split algorithm. This is fixed with r264.
While fixing the error I found a general problem: Some objects in the OSM database are crossing large areas, eg. "The Arctic Circle" http://www.openstreetmap.org/browse/way/162812278
Since the asia extract contains this way completely, splitter creates a tile that covers almost whole Europe if you don't provide a bounding polygon. I've attached the results, once with using --polygon-file=asia.poly, once without.
asia.zip <http://gis.19327.n5.nabble.com/file/n5740975/asia.zip> Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Splitter-crashing-on-asia-osm-pbf-with-keep-c... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org