Hi, On Mon, Feb 11, WanMil wrote:
Hi,
has the problem been solved or is there still something to explain? If the greater tolerance of mkgmap for mapping errors (ignore mp tags if name is set only) causes problems I think I should revert that.
I think you should revert that change. Looking at this example, the outcome is not always what we expect, and you cannot fix it in the style file. Thorsten
I see on my maps that all ways from http://www.openstreetmap.org/browse/relation/1338717 are rendered as country border now (mkgmap r-2479)
This relation contains only two tags: name = Hires coverage of Bing in Bulgaria type = multipolygon
No other tags, and yet it gets a admin_level=2 somehow. I think the relation contains ways with admin_level2 borders and gets 'contamined' with those tags.
Tested it with the default styles as well as mine, both render all those lines as international border. In mkgmap r2459 those lines were not rendered at all (as it should be), so i think there is a serious bug here.
I also get marine borders at some borders inland now (tagged with maritime=yes but they dont have those tags at all).
Use outer polygon tags if the multipolygon is tagged with name only
Quite a lot of mps are errorneously tagged with name only. This was ignored by the mp algorithm some time ago but at any point of time it disappeared. Fixing that now.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)