You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: travelling_salesman [Submitted to the original trac issue database at 7.31pm, Tuesday, 11th June 2013]
Every few weeks I find a destroyed multipolygon relation in my mapping area, of which segements are deleted so that mapnik cannot render them anymore. The associated editor is always potlach2. And the responsible mappers are always unaware of the damage they do. This is because potlach2 doesn't make clear enough that a way is part of a multipolygon relation and doesn't give proper warnings when a multipolygon is invalidated. JOSM for instance performs a validity check when uploading.
Please include clear warnings in potlach2 to alert mappers if they are about to invalidate a multipolygon or show it much clearer if a way's role is to be part of a multipolygon.
Thank you!
The text was updated successfully, but these errors were encountered:
Reporter: travelling_salesman
[Submitted to the original trac issue database at 7.31pm, Tuesday, 11th June 2013]
Every few weeks I find a destroyed multipolygon relation in my mapping area, of which segements are deleted so that mapnik cannot render them anymore. The associated editor is always potlach2. And the responsible mappers are always unaware of the damage they do. This is because potlach2 doesn't make clear enough that a way is part of a multipolygon relation and doesn't give proper warnings when a multipolygon is invalidated. JOSM for instance performs a validity check when uploading.
Please include clear warnings in potlach2 to alert mappers if they are about to invalidate a multipolygon or show it much clearer if a way's role is to be part of a multipolygon.
Thank you!
The text was updated successfully, but these errors were encountered: