On 26/09/2012 15:42, Marko Mäkelä wrote:
On Wed, Sep 26, 2012 at 12:04:59PM +0100, Roger Calvert wrote:

If a relation has the same name as one of its components (or perhaps 
any name), the name of the component is lost.

I identified this on way 4798060, a small lake called 'High Dam'.  
Because there are islands in the lake, it is the outer component of 
relation 1369084, which also had the name 'High Dam'. Following mkgmap 
processing, the lake came out with its default name 'Reservoir'.  
However, when I removed the name from the relation, it came out with 
its correct name. (It appears correctly on OSM renderings such as 
mapnik).

I believe that the correct fix would have been to remove the name from 
the role=outer ways and keep the name in the relation. Similarly, remove 
any natural=water from the outer way(s) and add them to the relation.  
This would make the multipolygon unambiguous.

	Marko
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I'm sure this is correct, but it is not very intuitive to the mapper, particularly as the relation may be created by someone other than the original mapper. For example, mapper A puts in the lake, and some time later, mapper B puts in more detail, including the islands and the relation. I am sure there are many cases where this may happen or has happened - I found this one by chance as it is in my local area. It would be nice if all mappers were perfect, but .........

It would be helpful if some workround could be found in mkgmap. All the other renderings I have looked at seem able to handle it. If the relation name and the polygon name (or other tags) are different, I agree there is a problem. But if they are the same, I don't think the result should be that the polygon loses its name completely.

Roger
--

Roger Calvert