[OSM-dev] Moving to stricter multipolygon parsing
yvecai at gmail.com
Fri Jun 13 07:53:50 UTC 2014
+1 for consistency
MP would be easier to learn from example if a single method 'works'.
On 13 juin 2014 01:25:42 UTC+02:00, Paul Norman <penorman at mac.com> wrote:
>Osm2pgsql currently tries *very* hard to turn multipolygon relations
>geometries. It currently detects two types of MP relations, new-style
>old-style. A new-style MP has tags on the relation while an old-style
>only has type=multipolygon on the relation and relies on the ways for
>It then tries to deal with odd tagging in various ways. MP handling is
>of the biggest sources of osm2pgsql bug reports and a big time-sink.
>One of the bigger issues is moving tags from ways to MPs that are
>detected as old-style. This is an attempt to interpret flawed tagging.
>I think we need to move to a more strict parsing of MPs, accepting only
>new-style MPs and old-style MPs where all outers have identical
>tags and the relation itself has no non-deleted tags.
>Osm2pgsql is not just a consumer of data, it is one of the main
>tools, so it is strongly integrated into the feedback cycle, so if
>doesn't process a multipolygon, a mapper will likely correct the
>doing this, it will make it easier for those interpreting raw OSM data.
>To support this, I looked for some numbers. Using a shortened deleted
>list, there are 1 million new-style and 261k old-style MPs. Of the
>256k have a member with role outer. 251k of these have entirely
>tags on outers, while 2.3k have two sets of tags among the ways. About
>have three or more. An old-style MP without entirely consistent tags
>outers is ambiguous and in error.
>: A deleted tag is one such as source that osm2pgsql is dropping
>dev mailing list
>dev at openstreetmap.org
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev