So, for instance, try replacing ST_Intersects with ST_3DIntersects,
and your example should work.
Many of the functions were written before curve support, which is why
you may see a generic-looking "unknown geometry type" error.
On 22 April 2017 at 06:59, James Klassen <klass...@gmail.com> wrote:
> I have been getting "ERROR: Unknown geometry type: 12 - MultiSurface" on
> some operations since importing a File GeoDatabase containing curved
> geometries into PostGIS using a recent OGR (2.2.0dev trunk@37918). Using
> ST_CurveToLine(geom) instead or the original curved geometry is a work
> around, but it would be desirable to directly use the original geometry if
> possible. Is this the expected behavior?
>
> I am running PostgreSQL 9.5.5/PostGIS 2.2.2 from
> http://apt.postgresql.org/pub/repos/apt/ on Ubuntu 12.04.
>
> It is unclear to me from the documentation if Curved geometries are
> generally supported or only with a few specific functions. I have found
> some references to "Unknown geometry type" errors from long ago that
> reference closed tickets against PostGIS 1.x and a Stack Exchange question
> "Smallworld > FME > PostGIS > QGIS" that seems similar but different.
_______________________________________________
postgis-users mailing list
postgi...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users