<br><br><div class="gmail_quote">On Wed, Oct 17, 2012 at 1:37 PM, Peter Wendorff <span dir="ltr"><<a href="mailto:wendorff@uni-paderborn.de" target="_blank">wendorff@uni-paderborn.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Igor.<br>
But if we're talking about topology, why (as I understand it) are
you trying to force topological stuff in the multipolygon
RELATION?<br>
That solves, well... nearly nothing.<br>
You have to do exactly the same work for any topological issues
that are not described by a mp relation, e.g. because they aren't
multipolygons, but distinct buildings, forests, water-surfaces or
whatever.<br>
There you have to do exactly what you don't want to do here and
where you want to have further restriction for multipolygon
relations.<br>
<br>
I would suggest you to work on the progress towards area types to
be part of the future api: discussion, decision and
implementation.<br>
I would like to see additional topology introduced: along,
beneath, .... are interesting, but yet difficult to get
topological relations for osm data users.<br>
<br>
But: Keep in mind that editing should not become more difficult
for mappers. If topology requires to assemble complex relations
that's no option.<br>
<br><br></div></div></blockquote><div><br></div><div>Hi Peter,</div><div><br></div><div>Maybe I haven't made myself clear: I haven't started this discussion to propose any kind of change in the OSM data structures or "rules" how to tag things. I'm merely trying to figure out ways to extract as much useful data from the existing OSM data and structures as possible. The problem with multipolygon handling is that it is a moving target. The rules have changed a lot and are still changing. I know, since I've been implementing MP processors ever since the first versions of Kosmos and every time I take a look at the Wiki page, I find some new stuff that makes my MP processing logic obsolete or not good enough. A lot of decisions have been made just to prevent breaking existing behavior, I can understand that, but some of those decision were not really good ones. So when anyone claims the OSM's MP concept is simple and straightforward, I beg to differ ;)</div>
<div><br></div><div>Igor</div></div>