[mkgmap-dev] LOCATOR: doubt about "contains no name tag" messages

Wed Mar 30 17:23:50 BST 2011

El 24/03/11 19:18, WanMil escribió:
>>>> Processing spain.osm.pbf from Geofabrik I get several "contains no name
>>>> tag" messages that point to ways tagged in the form:
>>>> admin_level=8
>>>> boundary=administrative
>>>> It's true they don't have a tag name, but they belong to relations with
>>>> the same tags + a name and the relation is fully within the tile, so
>>>> it's supposed they should get the name from the relation. Additionally,
>>>> there are thousands of ways in Spain tagged in the same way (all
>>>> administrative boundaries were imported that way) that don't trigger the
>>>> same warning.
>>>> As an example you can have a look at way 45338454. It's about 2 km away
>>>> from the tile border.
>>>>
>>>>          
>>> Carlos,
>>>
>>> I wasn't able to reproduce your problem probably due to different input
>>> data or different splitter settings. Geofabrik seems to be down at the
>>> moment so no real chance to get the same input data.
>>>
>>> If way 45338454 is only 2 km away from the tile border than it might be
>>> possible that it is contained in two tiles due to the splitter overlap.
>>> Please check if the warning message applies to the tile in which the way
>>> and the relation is contained completely.
>>>
>>>        
>> No, it applies to the adjacent tile.
>>      
>>> Anyhow I have synchronized changes from the trunk to the locator branch.
>>> Please try again with these changes. At least it should reduce the
>>> number of such warning messages.
>>>
>>>        
>> I'm afraid I got exactly the same warnings after recompiling with the
>> new changes.
>>      
> Please send me your splitter settings, the splitters areas.list file and
> your mkgmap parameters.
Continuing with the checks I've found several cases where ways tagged as 
enclave/exclave (instead of inner/outer) in a relation are included in 
the warnings. Aren't these tags parsed by the locator?
Example ways: 45315429 and 45315431