From 236b974442038f07c4ea58c15068dfe98c51e6c3 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Sun, 18 Jan 2015 09:50:52 +0000 Subject: [PATCH] flag ST_3DIntersects as overloaded sfcgal function git-svn-id: http://svn.osgeo.org/postgis/trunk@13183 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/reference_measure.xml | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml index fa5081a67..4a9b5387f 100644 --- a/doc/reference_measure.xml +++ b/doc/reference_measure.xml @@ -127,7 +127,7 @@ SELECT ST_AsEWKT(ST_3DClosestPoint(line,pt)) AS cp3d_line_pt, &P_support; &sqlmm_compliant; SQL-MM ? - &sfcgal_enhanced; + &sfcgal_enhanced; Availability: 2.0.0 @@ -313,7 +313,7 @@ ST_DWithin( ST_3DIntersects Returns TRUE if the Geometries "spatially - intersect" in 3d - only for points and linestrings + intersect" in 3d - only for points, linestrings, polygons, polyhedral surface (area). With SFCGAL backend enabled also supports TINS and Polyhedral Surfaces (including solids) in addition. @@ -345,9 +345,13 @@ ST_DWithin( comparison that will make use of any indexes that are available on the geometries. + + In order to take advantage of support for TINS and extended support for PolyHedralSurfaces, you need to enable the SFCGAL backend. This can be done at session time with: set postgis.backend = sfcgal; or at the database or system level. Database level can be done with ALTER DATABASE gisdb SET postgis.backend = sfcgal;. &Z_support; &P_support; + &T_support; + &sfcgal_enhanced; &sqlmm_compliant; SQL-MM 3: ? @@ -361,6 +365,14 @@ ST_DWithin( (1 row) + + TIN Examples + set postgis.backend = sfcgal; +SELECT ST_3DIntersects('TIN(((0 0,1 0,0 1,0 0)))'::geometry, 'POINT(.1 .1)'::geometry); + st_3dintersects +----------------- + t + See Also -- 2.50.1