[postgis-tickets] [SCM] PostGIS branch master updated. 3.1.0alpha1-120-g4c185f8
git at osgeo.org
git at osgeo.org
Tue May 12 13:17:10 PDT 2020
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 4c185f8617824a21f46569170dd16c3427e1b197 (commit)
via b10e2c272cd9921ee0683617d291d60ba1da9b2a (commit)
from d3a23521ffc319fc4827eb94fc7cedf414edfdfc (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 4c185f8617824a21f46569170dd16c3427e1b197
Author: Regina Obe <lr at pcorp.us>
Date: Tue May 12 16:17:06 2020 -0400
Fix misreference to ST_Point
diff --git a/doc/reference_input.xml b/doc/reference_input.xml
index ffd3e5a..21d9d1f 100644
--- a/doc/reference_input.xml
+++ b/doc/reference_input.xml
@@ -383,7 +383,7 @@ SELECT ST_GeomFromEWKT('POLYHEDRALSURFACE(
<para>&sfs_compliant; s3.2.6.2 - option SRID is from the conformance suite.</para>
<para>&sqlmm_compliant; SQL-MM 3: 5.1.40</para>
<para>&curve_support;</para>
- <note><para>While not OGC-compliant, <xref linkend="ST_MakePoint" /> is faster than ST_GeomFromText and ST_PointFromText. It is also easier to use for numeric coordinate values. <xref linkend="ST_Point" /> is another option similar in speed to <xref linkend="ST_Point" /> and is OGC-compliant, but doesn't support anything but 2D points.</para></note>
+ <note><para>While not OGC-compliant, <xref linkend="ST_MakePoint" /> is faster than ST_GeomFromText and ST_PointFromText. It is also easier to use for numeric coordinate values. <xref linkend="ST_Point" /> is another option similar in speed to <xref linkend="ST_MakePoint" /> and is OGC-compliant, but doesn't support anything but 2D points.</para></note>
<warning><para>Changed: 2.0.0 In prior versions of PostGIS ST_GeomFromText('GEOMETRYCOLLECTION(EMPTY)') was allowed. This is now illegal in PostGIS 2.0.0 to better conform with SQL/MM standards. This should now be
written as ST_GeomFromText('GEOMETRYCOLLECTION EMPTY')</para></warning>
commit b10e2c272cd9921ee0683617d291d60ba1da9b2a
Author: Regina Obe <lr at pcorp.us>
Date: Tue May 12 02:50:41 2020 -0400
Another example
diff --git a/doc/reference_constructor.xml b/doc/reference_constructor.xml
index 86c482b..4d18ea7 100644
--- a/doc/reference_constructor.xml
+++ b/doc/reference_constructor.xml
@@ -897,46 +897,46 @@ WHERE
</refentry>
- <refentry id="ST_SquareGrid">
- <refnamediv>
- <refname>ST_SquareGrid</refname>
- <refpurpose>Returns a set of grid squares and cell indices that completely cover the bounds of the geometry argument.</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
- <funcsynopsis>
- <funcprototype>
- <funcdef>setof record <function>ST_SquareGrid</function></funcdef>
- <paramdef><type>float8</type> <parameter>size</parameter></paramdef>
- <paramdef><type>geometry</type> <parameter>bounds</parameter></paramdef>
- </funcprototype>
- </funcsynopsis>
- </refsynopsisdiv>
+ <refentry id="ST_SquareGrid">
+ <refnamediv>
+ <refname>ST_SquareGrid</refname>
+ <refpurpose>Returns a set of grid squares and cell indices that completely cover the bounds of the geometry argument.</refpurpose>
+ </refnamediv>
+
+ <refsynopsisdiv>
+ <funcsynopsis>
+ <funcprototype>
+ <funcdef>setof record <function>ST_SquareGrid</function></funcdef>
+ <paramdef><type>float8</type> <parameter>size</parameter></paramdef>
+ <paramdef><type>geometry</type> <parameter>bounds</parameter></paramdef>
+ </funcprototype>
+ </funcsynopsis>
+ </refsynopsisdiv>
- <refsection>
- <title>Description</title>
+ <refsection>
+ <title>Description</title>
- <para>Starts with the concept of a square tiling of the plane.
- For a given planar SRS, and a given edge size, starting at the origin of the SRS,
- there is one unique square tiling of the plane, Tiling(SRS, Size).
- This function answers the question: what grids in a given Tiling(SRS, Size)
- overlap with a given bounds.</para>
+ <para>Starts with the concept of a square tiling of the plane.
+ For a given planar SRS, and a given edge size, starting at the origin of the SRS,
+ there is one unique square tiling of the plane, Tiling(SRS, Size).
+ This function answers the question: what grids in a given Tiling(SRS, Size)
+ overlap with a given bounds.</para>
- <para>The SRS for the output squares is the SRS provided by the bounds geometry.</para>
- <para>Doubling or edge size of the square generates a new parent tiling that
- perfectly fits with the original tiling. Standard web map tilings in mercator
- are just powers-of-two square grids in the mercator plane.</para>
+ <para>The SRS for the output squares is the SRS provided by the bounds geometry.</para>
+ <para>Doubling or edge size of the square generates a new parent tiling that
+ perfectly fits with the original tiling. Standard web map tilings in mercator
+ are just powers-of-two square grids in the mercator plane.</para>
- <para>Availability: 3.1</para>
+ <para>Availability: 3.1</para>
- </refsection>
+ </refsection>
- <refsection>
- <title>Example: Counting points in squares</title>
- <para>To do a point summary against a square tiling, generate a square grid using the
- extent of the points as the bounds, then spatially join to that grid.</para>
- <programlisting>SELECT COUNT(*), squares.geom
-FROM
+ <refsection>
+ <title>Example: Counting points in squares (using single chopped grid)</title>
+ <para>To do a point summary against a square tiling, generate a square grid using the
+ extent of the points as the bounds, then spatially join to that grid. Note the estimated extent might be off from actual extent, so be cautious and at very least make sure you've analyzed your table.</para>
+ <programlisting>SELECT COUNT(*), squares.geom
+ FROM
pointtable AS pts
INNER JOIN
ST_SquareGrid(
@@ -944,16 +944,31 @@ FROM
ST_SetSRID(ST_EstimatedExtent('pointtable', 'geom'), 3857)
) AS squares
ON ST_Intersects(pts.geom, squares.geom)
-GROUP BY squares.geom</programlisting>
- </refsection>
+ GROUP BY squares.geom</programlisting>
+ </refsection>
- <refsection>
- <title>See Also</title>
- <para><xref linkend="ST_TileEnvelope" />, <xref linkend="ST_HexagonGrid" />
+ <refsection>
+ <title>Example: Counting points in squares using set of grid per point</title>
+ <para>This yields the same result as the first example but will be slower for a large number of points</para>
+ <programlisting>SELECT COUNT(*), squares.geom
+ FROM
+ pointtable AS pts
+ INNER JOIN
+ ST_SquareGrid(
+ 1000,
+ pts.geom
+ ) AS squares
+ ON ST_Intersects(pts.geom, squares.geom)
+ GROUP BY squares.geom</programlisting>
+ </refsection>
+
+ <refsection>
+ <title>See Also</title>
+ <para><xref linkend="ST_TileEnvelope" />, <xref linkend="ST_HexagonGrid" />
, <xref linkend="ST_EstimatedExtent" />
, <xref linkend="ST_SetSRID" /></para>
- </refsection>
- </refentry>
+ </refsection>
+ </refentry>
<refentry id="ST_Hexagon">
<refnamediv>
-----------------------------------------------------------------------
Summary of changes:
doc/reference_constructor.xml | 97 +++++++++++++++++++++++++------------------
doc/reference_input.xml | 2 +-
2 files changed, 57 insertions(+), 42 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list