Hi Paul, please try to describe what you mean with "node and way id's in the order of 1,000,000,000,000,000,000 are what is causing the error" Is it a special id that triggers the error? Gerd News-3 wrote
On 24/07/13 08:43, Gerd Petermann wrote:
Hi Paul,
I have no clue yet. Are you able to reproduce the error when you convert the input file to o5m or osm.pbf first? If yes, please upload the file and send a link.
Gerd
Gerd,
I've had some spare time today to do some experimentation and it seems that with --keep-complete=true (the default) then node and way id's in the order of 1,000,000,000,000,000,000 are what is causing the error. With --keep-complete=false then such node and way id's are acceptable so for now I'm re-writing the id's as part of the pre-processing but this would seem to be inconsistent behaviour in splitter
Hope that helps
Paul _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Splitter-Crash-tp5770025p5771352.html Sent from the Mkgmap Development mailing list archive at Nabble.com.