Hi Toby,
I didn't get this exception prior to applying the patch:
/-------- | Exception in thread "main" java.lang.IllegalStateException: Offset not known yet. | at uk.me.parabola.imgfmt.app.lbl.POIRecord.getOffset(POIRecord.java:377) | at uk.me.parabola.imgfmt.app.trergn.Point.write(Point.java:61) | at uk.me.parabola.imgfmt.app.trergn.RGNFile.addMapObject(RGNFile.java:96) | at uk.me.parabola.imgfmt.app.map.Map.addMapObject(Map.java:237) | at uk.me.parabola.mkgmap.build.MapBuilder.processPoints(MapBuilder.java:817) | at uk.me.parabola.mkgmap.build.MapBuilder.makeSubdivision(MapBuilder.java:697) | at uk.me.parabola.mkgmap.build.MapBuilder.makeMapAreas(MapBuilder.java:633) | at uk.me.parabola.mkgmap.build.MapBuilder.makeMap(MapBuilder.java:178) | at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:90) | at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) | at uk.me.parabola.mkgmap.main.Main.processFilename(Main.java:163) | at uk.me.parabola.mkgmap.CommandArgs$Filename.processArg(CommandArgs.java:340) | at uk.me.parabola.mkgmap.CommandArgs.readArgs(CommandArgs.java:119) | at uk.me.parabola.mkgmap.main.Main.main(Main.java:98) \--------
Could that be caused by the parallelisation?
Absolutely! I have weeded a few similar bugs out but, obviously, some are still lurking and are not being triggered by my test maps. I shall investigate. Cheers, Mark PS - if any other diagnostic messages appeared before the exception, please post them here.