[mkgmap-dev] Error in Africa?

Sun Aug 2 14:44:48 BST 2020

Hello, all!

Does this tile happen to contain the Port Said area near Cairo, Egypt? 
If so, you may be facing the same problem that I encountered in 
splitter. Splitter only limits the number of nodes in a tile. It ought 
to limit the number of ways as well. The Port Said area has an immense 
number of single city block length streets not joined into longer 
streets. I have built maps for the entire planet. That is the only place 
that I found that had that problem. The solution was to build Africa 
using a max nodes value of about 600 thousand nodes as you did, which 
brought the number of ways down sufficiently to avoid the problem in 
mkgmap. If splitter had an option to limit the number of nodes, then 
splitter would have divided the Port Said tile sufficiently that just 
those tiles would have had to be made small.

Randolph J. Herber

On 7/31/2020 3:09 PM, valentin3151 at gmail.com wrote:
> Re: Error in Africa? Hi Ticker, hi Gerd,
> thanks for your attention.
>
> I continue to do my experiments. I tried to compile the map from this 
> one 63240201.osm.pbf with and without the --gmapsupp option (of course 
> to an empty output folder). I get the same result on my two FreeBSD 
> servers and my Windows home computer. I am getting this error on all 
> my systems.
>
> Command line for testing:
> java -jar ^
>        D:\OSM\mkgmap\mkgmap-r4564\mkgmap4564.jar ^
>        --output-dir=D:\Garmin\test\ ^
>        --family-name="OSM test %date%" ^
>        --series-name="OSM test %date%" ^
>        --overview-mapname="OSM_test" ^
>        --area-name="OSM Test %date%" ^
>        --family-id=480 ^
>        --read-config=./config2018/optionsfile.args ^
>        --mapname=63080000 ^
>        --style-file=Config2018 ^
>        --tdbfile ^
>          --bounds=D:\OSM\mkgmap\boundary\world ^
>        --road-name-config=./config2018/roadNameConfig.txt ^
>        --name-tag-list=name:en,int_name,name ^
>        --code-page:65001 --style-option=code-page=1250 ^
>        ./config2018/OSM-2018.txt --description="OSM test" ^
>        --gmapsupp ^
>        --add-boundary-nodes-at-admin-boundaries=3 ^
>        D:\OSM\test\63240201.osm.pbf
>
> Link to my Style files:
> https://maptourist.org/osm-garmin/CurrentConfigs/
>
> Earlier I found a way to fix this error when I use the 
> --max-nodes=600000 value. But this will produce an extremely large 
> number of tiles! I really don't like this result. The same number of 
> tiles is produced by the splitter when I making a map of the whole of 
> Europe without the --max-nodes option. The compilation of the map of 
> Europe is stable and looks very good without errors. But the original 
> europe-latest.o5m is four times larger than africa-latest.o5m!
> I see this is an old and complex spiltter problem. I'm just trying to 
> find out how OSM data is causing this error. It is still unpredictable 
> for me.
>
>
>
>
> 	Hi Ticker, hi Valentin
>
> my understanding is that the error message from MapSplitter was a 
> false positive because mkgmap reports 0
> MapFailedExceptions.
>
> The crash with IndexOutOfBoundsException occurs in the final combiner 
> phase for the gmapsupp. It might be caused by an I/O error or a 
> corrupted *.img file.
>
> @Valentin: If you didn't already try that I suggest to clear the 
> directory and restart the compilation. If that produces the same 
> IndexOutOfBoundsException  please try again without the file 
> 63240201.osm.pbf. Only if that works fine we can be sure that 
> 63240201.osm.pbf is causing the crash.
>
> ciao,
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <[hidden email] 
> </user/SendEmail.jtp?type=node&node=5971915&i=0>> im Auftrag von 
> Ticker Berkin <[hidden email] 
> </user/SendEmail.jtp?type=node&node=5971915&i=1>>
> Gesendet: Freitag, 31. Juli 2020 17:01
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Error in Africa?
>
> Hi Valentin & Gerd
>
> @Gerd, have you started looking at this?
>
> The initial error is related to the splitting of the tile into
> subdivisions and is VERY dependent on the size and layout of all map
> elements in the tile, which will depend on the style and many options
> as well as the actual OSM input.
>
> If not using the default style, can you zip up and post what you are
> using, also mkgmap command line and options.
>
> The exception happens later but is probably a consequence of the split
> failure.
>
> Ticker
>
> On Thu, 2020-07-30 at 23:33 +0300, [hidden email] 
> </user/SendEmail.jtp?type=node&node=5971915&i=2> wrote:
>
> > Hi all,
> > My daily compilation of Africa was stopped because error is appear:
> > SEVERE (MapSplitter): 63240201.osm.pbf: Single item predicted to
> > exceed subdivision
> > http://www.openstreetmap.org/?mlat=10.412207&mlon=-13.010709&zoom=17
> >         Number  of  MapFailedExceptions:  0 Exception in thread
> > "main"
> >         java.lang.IndexOutOfBoundsException:  Index:  113,  Size: 3
> >         at java.util.ArrayList.rangeCheck(Unknown Source)
> >         at java.util.ArrayList.get(Unknown Source)
> >         at
> > uk.me.parabola.imgfmt.app.net.NETFileReader.getRoads(NETFileReader.ja
> > va:116)
> >         at
> > uk.me.parabola.imgfmt.app.map.MapReader.getRoads(MapReader.java:205)
> >         at
> > uk.me.parabola.mkgmap.combiners.MdrBuilder.addStreets(MdrBuilder.java
> > :298)
> >         at
> > uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java:1
> > 71)
> >         at
> > uk.me.parabola.mkgmap.combiners.GmapsuppBuilder.onMapEnd(GmapsuppBuil
> > der.java:164)
> >         at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:665)
> >         at
> > uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.ja
> > va:125)
> >         at uk.me.parabola.mkgmap.main.Main.mainStart(Main.java:144)
> >         at uk.me.parabola.mkgmap.main.Main.main(Main.java:115)
> >
> > Link to my tile where the error is:
> > https://maptourist.org/tmp/63240201.osm.pbf
> >
> > I tried to find the cause of this error in OSM but could not. The
> > link
> > from  above  error  log  points  to  the  location  with completely
> > no
> > data somewhere in the middle of Guinea.
> > As  an  experiment, I loaded the problem  tile  into  JOSM  and
> >  fixed
> > all  automatically found errors. Then I tried to compile the
> > corrected
> > file. No positive effect. The error is still there.
> > I use mkgmap-r4564, but I found there is no dependency with other
> > versions.
> > How  do  I  find what exactly is causing this error in the OSM data?
> > Previously, this map was compiled many times over a long time without
> > such problem.
> >
> >
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email] </user/SendEmail.jtp?type=node&node=5971915&i=3>
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> [hidden email] </user/SendEmail.jtp?type=node&node=5971915&i=4>
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
>
> ------------------------------------------------------------------------
> *If you reply to this email, your message will be added to the 
> discussion below:
> *http://gis.19327.n8.nabble.com/Error-in-Africa-tp5971902p5971915.html
> To unsubscribe from Mkgmap Development, click here 
> <http://gis.19327.n8.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5324443&code=dmFsZW50aW4zMTUxQGdtYWlsLmNvbXw1MzI0NDQzfC0xMDQyNTE0Njg2>.
> NAML 
> <http://gis.19327.n8.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
>
>
>
>
>
> /--
> С уважением,
>  Valentin3151 /mailto:valentin3151 at gmail.com
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20200802/f6b719bd/attachment-0001.html>