[mkgmap-dev] Wishlist: Better multipolygon error reporting

Fri Jul 6 09:45:15 BST 2012

> On Thu, Jul 05, 2012 at 10:03:18PM +0200, WanMil wrote:
>>> 2012/07/05 21:37:39 WARNING (MultiPolygonRelation): 63240005.osm.pbf:
>>> Polygon 4611686018427683240(7P)(31081024[7P]) carries role inner but
>>> lies inside an inner polygon. Potentially its role should be outer.
>>
>> This message tells you all, almost :-)
>> Way 31081024 with 7 points is assigned with the role inner. But it is
>> not an inner polygon. It lies completely within way 168463590 which
>> also has role inner. This is not allowed in mps. So mkgmap assumes that
>> way 31081024 has role outer and the tagging is a mistake.
>
> Thanks, I fixed this now. Recently, Someone added lots of islands from
> Bing images (originally with natural=coastline) around the existing
> ones, which were added from Landsat images years ago.
>
> Where did you get the 168463590? By looking at the map?

Yes, I downloaded the mp with JOSM and looked around the way 31081024.
You could also get the way number using the FINE debug level for 
multipolygons. In this level the contains matrix is printed (which 
polygon is inside which other polygons). But you will get that for all 
multipolygons and therefore it is not very useful.

I think about a little change in the mp debugging. What do you think:
You can set an environment variable (or a logging parameter? I don't 
know if that's possilbe). This variable contains a comma separated list 
of mps that should be traced, e.g. MP_TRACE=1239779,124484. For all mps 
listed in this variable all debug messages are printed out with a 
separate logger and log level INFO (or WARN or ERROR).

This would make it possible to get detailed information about some mps 
without getting tons of logfiles.

WanMil

>
> Best regards,
>
> 	Marko
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>