Hi! After upgrading to the release 2679 i get such exception during map compilation: Exception in thread "main" java.lang.AssertionError: mdr20 value changed f=293 t =295 count=357 at uk.me.parabola.imgfmt.app.mdr.Mdr5Record.setMdr20(Mdr5Record.java:129 ) at uk.me.parabola.imgfmt.app.mdr.Mdr20.buildFromStreets(Mdr20.java:116) at uk.me.parabola.imgfmt.app.mdr.MDRFile.writeSections(MDRFile.java:312) at uk.me.parabola.imgfmt.app.mdr.MDRFile.write(MDRFile.java:252) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onFinishForDevice(MdrBuild er.java:382) at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish(GmapsuppBuil der.java:161) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:560) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.ja va:128) at uk.me.parabola.mkgmap.main.Main.main(Main.java:119) I suppose that root of the problem lays in --lower-case --code-page=1250 switches, because without them everything works fine. Thank you in advance for any help :).
Hi
After upgrading to the release 2679 i get such exception during map compilation:
Can I ask which version you were using before? (or if you don't know exactly, the rough date).
Exception in thread "main" java.lang.AssertionError: mdr20 value changed f=293 t =295 count=357 at uk.me.parabola.imgfmt.app.mdr.Mdr5Record.setMdr20(Mdr5Record.java:129
I suppose that root of the problem lays in --lower-case --code-page=1250 switches, because without them everything works fine.
There was a chnage in r2662 in the sort order for code page 1250. If you are trying to create an index for files created with an earlier version of mkgmap with a version after - then that may cause problems and you should re-compile everything from scratch. Just a thought, it could be something entirely different. ..Steve
hi! Former version was 2606. Map is compiled from scratch. best regards Michal 2013/9/8 Steve Ratcliffe <steve@parabola.me.uk>
Hi
After upgrading to the release 2679 i get such exception during map compilation:
Can I ask which version you were using before? (or if you don't know exactly, the rough date).
Exception in thread "main" java.lang.AssertionError: mdr20 value changed f=293 t =295 count=357 at uk.me.parabola.imgfmt.app.mdr.Mdr5Record.setMdr20(Mdr5Record.java:129
I suppose that root of the problem lays in --lower-case --code-page=1250 switches, because without them everything works fine.
There was a chnage in r2662 in the sort order for code page 1250. If you are trying to create an index for files created with an earlier version of mkgmap with a version after - then that may cause problems and you should re-compile everything from scratch.
Just a thought, it could be something entirely different.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 09/09/13 08:36, Michał Rogala wrote:
Former version was 2606. Map is compiled from scratch.
I have not been able to reproduce this. I tried a complete map of Poland with --index --route --code-page=1250 --lower-case So for you does it always happen or is just one particular tile or set of tiles? I am going to need access to a specific of where it goes wrong. Best regards ..Steve
hi! Yes, it happens every time. Did you compile your maps with --gmapsupp switch? Both my scripts use it, also stack trace shows: at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish I use custom map extract (Poland and some border terrains of Germany, Czech Republic, itp): http://garmin.osmapa.pl/mkgmap/poland.extract.osm.zip here is splitted map: http://garmin.osmapa.pl/mkgmap/OSM-Poland-split-ogonki.zip Below are full mkgmap arguments I use. This works fine: java -enableassertions -Xmx1000m -jar {binarki}/mkgmap.jar --verbose --family-name=OSMapaPL --coastlinefile={dane_osm}/coastlines_europe.osm.pbf --read-config={mapa_root}/config/osmapa.config --bounds={dane_osm}/bounds --family-id={fid_glowna} --product-id={fid_glowna} --mapname=66{fid_glowna}001 --overview-mapname=66{fid_glowna}000 --description=OSMapaPL --series-name=OSMapaPL --style-file={binarki}/resources/styles/ --style={styl} --check-styles -c template.args style.typ' This doesn't: java -enableassertions -Xmx1000m -jar {binarki}/mkgmap.jar --family-name=OSMapaPL-OGONKI --coastlinefile={dane_osm}/coastlines_europe.osm.pbf --read-config={mapa_root}/config/osmapa_ogonki.config --bounds={dane_osm}/bounds --family-id={fid_ogonki} --product-id={fid_ogonki} --mapname=66{fid_ogonki}001 --overview-mapname=66{fid_ogonki}000 --description=OSMapaPL-OGONKI --series-name=OSMapaPL-OGONKI --style-file={binarki}/resources/styles/ --style={styl} --check-styles --lower-case --code-page=1250 -c template.args style.typ config file for both scripts is: verbose max-jobs country-name=Polska name-tag-list=name:pl,name generate-sea location-autofill=is_in tdbfile index add-pois-to-areas link-pois-to-ways remove-short-arcs preserve-element-order country-abbr=POL route net gmapsupp nsis check-styles process-exits x-housenumbers best regards Michal 2013/9/11 Steve Ratcliffe <steve@parabola.me.uk>
On 09/09/13 08:36, Michał Rogala wrote:
Former version was 2606. Map is compiled from scratch.
I have not been able to reproduce this. I tried a complete map of Poland with --index --route --code-page=1250 --lower-case
So for you does it always happen or is just one particular tile or set of tiles? I am going to need access to a specific of where it goes wrong.
Best regards ..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi
Yes, it happens every time. Did you compile your maps with --gmapsupp switch? Both my scripts use it, also stack trace shows: at uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onFinish
I did try that, although I hadn't noticed that line in stack trace which will help.
I use custom map extract (Poland and some border terrains of Germany, Czech Republic, itp):
http://garmin.osmapa.pl/mkgmap/poland.extract.osm.zip
here is splitted map: http://garmin.osmapa.pl/mkgmap/OSM-Poland-split-ogonki.zip
Thanks for the extracts and option lists I will try them out. ..Steve
Hi
I have fixed the problem, which was that space was being treated as an ignored character for sorting purposes in cp 1250. The commit message gives a bit more detail if you are interested! I found that it was only 66005025.img that had the problem. ..Steve
thank you! :) Michal 2013/9/16 Steve Ratcliffe <steve@parabola.me.uk>
Hi
I have fixed the problem, which was that space was being treated as an ignored character for sorting purposes in cp 1250.
The commit message gives a bit more detail if you are interested!
I found that it was only 66005025.img that had the problem.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
Michał Rogala -
Steve Ratcliffe