Changes between Initial Version and Version 1 of Ticket #4182, comment 8


Ignore:
Timestamp:
Aug 22, 2019, 6:58:48 AM (15 months ago)
Author:
fengel
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4182, comment 8

    initial v1  
    11I have similar TopologyExceptions on valid geometries quite often and I am looking forward to the approvements that are on the way in JTS and GEOS. In my experience large polygon tables in the real world (data from institutions, geo portals etc.) are very often subject to this kind of problem. Since the exception results in aborting the process it can become quite problematic if you have to come up with a solution.
    2 I was wondering if there are any recommendations for workarounds to this issue. I currently use the functions st_safe_difference and st_safe_intersection from this extension at the moment: https://pgxn.org/dist/lostgis/1.0.2/ plus a self created safe_union function. The main mechanism is exception handling which allows you to ignore exceptions that cannot be solved. Using these functions I was able to work with any kind of data so far and I didn't notice any major drawbacks. But I am not sure if these solutions are reasonable and it would be very interesting to see workaround strategies from other people.
     2I was wondering if there are any recommendations for workarounds to this issue. I currently use the functions st_safe_difference and st_safe_intersection from this extension: https://pgxn.org/dist/lostgis/1.0.2/ plus a self created safe_union function. The main mechanism is exception handling which allows you to ignore exceptions that cannot be solved. Using these functions I was able to work with any kind of data so far and I didn't notice any major drawbacks. But I am not sure if these solutions are reasonable and it would be very interesting to see workaround strategies from other people.