From 794627ea67ffd91803608e41fd98bcb6346dbb44 Mon Sep 17 00:00:00 2001 From: Mark Leslie Date: Mon, 16 Jul 2007 18:53:52 +0000 Subject: [PATCH] Added notes about the implicit index operators on the relational functions. git-svn-id: http://svn.osgeo.org/postgis/trunk@2664 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/postgis.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/postgis.xml b/doc/postgis.xml index 96ae3999b..88df42d7e 100644 --- a/doc/postgis.xml +++ b/doc/postgis.xml @@ -1841,6 +1841,10 @@ box". Assuming that our query box is much smaller than the extents of the entire geometry table, this will drastically reduce the number of distance calculations that need to be done. + + As of PostGIS 1.3.0, most of the Geometry + Relationship Functions, with the notable exceptions of ST_Disjoint and + ST_Relate, include implicit bounding box overlap operators. @@ -2719,6 +2723,8 @@ Do not call with a GeometryCollection as an argument + This function call will autowatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Intersects. + NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2737,6 +2743,8 @@ Performed by the GEOS module Do not call with a GeometryCollection as an argument + + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Touches. NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2758,6 +2766,8 @@ Do not call with a GeometryCollection as an argument + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Crosses. + NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2777,6 +2787,8 @@ Do not call with a GeometryCollection as an argument + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Within. + NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2796,6 +2808,8 @@ Do not call with a GeometryCollection as an argument + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Overlaps. + NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2814,6 +2828,8 @@ Do not call with a GeometryCollection as an argument + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Contains. + NOTE: this is the "allowable" version that returns a boolean, not an integer. @@ -2830,6 +2846,7 @@ Geometry A Refer to http://lin-ear-th-inking.blogspot.com/2007/06/subtleties-of-ogc-covers-spatial.html for an explaination of the need of this function. + This function call will automatically include a bounding box comparison that will make use of any indicies that are available on the geometries. To avoid index use, use the function _ST_Covers. -- 2.49.0