Moin, I have a problem with mkgmap version r1699: it crashes while generating my maps. With r1673 everything was ok. It does not seem to be related to the style, I tried different layers of my maps and all are crashing. I use the following mkgmap command line and get this error message: java -jar -Xmx6144M ../../mkgmap-r1699/mkgmap.jar --style-file=../../styles/09_maxspeed --remove-short-arcs=5 --transparent --family-id=49 --country-name="Deutschland" --country-abbr="D" --overview-name="Tempolimits" --family-name="Tempolimits" --series-name="Tempolimits" --description="Tempolimits" --tdbfile --draw-priority=23 --max-jobs=3 -c maplist.txt java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation.processEle (MultiPolygonRelation.java:818) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.endRelation( mlHandler.java:620) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.endElement(O lHandler.java:590) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.end nt(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.xinclude.XIncludeHandler.endE t(XIncludeHandler.java:1014) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l.scanEndElement(XMLDocumentFragmentScannerImpl.java:1774) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2930) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.n MLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl (XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.pa ML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.pa ML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLPa java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.par stractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXPar arse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5 taSource.java:84) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:1 at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:189) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:186) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:30 at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoo utor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe .java:907) at java.lang.Thread.run(Thread.java:619) Exiting - if you want to carry on regardless, use the --keep-going option Gruss Torsten
Hi Torsten, I can confirm that this is a problem of the MultiPolygon code that has been changed with r1694. Attached patch fixes that. But I am not sure in what situations the bug happens. Could you do me a favour and run mkgmap with the following log.properties file? === .level=SEVERE handlers: java.util.logging.FileHandler java.util.logging.FileHandler.level=FINE java.util.logging.FileHandler.formatter=uk.me.parabola.log.UsefulFormatter java.util.logging.FileHandler.limit=1000000 java.util.logging.FileHandler.count=4 java.util.logging.FileHandler.pattern=mkgmap.log java.util.logging.FileHandler.append=false uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation.level=FINE === Please run it without the --keep-going option and send me the logfile with the exception which should be mkgmap.log.0. Thanks! WanMil
Moin,
I have a problem with mkgmap version r1699: it crashes while generating my maps.
With r1673 everything was ok.
It does not seem to be related to the style, I tried different layers of my maps and all are crashing.
I use the following mkgmap command line and get this error message:
java -jar -Xmx6144M ../../mkgmap-r1699/mkgmap.jar --style-file=../../styles/09_maxspeed --remove-short-arcs=5 --transparent --family-id=49 --country-name="Deutschland" --country-abbr="D" --overview-name="Tempolimits" --family-name="Tempolimits" --series-name="Tempolimits" --description="Tempolimits" --tdbfile --draw-priority=23 --max-jobs=3 -c maplist.txt
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at uk.me.parabola.mkgmap.reader.osm.MultiPolygonRelation.processEle (MultiPolygonRelation.java:818) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.endRelation( mlHandler.java:620) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5XmlHandler.endElement(O lHandler.java:590) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.end nt(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.xinclude.XIncludeHandler.endE t(XIncludeHandler.java:1014) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l.scanEndElement(XMLDocumentFragmentScannerImpl.java:1774) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2930) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.n MLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl (XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScann l.scanDocument(XMLDocumentFragmentScannerImpl.java:510) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.pa ML11Configuration.java:807) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.pa ML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLPa java:107) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.par stractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXPar arse(SAXParserImpl.java:522) at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) at javax.xml.parsers.SAXParser.parse(SAXParser.java:198) at uk.me.parabola.mkgmap.reader.osm.xml.Osm5MapDataSource.load(Osm5 taSource.java:84) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:1 at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:189) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:186) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:30 at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoo utor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe .java:907) at java.lang.Thread.run(Thread.java:619) Exiting - if you want to carry on regardless, use the --keep-going option
Gruss Torsten _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
WanMil schrieb am 20.09.2010 20:37:
But I am not sure in what situations the bug happens. Could you do me a favour and run mkgmap with the following log.properties file?
Is this problem already solved with r1700? Otherwise I have to admit, that I do not know how to run mkgmap with a log.properties file. So could you please explain me, how to use such a file. Gruss Torsten
On Tue, Sep 21, 2010 at 07:01:21PM +0200, Torsten Leistikow wrote:
WanMil schrieb am 20.09.2010 20:37:
But I am not sure in what situations the bug happens. Could you do me a favour and run mkgmap with the following log.properties file?
Is this problem already solved with r1700?
Otherwise I have to admit, that I do not know how to run mkgmap with a log.properties file. So could you please explain me, how to use such a file.
java -Dlog.config=log.properties ... -jar mkgmap.jar ... Marko
Torsten, thanks for sending me your logfiles (apart the mailing list). The "Grüngürtel" multipolygon of Cologne (http://www.openstreetmap.org/browse/relation/1152542) caused the Exception. It is defined wrong. The inner way http://www.openstreetmap.org/browse/way/30777954 lies inside the another inner way http://www.openstreetmap.org/browse/way/75211982. This is not allowed. Usually mkgmap logs some warnings about this and does not throw an exception. This has been fixed with r1700 so the problem should not exist any more. WanMil
On Tue, Sep 21, 2010 at 07:01:21PM +0200, Torsten Leistikow wrote:
WanMil schrieb am 20.09.2010 20:37:
But I am not sure in what situations the bug happens. Could you do me a favour and run mkgmap with the following log.properties file?
Is this problem already solved with r1700?
Otherwise I have to admit, that I do not know how to run mkgmap with a log.properties file. So could you please explain me, how to use such a file.
java -Dlog.config=log.properties ... -jar mkgmap.jar ...
Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hello, I sometimes use the default Mkgmap style, editing some of the resolutions to display at lower zoom levels. I use the following splitter switches. I set the --resolution=12 as the default style has natural=coastline [0x15 resolution 12] java -ea -Xmx2500m -jar splitter.jar --geonames-file=AU.txt --mapid=40000001 --resolution=12 --no-trim --overlap=50000 myaustralia.osm And this for Mkgmap. java -Xms3500m -ea -jar mkgmap.jar --family-name=Mydefault --series-name=MyDefault --style-file=o:\garmin\mkgmap\resources\styles\default --nsis --net --route --remove-short-arcs --drive-on-left --check-roundabouts --make-poi-index --add-pois-to-areas --max-jobs --location-autofill:1 --tdbfile --index --preserve-element-order -c template.args What I have found is that only --overlap=50000 produces perfect maritime borders fully around Australia anything other than 50000, gaps are produced in the maritime borders. I have tried overlap 2000, 6000, 10,000, 15,000, 20,000 30,000, 49,000. Also for other styles I have used, I find --overlap=50000 works the best also. I use the default max nodes as this seems to work fine for me. I tried decreasing the max nodes but then --overlap=50000 is way to high and I then use --overlap=6000 but will have some gaps in the maritime borders. Not too much of a problem as 50000 works perfectly for me, but I was wondering if this maybe a bug. This is what I use in osmosis to produce the MyAustrala.osm file. bin\osmosis.bat -v --rx -b500 enableDateParsing=no file=planet.new.osm.gz --bb top=-6 left=107.1 bottom=-48 right=163.5 completeWays=yes completeRelations=yes --wx -bc500 file=o:\garmin\splitter\myAustralia.osm Regards, Markus_g
participants (4)
-
Marko Mäkelä -
Markus -
Torsten Leistikow -
WanMil