I'll have a look. I didn't intentionally change extended type behaviour, but shapes will end up in different subdivisions with the option applied Ticker On Fri, 2016-12-02 at 07:09 -0700, Gerd Petermann wrote:
I've got some more test data from Arndt, I've reproduced the assertion, here is the test data: http://files.mkgmap.org.uk/download/316/test.zip
The problem seems to be caused by the new --order-by-decreasing-area option, if I remove that from the options file the problem is gone.
@Ticker: Do you have time to analyse it? I assume the problem is that we set a flag like "extended type points exist" and later remove the corresponding data. Does that ring a bell?
Gerd
Arndt Röhrig wrote
<!DOCTYPE html>
Hello everybody, i use mkgmap r3706. It run 2 times. The first one makes the img-files. The second one makes the mdr/mdrx files. The first step works fine, without error-messages, but the second step produces an error message and crashes: "Exception in thread "main" java.lang.AssertionError: Invalid label offset found 1315595 at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.fetchLabel(LBLFileReade r. java:87) at uk.me.parabola.imgfmt.app.trergn.RGNFileReader.fetchPointsCommon(RG NF ileReader.java:123) at uk.me.parabola.imgfmt.app.trergn.RGNFileReader.pointsForSubdiv(RGNF il eReader.java:84) at uk.me.parabola.imgfmt.app.map.MapReader.pointsForLevel(MapReader.ja va :119) at uk.me.parabola.mkgmap.combiners.MdrBuilder.addPoints(MdrBuilder.jav a: 273) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java :1 78) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:600) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader. ja va:128) at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:135) at uk.me.parabola.mkgmap.main.Main.main(Main.java:106)" When i use mkgmap 3702 an error message at the first step appears, the second step works fine: "SCHWERWIEGEND (ShapeMergeFilter): ..\Splitter\88000004.osm.pbf: ignoring shape w ith id 364926659 and type 0x13 at resolution 24, it has 4 points and has an empt y area" The OSM-Data is "nordrhein-westfalen.osm.pbf". An other map "Kanaran" works fine, without error. Whats the reason for this and what can i do? Best regards Arndt
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n8.nabble.com/Problem- with-r3706-tp5886790p5886799.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev