#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 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 by , 6 years ago
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 by , 6 years ago
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?
In 17396: