Changes between Initial Version and Version 1 of Ticket #1038, comment 11


Ignore:
Timestamp:
Aug 18, 2020, 10:39:37 AM (4 years ago)
Author:
mdavis

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1038, comment 11

    initial v1  
    2121> We could leave with requiring user input to be valid, but calling MakeValid at any moment in the process kills performance.
    2222
    23 Agreed, calling MakeValid is a showstopper.  And I can't see being able to handle *any* invalid use input.  However, "mildly" invalid data should be feasible to handle.  "Mildly" invalid includes data which contains topology collapse (either originally or due to rounding).  For example, the data in this [https://github.com/CrunchyData/pg_tileserv/issues/48 MVT issue]  works with OverlayNG-SR.
     23Agreed, calling MakeValid is a showstopper.  And I can't see being able to handle *any* invalid use input.  However, "mildly" invalid data should be feasible to handle.  "Mildly" invalid includes data which contains topology collapse (either originally or due to rounding).  For example, the data in this [https://github.com/CrunchyData/pg_tileserv/issues/48 MVT issue]  works with OverlayNG-SR, in spite of containing several polygons which self-touch along their boundary.