[postgis-tickets] [SCM] PostGIS branch stable-3.2 updated. 3.2.1-2-g3422d27f6
git at osgeo.org
git at osgeo.org
Sun Feb 13 23:45:22 PST 2022
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, stable-3.2 has been updated
via 3422d27f6dc45c1e17d302857c3d4d21ac56586d (commit)
from 543335e6e692339fe905c810848a16cbdca19795 (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 3422d27f6dc45c1e17d302857c3d4d21ac56586d
Author: Regina Obe <lr at pcorp.us>
Date: Mon Feb 14 02:45:14 2022 -0500
Fix version number, add 3.2.1 to upgrade target, backport some doc corrections
diff --git a/Version.config b/Version.config
index d58de7926..92a4da189 100644
--- a/Version.config
+++ b/Version.config
@@ -5,7 +5,7 @@
POSTGIS_MAJOR_VERSION=3
POSTGIS_MINOR_VERSION=2
-POSTGIS_MICRO_VERSION=2
+POSTGIS_MICRO_VERSION=2dev
# Liblwgeom interface versioning, reset to 0:0:0 (cur:age:rev)
# when changing POSTGIS_MINOR_VERSION
diff --git a/doc/reference_constructor.xml b/doc/reference_constructor.xml
index 36adb4366..5882517c7 100644
--- a/doc/reference_constructor.xml
+++ b/doc/reference_constructor.xml
@@ -685,12 +685,13 @@ FROM provinces p;
<refsection>
<title>Examples: Geography</title>
-
- <programlisting>SELECT CAST(ST_SetSRID( ST_Point( -71.104, 42.315), 4326) AS geography);</programlisting>
+ <para>Pre-PostGIS 3.2 syntax</para>
+ <programlisting>SELECT CAST( ST_SetSRID(ST_Point( -71.104, 42.315), 4326) AS geography);</programlisting>
+ <para>3.2 and on you can include the srid</para>
+ <programlisting>SELECT CAST( ST_Point( -71.104, 42.315, 4326) AS geography);</programlisting>
<para>PostgreSQL also provides the <varname>::</varname> short-hand for casting</para>
- <programlisting>
-SELECT ST_SetSRID( ST_Point( -71.104, 42.315), 4326)::geography;</programlisting>
+ <programlisting>SELECT ST_Point( -71.104, 42.315, 4326)::geography;</programlisting>
<para>If the point coordinates are not in a geodetic coordinate system (such as WGS84),
then they must be reprojected before casting to a geography.
@@ -730,6 +731,7 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
<refsection>
<title>Description</title>
<para>Returns an Point with the given X, Y and Z coordinate values, and optionally an SRID number.</para>
+ <para>Enhanced: 3.2.0 srid as an extra optional argument was added. Older installs require combining with ST_SetSRID to mark the srid on the geometry.</para>
</refsection>
<refsection>
@@ -766,6 +768,7 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
<refsection>
<title>Description</title>
<para>Returns an Point with the given X, Y and M coordinate values, and optionally an SRID number.</para>
+ <para>Enhanced: 3.2.0 srid as an extra optional argument was added. Older installs require combining with ST_SetSRID to mark the srid on the geometry.</para>
</refsection>
<refsection>
@@ -804,6 +807,7 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
<refsection>
<title>Description</title>
<para>Returns an Point with the given X, Y, Z and M coordinate values, and optionally an SRID number.</para>
+ <para>Enhanced: 3.2.0 srid as an extra optional argument was added. Older installs require combining with ST_SetSRID to mark the srid on the geometry.</para>
</refsection>
<refsection>
@@ -815,7 +819,7 @@ SELECT ST_Transform(ST_SetSRID( ST_Point( 3637510, 3014852 ), 2273), 4326)::geog
<refsection>
<title>See Also</title>
- <para><xref linkend="ST_MakePoint" />, <xref linkend="ST_Point" />, <xref linkend="ST_PointM" />, <xref linkend="ST_PointZ" /></para>
+ <para><xref linkend="ST_MakePoint" />, <xref linkend="ST_Point" />, <xref linkend="ST_PointM" />, <xref linkend="ST_PointZ" />, <xref linkend="ST_SetSRID" /></para>
</refsection>
</refentry>
diff --git a/doc/reference_output.xml b/doc/reference_output.xml
index 1c55f2bb7..7c0e36ebc 100644
--- a/doc/reference_output.xml
+++ b/doc/reference_output.xml
@@ -1289,7 +1289,7 @@ SELECT (ST_AsLatLonText('POINT (-302.2342342 -792.32498)'));
<para><varname>row</varname> row data with at least a geometry column.</para>
<para><varname>name</varname> is the name of the layer. Default is the string "default".</para>
<para><varname>extent</varname> is the tile extent in screen space as defined by the specification. Default is 4096.</para>
- <para><varname>geom_name</varname> is the name of the geometry column in the row data. Default is the first geometry column.</para>
+ <para><varname>geom_name</varname> is the name of the geometry column in the row data. Default is the first geometry column. Note that PostgreSQL by default automatically <ulink url="https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS">folds unquoted identifiers to lower case</ulink>, which means that unless the geometry column is quoted, e.g. <varname>"MyMVTGeom"</varname>, this parameter must be provided as lowercase.</para>
<para><varname>feature_id_name</varname> is the name of the Feature ID column in the row data. If NULL or negative the Feature ID is not set. The first column matching name and valid type (smallint, integer, bigint) will be used as Feature ID, and any subsequent column will be added as a property. JSON properties are not supported.</para>
@@ -1406,7 +1406,7 @@ FROM mvtgeom;
<para>Returns the geometry in TWKB (Tiny Well-Known Binary) format. TWKB is a <ulink url="https://github.com/TWKB/Specification/blob/master/twkb.md">compressed binary format</ulink> with a focus on minimizing the size of the output. </para>
<para>The decimal digits parameters control how much precision is stored in the output. By default, values are rounded to the nearest unit before encoding. If you want to transfer more precision, increase the number. For example, a value of 1 implies that the first digit to the right of the decimal point will be preserved.</para>
<para>The sizes and bounding boxes parameters control whether optional information about the encoded length of the object and the bounds of the object are included in the output. By default they are not. Do not turn them on unless your client software has a use for them, as they just use up space (and saving space is the point of TWKB).</para>
- <para>The array-input form of the function is used to convert a collection of geometries and unique identifiers into a TWKB collection that preserves the identifiers. This is useful for clients that expect to unpack a collection and then access further information about the objects inside. You can create the arrays using the <ulink url="http://www.postgresql.org/docs/9.4/static/functions-aggregate.html">array_agg</ulink> function. The other parameters operate the same as for the simple form of the function.</para>
+ <para>The array-input form of the function is used to convert a collection of geometries and unique identifiers into a TWKB collection that preserves the identifiers. This is useful for clients that expect to unpack a collection and then access further information about the objects inside. You can create the arrays using the <ulink url="https://www.postgresql.org/docs/current/functions-aggregate.html">array_agg</ulink> function. The other parameters operate the same as for the simple form of the function.</para>
<note>
<para>The format specification is available online at <ulink url="https://github.com/TWKB/Specification">https://github.com/TWKB/Specification</ulink>, and code for building a JavaScript client can be found at <ulink url="https://github.com/TWKB/twkb.js">https://github.com/TWKB/twkb.js</ulink>.</para>
</note>
@@ -1534,7 +1534,7 @@ SELECT ST_AsTWKB(array_agg(geom), array_agg(gid)) FROM mytable;
<note><para>2D geometry support not yet complete. Inner rings currently just drawn as separate polygons. We are working on these.</para></note>
<para>Lots of advancements happening in 3D space particularly with <ulink url="https://www.web3d.org/wiki/index.php/X3D_and_HTML5">X3D Integration with HTML5</ulink></para>
<para>There is also a nice open source X3D viewer you can use to view rendered geometries. Free Wrl <ulink url="http://freewrl.sourceforge.net/">http://freewrl.sourceforge.net/</ulink> binaries available for Mac, Linux, and Windows. Use the FreeWRL_Launcher packaged to view the geometries.</para>
- <para>Also check out <ulink url="https://github.com/robe2/postgis_x3d_viewer">PostGIS minimalist X3D viewer</ulink> that utilizes this function and <ulink url="http://www.x3dom.org/">x3dDom html/js open source toolkit</ulink>.</para>
+ <para>Also check out <ulink url="https://git.osgeo.org/gitea/robe/postgis_x3d_viewer">PostGIS minimalist X3D viewer</ulink> that utilizes this function and <ulink url="http://www.x3dom.org/">x3dDom html/js open source toolkit</ulink>.</para>
<para>Availability: 2.0.0: ISO-IEC-19776-1.2-X3DEncodings-XML</para>
<para>Enhanced: 2.2.0: Support for GeoCoordinates and axis (x/y, long/lat) flipping. Look at options for details.</para>
<!-- Optionally mention 3d support -->
diff --git a/extensions/upgradeable_versions.mk b/extensions/upgradeable_versions.mk
index 1d19f154d..4742d1831 100644
--- a/extensions/upgradeable_versions.mk
+++ b/extensions/upgradeable_versions.mk
@@ -68,4 +68,5 @@ UPGRADEABLE_VERSIONS = \
3.1.3 \
3.1.4 \
3.1.5 \
- 3.2.0
+ 3.2.0 \
+ 3.2.1
-----------------------------------------------------------------------
Summary of changes:
Version.config | 2 +-
doc/reference_constructor.xml | 14 +++++++++-----
doc/reference_output.xml | 6 +++---
extensions/upgradeable_versions.mk | 3 ++-
4 files changed, 15 insertions(+), 10 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list