[postgis-tickets] [SCM] PostGIS branch master updated. 3.1.0rc1-56-g52f9425

[git at osgeo.org]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, master has been updated
       via  52f942583b5b9c975799bf8eefadc756a5f56215 (commit)
      from  e7973308de3df4515c6456880e162040e285ee2b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 52f942583b5b9c975799bf8eefadc756a5f56215
Author: Martin Davis <mtnclimb at gmail.com>
Date:   Wed Feb 3 22:22:58 2021 -0800

    Dcc Reference editing

diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml
index 482d85c..1590373 100644
--- a/doc/reference_processing.xml
+++ b/doc/reference_processing.xml
@@ -66,10 +66,6 @@ Returns a geometry covering all points within a given distance from a geometry.
                     fits the bounding box of the geography object (favoring UTM, Lambert Azimuthal Equal Area (LAEA) north/south pole, and falling back on mercator in worst case scenario) and then buffers in that planar spatial ref and retransforms back to WGS84 geography.</para></note>
             <warning><para>
             For geography this may not behave as expected if object is sufficiently large that it falls between two UTM zones or crosses the dateline</para></warning>
-                <para>Enhanced: 2.5.0 - ST_Buffer geometry support was enhanced to allow for side buffering specification <code>side=both|left|right</code>.</para>
-                <para>Availability: 1.5 - ST_Buffer was enhanced to support different endcaps and join types. These are useful for example to convert road linestrings
-                    into polygon roads with flat or square edges instead of rounded edges. Thin wrapper for geography was added.
-                </para>
                 <para>
 The optional third parameter (currently only applies to geometry) can either specify number of segments used to approximate a quarter circle (integer case, defaults to 8) or a list of blank-separated key=value pairs (string case) to tweak operations as follows:
 <itemizedlist>
@@ -94,14 +90,21 @@ This is only really relevant to LINESTRING geometry and does not affect POINT or
 
                 <para>Units of radius are measured in units of the spatial reference system.</para>
                 <para>The inputs can be POINTS, MULTIPOINTS, LINESTRINGS, MULTILINESTRINGS, POLYGONS, MULTIPOLYGONS, and GeometryCollections.</para>
-                <note><para>This function ignores the third dimension (z) and will always give a 2-d buffer even when presented with a 3d-geometry.</para></note>
+
+                <note><para>Creating a buffer to do a radius search is inefficient.  Use <xref linkend="ST_DWithin" /> instead.</para></note>
+
+            <note><para>This function ignores the Z dimension.
+It always gives a 2D result even when used on a 3D geometry.</para></note>
+
+                <para>Enhanced: 2.5.0 - ST_Buffer geometry support was enhanced to allow for side buffering specification <code>side=both|left|right</code>.</para>
+                <para>Availability: 1.5 - ST_Buffer was enhanced to support different endcaps and join types. These are useful for example to convert road linestrings
+                    into polygon roads with flat or square edges instead of rounded edges. Thin wrapper for geography was added.
+                </para>
 
                 <para>Performed by the GEOS module.</para>
                 <para>&sfs_compliant; s2.1.1.3</para>
                 <para>&sqlmm_compliant; SQL-MM 3: 5.1.17</para>
 
-                <note><para>People often make the mistake of using this function to try to do radius searches.  Creating a
-                    buffer to a radius search is slow and pointless.  Use <xref linkend="ST_DWithin" /> instead.</para></note>
             </refsection>
 
               <refsection>
@@ -1550,13 +1553,11 @@ and retains the same direction. For a negative distance it is on the right
 side and in the opposite direction.
             </para>
             <para>
+Units of distance are measured in units of the spatial reference system.
+            </para>
+            <para>
 Note that output may be a MULTILINESTRING or EMPTY for some jigsaw-shaped input geometries.
             </para>
-
-            <para>Performed by the GEOS module.</para>
-            <para>Availability: 2.0</para>
-            <para>Enhanced: 2.5 - added support for GEOMETRYCOLLECTION and MULTILINESTRING</para>
-
             <para>
 The optional third parameter allows specifying a list of blank-separated
 key=value pairs to tweak operations as follows:
@@ -1573,15 +1574,12 @@ key=value pairs to tweak operations as follows:
 </itemizedlist>
                 </para>
 
-                <para>
-Units of distance are measured in units of the spatial reference system.
-                </para>
-
-                <para>Performed by the GEOS module.</para>
+            <para>Performed by the GEOS module.</para>
+            <para>Availability: 2.0</para>
+            <para>Enhanced: 2.5 - added support for GEOMETRYCOLLECTION and MULTILINESTRING</para>
 
-                <note><para>
-This function ignores the third dimension (z) and will always give a
-2-d result even when presented with a 3d-geometry.</para></note>
+            <note><para>This function ignores the Z dimension.
+It always gives a 2D result even when used on a 3D geometry.</para></note>
 
             </refsection>
 

-----------------------------------------------------------------------

Summary of changes:
 doc/reference_processing.xml | 38 ++++++++++++++++++--------------------
 1 file changed, 18 insertions(+), 20 deletions(-)


hooks/post-receive
-- 
PostGIS