Coast branch generates bogus-looking multipolygon errors

Hi WanMil, I compiled today's finland.osm.pbf with mkgmap r1755 and then reverted to r1751, the revision just before you merged back the coast branch. r1751 does not generate these errors: 2010/12/26 22:11:54 WARNING (MultiPolygonRelation): 63240002.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427393507 contains errors. 2010/12/26 22:13:21 WARNING (MultiPolygonRelation): 63240001.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427403587 contains errors. 2010/12/26 22:15:02 WARNING (MultiPolygonRelation): 63240005.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427471668 contains errors. 2010/12/26 22:15:15 WARNING (MultiPolygonRelation): 63240004.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427463146 contains errors. 2010/12/26 22:15:39 WARNING (MultiPolygonRelation): 63240006.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427479870 contains errors. (Both revisions did complain about two dead-end oneways, which I fixed in the database.) The mkgmap.log.0 is 322973 bytes with r1751 and 3855601 bytes with r1755, which are comparable to the numbers that I posted for r1728, r1753 and the map data from 3 days ago (December 23). In other words, the change in the mkgmap.log.0 size seems to be due to the merge of the coast branch. You should be able to reproduce this as follows (simplified from my osm2img.sh). You will need the files areas.list, mkgmap.args, logging.properties, logging.ignore from http://www.polkupyoraily.net/osm/. wget http://download.geofabrik.de/osm/europe/finland.osm.pbf java -jar splitter.jar --split-file=areas.list finland.osm.pbf java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar \ -c mkgmap.args grep -vf logging.ignore mkgmap.log.0 Repeat the last two commands after recompiling mkgmap.jar. Best regards, Marko

Hi WanMil,
I compiled today's finland.osm.pbf with mkgmap r1755 and then reverted to r1751, the revision just before you merged back the coast branch. r1751 does not generate these errors:
2010/12/26 22:11:54 WARNING (MultiPolygonRelation): 63240002.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427393507 contains errors. 2010/12/26 22:13:21 WARNING (MultiPolygonRelation): 63240001.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427403587 contains errors. 2010/12/26 22:15:02 WARNING (MultiPolygonRelation): 63240005.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427471668 contains errors. 2010/12/26 22:15:15 WARNING (MultiPolygonRelation): 63240004.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427463146 contains errors. 2010/12/26 22:15:39 WARNING (MultiPolygonRelation): 63240006.osm.gz: Multipolygon http://www.openstreetmap.org/browse/relation/4611686018427479870 contains errors.
(Both revisions did complain about two dead-end oneways, which I fixed in the database.)
The mkgmap.log.0 is 322973 bytes with r1751 and 3855601 bytes with r1755, which are comparable to the numbers that I posted for r1728, r1753 and the map data from 3 days ago (December 23). In other words, the change in the mkgmap.log.0 size seems to be due to the merge of the coast branch.
You should be able to reproduce this as follows (simplified from my osm2img.sh). You will need the files areas.list, mkgmap.args, logging.properties, logging.ignore from http://www.polkupyoraily.net/osm/.
wget http://download.geofabrik.de/osm/europe/finland.osm.pbf java -jar splitter.jar --split-file=areas.list finland.osm.pbf java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar \ -c mkgmap.args grep -vf logging.ignore mkgmap.log.0
Repeat the last two commands after recompiling mkgmap.jar.
Best regards,
Marko
Hi Marko, great work! Your detailed analysis helped a lot to find the problem. It is fixed in r1760. Have fun! WanMil

Hi WanMil,
The mkgmap.log.0 is 322973 bytes with r1751 and 3855601 bytes with r1755, which are comparable to the numbers that I posted for r1728, r1753 and the map data from 3 days ago (December 23). In other words, the change in the mkgmap.log.0 size seems to be due to the merge of the coast branch. great work! Your detailed analysis helped a lot to find the problem. It is fixed in r1760.
Thank you for fixing the bug. I confirm that r1760 is OK. The mkgmap.log.0 for today's dump is 323685 bytes with both r1751 and r1760, and after stripping the timestamps and sorting the lines, the output is identical, except for some generated polygon IDs. Also the gmapsupp.img is the same size with both r1751 and r1760. Marko
participants (2)
-
Marko Mäkelä
-
WanMil