WanMil wrote:
What do you mean with "tagging the 'inner' of a multipolygon"? I have reimplemented the whole mulitpoylgon code so I am very interested in problems that still exist.
Can you give a relation id which makes problems? I'm using r1505 on an Oregon 300 using the latest firm/software.
http://www.openstreetmap.org/browse/relation/383291
With these tags added to the inner relation the void doesn't fully show on the Garmin. There is a thin slit where it should be a sort of sausage shape. <tag k='name' v='River Avon' /> <tag k='waterway' v='riverbank' />
Because there's that slit it's as if with those tags, the inner polygon has been some width.
If I remove them it works.
I thought it might be because I also had waterway=river, width=15 but by using an extraction of OSM& deleting those ways manually from the XML data, I verified that wasn't the cause.
Cheers Dave F.
Dave, I compiled a map using default style that covers the relation. There were no problems with the relation (the island shows as big as expected on my Oregon). But http://www.openstreetmap.org/browse/way/37737680 overlaps the river and produces a very wide bridge. This is either a data or a style problem. As far as I could see the multipolyon code works as expected. WanMil