[postgis-tickets] [SCM] PostGIS branch master updated. 3.2.0-475-g289bc3830

[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  289bc3830c2af633f92ea86c3d3c65f969379083 (commit)
      from  9416eb1705253f8365461f8050a7536b0a0ce060 (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 289bc3830c2af633f92ea86c3d3c65f969379083
Author: Martin Davis <mtnclimb at gmail.com>
Date:   Thu Feb 3 13:27:39 2022 -0800

    Add doc simple SQLMM and UnaryUnion refs

diff --git a/doc/reference_overlay.xml b/doc/reference_overlay.xml
index e3c944c28..1c5d0a9f4 100644
--- a/doc/reference_overlay.xml
+++ b/doc/reference_overlay.xml
@@ -890,29 +890,35 @@ MULTILINESTRING((1 3 2.75,1 4 2),(1 1 3,1 2 2.25))
         <para>
         A single-input variant of <xref linkend="ST_Union" />.
         The input may be a single geometry, a MultiGeometry, or a GeometryCollection.
-        The union is applied to the individual components of the input.
-        This allow using this function to fix MultiPolygons which  are
+        The union is applied to the individual elements of the input.
+        </para>
+        <para>
+        This function can be used to fix MultiPolygons which  are
         invalid due to overlapping components.
-        (However, the input components must each be valid.
-        An invalid input component such as a bow-tie polygon may cause an error.)
+        However, the input components must each be valid.
+        An invalid input component such as a bow-tie polygon may cause an error.
+        For this reason it may be better to use <xref linkend="ST_MakeValid" />.
         </para>
 
         <para>
-        Another use of this function is to node and dissolve a collection of linestrings.
-        (This can also be done with <xref linkend="ST_Node" />.)
+        Another use of this function is to node and dissolve a collection of
+        linestrings which cross or overlap
+        to make them <link linkend="Simple_Geometry">simple</link>.
+        (To add nodes but not dissolve duplicate linework
+        use <xref linkend="ST_Node" />.)
         </para>
 
         <para>
-        It is possible to mix ST_UnaryUnion with <xref linkend="ST_Collect" /> to fine-tune
+        It is possible to combine ST_UnaryUnion with <xref linkend="ST_Collect" /> to fine-tune
         how many geometries are be unioned at once.
         This allows trading off between memory usage and compute time,
         striking a balance between ST_Union and <xref linkend="ST_MemUnion" />.
         </para>
 
         <para>
-If the optional <code>gridSize</code> argument is provided, the inputs are
-snapped to a grid of the given size, and the result vertices are computed
-on that same grid. (Requires GEOS-3.9.0 or higher)
+        If the optional <code>gridSize</code> argument is provided, the inputs are
+        snapped to a grid of the given size, and the result vertices are computed
+        on that same grid. (Requires GEOS-3.9.0 or higher)
         </para>
 
         <para>&Z_support; However, the result is computed using XY only.
@@ -930,6 +936,7 @@ on that same grid. (Requires GEOS-3.9.0 or higher)
         <para>
             <xref linkend="ST_Union" />,
             <xref linkend="ST_MemUnion" />,
+            <xref linkend="ST_MakeValid" />,
             <xref linkend="ST_Collect" />,
             <xref linkend="ST_Node" />
         </para>
diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index 1629f4527..4c6c8ab77 100644
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -879,12 +879,13 @@ SELECT ST_Distance('LINESTRING(-122.33 47.606, 0.0 51.5)'::geometry, 'POINT(-21.
 	  <title>Geometry Validation</title>
 
 	  <para>PostGIS is compliant with the Open Geospatial Consortium’s (OGC)
-	  Simple Features Specification.
-      It defines the concepts of geometry being
+	  Simple Features specification.
+      That standard defines the concepts of geometry being
       <emphasis>simple</emphasis> and <emphasis>valid</emphasis>.
       These definitions allow the Simple Features geometry model
       to represent spatial objects in a consistent and unambiguous way
       that supports efficient computation.
+      (Note: the OGC SF and SQL/MM have the same definitions for simple and valid.)
         </para>
 
 	<sect2 id="Simple_Geometry">
@@ -1025,8 +1026,8 @@ SELECT ST_Distance('LINESTRING(-122.33 47.606, 0.0 51.5)'::geometry, 'POINT(-21.
 		</tgroup>
 	  </informaltable>
 
-    <para>As described in the next section, the linear rings forming a
-    <varname>POLYGON</varname> must be simple for it to be valid.</para>
+    <para><varname>POLYGON</varname>s are formed from linear rings, so
+    valid polygonal geometry is always <emphasis>simple</emphasis>.</para>
 
     <para>To test if a geometry is simple
 	use the <xref linkend="ST_IsSimple" /> function:</para>
@@ -1045,6 +1046,7 @@ SELECT
 	Simplicity is primarily used as a basis for defining geometric validity.
     It is also a requirement for some kinds of spatial data models
     (for example, linear networks often disallow lines that cross).
+    Multipoint and linear geometry can be made simple using <xref linkend="ST_UnaryUnion" />.
     </para>
     </sect2>
 

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

Summary of changes:
 doc/reference_overlay.xml     | 27 +++++++++++++++++----------
 doc/using_postgis_dataman.xml | 10 ++++++----
 2 files changed, 23 insertions(+), 14 deletions(-)


hooks/post-receive
-- 
PostGIS