[SCM] PostGIS branch master updated. 3.6.0rc2-173-gd19e312fc
git at osgeo.org
git at osgeo.org
Thu Oct 30 12:52:18 PDT 2025
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 d19e312fccf56ee6b50e1e90f1dfeffadb0eb336 (commit)
from a474eff150abde9c83b0385cac88cb529779f705 (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 d19e312fccf56ee6b50e1e90f1dfeffadb0eb336
Author: Darafei Praliaskouski <me at komzpa.net>
Date: Thu Oct 30 23:46:20 2025 +0400
[doc] Clean up mentions of legacy software versions
diff --git a/doc/administration.xml b/doc/administration.xml
index da9f063f4..9756f184b 100644
--- a/doc/administration.xml
+++ b/doc/administration.xml
@@ -384,7 +384,5 @@ ALTER TABLE spatial_ref_sys ADD PRIMARY KEY(srid));
</section>
</section>
-
-
-
+ </section>
</chapter>
diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index 92005387e..ffacaeaf3 100644
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -20,14 +20,14 @@
<para> <note><para>
-If you are using tiger geocoder (tiger_2010),
+If you are using the TIGER Geocoder (tiger_2010),
you can upgrade the scripts using the accompanying upgrade_geocoder.bat
/ .sh scripts in extras/tiger. One major change between <varname>tiger_2010</varname> and <varname>tiger_2011+</varname> is that the <varname>county</varname> and <varname>state</varname> tables are no longer broken out by state. If you have data from tiger_2010 and want to replace with tiger_2015, refer to <xref linkend="upgrade_tiger_geocoder"/>
</para></note>
<note>
- <para>New in PostGIS 2.2.0 release is support for Tiger 2015 data and inclusion of Address Standardizer as part of PostGIS.</para>
- <para>New in PostGIS 2.1.0 release is ability to install tiger geocoder with PostgreSQL extension model if you are running PostgreSQL 9.1+. Refer to <xref linkend="install_tiger_geocoder_extension"/> for details.</para></note>
+ <para>New in PostGIS 2.2.0 release is support for TIGER 2015 data and inclusion of Address Standardizer as part of PostGIS.</para>
+ <para>New in PostGIS 2.1.0 release is ability to install the TIGER Geocoder with the PostgreSQL extension model. Refer to <xref linkend="install_tiger_geocoder_extension"/> for details.</para></note>
</para>
<para>The <xref linkend="Pagc_Normalize_Address"/> function as a drop in replacement for in-built <xref linkend="Normalize_Address"/>. Refer to <xref linkend="installing_pagc_address_standardizer"/> for compile and installation instructions.</para>
@@ -48,11 +48,11 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat
</info>
- <para>There are a couple other open source geocoders for PostGIS, that unlike tiger geocoder have the advantage of multi-country geocoding support</para>
+ <para>There are a couple other open source geocoders for PostGIS, that unlike the TIGER Geocoder have the advantage of multi-country geocoding support</para>
<itemizedlist>
<listitem><para><link xlink:href="http://wiki.openstreetmap.org/wiki/Nominatim">Nominatim</link>
uses OpenStreetMap gazeteer formatted data. It requires osm2pgsql for loading the data together with PostgreSQL and PostGIS. It is packaged as a webservice interface and seems designed to be called as a webservice.
- Just like the tiger geocoder, it has both a geocoder and a reverse geocoder component. From the documentation, it is unclear if it has a pure SQL interface like the tiger geocoder, or if a good deal of the logic is implemented in the web interface.</para></listitem>
+ Just like the TIGER Geocoder, it has both a geocoder and a reverse geocoder component. From the documentation, it is unclear if it has a pure SQL interface like the TIGER Geocoder, or if a good deal of the logic is implemented in the web interface.</para></listitem>
<listitem><para><link xlink:href="http://www.gisgraphy.com/">GIS Graphy</link> also utilizes PostGIS and like Nominatim works with OpenStreetMap (OSM) data. It comes with a loader to load OSM data and similar to Nominatim is capable of geocoding not just US. Much like Nominatim, it runs as a webservice and relies on Java 1.5, Servlet apps, Solr. GisGraphy is cross-platform and also has a reverse geocoder among some other neat features.</para></listitem>
</itemizedlist>
@@ -632,7 +632,7 @@ tract_id
</listitem>
</orderedlist>
<para role="availability" conformance="2.0.0">Availability: 2.0.0 </para>
- <note><para><xref linkend="Loader_Generate_Script"/> includes this logic, but if you installed the tiger geocoder with older scripts, rerun it on the states you have already processed
+ <note><para><xref linkend="Loader_Generate_Script"/> includes this logic, but if you installed the TIGER Geocoder with older scripts, rerun it on the states you have already processed
to get these additional tables.</para></note>
</refsection>
@@ -646,7 +646,7 @@ set STATEDIR="\gisdata\www2.census.gov\geo\pvs\tiger2010st\25_Massachusetts"
set TMPDIR=\gisdata\temp\
set UNZIPTOOL="C:\Program Files\7-Zip\7z.exe"
set WGETTOOL="C:\wget\wget.exe"
-set PGBIN=C:\projects\pg\pg<version>win\bin\
+set PGBIN=C:\projects\pg\pg[version]win\bin\
set PGPORT=5432
set PGHOST=localhost
set PGUSER=postgres
@@ -675,7 +675,7 @@ cd %TMPDIR%
TMPDIR="/gisdata/temp/"
UNZIPTOOL=unzip
WGETTOOL="/usr/bin/wget"
-export PGBIN=/usr/pgsql-<version>/bin
+export PGBIN=/usr/pgsql-[version]/bin
export PGPORT=5432
export PGHOST=localhost
export PGUSER=postgres
@@ -759,7 +759,7 @@ for z in *.zip; do $UNZIPTOOL -o -d $TMPDIR $z; done
set TMPDIR=\gisdata\temp\
set UNZIPTOOL="C:\Program Files\7-Zip\7z.exe"
set WGETTOOL="C:\wget\wget.exe"
-set PGBIN=C:\Program Files\PostgreSQL\<version>\bin\
+set PGBIN=C:\Program Files\PostgreSQL\[version]\bin\
set PGPORT=5432
set PGHOST=localhost
set PGUSER=postgres
@@ -780,7 +780,7 @@ cd \gisdata/ftp2.census.gov/geo/tiger/TIGER2015/PLACE
TMPDIR="/gisdata/temp/"
UNZIPTOOL=unzip
WGETTOOL="/usr/bin/wget"
-export PGBIN=/usr/lib/postgresql/<version>/bin
+export PGBIN=/usr/lib/postgresql/[version]/bin
-- variables used by psql: https://www.postgresql.org/docs/current/static/libpq-envars.html
export PGPORT=5432
export PGHOST=localhost
diff --git a/doc/reference_input.xml b/doc/reference_input.xml
index 62ce603dc..c6a264d30 100644
--- a/doc/reference_input.xml
+++ b/doc/reference_input.xml
@@ -1076,8 +1076,8 @@ ST_GeogFromWKB(E'\\001\\002\\000\\000\\000\\002\\000\\000\\000\\037\\205\\353Q\\
\\312Q\\300\\366{b\\235*!E@\\225|\\354.P\\312Q
\\300p\\231\\323e1!E@');</programlisting>
- <note><para>In PostgreSQL 9.1+ - standard_conforming_strings is set to on by default, where as in past versions it was set to off. You can change defaults as needed
- for a single query or at the database or server level. Below is how you would do it with standard_conforming_strings = on. In this case we escape the ' with standard ansi ',
+ <note><para>In PostgreSQL, standard_conforming_strings is set to on by default. You can change the default as needed
+ for a single query or at the database or server level. Below is how you would do it with standard_conforming_strings = on. In this case we escape the ' with standard ANSI ',
but slashes are not escaped</para></note>
<programlisting>
set standard_conforming_strings = on;
diff --git a/doc/reference_measure.xml b/doc/reference_measure.xml
index 4e15fd519..d50c5758c 100644
--- a/doc/reference_measure.xml
+++ b/doc/reference_measure.xml
@@ -1012,7 +1012,7 @@ SELECT DISTINCT ON (buildings.gid) buildings.gid, parcels.parcel_id
The units of length is determined by the
spatial reference system of the geometry.</para>
<para>For geography types: computation is performed using the inverse geodesic calculation. Units of length are in meters.
- If PostGIS is compiled with PROJ version 4.8.0 or later, the spheroid is specified by the SRID, otherwise it is exclusive to WGS84.
+ The spheroid is specified by the SRID; when no SRID is provided, WGS84 is used.
If <varname>use_spheroid = false</varname>, then the calculation is based on a sphere instead of a spheroid.
</para>
@@ -1722,7 +1722,7 @@ LINESTRING(0.5 0.00032,0.5 0)
non-areal geometries. For linear geometries use <xref linkend="ST_Length"/>. For geometry types, units for perimeter measures are specified by the
spatial reference system of the geometry.</para>
<para>For geography types, the calculations are performed using the inverse geodesic problem, where perimeter units are in meters.
- If PostGIS is compiled with PROJ version 4.8.0 or later, the spheroid is specified by the SRID, otherwise it is exclusive to WGS84.
+ The spheroid is specified by the SRID; when no SRID is provided, WGS84 is used.
If <varname>use_spheroid = false</varname>, then calculations will approximate a sphere instead of a spheroid.</para>
<para>Currently this is an alias for ST_Perimeter2D, but this may change to support higher dimensions.</para>
diff --git a/doc/reference_raster.xml b/doc/reference_raster.xml
index 79d82cec2..dc1e99c9b 100644
--- a/doc/reference_raster.xml
+++ b/doc/reference_raster.xml
@@ -14181,7 +14181,7 @@ FROM (SELECT ST_SetRotation(rast, 0.1, 0.1) As rast
<refsection>
<title>Examples</title>
- <programlisting> -- this syntax requires PostgreSQL 9.3+
+ <programlisting> -- this syntax uses a LATERAL join
SELECT val, ST_AsText(geom) As geomwkt
FROM (
SELECT dp.*
diff --git a/extensions/README b/extensions/README
index 7f941b69d..16729759e 100644
--- a/extensions/README
+++ b/extensions/README
@@ -1,16 +1,11 @@
PostGIS Extension for PostgreSQL
================================
-PostgreSQL 9.6 (and up) supports PostGIS extensions. A database can easily be
-extended to use PostGIS using the syntax::
+A database can easily be extended to use PostGIS using the syntax::
CREATE EXTENSION postgis; -- Includes raster
CREATE EXTENSION postgis_topology; -- Depends on postgis
-Requirements
-------------
- * PostgreSQL 9.6 or later
-
Building and installing
-----------------------
First, make sure you follow the regular configuration and installation steps,
diff --git a/postgis/gserialized_gist_2d.c b/postgis/gserialized_gist_2d.c
index 3ac5a3567..06224676f 100644
--- a/postgis/gserialized_gist_2d.c
+++ b/postgis/gserialized_gist_2d.c
@@ -1077,8 +1077,8 @@ Datum gserialized_gist_consistent_2d(PG_FUNCTION_ARGS)
bool result;
BOX2DF query_gbox_index;
- /* PostgreSQL 8.4 and later require the RECHECK flag to be set here,
- rather than being supplied as part of the operator class definition */
+ /* PostgreSQL requires the RECHECK flag to be set here,
+ rather than being supplied as part of the operator class definition */
bool *recheck = (bool *) PG_GETARG_POINTER(4);
/* We set recheck to false to avoid repeatedly pulling every "possibly matched" geometry
diff --git a/postgis/gserialized_gist_nd.c b/postgis/gserialized_gist_nd.c
index 8fe07b0ea..a6e44da63 100644
--- a/postgis/gserialized_gist_nd.c
+++ b/postgis/gserialized_gist_nd.c
@@ -1087,8 +1087,8 @@ Datum gserialized_gist_consistent(PG_FUNCTION_ARGS)
char gidxmem[GIDX_MAX_SIZE];
GIDX *query_gbox_index = (GIDX *)gidxmem;
- /* PostgreSQL 8.4 and later require the RECHECK flag to be set here,
- rather than being supplied as part of the operator class definition */
+ /* PostgreSQL requires the RECHECK flag to be set here,
+ rather than being supplied as part of the operator class definition */
bool *recheck = (bool *)PG_GETARG_POINTER(4);
/* We set recheck to false to avoid repeatedly pulling every "possibly matched" geometry
diff --git a/postgis/gserialized_typmod.c b/postgis/gserialized_typmod.c
index b07ad9343..308297fa7 100644
--- a/postgis/gserialized_typmod.c
+++ b/postgis/gserialized_typmod.c
@@ -332,7 +332,7 @@ static uint32 gserialized_typmod_in(ArrayType *arr, int is_geography)
/*
** geography_typmod_in(cstring[]) returns int32
**
-** Modified from ArrayGetIntegerTypmods in PostgreSQL 8.3
+** Modified from ArrayGetIntegerTypmods in PostgreSQL
*/
PG_FUNCTION_INFO_V1(geography_typmod_in);
Datum geography_typmod_in(PG_FUNCTION_ARGS)
@@ -349,7 +349,7 @@ Datum geography_typmod_in(PG_FUNCTION_ARGS)
/*
** geometry_typmod_in(cstring[]) returns int32
**
-** Modified from ArrayGetIntegerTypmods in PostgreSQL 8.3
+** Modified from ArrayGetIntegerTypmods in PostgreSQL
*/
PG_FUNCTION_INFO_V1(geometry_typmod_in);
Datum geometry_typmod_in(PG_FUNCTION_ARGS)
diff --git a/postgis/lwgeom_box3d.c b/postgis/lwgeom_box3d.c
index 11ba71483..1fbde98e2 100644
--- a/postgis/lwgeom_box3d.c
+++ b/postgis/lwgeom_box3d.c
@@ -631,7 +631,7 @@ Datum BOX3D_construct(PG_FUNCTION_ARGS)
PG_RETURN_POINTER(result);
}
-/** needed for sp-gist support PostgreSQL 11+ **/
+/** Needed for SP-GiST support. **/
/*****************************************************************************
* BOX3D functions
*****************************************************************************/
diff --git a/postgis/lwgeom_box3d.h b/postgis/lwgeom_box3d.h
index 80107977e..39ec10f3a 100644
--- a/postgis/lwgeom_box3d.h
+++ b/postgis/lwgeom_box3d.h
@@ -63,7 +63,7 @@ bool BOX3D_back_internal(BOX3D *box1, BOX3D *box2);
bool BOX3D_overback_internal(BOX3D *box1, BOX3D *box2);
double BOX3D_distance_internal(BOX3D *box1, BOX3D *box2);
-/** needed for sp-gist support PostgreSQL 11+ **/
+/** Needed for SP-GiST support. **/
Datum BOX3D_contains(PG_FUNCTION_ARGS);
Datum BOX3D_contained(PG_FUNCTION_ARGS);
Datum BOX3D_overlaps(PG_FUNCTION_ARGS);
-----------------------------------------------------------------------
Summary of changes:
doc/administration.xml | 4 +---
doc/extras_tigergeocoder.xml | 20 ++++++++++----------
doc/reference_input.xml | 4 ++--
doc/reference_measure.xml | 4 ++--
doc/reference_raster.xml | 2 +-
extensions/README | 7 +------
postgis/gserialized_gist_2d.c | 4 ++--
postgis/gserialized_gist_nd.c | 4 ++--
postgis/gserialized_typmod.c | 4 ++--
postgis/lwgeom_box3d.c | 2 +-
postgis/lwgeom_box3d.h | 2 +-
11 files changed, 25 insertions(+), 32 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list