The PostGIS development team is pleased to release PostGIS 2.5.0beta1.
This release is a work in progress. No more api changes will be made from this point on before 2.5.0 release. Remaining time will be focused on bug fixes and documentation for the new functionality and performance enhancements under the covers. Although this release will work for PostgreSQL 9.4 and above, to take full advantage of what PostGIS 2.5 will offer, you should be running PostgreSQL 11beta2+ and GEOS 3.7.0beta1 which were released recently.
Best served with PostgreSQL 11beta2 which was recently released.
View all closed tickets for 2.5.0.
After installing the binaries or after running pg_upgrade, make sure to do:
ALTER EXTENSION postgis UPDATE;
— if you use the other extensions packaged with postgis — make sure to upgrade those as well
ALTER EXTENSION postgis_sfcgal UPDATE; ALTER EXTENSION postgis_topology UPDATE; ALTER EXTENSION postgis_tiger_geocoder UPDATE;
If you use legacy.sql or legacy_minimal.sql, make sure to rerun the version packaged with these releases.
The PostGIS Team is pleased to release PostGIS 3.2.0, the Olivier Courtin release.
This release would not be possible without the various developers listed in the credits as well as the companies that provided funding and developer time.
Companies that contributed significantly to this release are:
In March 2020 we lost a long time PostGIS developer and friend, Olivier Courtin. The PostGIS 3.2.0 release is named in his honor.
The PostGIS Team is pleased to release the first rc of the upcoming PostGIS 3.2.0 release.
Best served with PostgreSQL 14. This version of PostGIS can utilize the faster GiST building support API introduced in PostgreSQL 14. If compiled with recently released GEOS 3.10.1 you can take advantage of improvements in ST_MakeValid and numerous speed improvements. This release also includes many additional functions and improvements for
postgis_topology extensions and a new input/export format FlatGeobuf.