Opened 7 months ago

Closed 7 months ago

Last modified 7 months ago

#4378 closed enhancement (fixed)

Allow passing TINs to GEOS functions

Reported by: komzpa Owned by: komzpa
Priority: medium Milestone: PostGIS 3.0.0
Component: postgis Version: 2.4.x
Keywords: Cc:

Description

GEOS functions now fail with TINs.

They could work if we represent them as GEOMETRYCOLLECTION(POLYGON(...)...).

Change History (4)

comment:1 Changed 7 months ago by komzpa

Resolution: fixed
Status: assignedclosed

In 17396:

Allow passing TINs to GEOS functions.

Closes #4378
Closes https://github.com/postgis/postgis/pull/392

comment:2 Changed 7 months ago by mdavis

Ideally the docs should be updated to reflect this change.

comment:3 Changed 7 months ago by dbaston

It might be more clear have a function to convert a TIN to a GeometryCollection? on the PostGIS side, rather than silently changing the type when passing it to GEOS.

comment:4 Changed 7 months ago by mdavis

Perhaps having both is good?

An explicit PostGIS function is good for explanatory purposes (and might support other functionality in the future). It also might be useful for converting the TIN type to a simpler WKT type for output purposes or compatibility with other systems.

But surely there's no harm in auto-converting as well?

Note: See TracTickets for help on using tickets.