Opened 14 years ago
Closed 5 years ago
#3319 closed defect (wontfix)
self intersection issue with polygonize routine.
| Reported by: | warmerdam | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | closed_because_of_github_migration |
| Component: | Algorithms | Version: | unspecified |
| Severity: | normal | Keywords: | polygonize |
| Cc: | ysid |
Description
The attached zip file contains a small ascii grid file which produces a self-intersecting polygon when gdal_polygonize.py is run against it. I have also attached a picture showing the self-intersection.
I'm not sure how to fix this!
Attachments (2)
Change History (5)
by , 14 years ago
| Attachment: | polygonize_self_intersection.zip added |
|---|
comment:1 by , 14 years ago
| Cc: | added |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
St_MakeValid from SpatiaLite is converting the original self-intersecting polygon POLYGON (( 0 5, 3 5, 3 4, 2 4, 2 2, 3 2, 3 4, 5 4, 5 0, 0 0, 0 5 )) into a polygon with a hole POLYGON((0 5, 3 5, 3 4, 5 4, 5 0, 0 0, 0 5), (3 4, 2 4, 2 2, 3 2, 3 4))
I am not sure if gdal_polygonize should try to correct self-intersections during execution or as a post-process or just let them be.
comment:3 by , 5 years ago
| Milestone: | → closed_because_of_github_migration |
|---|---|
| Resolution: | → wontfix |
| Status: | assigned → closed |
This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to https://github.com/OSGeo/gdal/issues if it is not already reported there.
zip containing problem ascii grid, and generated shapefile.