[SCM] PostGIS branch master updated. 3.6.0beta1-46-g785b53cd7
git at osgeo.org
git at osgeo.org
Sun Aug 17 23:10:35 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 785b53cd7d2526f972ce12d1b305d0db968da951 (commit)
via 984724955929c49c8ff832d54a267f4880d48e58 (commit)
via 556eb64538bc5bd3ae1fb39f02fadd5ad9b11379 (commit)
via c3b29709e612bcdb9a2cf74172a569d30d763f7a (commit)
from 136e4f62cb0d4e3400ac2a97b903bdf1ecc5f075 (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 785b53cd7d2526f972ce12d1b305d0db968da951
Author: Regina Obe <lr at pcorp.us>
Date: Mon Aug 18 02:09:18 2025 -0400
PREP for 3.6.0rc1 release
- Clean up NEWS
- Update release_notes
- Update date and GEOS 3.14 dependences on README
- Update pot
- Update version numbers
diff --git a/NEWS b/NEWS
index 0346015d6..4f946b0ba 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,7 @@
-PostGIS 3.6.0beta1
-2025/07/20
+PostGIS 3.6.0rc1
+2025/08/18
-This version requires PostgreSQL 12-18beta2, GEOS 3.8 or higher, and Proj 6.1+.
+This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
To take advantage of all features, GEOS 3.14+ is needed.
To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed.
@@ -50,7 +50,7 @@ Dapeng Wang, Zuo Chenwei from HighGo (Chinese Team)
- #5841, Change interrupt handling to remove use of pqsignal to support PG 18 (Paul Ramsey)
- Add ST_CoverageClean to edge match and gap remove polygonal
coverages (Paul Ramsey) from GEOS 3.14 (Martin Davis)
- - Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)
- #3110, GT-242 [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)
- - #5963, add ST_IntersectionFractions (Paul Ramsey)
+ - [raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)
+ - #5963, [raster] add ST_IntersectionFractions - Requires GEOS 3.14 (Paul Ramsey)
diff --git a/README.postgis b/README.postgis
index 7643c270d..51a1dff89 100644
--- a/README.postgis
+++ b/README.postgis
@@ -1,8 +1,8 @@
PostGIS - Geographic Information Systems Extensions to PostgreSQL
=================================================================
-:Version: 3.6.0beta1
-:Date: 2025-07-19
+:Version: 3.6.0rc1
+:Date: 2025-08-18
:Website: https://postgis.net
This distribution contains a module which implements GIS simple features, ties
@@ -65,7 +65,7 @@ For apt-based systems you can run this command to install the below dependencies
https://proj.org
* GEOS (Required, Version 3.8 or higher)
- - 3.14+ for ST_CoverageClean
+ - 3.14+ for ST_CoverageClean, raster ST_IntersectionFractions
- 3.12+ for ST_CoverageSimplify and ST_CoverageInvalidEdges
- 3.11+ for improved ST_ConcaveHull, ST_lineMerge,
and new functions ST_SimplifyPolygonHull, ST_TriangulatePolygon
diff --git a/Version.config b/Version.config
index cf6d63e9f..bce44cdfe 100644
--- a/Version.config
+++ b/Version.config
@@ -5,7 +5,7 @@
POSTGIS_MAJOR_VERSION=3
POSTGIS_MINOR_VERSION=6
-POSTGIS_MICRO_VERSION=0dev
+POSTGIS_MICRO_VERSION=0rc1
# Liblwgeom interface versioning, reset to 0:0:0 (cur:age:rev)
# when changing POSTGIS_MINOR_VERSION
diff --git a/doc/po/templates/postgis-manual.pot b/doc/po/templates/postgis-manual.pot
index 94054b27a..d3b3227ca 100644
--- a/doc/po/templates/postgis-manual.pot
+++ b/doc/po/templates/postgis-manual.pot
@@ -23795,143 +23795,6 @@ msgid ""
"linkend=\"postgis_gdal_enabled_drivers\"/>"
msgstr ""
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"<refpurpose>Generates a set of vector contours from the provided raster "
-"band, using the <link xlink:href=\"https://gdal.org/api/gdal_alg.html?"
-"highlight=contour#_CPPv421GDALContourGenerateEx15GDALRasterBandHPv12CSLConstList16GDALProgressFuncPv\">GDAL "
-"contouring algorithm</link>.</refpurpose>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"<para>Generates a set of vector contours from the provided raster band, "
-"using the <link xlink:href=\"https://gdal.org/api/gdal_alg.html?"
-"highlight=contour#_CPPv421GDALContourGenerateEx15GDALRasterBandHPv12CSLConstList16GDALProgressFuncPv\">GDAL "
-"contouring algorithm</link>.</para>"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"When the <varname>fixed_levels</varname> parameter is a non-empty array, the "
-"<varname>level_interval</varname> and <varname>level_base</varname> "
-"parameters are ignored."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Input parameters are:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The raster to generate the contour of"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The band to generate the contour of"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The elevation interval between contours generated"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The \"base\" relative to which contour intervals are applied, this is "
-"normally zero, but could be different. To generate 10m contours at 5, 15, "
-"25, ... the LEVEL_BASE would be 5."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"If <literal>true</literal>, contour polygons will be created, rather than "
-"polygon lines."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "Return values are a set of records with the following attributes:"
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "The geometry of the contour line."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid "A unique identifier given to the contour line by GDAL."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The raster value the line represents. For an elevation DEM input, this would "
-"be the elevation of the output contour."
-msgstr ""
-
-#. Tag: refpurpose
-#, no-c-format
-msgid ""
-"Interpolates a gridded surface based on an input set of 3-d points, using "
-"the X- and Y-values to position the points on the grid and the Z-value of "
-"the points as the surface elevation."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"Interpolates a gridded surface based on an input set of 3-d points, using "
-"the X- and Y-values to position the points on the grid and the Z-value of "
-"the points as the surface elevation. There are five interpolation algorithms "
-"available: inverse distance, inverse distance nearest-neighbor, moving "
-"average, nearest neighbor, and linear interpolation. See the <link xlink:"
-"href=\"https://gdal.org/programs/gdal_grid.html#interpolation-"
-"algorithms\">gdal_grid documentation</link> for more details on the "
-"algorithms and their parameters. For more information on how interpolations "
-"are calculated, see the <link xlink:href=\"https://gdal.org/tutorials/"
-"gdal_grid_tut.html\">GDAL grid tutorial</link>."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"The points to drive the interpolation. Any geometry with Z-values is "
-"acceptable, all points in the input will be used."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A string defining the algorithm and algorithm options, in the format used by "
-"<link xlink:href=\"https://gdal.org/programs/gdal_grid.html#interpolation-"
-"algorithms\">gdal_grid</link>. For example, for an inverse-distance "
-"interpolation with a smoothing of 2, you would use \"invdist:smoothing=2.0\""
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"A raster template to drive the geometry of the output raster. The width, "
-"height, pixel size, spatial extent and pixel type will be read from this "
-"template."
-msgstr ""
-
-#. Tag: para
-#, no-c-format
-msgid ""
-"By default the first band in the template raster is used to drive the output "
-"raster, but that can be adjusted with this parameter."
-msgstr ""
-
#. Tag: refpurpose
#, no-c-format
msgid "Change the SRID of all rasters in the user-specified column and table."
@@ -29339,6 +29202,143 @@ msgid ""
"linkend=\"RT_ST_Aspect\"/>"
msgstr ""
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Interpolates a gridded surface based on an input set of 3-d points, using "
+"the X- and Y-values to position the points on the grid and the Z-value of "
+"the points as the surface elevation."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Interpolates a gridded surface based on an input set of 3-d points, using "
+"the X- and Y-values to position the points on the grid and the Z-value of "
+"the points as the surface elevation. There are five interpolation algorithms "
+"available: inverse distance, inverse distance nearest-neighbor, moving "
+"average, nearest neighbor, and linear interpolation. See the <link xlink:"
+"href=\"https://gdal.org/programs/gdal_grid.html#interpolation-"
+"algorithms\">gdal_grid documentation</link> for more details on the "
+"algorithms and their parameters. For more information on how interpolations "
+"are calculated, see the <link xlink:href=\"https://gdal.org/tutorials/"
+"gdal_grid_tut.html\">GDAL grid tutorial</link>."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Input parameters are:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The points to drive the interpolation. Any geometry with Z-values is "
+"acceptable, all points in the input will be used."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A string defining the algorithm and algorithm options, in the format used by "
+"<link xlink:href=\"https://gdal.org/programs/gdal_grid.html#interpolation-"
+"algorithms\">gdal_grid</link>. For example, for an inverse-distance "
+"interpolation with a smoothing of 2, you would use \"invdist:smoothing=2.0\""
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"A raster template to drive the geometry of the output raster. The width, "
+"height, pixel size, spatial extent and pixel type will be read from this "
+"template."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"By default the first band in the template raster is used to drive the output "
+"raster, but that can be adjusted with this parameter."
+msgstr ""
+
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"<refpurpose>Generates a set of vector contours from the provided raster "
+"band, using the <link xlink:href=\"https://gdal.org/api/gdal_alg.html?"
+"highlight=contour#_CPPv421GDALContourGenerateEx15GDALRasterBandHPv12CSLConstList16GDALProgressFuncPv\">GDAL "
+"contouring algorithm</link>.</refpurpose>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"<para>Generates a set of vector contours from the provided raster band, "
+"using the <link xlink:href=\"https://gdal.org/api/gdal_alg.html?"
+"highlight=contour#_CPPv421GDALContourGenerateEx15GDALRasterBandHPv12CSLConstList16GDALProgressFuncPv\">GDAL "
+"contouring algorithm</link>.</para>"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"When the <varname>fixed_levels</varname> parameter is a non-empty array, the "
+"<varname>level_interval</varname> and <varname>level_base</varname> "
+"parameters are ignored."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The raster to generate the contour of"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The band to generate the contour of"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The elevation interval between contours generated"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The \"base\" relative to which contour intervals are applied, this is "
+"normally zero, but could be different. To generate 10m contours at 5, 15, "
+"25, ... the LEVEL_BASE would be 5."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"If <literal>true</literal>, contour polygons will be created, rather than "
+"polygon lines."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Return values are a set of records with the following attributes:"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "The geometry of the contour line."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "A unique identifier given to the contour line by GDAL."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"The raster value the line represents. For an elevation DEM input, this would "
+"be the elevation of the output contour."
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Raster Processing: Raster to Geometry"
@@ -29548,6 +29548,31 @@ msgid ""
"to always return multipolygon."
msgstr ""
+#. Tag: refpurpose
+#, no-c-format
+msgid ""
+"Calculates the fraction of each raster cell that is covered by a given "
+"geometry."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"Calculates the fraction of each raster cell that is covered by a given "
+"geometry. The first argument is a raster, which defines the grid geometry to "
+"use for the calculation. The extent and cell size are read from the raster "
+"parameter. The second argument is a geometry, which is overlaid with the "
+"grid, and each grid populated based on overlaying the geometry on the grid. "
+"For polygons, the value returned for each cell is the proportion of its area "
+"that is covered by the geometry. For linestrings, the value returned for "
+"each cell is the length contained in the cell."
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid "Availability: 3.6.0 Requires GEOS 3.14 or higher."
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Raster Operators"
@@ -35161,18 +35186,18 @@ msgstr ""
#. Tag: title
#, no-c-format
-msgid "PostGIS 3.6.0beta1"
+msgid "PostGIS 3.6.0rc1"
msgstr ""
#. Tag: para
#, no-c-format
-msgid "2025/07/19"
+msgid "2025/08/18"
msgstr ""
#. Tag: para
#, no-c-format
msgid ""
-"This version requires PostgreSQL 12-18beta2, GEOS 3.8 or higher, and Proj "
+"This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj "
"6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take "
"advantage of all SFCGAL features, SFCGAL 2.2+ is needed."
msgstr ""
@@ -35244,11 +35269,30 @@ msgid ""
"Census Bureau)"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid ""
+"<link xlink:href=\"https://trac.osgeo.org/postgis/ticket/5359\">#5359</"
+"link>, <link xlink:href=\"https://trac.osgeo.org/postgis/"
+"ticket/5897\">#5897</link>, <link xlink:href=\"https://git.osgeo.org/gitea/"
+"postgis/postgis/pulls/260\">GT-260</link> [tiger_geocoder] Use @extschema:"
+"extension@ for PG >= 16 to schema qualify dependent extensions, switch to "
+"use typmod for tiger tables (Regina Obe)"
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "Removed / Deprecate signatures"
msgstr ""
+#. Tag: para
+#, no-c-format
+msgid ""
+"<link xlink:href=\"https://trac.osgeo.org/postgis/ticket/5498\">#5498</link> "
+"Drop st_approxquantile(raster, double precision), wasn't usable as it "
+"triggered is not unique error when used (Regina Obe)"
+msgstr ""
+
#. Tag: title
#, no-c-format
msgid "New Features"
@@ -35347,7 +35391,17 @@ msgstr ""
#. Tag: para
#, no-c-format
-msgid "Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)"
+msgid ""
+"<link xlink:href=\"https://trac.osgeo.org/postgis/ticket/3110\">#3110</"
+"link>, <link xlink:href=\"https://git.osgeo.org/gitea/postgis/postgis/"
+"pulls/242\">GT-242</link> [topology] Support for bigint (Ayo Adesugba, U.S. "
+"Census Bureau)"
+msgstr ""
+
+#. Tag: para
+#, no-c-format
+msgid ""
+"[raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)"
msgstr ""
#. Tag: title
diff --git a/doc/release_notes.xml b/doc/release_notes.xml
index 5e03e9723..cb43b7d44 100644
--- a/doc/release_notes.xml
+++ b/doc/release_notes.xml
@@ -3,9 +3,9 @@
<title>Appendix</title>
<subtitle>Release Notes</subtitle>
<section>
- <title>PostGIS 3.6.0beta1</title>
- <para>2025/07/19</para>
- <para>This version requires PostgreSQL 12-18beta2, GEOS 3.8 or higher, and Proj 6.1+.
+ <title>PostGIS 3.6.0rc1</title>
+ <para>2025/08/18</para>
+ <para>This version requires PostgreSQL 12-18beta3, GEOS 3.8 or higher, and Proj 6.1+.
To take advantage of all features, GEOS 3.14+ is needed.
To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed.</para>
@@ -23,10 +23,14 @@
<para><link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/252">GT-252</link>, ST_NumGeometries/ST_GeometryN treat TIN and PolyhedralSurface as unitary geometries,
use ST_NumPatches/ST_PatchN for patch access (Loïc Bartoletti)</para>
<para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link>, [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
+ <para><link xlink:href="https://trac.osgeo.org/postgis/ticket/5359">#5359</link>, <link xlink:href="https://trac.osgeo.org/postgis/ticket/5897">#5897</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/260">GT-260</link>
+ [tiger_geocoder] Use @extschema:extension@ for PG >= 16 to schema qualify dependent extensions, switch to use typmod for tiger tables (Regina Obe)</para>
</simplesect>
<simplesect><title>Removed / Deprecate signatures</title>
<para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link>, [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
+ <para><link xlink:href="https://trac.osgeo.org/postgis/ticket/5498">#5498</link> Drop st_approxquantile(raster, double precision), wasn't usable as it triggered
+ is not unique error when used (Regina Obe)</para>
</simplesect>
<simplesect><title>New Features</title>
@@ -46,7 +50,8 @@
<para><link xlink:href="https://trac.osgeo.org/postgis/ticket/5841">#5841</link>, Change interrupt handling to remove use of pqsignal to support PG 18 (Paul Ramsey)</para>
<para>Add ST_CoverageClean to edge match and gap remove polygonal
coverages (Paul Ramsey) from GEOS 3.14 (Martin Davis)</para>
- <para>Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)</para>
+ <para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link> [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
+ <para>[raster] Add ST_ReclassExact to quickly remap values in raster (Paul Ramsey)</para>
<para><link xlink:href="https://trac.osgeo.org/postgis/ticket/3110">#3110</link>, <link xlink:href="https://git.osgeo.org/gitea/postgis/postgis/pulls/242">GT-242</link>, [topology] Support for bigint (Ayo Adesugba, U.S. Census Bureau)</para>
</simplesect>
</section>
diff --git a/extensions/upgradeable_versions.mk b/extensions/upgradeable_versions.mk
index e2734a44b..ca1f5d227 100644
--- a/extensions/upgradeable_versions.mk
+++ b/extensions/upgradeable_versions.mk
@@ -113,4 +113,5 @@ UPGRADEABLE_VERSIONS = \
3.5.2 \
3.5.3 \
3.6.0alpha1 \
- 3.6.0beta1
+ 3.6.0beta1 \
+ 3.6.0dev
commit 984724955929c49c8ff832d54a267f4880d48e58
Author: Regina Obe <lr at pcorp.us>
Date: Mon Aug 18 01:12:49 2025 -0400
Flip berrie 32-bit to 3.12.4, see if that is any better
diff --git a/ci/berrie/configs.sh b/ci/berrie/configs.sh
index 5119fcccc..fae39a0af 100644
--- a/ci/berrie/configs.sh
+++ b/ci/berrie/configs.sh
@@ -1,5 +1,5 @@
export WORKSPACE=/home/jenkins/workspace
-export GEOS_VER=3.11.6
+export GEOS_VER=3.12.4
export OS_BUILD=32
export PG_VER=15
commit 556eb64538bc5bd3ae1fb39f02fadd5ad9b11379
Author: Regina Obe <lr at pcorp.us>
Date: Mon Aug 18 00:05:12 2025 -0400
Change developer doc to markdown and rename to .md
This is for easier viewing on the repo
Also add more content about library guarding and terminology
diff --git a/doc/developer.md b/doc/developer.md
new file mode 100644
index 000000000..98f934a89
--- /dev/null
+++ b/doc/developer.md
@@ -0,0 +1,233 @@
+-------------------------------------------------------------------------
+
+TITLE: PostGIS Developer How-To
+
+AUTHOR: Name: Regina Obe
+
+DATE: 2025-08-12
+
+CATEGORY: Development Docs
+
+-------------------------------------------------------------------------
+Terminology
+============
+
+* PostGIS versions are 3 digits separated by a period
+
+ Major.Minor.Patch
+
+ - 3.0.0 is a major version
+ - 3.6.0 is a minor version
+ - 3.5.3 is a patch version
+
+* SQL Api functions are functions that are exposed to the user in the database.
+ They are either SQL, plpgsql, or C backed functions.
+
+* C Api functions are library functions that back SQL Api functions.
+
+Naming of library files
+========================
+Since PostGIS 3.0 library files are major versioned. Prior to 3 they were minor versioned.
+This means you'll find in the wild the following - the extension .so will be different based on OS
+
+ - postgis-2.4.so, postgis_topology-2.4.so, rtpostgis-2.4.so
+ - postgis-2.5.so, postgis_topology-2.5.so, rtpostgis-2.5.so
+ - postgis-3.so, postgis_raster-3.so, postgis_sfcgal-3.so, postgis_topology-3.so
+
+PostGIS 3 was a bit rocky in that some things were missed in 3.0 release and fixed in 3.1.
+Namely, postgis_sfcgal prior to 3.1 was embedded in the postgis-*.so which meant not all postgis libs
+had the same set of functions, which was BAD. When 3.1 rolled around the siamese beast was separated to form
+postgis-3.so, postgis_sfcgal-3.so.
+
+Also in 3.0.0, the raster functionality was removed from the postgis extension and moved to an extension called postgis_raster.
+The libraries of these were always separate, however the name rtpostgis- that packaged all the raster functions, did not match the extension
+name so was renamed, but for all purposes rtpostgis of the past is equivalent to postgis_raster of the present.
+
+All these changes were made to ease upgrade pains with pg_upgrade.
+As a developer you still have the option of having your lib files minor versioned
+for easier testing in the same cluster.
+
+To take advantage of this feature, when configuring postgis compile, use the switch *--with-library-minor-version*
+
+Does and Don'ts
+===================
+
+* Don't introduce new SQL Api functions in a Patch release.
+* Don't change structure definitions e.g. geometry_columns, geometry/raster type
+ in a patch release.
+
+* Do introduce new SQL Api functions in a Minor release.
+* Functions that are not exposed via the SQL Api can be introduced any time.
+* Only major versions can remove SQL api functions
+ or C api functions without stubbing (which we will cover shortly).
+
+* Only major versions can introduce functionality that requires a pg_dump / pg_restore.
+
+
+
+When removing objects impacts upgrade
+==========================================================
+
+There are several types of removals that impact user upgrades and should be carefully thought thru.
+
+* SQL Api functions
+* C Api functions
+* Types, Views, Tables are also exposed via SQL Api
+
+Functions internal to postgis that are never exposed and only used within postgis libraries
+can be shuffled around to your hearts content.
+
+UPGRADING C Api functions
+==========================
+
+You should avoid ever removing C Api function in Minor and patch releases of PostGIS.
+
+If there is a C Api function that you badly want to remove you need to stub it so the signature still
+exists but throws an error.
+
+These functions should be removed from whatever file
+they were in and stubbed in a deprecation file. Ideally you should never do this in a micro. Only minor.
+For Major such as when PostGIS 4 comes out we could in theory skip the legacy file and just chuck the function entirely.
+We could even blank out all the legacy files.
+
+A function can be stubbed in 3.0.0, but not 3.0.1, though there are cases where you might as long as
+you carefully fix up the SQL signature exposing it. The reason to avoid not doing this in a micro is people often do not
+run ALTER EXTENSION or SELECT postgis_extensions_upgrade() in a micro, so taking these out will break production code.
+
+ * For the postgis extension, these should go in postgis/postgis_legacy.c the stub will look something like this.
+
+ POSTGIS_DEPRECATE("2.0.0", postgis_uses_stats)
+
+ Note the specification of the version it was removed and the name of the function
+
+ * For postgis_sfcgal, deprecated C api functions should go in sfcgal/postgis_sfcgal_legacy.c
+ * For postgis_raster, raster/rt_pg/rtpg_legacy.c
+ * postgis_topology extension has never had any deprecated functions so there is currently no legacy file for it.
+ If there comes a need to deprecate C functions, then a file topology/postgis_topology_legacy.c will be created to store these.
+ * postgis_tiger_geocoder is all sql and plpgsql so it has no C backing functions.
+
+Why do we even bother replacing a good function with a function that throws an error? Because of pg_upgrade tool used
+to upgrade PostgreSQL clusters. When pg_upgrade runs, it does not use the regular CREATE EXTENSION routine that loads function definitions from
+a file. Instead it uses a naked CREATE EXTENSION and then tries to load all functions /types /etc/ from the old databases as they existed
+meaning they point at the same .so, .dll, .dylib whatever. When it tries to load these in, it validates the library to make sure said
+functions exist in the library. If these functions don't it will bail and pg_upgrade will fail. It however will do fine
+not complain if the function exists even if all the function knows how to do is throw an error.
+
+WHY oh WHY does it use old signatures in an old database instead of a fresh CREATE EXTENSION install?
+Primarily because objects are referenced by object identifiers AKA oids in views, tables, you name it, and if you create new function
+from scratch, even if it has the same exact definition as the old, it does not have the same OID.
+As such all db internal references would be broken
+if you try to overlay the old def structures onto the new extension install.
+
+So this whole care of legacy functions is to appease pg_upgrade.
+
+
+UPGRADING SQL Api functions
+============================
+
+For most SQL Api functions, nothing special needs to be done beyond
+noting a CHANGED in version or AVAILABILITY in the respective .sql.in files.
+
+The SQL Api definitions are found in following places:
+
+* postgis extension, postgis/postgis_sql.in, geography.sql.in, postgis.bin.sql.in, or postgis_spgist.sql.in
+* postgis_raster extension raster/rt_pg/rtpostgis.sql.in
+* postgis_sfcgal extension sfcgal/sfcgal.sql.in
+* postgis_topology - topology/sql/*.sql.in
+
+We use perl scripts to stitch together these various SQL and
+read meta comments to determine what to do during an upgrade.
+The utils/create_upgrade.pl is the script that is tasked with creating upgrade scripts.
+
+The various notes you put in .sql.in files take the following form and precede the function/type/etc definition:
+
+* -- Availability: Is only informational 2.0.0 where 2.0.0 represents the version it was introduced in.
+* -- Changed: Is only informational. You'll often see an Availability comment followed by a changed comment.
+ e.g.
+ -- Availability: 0.1.0
+ -- Changed: 2.0.0 use gserialized selectivity estimators
+* -- Replaces: is both informational and also instructs the perl upgrade script to protect the user from some upgrade pains.
+ You use Replaces instead of just a simple Changed, if you are changing inputs to the function or changing
+ outputs of the function. So any change to the api
+
+ Such a comment would look something like:
+
+ -- Availability: 2.1.0
+ -- Changed: 3.1.0 - add zvalue=0.0 parameter
+ -- Replaces ST_Force3D(geometry) deprecated in 3.1.0
+
+ When utils/create_upgrade.pl script comes across a Replaces clause, the perl script will change the statement to do the following
+ 1) Finds the old definition
+ 2) renames the old definition to ST_Force3D_deprecated_by_postgis_310
+ 3) Installs the new version of the function.
+ 4) At the end of the upgrade script, it will try to drop the function. If the old function is bound
+ to user objects, it will leave the old function alone and warn the user as part of the upgrade, that they have objects bound to an old signature.
+
+ Why do we do this? Because all objects are bound by oids and not names. So if a user has a view or materialized view, it will be bound to
+ ST_Force3D_deprecated_by_postgis_310 and not the new ST_Force3D. We can't drop things bound to user objects without executing a
+ DROP ... CASCADE, which will destroy user objects.
+
+
+For some objects such as types and casts, comments are not sufficient to get create_upgrade.pl to do the right thing.
+In these cases you need to do this work yourself as needed.
+Case in point, if you are removing a signature and have no replacement for it. You just want to drop it.
+You'll put the code in the relevant **after_upgrade** script corresponding to the extension you are changing.
+If you need something dropped or need to make some system changes that would prevent new function from being installed, then you would put this in a **before_upgrade** script.
+
+The relevant files for each extension are as follows:
+
+* postgis - postgis/postgis_before_upgrade.sql , postgis/postgis_after_upgrade.sql
+* postgis_raster - raster/rtpostgis_drop.sql.in, rtpostgis_upgrade_cleanup.sql.in
+ (the rtpostgis_upgrade_cleanup.sql.in is equivalent to the after_ugprade script of other extensions)
+* postgis_sfcgal - sfcgal/sfcgal_before_upgrade.sql.in, sfcgal/sfcgal_after_upgrade.sql.in
+* postgis_topology - sfcgal/topology_before_upgrade.sql.in, sfcgal/topology_after_upgrade.sql.in
+
+Helper function calls you'll find in these scripts are the following and are defined in postgis/common_before_upgrade.sql and dropped in
+postgis/common_after_upgrade.sql
+
+* _postgis_drop_function_by_signature - generally you want to use this one as it only cares about input types of functions
+* _postgis_drop_function_by_identity - this one you'll want to use if for some awful reason, all you are doing is changing the names of input types.
+
+These ones are new in 3.6.0 to handle the very delicate major upgrade of topology which required changing of data types and tables
+
+* _postgis_drop_cast_by_types
+* _postgis_add_column_to_table
+
+
+Dependency Library Guarding
+============================
+
+On many occasions, we'll introduce functionality that can only be used if PostGIS is compiled
+with a dependency library higher than X? Where X is some version of a dependency library.
+
+Dependency guards need to be put in both the C library files and our test files.
+On some occassions where we need to do something different based on version of PostgreSQL,
+you'll see guards in the SQL files as well.
+
+We have guards in place in the code to handle these for dependency libraries
+
+* PostgreSQL
+ - sql, c: ``#if POSTGIS_PGSQL_VERSION >= 150``
+ - regress/../tests.mk.in
+* GEOS
+ - c: ``#if POSTGIS_GEOS_VERSION < 31000``
+ - tests: shell expr "$(POSTGIS_GEOS_VERSION)" ">=" 30900
+ * regress/../tests.mk.in
+ * raster/rt_pg/tests/tests.mi.in
+* SFCGAL
+ - c: ``#if POSTGIS_SFCGAL_VERSION >= 10400``
+ - tests: ``ifeq ($(shell expr "$(POSTGIS_SFCGAL_VERSION)" ">=" 10401),1)``
+ * sfcgal/regress/tests.mk.in
+* PROJ
+* GDAL
+
+Even if a user can't use a certain function, that function still needs to be exposed,
+but instead of doing something functional, will output an error that the extension needs to be compiled
+with lib xxx or higher. Also the function has to be available in the C lib, as such the guarding is always done
+on the C lib side and very rarely on the sql files.
+
+
+
+
+
+
diff --git a/doc/developer.txt b/doc/developer.txt
deleted file mode 100644
index 580ebe79e..000000000
--- a/doc/developer.txt
+++ /dev/null
@@ -1,143 +0,0 @@
--------------------------------------------------------------------------
-
-TITLE: PostGIS Developer How-To
-
-AUTHOR: Name: Regina Obe
-
-DATE: 2025-08-12
-
-CATEGORY: Development Docs
-
--------------------------------------------------------------------------
-
-When removing objects impacts upgrade
-==========================================================
-
-There are two types of function removals that impact user upgrades and should be carefully thought thru.
-
-* SQL Api functions - these are functions that are exposed to the user in the database.
- They are either SQl, plpgsql, or C backed functions.
-
-* C Api functions -- these are postgis lib functions that back SQL Api functions
-
-* Types, Views are also exposed via SQL Api
-
-Functions internal to postgis that are never exposed and only used within postgis libraries
-can be shuffled around to your hearts content.
-
-UPGRADING C Api functions
-==========================
-
-You should avoid ever removing C Api function in Minor and Micro releases of PostGIS.
-If there is a C Api function that you badly want to remove you need to stub it so the signature still
-exists but throws an error.
-
-These functions should be removed from whatever file
-they were in and stubbed in a deprecation file. Ideally you should never do this in a micro. Only minor.
-For Major such as when PostGIS 4 comes out we could in theory skip the legacy file and just chuck the function entirely.
-
-So a function can be stubbed in 3.0.0, but not 3.0.1, though there are cases where you might as long as
-you carefully fix up the SQL signature exposing it. The reason to avoid not doing this in a micro is people often do not
-run ALTER EXTENSION or SELECT postgis_extensions_upgrade() in a micro, so taking these out will break production code.
-
- * For the postgis extension, these should go in postgis/postgis_legacy.c the stub will look something like this.
-
- POSTGIS_DEPRECATE("2.0.0", postgis_uses_stats)
-
- Note the specification of the version it was removed and the name of the function
-
- * For postgis_sfcgal, deprecated C api functions should go in sfcgal/postgis_sfcgal_legacy.c
- * For postgis_raster, raster/rt_pg/rtpg_legacy.c
- * postgis_topology extension has never had any deprecated functions so there is currently no legacy file for it.
- If there comes a need to deprecate C functions, then a file topology/postgis_topology_legacy.c will be created to store these.
- * postgis_tiger_geocoder is all sql and plpgsql so it has no C backing functions.
-
-Why do we even bother replacing a good function with a function that throws an error? Because of pg_upgrade tool used
-to upgrade PostgreSQL clusters. When pg_upgrade runs, it does not use the regular CREATE EXTENSION routine that loads function definitions from
-a file. Instead it uses a naked CREATE EXTENSION and then tries to load all functions /types /etc/ from the old databases as they existed
-meaning they point at the same .so, .dll, .dylib whatever. When it tries to load these in, it validates the library to make sure said
-functions exist in the library. If these functions don't it will bail and pg_upgrade will fail. It however will do fine
-not complain if the function exists even if all the function knows how to do is throw an error.
-
-WHY oh WHY does it use old signatures in an old database instead of a fresh CREATE EXTENSION install?
-Primarily because objects are referenced by object identifiers AKA oids in views, tables, you name it, and if you create new function
-from scratch, even if it has the same exact definition as the old, it does not have the same OID.
-As such all db internal references would be broken
-if you try to overlay the old def structures onto the new extension install.
-
-So this whole care of legacy functions is to appease pg_upgrade.
-
-
-UPGRADING SQL Api functions
-============================
-
-For most SQL Api functions, nothing special needs to be done beyond
-noting a CHANGED in version or AVAILABILITY in the respective .sql.in files.
-
-The SQL Api definitions are found in following places:
-
-* postgis extension, postgis/postgis_sql.in, geography.sql.in, postgis.bin.sql.in, or postgis_spgist.sql.in
-* postgis_raster extension raster/rt_pg/rtpostgis.sql.in
-* postgis_sfcgal extension sfcgal/sfcgal.sql.in
-* postgis_topology - topology/sql/*.sql.in
-
-We use perl scripts to stitch together these various SQL and
-read meta comments to determine what to do during an upgrade.
-The utils/create_upgrade.pl is the script that is tasked with creating upgrade scripts.
-
-The various notes you put in .sql.in files take the following form and precede the function/type/etc definition:
-
-* -- Availability: Is only informational 2.0.0 where 2.0.0 represents the version it was introduced in.
-* -- Changed: Is only informational. You'll often see an Availability comment followed by a changed comment.
- e.g.
- -- Availability: 0.1.0
- -- Changed: 2.0.0 use gserialized selectivity estimators
-* -- Replaces: is both informational and also instructs the perl upgrade script to protect the user from some upgrade pains.
- You use Replaces instead of just a simple Changed, if you are changing inputs to the function or changing
- outputs of the function. So any change to the api
-
- Such a comment would look something like:
- -- Availability: 2.1.0
- -- Changed: 3.1.0 - add zvalue=0.0 parameter
- -- Replaces ST_Force3D(geometry) deprecated in 3.1.0
-
- When utils/create_upgrade.pl script comes across a Replaces clause, the perl script will change the statement to do the following
- 1) Finds the old definition
- 2) renames the old definition to ST_Force3D_deprecated_by_postgis_310
- 3) Installs the new version of the function.
- 4) At the end of the upgrade script, it will try to drop the function. If the old function is bound
- to user objects, it will leave the old function alone and warn the user as part of the upgrade, that they have objects bound to an old signature.
-
- Why do we do this? Because all objects are bound by oids and not names. So if a user has a view or materialized view, it will be bound to
- ST_Force3D_deprecated_by_postgis_310 and not the new ST_Force3D. We can't drop things bound to user objects without executing a
- DROP ... CASCADE, which will destroy user objects.
-
-
-
-For some objects such as types and casts, comments are not sufficient to get create_upgrade.pl to do the right thing.
-In these cases you need to do this work yourself as needed.
-Case in point, if you are removing a signature and have no replacement for it. You just want to drop it.
-In these cases you'll put code in the before_upgrade.sql or after_upgrade.sql corresponding to the extension you are changing.
-
-
-* postgis extension - postgis/postgis_before_upgrade.sql , postgis/postgis_after_upgrade.sql
-* postgis_sfcgal - sfcgal/sfcgal_before_upgrade.sql.in, sfcgal/sfcgal_after_upgrade.sql.in
-* postgis_topology - sfcgal/topology_before_upgrade.sql.in, sfcgal/topology_after_upgrade.sql.in
-
-Helper function calls you'll find in these scripts are the following and are defined in postgis/common_before_upgrade.sql and dropped in
-postgis/common_after_upgrade.sql
-
-* _postgis_drop_function_by_signature
-* _postgis_drop_function_by_identity
-
-# these ones are new in 3.6.0 to handle the very delicate major upgrade of topology
-
-* _postgis_drop_cast_by_types
-* _postgis_add_column_to_table
-
-
-
-
-
-
-
commit c3b29709e612bcdb9a2cf74172a569d30d763f7a
Author: Regina Obe <lr at pcorp.us>
Date: Mon Aug 18 00:04:01 2025 -0400
Remove accidentally committed raster/regress/tests.mk
Also prevent it from being committed in future
diff --git a/.gitignore b/.gitignore
index e9e76c0a9..7b0df68ff 100644
--- a/.gitignore
+++ b/.gitignore
@@ -28,6 +28,10 @@ doc/images
doc/html/images/generator
doc/html/images/Makefile
regression.out
+raster/test/regress/tests.mk
+regress/core/tests.mk
+sfcgla/regress/tests.mk
+
# PNG images under doc/html/images
# should be either symlinks or generated
diff --git a/raster/test/regress/tests.mk b/raster/test/regress/tests.mk
deleted file mode 100644
index 7bcdda63b..000000000
--- a/raster/test/regress/tests.mk
+++ /dev/null
@@ -1,156 +0,0 @@
-# **********************************************************************
-# *
-# * PostGIS - Spatial Types for PostgreSQL
-# * http://postgis.net
-# *
-# * Copyright (C) 2020 Sandro Santilli <strk at kbt.io>
-# *
-# * This is free software; you can redistribute and/or modify it under
-# * the terms of the GNU General Public Licence. See the COPYING file.
-# *
-# **********************************************************************
-
-POSTGIS_GEOS_VERSION=31400
-
-override RUNTESTFLAGS := $(RUNTESTFLAGS) --raster
-
-override RUNTESTFLAGS_INTERNAL := \
- --before-upgrade-script $(top_srcdir)/raster/test/regress/hooks/hook-before-upgrade-raster.sql \
- $(RUNTESTFLAGS_INTERNAL) \
- --after-upgrade-script $(top_srcdir)/raster/test/regress/hooks/hook-after-upgrade-raster.sql
-
-RASTER_TEST_FIRST = \
- $(top_srcdir)/raster/test/regress/check_gdal \
- $(top_srcdir)/raster/test/regress/loader/load_outdb
-
-RASTER_TEST_LAST = \
- $(top_srcdir)/raster/test/regress/clean
-
-RASTER_TEST_METADATA = \
- $(top_srcdir)/raster/test/regress/check_raster_columns \
- $(top_srcdir)/raster/test/regress/check_raster_overviews
-
-RASTER_TEST_IO = \
- $(top_srcdir)/raster/test/regress/rt_io
-
-RASTER_TEST_BASIC_FUNC = \
- $(top_srcdir)/raster/test/regress/rt_bytea \
- $(top_srcdir)/raster/test/regress/rt_wkb \
- $(top_srcdir)/raster/test/regress/box3d \
- $(top_srcdir)/raster/test/regress/rt_addband \
- $(top_srcdir)/raster/test/regress/rt_band \
- $(top_srcdir)/raster/test/regress/rt_tile
-
-RASTER_TEST_PROPS = \
- $(top_srcdir)/raster/test/regress/rt_dimensions \
- $(top_srcdir)/raster/test/regress/rt_scale \
- $(top_srcdir)/raster/test/regress/rt_pixelsize \
- $(top_srcdir)/raster/test/regress/rt_upperleft \
- $(top_srcdir)/raster/test/regress/rt_rotation \
- $(top_srcdir)/raster/test/regress/rt_georeference \
- $(top_srcdir)/raster/test/regress/rt_set_properties \
- $(top_srcdir)/raster/test/regress/rt_isempty \
- $(top_srcdir)/raster/test/regress/rt_hasnoband \
- $(top_srcdir)/raster/test/regress/rt_metadata \
- $(top_srcdir)/raster/test/regress/rt_rastertoworldcoord \
- $(top_srcdir)/raster/test/regress/rt_worldtorastercoord \
- $(top_srcdir)/raster/test/regress/rt_convexhull \
- $(top_srcdir)/raster/test/regress/rt_envelope
-
-RASTER_TEST_BANDPROPS = \
- $(top_srcdir)/raster/test/regress/rt_band_properties \
- $(top_srcdir)/raster/test/regress/rt_set_band_properties \
- $(top_srcdir)/raster/test/regress/rt_pixelaspolygons \
- $(top_srcdir)/raster/test/regress/rt_pixelaspoints \
- $(top_srcdir)/raster/test/regress/rt_pixelascentroids \
- $(top_srcdir)/raster/test/regress/rt_setvalues_array \
- $(top_srcdir)/raster/test/regress/rt_summarystats \
- $(top_srcdir)/raster/test/regress/rt_count \
- $(top_srcdir)/raster/test/regress/rt_histogram \
- $(top_srcdir)/raster/test/regress/rt_quantile \
- $(top_srcdir)/raster/test/regress/rt_valuecount \
- $(top_srcdir)/raster/test/regress/rt_valuepercent \
- $(top_srcdir)/raster/test/regress/rt_bandmetadata \
- $(top_srcdir)/raster/test/regress/rt_pixelvalue \
- $(top_srcdir)/raster/test/regress/rt_neighborhood \
- $(top_srcdir)/raster/test/regress/rt_nearestvalue \
- $(top_srcdir)/raster/test/regress/rt_pixelofvalue \
- $(top_srcdir)/raster/test/regress/rt_polygon \
- $(top_srcdir)/raster/test/regress/rt_setbandpath
-
-RASTER_TEST_UTILITY = \
- $(top_srcdir)/raster/test/regress/rt_utility \
- $(top_srcdir)/raster/test/regress/rt_fromgdalraster \
- $(top_srcdir)/raster/test/regress/rt_asgdalraster \
- $(top_srcdir)/raster/test/regress/rt_astiff \
- $(top_srcdir)/raster/test/regress/rt_asjpeg \
- $(top_srcdir)/raster/test/regress/rt_aspng \
- $(top_srcdir)/raster/test/regress/rt_reclass \
- $(top_srcdir)/raster/test/regress/rt_reclassexact \
- $(top_srcdir)/raster/test/regress/rt_gdalwarp \
- $(top_srcdir)/raster/test/regress/rt_gdalcontour \
- $(top_srcdir)/raster/test/regress/rt_asraster \
- $(top_srcdir)/raster/test/regress/rt_asrasteragg \
- $(top_srcdir)/raster/test/regress/rt_dumpvalues \
- $(top_srcdir)/raster/test/regress/rt_makeemptycoverage \
- $(top_srcdir)/raster/test/regress/rt_createoverview
-
-RASTER_TEST_MAPALGEBRA = \
- $(top_srcdir)/raster/test/regress/rt_mapalgebraexpr \
- $(top_srcdir)/raster/test/regress/rt_mapalgebrafct \
- $(top_srcdir)/raster/test/regress/rt_mapalgebraexpr_2raster \
- $(top_srcdir)/raster/test/regress/rt_mapalgebrafct_2raster \
- $(top_srcdir)/raster/test/regress/rt_mapalgebrafctngb \
- $(top_srcdir)/raster/test/regress/rt_mapalgebrafctngb_userfunc \
- $(top_srcdir)/raster/test/regress/rt_intersection \
- $(top_srcdir)/raster/test/regress/rt_clip \
- $(top_srcdir)/raster/test/regress/rt_mapalgebra \
- $(top_srcdir)/raster/test/regress/rt_mapalgebra_expr \
- $(top_srcdir)/raster/test/regress/rt_mapalgebra_mask \
- $(top_srcdir)/raster/test/regress/rt_union \
- $(top_srcdir)/raster/test/regress/rt_invdistweight4ma \
- $(top_srcdir)/raster/test/regress/rt_4ma \
- $(top_srcdir)/raster/test/regress/rt_setvalues_geomval \
- $(top_srcdir)/raster/test/regress/rt_elevation_functions \
- $(top_srcdir)/raster/test/regress/rt_colormap \
- $(top_srcdir)/raster/test/regress/rt_grayscale
-
-RASTER_TEST_SREL = \
- $(top_srcdir)/raster/test/regress/rt_gist_relationships \
- $(top_srcdir)/raster/test/regress/rt_intersects \
- $(top_srcdir)/raster/test/regress/rt_samealignment \
- $(top_srcdir)/raster/test/regress/rt_geos_relationships \
- $(top_srcdir)/raster/test/regress/rt_iscoveragetile
-
-RASTER_TEST_BUGS = \
- $(top_srcdir)/raster/test/regress/bug_test_car5 \
- $(top_srcdir)/raster/test/regress/permitted_gdal_drivers \
- $(top_srcdir)/raster/test/regress/tickets
-
-RASTER_TEST_LOADER = \
- $(top_srcdir)/raster/test/regress/loader/Basic \
- $(top_srcdir)/raster/test/regress/loader/Projected \
- $(top_srcdir)/raster/test/regress/loader/BasicCopy \
- $(top_srcdir)/raster/test/regress/loader/BasicFilename \
- $(top_srcdir)/raster/test/regress/loader/BasicOutDB \
- $(top_srcdir)/raster/test/regress/loader/Tiled10x10 \
- $(top_srcdir)/raster/test/regress/loader/Tiled10x10Copy \
- $(top_srcdir)/raster/test/regress/loader/Tiled8x8 \
- $(top_srcdir)/raster/test/regress/loader/TiledAuto \
- $(top_srcdir)/raster/test/regress/loader/TiledAutoSkipNoData \
- $(top_srcdir)/raster/test/regress/loader/TiledAutoCopyn
-
-RASTER_TESTS := $(RASTER_TEST_FIRST) \
- $(RASTER_TEST_METADATA) $(RASTER_TEST_IO) $(RASTER_TEST_BASIC_FUNC) \
- $(RASTER_TEST_PROPS) $(RASTER_TEST_BANDPROPS) \
- $(RASTER_TEST_UTILITY) $(RASTER_TEST_MAPALGEBRA) $(RASTER_TEST_SREL) \
- $(RASTER_TEST_BUGS) \
- $(RASTER_TEST_LOADER) \
- $(RASTER_TEST_LAST)
-
-TESTS += $(RASTER_TESTS)
-
-ifeq ($(shell expr "$(POSTGIS_GEOS_VERSION)" ">=" 31400),1)
- TESTS += \
- $(top_srcdir)/raster/test/regress/rt_intersection_fractions
-endif
-----------------------------------------------------------------------
Summary of changes:
.gitignore | 4 +
NEWS | 10 +-
README.postgis | 6 +-
Version.config | 2 +-
ci/berrie/configs.sh | 2 +-
doc/developer.md | 233 +++++++++++++++++++++++++
doc/developer.txt | 143 ---------------
doc/po/templates/postgis-manual.pot | 336 +++++++++++++++++++++---------------
doc/release_notes.xml | 13 +-
extensions/upgradeable_versions.mk | 3 +-
raster/test/regress/tests.mk | 156 -----------------
11 files changed, 453 insertions(+), 455 deletions(-)
create mode 100644 doc/developer.md
delete mode 100644 doc/developer.txt
delete mode 100644 raster/test/regress/tests.mk
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list