Hi, I am processing a contours file that is 95MB in Gzipped format. If I don't use the --cache option then splitter gets confused and doesn't count the nodes properly, putting all the data into a single file: java -Xmx1500m -ea -jar "../../splitter/splitter-r97/splitter.jar" --mapid=63240201 Scotland_contours.osm cache= description= geonames-file= legacy-mode=false mapid=63240201 max-areas=255 max-nodes=1600000 mixed=false overlap=2000 resolution=13 split-file= write-kml= Time started: Fri Oct 16 12:25:48 BST 2009 Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high The input osm file(s) will be re-parsed during the split (slower) because no --cache parameter was specified Processing Scotland_contours.osm A total of 21,813 nodes, 0 ways and 0 relations were processed in 1 file Min node ID = 1000000000 Max node ID = 1000021812 Time: Fri Oct 16 12:25:49 BST 2009 Exact map coverage is (56.000404357910156,-7.9987335205078125) to (60.38789749145508,-0.0012445449829101562) Rounded map coverage is (55.986328125,-8.0419921875) to (60.46875,0.0439453125) Splitting nodes into areas containing a maximum of 1,600,000 nodes each... 1 areas: Area 63240201 covers (0x27d000,0xfffa4800) to (0x2b0000,0x800) Writing out split osm files Fri Oct 16 12:25:49 BST 2009 Processing 1 areas in a single pass Starting pass 1 of 1, processing 1 areas (63240201 to 63240201) Processing Scotland_contours.osm Writing ways Fri Oct 16 12:25:49 BST 2009 2,500,000 nodes processed... 5,000,000 nodes processed... 7,500,000 nodes processed... Wrote 8,591,927 nodes, 113,945 ways, 0 relations Time finished: Fri Oct 16 12:27:47 BST 2009 Total time taken: 118s If I use the --cache option, it works properly. Here's the output this time: java -Xmx1500m -ea -jar "../../splitter/splitter-r97/splitter.jar" --cache=cache --mapid=63240201 Scotland_contours.osm cache=cache description= geonames-file= legacy-mode=false mapid=63240201 max-areas=255 max-nodes=1600000 mixed=false overlap=2000 resolution=13 split-file= write-kml= Time started: Fri Oct 16 12:00:00 BST 2009 Checking for an existing cache and verifying contents... No suitable cache was found. A new cache will be created to speed up the splitting stage Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high Processing Scotland_contours.osm 2,500,000 nodes processed... 5,000,000 nodes processed... 7,500,000 nodes processed... A total of 8,591,927 nodes, 113,945 ways and 0 relations were processed in 1 file Min node ID = 1000000000 Max node ID = 1008591926 Time: Fri Oct 16 12:01:30 BST 2009 Exact map coverage is (56.000404357910156,-7.9987335205078125) to (60.38789749145508,-0.0012445449829101562) Rounded map coverage is (55.986328125,-8.0419921875) to (60.46875,0.0439453125) Splitting nodes into areas containing a maximum of 1,600,000 nodes each... 7 areas: Area 63240201 covers (0x27d000,0xfffa8800) to (0x28a000,0xfffc3800) Area 63240202 covers (0x27d000,0xfffc3800) to (0x28a000,0xfffcc800) Area 63240203 covers (0x28a000,0xfffa8800) to (0x290000,0xfffcc800) Area 63240204 covers (0x290000,0xfffa4800) to (0x2ab000,0xfffcc800) Area 63240205 covers (0x27d000,0xfffcc800) to (0x28e000,0xfffd6800) Area 63240206 covers (0x27d000,0xfffd6800) to (0x28e000,0xffff5800) Area 63240207 covers (0x28e000,0xfffcc800) to (0x2b0000,0x800) Writing out split osm files Fri Oct 16 12:01:30 BST 2009 Processing 7 areas in a single pass Starting pass 1 of 1, processing 7 areas (63240201 to 63240207) Loading and processing nodes 2,500,000 nodes processed... 5,000,000 nodes processed... 7,500,000 nodes processed... Loading and processing ways Writing ways Fri Oct 16 12:02:54 BST 2009 Loading and processing relations Wrote 8,591,927 nodes, 113,945 ways, 0 relations Time finished: Fri Oct 16 12:03:14 BST 2009 Total time taken: 193s -- Charlie