[OSM-talk] multipolygon inners that aren't inside.

Ian Dees ian.dees at gmail.com
Mon Jul 12 20:37:55 BST 2010


On Mon, Jul 12, 2010 at 2:27 PM, John Harvey <john at johnharveyphoto.com>wrote:

> It sure would be nice if users couldn't submit bad data.  Incorrect data
> (wrong street name) takes a human to spot, but bad topology (doesn't conform
> to the rules and a computer can verify conformance) shouldn't be possible to
> submit.  For instance look at this relation:
>
> http://www.openstreetmap.org/browse/relation/542980
>
> Two ways are marked as inners but nothing is inside anything else.  The
> problem is these kinds of errors present a barrier to entry for anyone using
> the OSM data - if you try to write a "by the books" renderer for this area
> you get a spill.  To render it correctly you have to test ways marked the
> inner are actually inside something marked outside.
>
>
For better or worse there is no "incorrect data". If your parser/renderer
can't handle data like this, then you should probably filter it out. You'll
have a very hard time convincing anyone to add the data integrity checks
that would be required on the API for this sort of thing.

Maybe you could write a bot that messages the owner of the relation when it
finds incorrect topology?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20100712/08f5e757/attachment.html>


More information about the talk mailing list