Hi Gerd, thesurveyor wrote
As I understand there is a rule within the style and there is at least an OSM object in the map which must come together that mkgmap will fail.
So from my point it is not clear where it must be fixed. You can fix it in the code of mkgmap, of course that is the best solution, but is it the only one?
Yes, with your data it was easy to identify: the problem is caused by an emty ref tag as in http://www.openstreetmap.org/browse/way/46197501 I've committed r2650 to handle this case, the binary is here: http://files.mkgmap.org.uk/download/141/mkgmap.jar I still have to analyse if the result of split() is used without checks elsewhere. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/java-lang-ArrayIndexOutOfBoundsException-0-tp... Sent from the Mkgmap Development mailing list archive at Nabble.com.