Re: [mkgmap-dev] error handling in splitter

Hi Gerd, this sounds very reasonable! How about implementing this like the way mkgmap handles it? If given the option --keep-going it will continue as splitter does now and the new default would be to stop processing? BTW: Last time i suspected mkgmap to produce bad maps, it was because of a corrupted *.o5m, which splitter happily converted to useless data. So again, yes, i would love this new behavior! Cheers, Uli -- View this message in context: http://gis.19327.n5.nabble.com/error-handling-in-splitter-tp5806188p5806198.... Sent from the Mkgmap Development mailing list archive at Nabble.com.