[postgis-tickets] [PostGIS] #3678: Invalid geometry in a table returns conflicting ST_Intersects results

[PostGIS]

#3678: Invalid geometry in a table returns conflicting ST_Intersects results
----------------------+---------------------------
  Reporter:  mwtoews  |      Owner:  pramsey
      Type:  defect   |     Status:  closed
  Priority:  medium   |  Milestone:  PostGIS 2.3.2
 Component:  postgis  |    Version:  2.3.x
Resolution:  wontfix  |   Keywords:
----------------------+---------------------------
Changes (by pramsey):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I'm afraid this one has to be closed. Computational geometry algorithms
 can either pay the overhead of cleaning up inputs at every invocation, or
 expect some kind of minimal structural rules to be in place before the
 data arrive (validity). We opt for the latter approach, and the reason we
 tell people "you should make sure your geometry is valid" is precisely
 because algorithms will get wrong answers with invalid inputs.

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3678#comment:2>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.