This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
osm2pgsql does not handle role=outer and role=inner on same polygon #1308
Assignees
Comments
|
Author: steve8[at]mdx.ac.uk Re-assign to jburgess |
|
Author: jburgess777[at]googlemail.com I think this should be fixed now. There were two underlying issues in osm2pgsql relating to the orientation and tagging of ways in multiple relations. You may not see the full benefit of these changes until things start to re-render after the bulk import on Wednesday. |
|
Author: pnorman Believed to be fixed. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reporter: gustav[at]foseid.priv.no
[Submitted to the original trac issue database at 7.30pm, Friday, 31st October 2008]
If you have a polygon that is both inner in one mulitpolygon and outer in another, rendering fails. Example: A lake is a whole in a forest (forest polygon=outer and the lake=inner). This lake may have islands (lake=outer and islands=inner).
See also http://lists.openstreetmap.org/pipermail/talk/2008-November/031080.html
The text was updated successfully, but these errors were encountered: