Hi Thorsten, attached is a patch for the problem reported here: http://gis.19327.n5.nabble.com/Bug-in-splitter-tp5610856p5610856.html I don't have the data nor the machine to test it, so I tried to find all places were nodes are counted and changed the variables to long. I did not find a good explanation for the small difference in the numbers: osmconvert reported 2518069911 nodes, which is ~ 2.518.069.911 -(2^31 - 1) = 370.586.264 - 2^31 + 370.586.264 =* -1.776.897.384* but splitter r200 reported * -1.776.905.107* nodes The formatting routine is not the reason. Any ideas? Gerd http://gis.19327.n5.nabble.com/file/n5611808/nodes_int_overflow_v1.patch nodes_int_overflow_v1.patch -- View this message in context: http://gis.19327.n5.nabble.com/Patch-Overflow-in-splitter-node-counters-tp56... Sent from the Mkgmap Development mailing list archive at Nabble.com.