[SCM] PostGIS branch master updated. 3.6.0rc2-480-geeffb4311
git at osgeo.org
git at osgeo.org
Sat May 9 20:43:15 PDT 2026
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 eeffb4311706d8b93c84b4817bbbbf3142cd3626 (commit)
from f3f83293aa7ba73988d579937a0251ee313f042f (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 eeffb4311706d8b93c84b4817bbbbf3142cd3626
Author: Paul Ramsey <pramsey at cleverelephant.ca>
Date: Sat May 9 20:43:01 2026 -0700
Edits and tweaks to docs, closes #6077
diff --git a/doc/reference_accessor.xml b/doc/reference_accessor.xml
index 014d71b8f..fd1efaaf1 100644
--- a/doc/reference_accessor.xml
+++ b/doc/reference_accessor.xml
@@ -2692,7 +2692,7 @@ VALUES (ST_GeomFromEWKT('POLYHEDRALSURFACE( ((0 0 0, 0 0 1, 0 1 1, 0 1 0, 0 0 0)
<note>
<para>Index is 1-based as for OGC specs since version 0.8.0.
- Backward indexing (negative index) is not in OGC
+ Backward indexing (negative index) is not in OGC.
Previous versions implemented this as 0-based instead.</para>
</note>
diff --git a/doc/reference_constructor.xml b/doc/reference_constructor.xml
index 93d2a06cc..f3ddbc048 100644
--- a/doc/reference_constructor.xml
+++ b/doc/reference_constructor.xml
@@ -1287,7 +1287,7 @@ has an unknown SRID (as is the case by default).</para>
<refsection>
<title>Example: Generating the word 'Yo'</title>
- <programlisting>SELECT ST_AsText(ST_Letters('Yo'), 1);</programlisting>
+ <programlisting>SELECT ST_AsText(ST_Letters('Yo'));</programlisting>
<informalfigure>
<mediaobject>
<imageobject>
diff --git a/doc/reference_editor.xml b/doc/reference_editor.xml
index a74e529da..cff821413 100644
--- a/doc/reference_editor.xml
+++ b/doc/reference_editor.xml
@@ -2013,9 +2013,7 @@ SELECT ST_AsText( ST_RemoveRepeatedPoints( 'LINESTRING (0 0, 0 0, 1 1, 5 5, 1 1,
<title>Examples</title>
<programlisting>
SELECT ST_AsText(geom) as line, ST_AsText(ST_Reverse(geom)) As reverseline
-FROM
-(SELECT ST_MakeLine(ST_Point(1,2),
- ST_Point(1,10)) As geom) as foo;
+FROM ST_MakeLine(ST_Point(1,2), ST_Point(1,10)) As geom;
--result
line | reverseline
---------------------+----------------------
diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml
index d50c5758c..5b2de34fa 100644
--- a/doc/reference_measure.xml
+++ b/doc/reference_measure.xml
@@ -68,7 +68,7 @@ from (
</programlisting>
<para>Return area square feet and transform to Massachusetts state plane meters (EPSG:26986) to get square meters.
Note this is in square feet because 2249 is
- Massachusetts State Plane Feet and transformed area is in square meters since EPSG:26986 is state plane Massachusetts meters </para>
+ Massachusetts State Plane Feet and transformed area is in square meters since EPSG:26986 is state plane Massachusetts meters. </para>
<programlisting>select ST_Area(geom) sqft,
ST_Area(ST_Transform(geom, 26986)) As sqm
from (
@@ -1175,7 +1175,7 @@ ST_3DLength
<refsection>
<title>Description</title>
- <para>Calculates the length or perimeter of a geometry on an ellipsoid. This
+ <para>Calculates the length or perimeter of a geometry on a spheroid. This
is useful if the coordinates of the geometry are in
longitude/latitude and a length is desired without reprojection.
The spheroid is specified by a text value as follows:</para>
diff --git a/doc/reference_overlay.xml b/doc/reference_overlay.xml
index 16ffc5f90..2e6eaa80d 100644
--- a/doc/reference_overlay.xml
+++ b/doc/reference_overlay.xml
@@ -284,8 +284,8 @@ where not ST_IsEmpty(ST_Buffer(ST_Intersection(country.geom, poly.geom), 0.0));<
</refsection>
<refsection>
- <title>Examples: 2.5Dish</title>
- <para>Note this is not a true intersection, compare to the same example using <xref linkend="ST_3DIntersection"/>.</para>
+ <title>Examples: 2.5D geometries</title>
+ <para>Note this is not a true 3D intersection. It uses 2.5D geometries (geometries with Z ordinates, but where calculations are performed in 2D). Compare to the same example using <xref linkend="ST_3DIntersection"/>.</para>
<programlisting>
select ST_AsText(ST_Intersection(linestring, polygon)) As wkt
from ST_GeomFromText('LINESTRING Z (2 2 6,1.5 1.5 7,1 1 8,0.5 0.5 8,0 0 10)') AS linestring
diff --git a/doc/reference_relationship.xml b/doc/reference_relationship.xml
index f0e9c7385..1cd519be8 100644
--- a/doc/reference_relationship.xml
+++ b/doc/reference_relationship.xml
@@ -2261,7 +2261,7 @@ SELECT s.gid, s.school_name
LEFT JOIN hospitals h ON ST_DWithin(s.geom, h.geom, 3000)
WHERE h.gid IS NULL;
--- Find broadcasting towers that receiver with limited range can receive.
+-- Find broadcasting towers that a receiver with limited range can receive.
-- Data is geometry in Spherical Mercator (SRID=3857), ranges are approximate.
-- Create geometry index that will check proximity limit of user to tower
diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index 896184c0f..0fc321fe7 100644
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -53,6 +53,7 @@
If Z or M values are present in a geometry value, they must be defined for each point in the geometry.
If a geometry has Z or M ordinates the <emphasis role="bold">coordinate dimension</emphasis> is 3D;
if it has both Z and M the coordinate dimension is 4D.
+ The coordinate dimension is at least 2, because every geometry has at least X and Y coordinates.
</para>
<para>Geometry values are associated with a
@@ -70,7 +71,7 @@
<para>The geometry <emphasis role="bold">dimension</emphasis> is a property of geometry types.
Point types have dimension 0, linear types have dimension 1,
- and polygonal types have dimension 2.
+ polygonal types have dimension 2, and solid types have dimension 3.
Collections have the dimension of the maximum element dimension.
</para>
@@ -96,12 +97,13 @@
are defined for each geometry type.
Geometries are topologically closed, so they always contain their boundary.
The boundary is a geometry of dimension one less than that of the geometry itself.
+ For example, the boundary of a Polygon is its rings (LineStrings), the boundary of a LineString is its endpoints (Points), and the boundary of a Point is empty.
</para>
<para>The OGC geometry model defines validity rules for each geometry type.
These rules ensure that geometry values represents realistic
situations (e.g. it is possible to specify a polygon
- with a hole lying outside the shell, but this makes no sense geometrically
+ with a hole lying outside its shell, but this makes no sense geometrically
and is thus invalid).
PostGIS also allows storing and manipulating invalid geometry values.
This allows detecting and fixing them if needed.
@@ -166,6 +168,9 @@ POINT ZM (1 2 3 4)
<title>MultiPolygon</title>
<para>A MultiPolygon is a collection of non-overlapping, non-adjacent Polygons.
Polygons in the collection may touch only at a finite number of points.
+ (Two polygons are adjacent if they share an edge.
+ They touch if they share only points or edges on their boundaries).
+ For more details on MultiPolygon validity, see <xref linkend="OGC_Validity"/>.
</para>
<programlisting>MULTIPOLYGON (((1 5, 5 5, 5 1, 1 1, 1 5)), ((6 5, 9 1, 6 1, 6 5)))</programlisting>
</section>
@@ -376,7 +381,7 @@ geometry = ST_GeomFromText(text WKT, SRID);</programlisting>
<para>For example, a statement to create and insert a spatial object from WKT and a SRID is:</para>
<programlisting>INSERT INTO geotable ( geom, name )
- VALUES ( ST_GeomFromText('POINT(-126.4 45.32)', 312), 'A Place');</programlisting>
+ VALUES ( ST_GeomFromText('POINT(-126.4 45.32)', 312), 'A Place'); -- 312 is the SRID</programlisting>
<para>Well-Known Binary (WKB) provides a portable, full-precision representation
of spatial data as binary data (arrays of bytes).
@@ -426,7 +431,7 @@ geometry = ST_GeomFromWKB(bytea WKB, SRID);
which means that all access is done via invoking functions on geometry values.
Functions allow creating geometry objects,
accessing or updating all internal fields,
- and compute new geometry values.
+ and computing new geometry values.
PostGIS supports all the functions specified in the OGC
<link xlink:href="https://portal.ogc.org/files/?artifact_id=25354"><emphasis>Simple feature access - Part 2: SQL option</emphasis></link>
(SFS) specification, as well many others.
@@ -825,8 +830,9 @@ SELECT ST_Distance('LINESTRING(-122.33 47.606, 0.0 51.5)'::geometry, 'POINT(-21.
</question>
<answer>
- <para> By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up will with local planar results in good local projections.
+ <para> By default, all distance and area calculations are done on the spheroid. You should find that the results of calculations in local areas match up well with local planar results in good local projections.
Over larger areas, the spheroidal calculations will be more accurate than any calculation done on a projected plane.
+ The difference is that the spheroid takes into account the curvature and non-spherical shape of the Earth, whereas planar calculations assume a flat surface.
</para>
<para>All the geography functions have the option of using a sphere calculation, by setting a final boolean parameter to 'FALSE'. This will somewhat speed up calculations, particularly for cases where the geometries are very simple.</para>
</answer>
@@ -1672,7 +1678,9 @@ VALUES ( 990000,
<term><varname>coord_dimension</varname></term>
<listitem>
- <para>The coordinate dimension (2, 3 or 4) of the column.</para>
+ <para>The coordinate dimension (2, 3 or 4) of the column.
+ The coordinate dimension is at least 2, representing X and Y coordinates.
+ </para>
</listitem>
</varlistentry>
diff --git a/doc/using_postgis_query.xml b/doc/using_postgis_query.xml
index c788ce92f..fb9776f51 100644
--- a/doc/using_postgis_query.xml
+++ b/doc/using_postgis_query.xml
@@ -316,7 +316,8 @@ FROM city JOIN state ON ST_Intersects(city.geom, state.geom);
</informalfigure></para><para>For example, consider a linear
dataset representing a road network. It may be required
to identify all road segments that cross
- each other, not at a point, but in a line (perhaps to validate some business rule).
+ each other, not at a point, but in a line (perhaps to validate a business rule
+ such as ensuring that no two different roads share a common segment).
In this case <xref linkend="ST_Crosses"/> does not
provide the necessary spatial filter, since for
linear features it returns <varname>true</varname> only where they cross at a point.
@@ -642,12 +643,12 @@ GROUP BY m.name
ORDER BY roads_km;
name | roads_km
-----------------------------+------------------
-SURREY | 1539.47553551242
-VANCOUVER | 1450.33093486576
-LANGLEY DISTRICT | 833.793392535662
-BURNABY | 773.769091404338
-PRINCE GEORGE | 694.37554369147
+----------------------------+----------
+SURREY | 1539.476
+VANCOUVER | 1450.331
+LANGLEY DISTRICT | 833.793
+BURNABY | 773.769
+PRINCE GEORGE | 694.376
...</programlisting>
<para>This query takes a while, because every road in the table is
-----------------------------------------------------------------------
Summary of changes:
doc/reference_accessor.xml | 2 +-
doc/reference_constructor.xml | 2 +-
doc/reference_editor.xml | 4 +---
doc/reference_measure.xml | 4 ++--
doc/reference_overlay.xml | 4 ++--
doc/reference_relationship.xml | 2 +-
doc/using_postgis_dataman.xml | 20 ++++++++++++++------
doc/using_postgis_query.xml | 15 ++++++++-------
8 files changed, 30 insertions(+), 23 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list