From 6b56bcdf63cc8b1030150374e8fc48f10bb726e0 Mon Sep 17 00:00:00 2001 From: Darafei Praliaskouski Date: Tue, 23 Oct 2018 12:19:59 +0000 Subject: [PATCH] [doc][raster] Fix typos in function names in ST_Intersection, interlink git-svn-id: http://svn.osgeo.org/postgis/trunk@16939 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/reference_raster.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml index 926976275..027a3425a 100644 --- a/doc/reference_raster.xml +++ b/doc/reference_raster.xml @@ -9797,7 +9797,7 @@ FROM apple; - The first three variants, returning a setof geomval, works in vector space. The raster is first vectorized (using ST_DumpAsPolygon) into a set of geomval rows and those rows are then intersected with the geometry using the ST_Intersection(geometry, geometry) PostGIS function. Geometries intersecting only with a nodata value area of a raster returns an empty geometry. They are normally excluded from the results by the proper usage of ST_Intersect in the WHERE clause. + The first three variants, returning a setof geomval, works in vector space. The raster is first vectorized (using ) into a set of geomval rows and those rows are then intersected with the geometry using the (geometry, geometry) PostGIS function. Geometries intersecting only with a nodata value area of a raster returns an empty geometry. They are normally excluded from the results by the proper usage of in the WHERE clause. @@ -9834,7 +9834,7 @@ FROM apple; - ST_Intersection should be used in conjunction with ST_Intersects and an index on the raster column and/or the geometry column. + ST_Intersection should be used in conjunction with and an index on the raster column and/or the geometry column. -- 2.40.0