[SCM] PostGIS branch master updated. 3.6.0rc2-172-ga474eff15
git at osgeo.org
git at osgeo.org
Thu Oct 30 12:19: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 a474eff150abde9c83b0385cac88cb529779f705 (commit)
from afc7eeac415514ddf0ba5cfe63d42cca7716cf6b (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 a474eff150abde9c83b0385cac88cb529779f705
Author: Darafei Praliaskouski <me at komzpa.net>
Date: Thu Oct 30 23:19:21 2025 +0400
[doc] Clean up mentions of legacy software versions
diff --git a/doc/administration.xml b/doc/administration.xml
index e7cf63d1b..da9f063f4 100644
--- a/doc/administration.xml
+++ b/doc/administration.xml
@@ -155,12 +155,12 @@ environment).</para></note>
<para>If you installed your database using extensions, you'll need to upgrade using the extension model as well. If you installed using the old sql script way, you are advised to switch your install to extensions because the script way is no longer supported. </para>
- <section xml:id="soft_upgrade_extensions"><title>Soft Upgrade 9.1+ using extensions</title>
- <para>If you originally installed PostGIS with extensions, then you need to upgrade using extensions as well. Doing a minor upgrade with extensions, is fairly painless.</para>
- <para>If you are running PostGIS 3 or above, then you should use the <xref linkend="PostGIS_Extensions_Upgrade"/> function to upgrade to the latest version you have installed.</para>
+ <section xml:id="soft_upgrade_extensions"><title>Soft upgrade using extensions</title>
+ <para>If you originally installed PostGIS with extensions, then you need to upgrade using extensions as well. Doing a minor upgrade with extensions is fairly painless.</para>
+ <para>Use the <xref linkend="PostGIS_Extensions_Upgrade"/> function to upgrade to the latest version you have installed.</para>
<programlisting>SELECT postgis_extensions_upgrade();</programlisting>
- <para>If you are running PostGIS 2.5 or lower, then do the following:</para>
+ <para>If you are upgrading a database that still runs PostGIS 2.5, issue an <command>ALTER EXTENSION</command> followed by <function>postgis_extensions_upgrade()</function> to make sure the legacy <varname>postgis_raster</varname> objects are folded back into the main extension.</para>
<programlisting>ALTER EXTENSION postgis UPDATE;
SELECT postgis_extensions_upgrade();
-- This second call is needed to rebundle postgis_raster extension
@@ -195,71 +195,12 @@ ALTER EXTENSION postgis_topology UPDATE TO "&last_release_version;next";</progra
</section>
<section xml:id="soft_upgrade_sql_script">
- <title>Soft Upgrade Pre 9.1+ or without extensions</title>
+ <title>Soft upgrade without extensions</title>
- <para>This section applies only to those who installed PostGIS
- not using extensions. If you have extensions and try to
- upgrade with this approach you'll get messages like:</para>
+ <para>Extensions have been the supported installation method for many releases. If you still rely on an unpackaged installation, perform a <link linkend="hard_upgrade">HARD UPGRADE</link> into a database created with extensions and migrate your data there.</para>
+ </section>
- <programlisting>can't drop … because postgis extension depends on it</programlisting>
-
- <para>NOTE: if you are moving from PostGIS 1.* to PostGIS 2.* or from
- PostGIS 2.* prior to r7409, you cannot use this procedure but
- would rather need to do a
- <link linkend="hard_upgrade">HARD UPGRADE</link>.
- </para>
-
- <para>
- After compiling and installing (make install) you should
- find a set of <filename>*_upgrade.sql</filename>
- files in the installation folders. You can list
- them all with:
- </para>
-
- <programlisting>ls `pg_config --sharedir`/contrib/postgis-&last_release_version;/*_upgrade.sql</programlisting>
-
- <para>
- Load them all in turn, starting from <filename>postgis_upgrade.sql</filename>.
- </para>
-
- <programlisting>psql -f postgis_upgrade.sql -d your_spatial_database</programlisting>
-
- <para>
- The same procedure applies to raster,
- topology and sfcgal extensions, with upgrade files named
- <filename>rtpostgis_upgrade.sql</filename>,
- <filename>topology_upgrade.sql</filename> and
- <filename>sfcgal_upgrade.sql</filename> respectively.
- If you need them:
- </para>
-
- <programlisting>psql -f rtpostgis_upgrade.sql -d your_spatial_database</programlisting>
- <programlisting>psql -f topology_upgrade.sql -d your_spatial_database</programlisting>
- <programlisting>psql -f sfcgal_upgrade.sql -d your_spatial_database</programlisting>
-
- <para>You are advised to switch to an extension based install by running</para>
- <programlisting>psql -c "SELECT postgis_extensions_upgrade();"</programlisting>
-
- <note>
- <para>
- If you can't find the
- <filename>postgis_upgrade.sql</filename> specific for
- upgrading your version you are using a version too
- early for a soft upgrade and need to do a
- <link linkend="hard_upgrade">HARD UPGRADE</link>.
- </para>
- </note>
-
- <para>
- The <xref linkend="PostGIS_Full_Version"/> function
- should inform you about the need to run this kind of
- upgrade using a "procs need upgrade" message.
- </para>
- </section>
-
- </section>
-
- <section xml:id="hard_upgrade">
+ <section xml:id="hard_upgrade">
<title>Hard upgrade</title>
<para>
diff --git a/doc/extras_historytable.xml b/doc/extras_historytable.xml
index 89214ff4b..18078427c 100644
--- a/doc/extras_historytable.xml
+++ b/doc/extras_historytable.xml
@@ -11,7 +11,7 @@
</abstract>
</info>
- <note><para>The <varname>history_table</varname> was also packaged in PostGIS 1.5, but added to the documentation in PostGIS 2.0. This package is written in plpgsql and located in the <varname>extras/history_table</varname> of PostGIS source tar balls and source repository.</para></note>
+ <note><para>The <varname>history_table</varname> extension is written in plpgsql and located in the <varname>extras/history_table</varname> directory of the PostGIS source tree.</para></note>
<para>If you have a table 'roads', this module will maintain a 'roads_history' side table, which contains all the columns of the parent table, and the following additional columns:</para>
<programlisting>history_id | integer | not null default
date_added | timestamp without time zone | not null default now()
diff --git a/doc/extras_tigergeocoder.xml b/doc/extras_tigergeocoder.xml
index c76f7bd6a..92005387e 100644
--- a/doc/extras_tigergeocoder.xml
+++ b/doc/extras_tigergeocoder.xml
@@ -37,7 +37,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat
<para>Design:</para>
<para>The goal of this project is to build a fully functional geocoder that can process an arbitrary
United States address string and using normalized TIGER census data, produce a point geometry and rating reflecting the location of the given address and likeliness of the location. The higher the rating number the worse the result.</para>
- <para>The <varname>reverse_geocode</varname> function, introduced in PostGIS 2.0.0 is useful for deriving the street address and cross streets of a GPS location.</para>
+ <para>The <varname>reverse_geocode</varname> function is useful for deriving the street address and cross streets of a GPS location.</para>
<para>The geocoder should be simple for anyone familiar with PostGIS to install and use, and should be easily installable and usable on all platforms supported by PostGIS.</para>
<para>It should be robust enough to function properly despite formatting and spelling errors.</para>
<para>It should be extensible enough to be used with future data updates, or alternate data sources with a minimum of coding changes.</para>
@@ -51,7 +51,7 @@ you can upgrade the scripts using the accompanying upgrade_geocoder.bat
<para>There are a couple other open source geocoders for PostGIS, that unlike 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, PostgreSQL 8.4+ and PostGIS 1.5+ to function. It is packaged as a webservice interface and seems designed to be called as a webservice.
+ 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>
<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>
@@ -278,7 +278,6 @@ DROP TABLE tiger_data.pa_zip_state_loc;
<refsection>
<title>Examples: Basic</title>
- <para>The below examples timings are on a 3.0 GHZ single processor Windows 7 machine with 2GB ram running PostgreSQL 9.1rc1/PostGIS 2.0 loaded with all of MA,MN,CA, RI state Tiger data loaded.</para>
<para>Exact matches are faster to compute (61ms)</para>
<programlisting>SELECT g.rating, ST_X(g.geomout) As lon, ST_Y(g.geomout) As lat,
(addy).address As stno, (addy).streetname As street,
@@ -418,8 +417,6 @@ Time: 622.939 ms
<refsection>
<title>Examples: Basic</title>
- <para>The below examples timings are on a 3.0 GHZ single processor Windows 7 machine with 2GB ram running PostgreSQL 9.0/PostGIS 1.5 loaded with all of MA state Tiger data loaded. Currently a bit slow (3000 ms)</para>
- <para>Testing on Windows 2003 64-bit 8GB on PostGIS 2.0 PostgreSQL 64-bit Tiger 2011 data loaded -- (41ms)</para>
<programlisting>SELECT pprint_addy(addy), st_astext(geomout),rating
FROM geocode_intersection( 'Haverford St','Germania St', 'MA', 'Boston', '02130',1);
pprint_addy | st_astext | rating
@@ -635,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 tiger geocoder prior to PostGIS 2.0.0 alpha5, you'll need to run this on the states you have already done
+ <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>
@@ -649,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\pg91win\bin\
+set PGBIN=C:\projects\pg\pg<version>win\bin\
set PGPORT=5432
set PGHOST=localhost
set PGUSER=postgres
@@ -678,7 +675,7 @@ cd %TMPDIR%
TMPDIR="/gisdata/temp/"
UNZIPTOOL=unzip
WGETTOOL="/usr/bin/wget"
-export PGBIN=/usr/pgsql-9.0/bin
+export PGBIN=/usr/pgsql-<version>/bin
export PGPORT=5432
export PGHOST=localhost
export PGUSER=postgres
@@ -762,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\9.4\bin\
+set PGBIN=C:\Program Files\PostgreSQL\<version>\bin\
set PGPORT=5432
set PGHOST=localhost
set PGUSER=postgres
@@ -783,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/9.4/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
@@ -1355,7 +1352,6 @@ FROM (SELECT address As actual_addr, lon, lat,
createtopology
--------------
15
--- 60,902 ms ~ 1 minute on windows 7 desktop running 9.1 (with 5 states tiger data loaded)
SELECT tiger.topology_load_tiger('topo_boston', 'place', '2507000');
-- topology_loader_tiger --
29722 edges holding in temporary. 11108 faces added. 1875 edges of faces added. 20576 nodes added.
diff --git a/doc/extras_topology.xml b/doc/extras_topology.xml
index a3846708b..640bee1fb 100644
--- a/doc/extras_topology.xml
+++ b/doc/extras_topology.xml
@@ -12,12 +12,12 @@ Vincent Picavet provides a good synopsis and overview of what is Topology,
how is it used, and various FOSS4G tools that support it in <link xlink:href="https://gitlab.com/Oslandia/documentation/presentations/-/blob/master/2012/pgconf_eu_2012/pgconfeu2012_vincent_picavet_postgis_topology.pdf">PostGIS Topology PGConf EU 2012</link>.
</para>
<para>An example of a topologically based GIS database is the <link xlink:href="https://www.census.gov/geo/maps-data/data/tiger.html">US Census Topologically Integrated Geographic Encoding and Referencing System (TIGER)</link> database. If you want to experiment with PostGIS topology and need some data, check out <xref linkend="Topology_Load_Tiger"/>.</para>
- <para>The PostGIS topology module has existed in prior versions of PostGIS but was never part of the Official PostGIS documentation.
- In PostGIS 2.0.0 major cleanup is going on to remove use of all deprecated functions in it, fix known usability issues, better document the features and functions, add new functions, and enhance to closer conform to SQL-MM standards.</para>
+ <para>The PostGIS topology module has existed for a long time but was not always part of the official documentation.
+ Extensive cleanup removed deprecated functions, fixed known usability issues, documented the features and functions, added new functionality, and improved SQL-MM compliance.</para>
<para>Details of this project can be found at <link xlink:href="http://trac.osgeo.org/postgis/wiki/UsersWikiPostgisTopology">PostGIS Topology Wiki</link></para>
<para>All functions and tables associated with this module are installed in a schema called <varname>topology</varname>.</para>
<para>Functions that are defined in SQL/MM standard are prefixed with ST_ and functions specific to PostGIS are not prefixed.</para>
- <para>Topology support is build by default starting with PostGIS 2.0, and can be disabled specifying --without-topology configure option at build time as described in <xref linkend="postgis_installation"/></para>
+ <para>Topology support is built by default and can be disabled by specifying the --without-topology configure option at build time as described in <xref linkend="postgis_installation"/></para>
<section xml:id="Topology_PrimitiveTables">
<title>Topology Primitive Tables</title>
diff --git a/doc/installation.xml b/doc/installation.xml
index da80070c7..bdbdf1611 100644
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -585,24 +585,24 @@ sh autogen.sh
successfully. Ready to install.</code>"
</para>
- <para>
- As of PostGIS v1.4.0, all the functions have comments generated from the
- documentation. If you wish to install these comments into your spatial
- databases later, run the command which requires docbook. The postgis_comments.sql and other
- package comments files raster_comments.sql, topology_comments.sql are
- also packaged in the tar.gz distribution in the doc folder so no need to make comments
- if installing from the tar ball. Comments are also included as part of the CREATE EXTENSION install.
- </para>
+ <para>
+ All the functions have comments generated from the
+ documentation. If you wish to install these comments into your spatial
+ databases later, run the command which requires docbook. The postgis_comments.sql and other
+ package comment files are
+ also packaged in the tar.gz distribution in the doc folder so no need to make comments
+ if installing from the tar ball. Comments are also included as part of the CREATE EXTENSION install.
+ </para>
<para>
<command>make comments</command>
</para>
- <para>
- Introduced in PostGIS 2.0. This generates html cheat sheets suitable for quick reference or for student handouts.
- This requires xsltproc to build and will generate 4 files in doc folder <filename>topology_cheatsheet.html</filename>, <filename>tiger_geocoder_cheatsheet.html</filename>,
- <filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet.html</filename>
- </para>
+ <para>
+ The <command>make cheatsheets</command> target generates html cheat sheets suitable for quick reference or for student handouts.
+ This requires xsltproc to build and will generate 4 files in doc folder <filename>topology_cheatsheet.html</filename>, <filename>tiger_geocoder_cheatsheet.html</filename>,
+ <filename>raster_cheatsheet.html</filename>, <filename>postgis_cheatsheet.html</filename>
+ </para>
<para>You can download some pre-built ones available in html and pdf from <link xlink:href="http://www.postgis.us/study_guides">PostGIS / PostgreSQL Study Guides</link></para>
<para>
@@ -715,9 +715,9 @@ Schema | topology
Description | PostGIS topology spatial types and functions</screen>
<warning><para>Extension tables <varname>spatial_ref_sys</varname>, <varname>layer</varname>, <varname>topology</varname> can not be explicitly backed up. They can only
-be backed up when the respective <varname>postgis</varname> or <varname>postgis_topology</varname> extension is backed up, which only seems to happen when you backup the whole database.
-As of PostGIS 2.0.1, only srid records not packaged with PostGIS are backed up when the database is backed up so don't go around changing srids we package and expect your changes to be there. Put in a ticket if you find an issue. The structures of extension tables are never backed up since they are created with <code>CREATE EXTENSION</code>
-and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model, so nothing we can do about it.</para></warning>
+be backed up when the respective <varname>postgis</varname> or <varname>postgis_topology</varname> extension is backed up, which only happens when you back up the whole database.
+Only srid records not packaged with PostGIS are captured in backups, so don't change the entries we ship and expect the modifications to persist. Put in a ticket if you find an issue. The structures of extension tables are never backed up since they are created with <code>CREATE EXTENSION</code>
+and assumed to be the same for a given version of an extension. These behaviors are built into the current PostgreSQL extension model.</para></warning>
<para>If you installed &last_release_version;, without using our
wonderful extension system, you can change it to be extension based by
@@ -1004,8 +1004,8 @@ All 2 tests passed.
</section>
<section xml:id="installing_pagc_address_standardizer"><title>Installing and Using the address standardizer</title>
- <para>The <code>address_standardizer</code> extension used to be a separate package that required separate download. From PostGIS 2.2 on, it is now bundled in.
- For more information about the address_standardize, what it does, and how to configure it for your needs, refer to <xref linkend="Address_Standardizer"/>.</para>
+ <para>The <code>address_standardizer</code> extension is bundled with PostGIS.
+ For more information about the address_standardizer, what it does, and how to configure it for your needs, refer to <xref linkend="Address_Standardizer"/>.</para>
<para>This standardizer can be used in conjunction with the PostGIS packaged tiger geocoder extension as a replacement for the <xref linkend="Normalize_Address"/> discussed.
To use as replacement refer to <xref linkend="tiger_pagc_address_standardizing"/>.
You can also use it as a building block for your own geocoder or use it to standardize your addresses for easier compare of addresses.</para>
@@ -1013,7 +1013,7 @@ All 2 tests passed.
<para>The address standardizer relies on PCRE which is usually already installed on many Nix systems,
but you can download the latest at: <link xlink:href="http://www.pcre.org">http://www.pcre.org</link>. If during <xref linkend="installation_configuration"/>, PCRE is found, then the address standardizer extension will automatically be built. If you have a custom pcre install you want to use instead, pass to configure <code>--with-pcredir=/path/to/pcre</code> where <filename>/path/to/pcre</filename> is the root folder for your pcre include and lib directories.</para>
- <para>For Windows users, the PostGIS 2.1+ bundle is packaged with the address_standardizer already so no need to compile and can move straight to <code>CREATE EXTENSION</code> step.</para>
+ <para>Windows installation packages include the address_standardizer so you can move straight to the <code>CREATE EXTENSION</code> step.</para>
<para>Once you have installed, you can connect to your database and run the SQL:</para>
@@ -1072,7 +1072,7 @@ SELECT 'debbie', declare_sect, pgbin, wget, unzip_command, psql, path_sep,
<para>If you don't edit this <varname>loader_platform</varname> table, it will just contain common case locations of items and you'll have to edit the generated script after the script is generated.</para>
</listitem>
- <listitem><para>As of PostGIS 2.4.1 the Zip code-5 digit tabulation area <varname>zcta5</varname> load step was revised to load current zcta5 data and is part of the <xref linkend="Loader_Generate_Nation_Script"/> when enabled.
+ <listitem><para>The Zip code-5 digit tabulation area <varname>zcta5</varname> load step uses current ZCTA data and is part of the <xref linkend="Loader_Generate_Nation_Script"/> when enabled.
It is turned off by default because it takes quite a bit of time to load (20 to 60 minutes), takes up quite a bit of disk space, and is not used that often.</para>
<para>To enable it, do the following:</para>
<programlisting>UPDATE tiger.loader_lookuptables SET load = true WHERE table_name = 'zcta520';</programlisting>
diff --git a/doc/introduction.xml b/doc/introduction.xml
index 209707e05..429253b27 100644
--- a/doc/introduction.xml
+++ b/doc/introduction.xml
@@ -417,7 +417,7 @@
<listitem>
<para>Crowd funding campaigns are campaigns we run to get badly wanted features funded that can service a large number of people. Each campaign is specifically focused on a particular feature or set of features. Each sponsor chips in a small fraction of the needed funding and with enough people/organizations contributing, we have the funds to pay for the work that will help many. If you have an idea for a feature you think many others would be willing to co-fund, please post to the <link xlink:href="https://lists.osgeo.org/mailman/listinfo/postgis-users">PostGIS newsgroup</link> your thoughts and together we can make it happen. </para>
- <para>PostGIS 2.0.0 was the first release we tried this strategy. We used <link xlink:href="http://www.pledgebank.com">PledgeBank</link> and we got two successful campaigns out of it.</para>
+ <para>PostGIS has experimented with community fundraising for features in the past. We used <link xlink:href="http://www.pledgebank.com">PledgeBank</link> and we got two successful campaigns out of it.</para>
<para><link xlink:href="http://www.pledgebank.com/postgistopology"><emphasis role="bold">postgistopology</emphasis></link> - 10 plus sponsors each contributed $250 USD to build toTopoGeometry function and beef up topology support in 2.0.0. It happened.</para>
<para><link xlink:href="http://www.pledgebank.com/postgis64windows"><emphasis role="bold">postgis64windows</emphasis></link> - 20 someodd sponsors each contributed $100 USD to pay for the work needed to work out PostGIS 64-bit issues on windows. It happened.</para>
</listitem>
diff --git a/extensions/postgis/META.json b/extensions/postgis/META.json
index f8742511d..82adb35bd 100644
--- a/extensions/postgis/META.json
+++ b/extensions/postgis/META.json
@@ -1,21 +1,21 @@
{
- "abstract" : "PostGIS 2.2 OGC/SQL-MM compliant spatial extender for PostgreSQL",
- "release_status" : "stable",
- "license" : "gpl_2",
- "generated_by" : "Regina O. Obe",
- "description" : "This module provides GIS geometry, geography, raster types, functions, and tables",
- "version" : "2.2.0",
- "resources" : {
- "bugtracker" : {
- "web" : "http://trac.osgeo.org/postgis"
+ "abstract": "PostGIS OGC/SQL-MM compliant spatial extender for PostgreSQL",
+ "release_status": "stable",
+ "license": "gpl_2",
+ "generated_by": "Regina O. Obe",
+ "description": "This module provides GIS geometry, geography, raster types, functions, and tables",
+ "version": "3.7.0dev",
+ "resources": {
+ "bugtracker": {
+ "web": "http://trac.osgeo.org/postgis"
},
- "repository" : {
- "type" : "git",
- "web" : "http://postgis.net",
- "url" : "https://git.osgeo.org/gitea/postgis/postgis.git"
+ "repository": {
+ "type": "git",
+ "web": "http://postgis.net",
+ "url": "https://git.osgeo.org/gitea/postgis/postgis.git"
}
},
- "tags" : [
+ "tags": [
"gis",
"spatial",
"geometry",
@@ -23,30 +23,30 @@
"geography",
"location"
],
- "meta-spec" : {
- "version" : "1.0.0",
- "url" : "http://pgxn.org/meta/spec.txt"
+ "meta-spec": {
+ "version": "1.0.0",
+ "url": "http://pgxn.org/meta/spec.txt"
},
- "provides" : {
- "spatial_ref_sys" : {
- "version" : "2.2.0",
- "file" : "sql/spatial_ref_sys.sql",
- "abstract" : "Directory of spatial reference systems needed for geometry transformation between different spatial reference systems"
+ "provides": {
+ "spatial_ref_sys": {
+ "version": "3.7.0dev",
+ "file": "sql/spatial_ref_sys.sql",
+ "abstract": "Directory of spatial reference systems needed for geometry transformation between different spatial reference systems"
},
- "postgis" : {
- "abstract" : "PostGIS GIS types, indexes and functions",
- "docfile" : "doc/postgis.md",
- "file" : "sql/postgis.sql",
- "version" : "2.2.0"
+ "postgis": {
+ "abstract": "PostGIS GIS types, indexes and functions",
+ "docfile": "doc/postgis.md",
+ "file": "sql/postgis.sql",
+ "version": "3.7.0dev"
}
},
- "name" : "postgis",
- "maintainer" : "PostGIS Steering Committee",
- "prereqs" : {
- "runtime" : {
- "requires" : {
- "PostgreSQL" : "9.1.0",
- "plpgsql" : 0
+ "name": "postgis",
+ "maintainer": "PostGIS Steering Committee",
+ "prereqs": {
+ "runtime": {
+ "requires": {
+ "PostgreSQL": "12",
+ "plpgsql": 0
}
}
}
diff --git a/extensions/postgis_topology/META.json b/extensions/postgis_topology/META.json
index 89d90ec1c..f7ea31180 100644
--- a/extensions/postgis_topology/META.json
+++ b/extensions/postgis_topology/META.json
@@ -1,47 +1,49 @@
{
- "name": "postgis_topology",
- "abstract": "PostGIS 2.0 Topology OGC/SQL-MM compliant spatial extender for PostgreSQL",
- "description": "This module provides GIS Topology geometry types and functions",
- "version": "2.0.0",
- "release_status": "unstable",
- "maintainer": "PostGIS Steering Committee",
- "license": "gpl_2",
- "provides": {
- "postgis_raster": {
- "abstract": "PostGIS SQL/MM Topology types and functions",
- "version": "2.0.0",
- "file": "sql/postgis_topology.sql",
- "docfile": "doc/postgis.md"
- }
- }
- "prereqs": {
+ "name": "postgis_topology",
+ "abstract": "PostGIS Topology OGC/SQL-MM compliant spatial extender for PostgreSQL",
+ "description": "This module provides GIS Topology geometry types and functions",
+ "version": "3.7.0dev",
+ "release_status": "stable",
+ "maintainer": "PostGIS Steering Committee",
+ "license": "gpl_2",
+ "provides": {
+ "postgis_raster": {
+ "abstract": "PostGIS SQL/MM Topology types and functions",
+ "version": "3.7.0dev",
+ "file": "sql/postgis_topology.sql",
+ "docfile": "doc/postgis.md"
+ }
+ },
+ "prereqs": {
"runtime": {
"requires": {
"plpgsql": 0,
- "PostgreSQL": "8.4.0",
- "postgis_core": "2.0.0"
+ "PostgreSQL": "12",
+ "postgis_core": "3.7.0dev"
}
}
- },
- "generated_by": "Regina O. Obe",
- "resources": {
- "bugtracker": {
- "web": "http://trac.osgeo.org/postgis"
- },
- "repository": {
- "url": "https://git.osgeo.org/gitea/postgis/postgis.git",
- "web": "http://postgis.net",
- "type": "git"
- }
- },
- "meta-spec": {
- "version": "1.0.0",
- "url": "http://pgxn.org/meta/spec.txt"
- },
- "tags": [
- "gis",
- "spatial",
- "geometry",
- "location", "topology", "sql/mm"
- ]
+ },
+ "generated_by": "Regina O. Obe",
+ "resources": {
+ "bugtracker": {
+ "web": "http://trac.osgeo.org/postgis"
+ },
+ "repository": {
+ "url": "https://git.osgeo.org/gitea/postgis/postgis.git",
+ "web": "http://postgis.net",
+ "type": "git"
+ }
+ },
+ "meta-spec": {
+ "version": "1.0.0",
+ "url": "http://pgxn.org/meta/spec.txt"
+ },
+ "tags": [
+ "gis",
+ "spatial",
+ "geometry",
+ "location",
+ "topology",
+ "sql/mm"
+ ]
}
-----------------------------------------------------------------------
Summary of changes:
doc/administration.xml | 75 ++++----------------------------
doc/extras_historytable.xml | 2 +-
doc/extras_tigergeocoder.xml | 18 +++-----
doc/extras_topology.xml | 6 +--
doc/installation.xml | 40 ++++++++---------
doc/introduction.xml | 2 +-
extensions/postgis/META.json | 68 ++++++++++++++---------------
extensions/postgis_topology/META.json | 82 ++++++++++++++++++-----------------
8 files changed, 116 insertions(+), 177 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list