[mkgmap-dev] New locator branch

Fri Mar 18 13:55:33 GMT 2011

> Hi,
>
> I did a test of the whole Benelux area plus border regions, splitted from the europe extract, and found a lot of cities in the border areas that were assigned to the wrong country. So I don't agree that admin_level=2 is working fine.

Ok, it would work in case the algorithm is slightly improved. But I am 
sure that this will work very well. The changes are not too complicated.

>
> I also observed a lot of elements that were not processed because they did not contain a name tag, for example http://www.openstreetmap.org/browse/way/93135578. Of course it has no name, because it belongs to two place name relations: Ter Aar and Nieuwveen, http://www.openstreetmap.org/browse/relation/1354658 and http://www.openstreetmap.org/browse/relation/1354654 The fact that the complete relations are not completely within the tile can be a reason for this warning? Despite the warning, most of the streets in those areas seemed assigned to the correct place names btw. So it seems functioning and I'm happy with it, apart from the wrong country names. The mkgmap compiling time for the whole Benelux area grew from 1,5u to roughly 2 hours.
>

At a first reaction I would say that way 93135578 is tagged wrong. The 
boundary tags should be added to the relation only and not to the way 
itself.
But now I am quite unsure if that doesn't uncover a problem in the 
multipolygon processing of mkgmap. Usually tags in the outer ways that 
are equal to relation tags are removed after multipolygon processing. So 
the way 93135578 should have no tags when the location handling is 
started. Maybe the cause is that the relations do not tag the ways with 
"outer". I have to check that.

Can you send me your splitter areas? Which dump do you use? This will 
help me to analyze the problem.

Thanks
WanMil

>
>
> WanMil wrote:
>
> For admin_level=2 it works. The problem starts with the other levels.
> The assignment between admin_level and is_in:xxx tag is somehow country
> specific.
>