Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#4103 closed defect (fixed)

ST_PointOnSurface on invalid inputs

Reported by: komzpa Owned by: komzpa
Priority: medium Milestone: PostGIS 2.5.0
Component: postgis Version: master
Keywords: Cc:

Description

18:27:31 [gis] > select ST_PointOnSurface('0103000020110F0000010000000A000000000000C41E644741000000EEA2A75A41000000F420644741000000629EA75A410000007A2D644741000000E49FA75A41000000C02E644741000000409DA75A41000000286A64474100000064A4A75A410000007867644741000000FAA9A75A41000000E82B644741000000D2A2A75A41000000222D64474100000046A0A75A41000000242B6447410000006CA4A75A41000000C41E644741000000EEA2A75A41');
ERROR:  XX000: GEOSPointOnSurface: TopologyException: Input geom 1 is invalid: Self-intersection at or near point 3065943.8190934439 6987403.2828343641 at 3065943.8190934439 6987403.2828343641
LOCATION:  pg_error, lwgeom_pg.c:128
Time: 0,866 ms

A polygon is output of ST_QuantizeCoordinates and was valid before that.

Change History (3)

comment:1 by komzpa, 6 years ago

Resolution: fixed
Status: assignedclosed

In 16609:

ST_PointOnSurface handling of invalid.

Prints a loud notice and passes input through MakeValid.

Closes #4103
Closes https://github.com/postgis/postgis/pull/257

comment:2 by komzpa, 6 years ago

In 16610:

Debbie / Postgres 9.4 calls function twice.

References #4103

comment:3 by pramsey, 6 years ago

In 17273:

Comment out old pointonsurface test, as newer versions
of GEOS will no longer throw the expected exception.
History marches on.
References #4103

Note: See TracTickets for help on using tickets.