cascading multipolygon relations

In the wiki it is suggested to cascade two multipolygon relations in a case when we've got area #1 inside area #2 inside area #3: http://wiki.openstreetmap.org/wiki/Talk:Relation:multipolygon#Advanced_multi... Looks like mkgmap can't handle this. Should I convert such cases into some other form of relation, or should I just wait for mkgmap to support this? A sample of a lake inside swamp, swamp inside forest, currently described using cascaded relations, which mkgmap can't render: http://openstreetmap.org/?lat=55.58181&lon=36.96216&zoom=15&layers=B000FTF -- Totus tuus, Glebius. GLEB-RIPE

Hi! Gleb Smirnoff schrieb:
In the wiki it is suggested to cascade two multipolygon relations in a case when we've got area #1 inside area #2 inside area #3:
http://wiki.openstreetmap.org/wiki/Talk:Relation:multipolygon#Advanced_multi...
Looks like mkgmap can't handle this. Should I convert such cases into some other form of relation, or should I just wait for mkgmap to support this?
It is my belief that some of the use cases described for multipolygons are needlessly complicated. I would suggest to break down all relations to the most simple and readily understandable form possible. Otherwise we will just have a different interpretation in every renderer (and different versions thereof) resulting in a chaotic edit war with continuous changes depending in what renderer you want it to look good. In short: Yes, break it down. bye Nop

On Mittwoch 01 April 2009, Nop wrote:
It is my belief that some of the use cases described for multipolygons are needlessly complicated. I would suggest to break down all relations to the most simple and readily understandable form possible. Otherwise we will just have a different interpretation in every renderer (and different versions thereof) resulting in a chaotic edit war with continuous changes depending in what renderer you want it to look good.
That is also my belief. That's why I made a new suggestion there a few days ago. I really whould like to know how others think about this. But do discuss there not in this mailing list... Regards Andre

On Wed, Apr 01, 2009 at 06:36:57PM +0400, Gleb Smirnoff wrote: T> A sample of a lake inside swamp, swamp inside forest, currently described T> using cascaded relations, which mkgmap can't render: T> T> http://openstreetmap.org/?lat=55.58181&lon=36.96216&zoom=15&layers=B000FTF Well, I've broke this cascaded relation into a simple one multipolygon relation, and mkgmap still doesn't draw a lake in a middle of swamp. -- Totus tuus, Glebius. GLEB-RIPE

2009/4/12 Gleb Smirnoff <glebius@glebius.int.ru>:
Well, I've broke this cascaded relation into a simple one multipolygon relation, and mkgmap still doesn't draw a lake in a middle of swamp.
Hi! Have you tried zooming out or/and reducing detail on the device, in Mapsource or Qlandkarte? I observed that some (many) multipolygon holes only become visible when the low-detail version of the outer polygon is displayed... Example: this farmland near the stream "Logebach" I mapped last Weekend: http://informationfreeway.org/?lat=50.663655772998936&lon=7.287712349115571&... -Martin

2009/4/12 Martin Simon <grenzdebil@gmail.com>:
2009/4/12 Gleb Smirnoff <glebius@glebius.int.ru>:
Well, I've broke this cascaded relation into a simple one multipolygon relation, and mkgmap still doesn't draw a lake in a middle of swamp.
Hi!
Have you tried zooming out or/and reducing detail on the device, in Mapsource or Qlandkarte?
I observed that some (many) multipolygon holes only become visible when the low-detail version of the outer polygon is displayed...
Example: this farmland near the stream "Logebach" I mapped last Weekend: http://informationfreeway.org/?lat=50.663655772998936&lon=7.287712349115571&...
I had a second look at the multipolygons where this problem exists and found out that if I zoom in (on the device) with the cursor right on the edge of the multipolygon hole, I can select 2 "wood" polygons when the hole disappears. So i suspect that in high zoom levels, mkgmap cuts the holes correctly, but fills them with a polygon that has the same object type as the outer polygon. In my examples, this creates wood-in-wood polygons. Even though I can't code, I hope this helps to fix the problem... :-) -Martin
participants (4)
-
Andre Hinrichs
-
Gleb Smirnoff
-
Martin Simon
-
Nop