[postgis-tickets] [SCM] PostGIS branch master updated. 3.4.0rc1-516-gca33aa7cb
git at osgeo.org
git at osgeo.org
Wed Sep 13 04:43:27 PDT 2023
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 ca33aa7cbce3b25eb7fdaa42b93b9e5a280525f9 (commit)
from d0b1200c304f0014e1f94ab368330b77bfeaec08 (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 ca33aa7cbce3b25eb7fdaa42b93b9e5a280525f9
Author: Sandro Santilli <strk at kbt.io>
Date: Wed Sep 13 13:43:06 2023 +0200
Revert drop of entities
diff --git a/doc/po/templates/reference_input.xml.pot b/doc/po/templates/reference_input.xml.pot
index 449e3c48f..2a541f759 100644
--- a/doc/po/templates/reference_input.xml.pot
+++ b/doc/po/templates/reference_input.xml.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
-"POT-Creation-Date: 2023-09-12 22:08+0000\n"
+"POT-Creation-Date: 2023-09-13 11:41+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
diff --git a/doc/po/templates/reference_measure.xml.pot b/doc/po/templates/reference_measure.xml.pot
index b229528c0..8d83afc65 100644
--- a/doc/po/templates/reference_measure.xml.pot
+++ b/doc/po/templates/reference_measure.xml.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.kde.org\n"
-"POT-Creation-Date: 2023-09-12 22:08+0000\n"
+"POT-Creation-Date: 2023-09-13 11:40+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -1055,7 +1055,9 @@ msgstr ""
#: reference_measure.xml:926
#, no-c-format
msgid ""
-"SPHEROID[<NAME>,<SEMI-MAJOR AXIS>,<INVERSE FLATTENING>]"
+"<![CDATA[[\n"
+"SPHEROID[<NAME>,<SEMI-MAJOR AXIS>,<INVERSE FLATTENING>]\n"
+"]]>"
msgstr ""
#. Tag: para
diff --git a/doc/reference_input.xml b/doc/reference_input.xml
index 913845202..9c626d44f 100644
--- a/doc/reference_input.xml
+++ b/doc/reference_input.xml
@@ -44,7 +44,7 @@
postgis-specific approach.</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
<para>Performed by the GEOS module.</para>
<para role="availability" conformance="1.1.0">Availability: 1.1.0</para>
</refsection>
@@ -95,7 +95,7 @@
approach.</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
<para>Performed by the GEOS module.</para>
<para role="availability" conformance="1.1.0">Availability: 1.1.0</para>
</refsection>
@@ -211,8 +211,8 @@ SELECT ST_AsEWKT(ST_GeogFromText('SRID=4267;POINT(-77.0092 38.889588)'));
</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]]</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant;</para>
</refsection>
@@ -255,10 +255,10 @@ SELECT ST_AsEWKT(ST_GeogFromText('SRID=4267;POINT(-77.0092 38.889588)'));
identifier</para>
</note>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced.</para>
- <para>[[[Z_support]]]</para>
- <para>[[[curve_support]]]</para>
- <para>[[[P_support]]]</para>
- <para>[[[T_support]]]</para>
+ <para>&Z_support;</para>
+ <para>&curve_support;</para>
+ <para>&P_support;</para>
+ <para>&T_support;</para>
</refsection>
<refsection>
@@ -489,8 +489,8 @@ SELECT ST_GeomFromEWKT('POLYHEDRALSURFACE(
</refsynopsisdiv>
<refsection>
<title>Description</title>
- <para>[[[sfs_compliant]]]</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 5.1.40</para>
+ <para>&sfs_compliant;</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 5.1.40</para>
</refsection>
<refsection>
<title>See Also</title>
@@ -530,9 +530,9 @@ SELECT ST_GeomFromEWKT('POLYHEDRALSURFACE(
</para>
</note>
- <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>
+ <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_MakePoint"/> and is OGC-compliant, but doesn't support anything but 2D points.</para></note>
<warning><para role="changed" conformance="2.0.0">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>
@@ -625,8 +625,8 @@ SELECT ST_GeomFromText('CIRCULARSTRING(220268 150415,220227 150505,220227 150406
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 7.2.8</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 7.2.8</para>
</refsection>
@@ -689,8 +689,8 @@ aline | null_return
</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]]SQL-MM 3: 9.4.4</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant;SQL-MM 3: 9.4.4</para>
</refsection>
@@ -750,8 +750,8 @@ aline | null_return
</para>
</note>
- <para>[[[sfs_compliant]]] 3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 9.2.4</para>
+ <para>&sfs_compliant; 3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 9.2.4</para>
</refsection>
@@ -812,8 +812,8 @@ SELECT ST_MPointFromText('MULTIPOINT((-70.9590 42.1180),(-70.9611 42.1223))', 43
</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 9.6.4</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 9.6.4</para>
</refsection>
@@ -875,8 +875,8 @@ SELECt ST_MPolyFromText('MULTIPOLYGON(((-70.916 42.1002,-70.9468 42.0946,-70.976
It is slower than ST_GeomFromText since it adds an additional validation step. If you are building points from long lat coordinates and care more about performance and accuracy than OGC compliance, use <xref linkend="ST_MakePoint"/> or OGC compliant alias <xref linkend="ST_Point"/>. </para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2 - option SRID is from the conformance suite.</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 6.1.8</para>
+ <para>&sfs_compliant; s3.2.6.2 - option SRID is from the conformance suite.</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 6.1.8</para>
</refsection>
<refsection>
@@ -926,8 +926,8 @@ SELECT ST_PointFromText('POINT(-71.064544 42.28787)', 4326);
<note><para>If you are absolutely sure all your WKT geometries are polygons, don't use this function.
It is slower than ST_GeomFromText since it adds an additional validation step. </para></note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 8.3.6</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 8.3.6</para>
</refsection>
<refsection>
@@ -971,7 +971,7 @@ t
</refsynopsisdiv>
<refsection>
<title>Description</title>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 5.1.34</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 5.1.34</para>
</refsection>
<refsection>
<title>See Also</title>
@@ -1011,7 +1011,7 @@ t
<para>If SRID is not specified, it defaults to 4326 (WGS 84 long lat).</para>
- <para>[[[curve_support]]]</para>
+ <para>&curve_support;</para>
</refsection>
@@ -1059,10 +1059,10 @@ ST_GeogFromWKB(E'\\001\\002\\000\\000\\000\\002\\000\\000\\000\\037\\205\\353Q\\
identifier</para>
</note>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced.</para>
- <para>[[[Z_support]]]</para>
- <para>[[[curve_support]]]</para>
- <para>[[[P_support]]]</para>
- <para>[[[T_support]]]</para>
+ <para>&Z_support;</para>
+ <para>&curve_support;</para>
+ <para>&P_support;</para>
+ <para>&T_support;</para>
</refsection>
<refsection>
@@ -1122,9 +1122,9 @@ SELECT ST_GeomFromEWKB('\001\002\000\000 \255\020\000\000\003\000\000\000\344J=\
SQL. This is an alternate name for ST_WKBToSQL.</para>
<para>If SRID is not specified, it defaults to 0 (Unknown).</para>
- <para>[[[sfs_compliant]]] s3.2.7.2 - the optional SRID is from the conformance suite</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 5.1.41</para>
- <para>[[[curve_support]]]</para>
+ <para>&sfs_compliant; s3.2.7.2 - the optional SRID is from the conformance suite</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 5.1.41</para>
+ <para>&curve_support;</para>
</refsection>
@@ -1209,8 +1209,8 @@ SELECT
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 7.2.9</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 7.2.9</para>
</refsection>
@@ -1280,8 +1280,8 @@ aline | null_return
<varname>LINESTRING</varname>.</para>
</note>
- <para>[[[sfs_compliant]]] s3.2.6.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 7.2.9</para>
+ <para>&sfs_compliant; s3.2.6.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 7.2.9</para>
</refsection>
<refsection>
@@ -1341,10 +1341,10 @@ aline | null_return
<para>If an SRID is not specified, it defaults to 0. <varname>NULL</varname> is
returned if the input <varname>bytea</varname> does not represent a
<varname>POINT</varname> geometry.</para>
- <para>[[[sfs_compliant]]] s3.2.7.2</para>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 6.1.9</para>
- <para>[[[Z_support]]]</para>
- <para>[[[curve_support]]]</para>
+ <para>&sfs_compliant; s3.2.7.2</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 6.1.9</para>
+ <para>&Z_support;</para>
+ <para>&curve_support;</para>
</refsection>
<refsection>
@@ -1396,7 +1396,7 @@ SELECT
</refsynopsisdiv>
<refsection>
<title>Description</title>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 5.1.36</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 5.1.36</para>
</refsection>
<refsection>
<title>See Also</title>
@@ -1567,9 +1567,9 @@ SELECT ST_AsText(ST_GeomFromGeoHash('9qqj7nmxncgyy4d0dbxqz0', 10));
<para role="availability" conformance="1.5">Availability: 1.5, requires libxml2 1.6+</para>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced.</para>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 default srid optional parameter added.</para>
- <para>[[[Z_support]]]</para>
- <para>[[[P_support]]]</para>
- <para>[[[T_support]]]</para>
+ <para>&Z_support;</para>
+ <para>&P_support;</para>
+ <para>&T_support;</para>
<para>GML allow mixed dimensions (2D and 3D inside the same MultiGeometry for instance). As PostGIS geometries don't, ST_GeomFromGML convert the whole geometry to 2D if a missing Z dimension is found once.</para>
<para>GML support mixed SRS inside the same MultiGeometry. As PostGIS geometries don't, ST_GeomFromGML, in this case, reproject all subgeometries to the SRS root node. If no srsName attribute available for the GML root node, the function throw an error.</para>
@@ -1707,7 +1707,7 @@ SELECT ST_AsEWKT(ST_GeomFromGML('
<para role="availability" conformance="2.0.0">Availability: 2.0.0 requires - JSON-C >= 0.9</para>
<note><para>If you do not have JSON-C enabled, support you will get an error notice instead of seeing an output.
To enable JSON-C, run configure --with-jsondir=/path/to/json-c. See <xref linkend="installation_configuration"/> for details.</para></note>
- <para>[[[Z_support]]]</para>
+ <para>&Z_support;</para>
</refsection>
<refsection>
@@ -1763,7 +1763,7 @@ LINESTRING(1 2,4 5,7 8)
</para>
<para role="availability" conformance="1.5">Availability: 1.5, requires libxml2 2.6+</para>
- <para>[[[Z_support]]]</para>
+ <para>&Z_support;</para>
<note>
<para>ST_GeomFromKML function not support SQL/MM curves geometries.</para>
</note>
@@ -1862,7 +1862,7 @@ LINESTRING(-113.98 39.198,-113.981 39.195)
</refsynopsisdiv>
<refsection>
<title>Description</title>
- <para>[[[sqlmm_compliant]]] SQL-MM 3: 5.1.50 (except for curves support).</para>
+ <para>&sqlmm_compliant; SQL-MM 3: 5.1.50 (except for curves support).</para>
<para role="availability" conformance="1.5">Availability: 1.5, requires libxml2 1.6+</para>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced.</para>
<para role="enhanced" conformance="2.0.0">Enhanced: 2.0.0 default srid optional parameter added.</para>
-----------------------------------------------------------------------
Summary of changes:
doc/po/templates/reference_input.xml.pot | 2 +-
doc/po/templates/reference_measure.xml.pot | 6 +-
doc/reference_input.xml | 98 +++++++++++++++---------------
3 files changed, 54 insertions(+), 52 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list