Commit 6b56bcdf authored by Darafei Praliaskouski's avatar Darafei Praliaskouski

[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
parent de8c3148
Pipeline #34007330 passed with stage
in 31 minutes and 51 seconds
......@@ -9797,7 +9797,7 @@ FROM apple;
</para>
<para>
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 <xref linkend="RT_ST_DumpAsPolygons" />) into a set of geomval rows and those rows are then intersected with the geometry using the <xref linkend="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 <xref linkend="RT_ST_Intersects" /> in the WHERE clause.
</para>
<para>
......@@ -9834,7 +9834,7 @@ FROM apple;
<note>
<para>
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 <xref linkend="RT_ST_Intersects" /> and an index on the raster column and/or the geometry column.
</para>
</note>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment