Hi all, I noticed that splitter has a major performance lag on osm.pbf files compared to o5m. splitting off my DACH region in pbf format takes 15min 45sec, while splitting the same region in o5m format is finished after 5min 17sec. So it takes almost 3 times as long splitting pbf data. mkgmap on the other hand has almost no difference at all when building the DACH map from the pbf-tiles, compared to o5m-tiles. mkgmap with pbf takes 12min 28sec, with o5m 12min 09sec. here are my command lines: java -ea -XX:+AggressiveHeap -jar splitter-r597/splitter.jar > splitter.log --geonames-file=cities15000.zip --mapid=65000001 --output=pbf --precomp-sea=sea-latest.zip --write-kml=dach.kml --keep-complete --overlap=0 --max-nodes=1200000 dach.osm.pbf java -ea -XX:+AggressiveHeap -jar splitter-r597/splitter.jar > splitter.log --geonames-file=cities15000.zip --mapid=65000001 --output=o5m --precomp-sea=sea-latest.zip --write-kml=dach.kml --keep-complete --overlap=0 --max-nodes=1200000 dach.o5m Any ideas why pbf splitting is so slow compared to o5m splitting ? Ciao, Franco