Hi Felix,

the problem is caused by the new check for large tiles.
The log shows a hint:
> Please specify a bounding polygon with the --polygon-file parameter.
You might try this. In the meantime I'll try to reproduce it and find a better solution.
This is the geofabrik asia.osm.pbf, right ?

Gerd

> Date: Tue, 18 Dec 2012 22:22:20 +0100
> From: extremecarver@gmail.com
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: [mkgmap-dev] Splitter crashing on asia.osm.pbf with --keep-complete
>
> Please see below output, this is happening since --keep-complete was
> introduced. This report is from splitter rev. 263
> any idea on how to go on about it? Also I noted that Mapsource/Basecamp
> won't display the most eastern part of Asian map since quite a long time....
>
> I suppose it has something to do with >179°??
>
> java -Xmx6600m -jar splitter.jar --max-nodes=800000 --output=pbf
> "--keep-complete" --max-areas=255 --geonames-file=cities15000
> --description=as
> asia.osm.pbf
> Splitter version unknown compiled 2012-12-18T12:44:14+0100
> cache=
> description=asia
> geonames-file=cities15000
> keep-complete=true
> mapid=65400000
> max-areas=255
> max-nodes=800000
> max-threads=8 (auto)
> mixed=false
> no-trim=false
> output=pbf
> output-dir=
> overlap=-1
> polygon-file=
> problem-file=
> problem-report=
> resolution=13
> split-file=
> status-freq=120
> stop-after=dist
> write-kml=
> Elapsed time: 0s Memory: Current 122MB (2MB used, 120MB free) Max 5866MB
> Time started: Tue Dec 18 18:24:02 CET 2012
> Map is being split for resolution 13:
> - area boundaries are aligned to 0x800 map units (0.0439453125 degrees)
> - areas are multiples of 0x800 map units wide and high
> Processing c:\openmtbmap\osmpbf_geofabrik\asia.osm.pbf
> Bounding box -179.99990000000003 -17.06773 179.99990000000003 84.52666
> 10'000'000 nodes processed... id=345469396
> 20'000'000 nodes processed... id=602633323
> 30'000'000 nodes processed... id=735433109
> 40'000'000 nodes processed... id=766952699
> 50'000'000 nodes processed... id=929389508
> 60'000'000 nodes processed... id=1054713652
> 70'000'000 nodes processed... id=1169860237
> 80'000'000 nodes processed... id=1244176605
> 90'000'000 nodes processed... id=1296405869
> 100'000'000 nodes processed... id=1346975878
> 110'000'000 nodes processed... id=1401150913
> 120'000'000 nodes processed... id=1451567888
> 130'000'000 nodes processed... id=1502517075
> 140'000'000 nodes processed... id=1594119652
> 150'000'000 nodes processed... id=1667582161
> 160'000'000 nodes processed... id=1730324902
> 170'000'000 nodes processed... id=1799260316
> 180'000'000 nodes processed... id=1864129020
> 190'000'000 nodes processed... id=1943914135
> 200'000'000 nodes processed... id=2017718514
> in 1 file
> Time: Tue Dec 18 18:25:32 CET 2012
> Exact map coverage is (-17.067711353302002,-179.9998927116394) to
> (84.52664136886597,179.9998927116394)
> Rounded map coverage is (-17.0947265625,-180.0) to (84.55078125,180.0)
> Splitting nodes into areas containing a maximum of 800'000 nodes each...
> Highest node count in a single grid element is 259'791
> Trying to find nice split for (-17.0947265625,-180.0) to
> (84.55078125,180.0) with 207'716'938 nodes
> Trying non-natural splits with spread 3 ...
> Trying non-natural splits with spread 5 ...
> Trying non-natural splits with spread 7 ...
> stored states 10000
> Split was not yet succesfull. Trying to remove large empty areas...
> Failed to calculate areas. See log for details.
> Failed to calculate areas.
> Sorry. Cannot split the file without creating huge, almost empty, tiles.
> Please specify a bounding polygon with the --polygon-file parameter.
> Time finished: Tue Dec 18 18:25:37 CET 2012
> Total time taken: 95s
>
> --
> keep on biking and discovering new trails
>
> Felix
> openmtbmap.org & www.velomap.org
>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev@lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev