The PostGIS Team is pleased to release the release of PostGIS 3.1.2!
This release is a bug fix release, addressing issues found in the previous 3.1 release.
- #4871, TopoGeometry::geometry cast returns NULL for empty TopoGeometry objects (Sandro Santilli)
- #4826, postgis_tiger_geocoder Better answers when no zip is provided (Regina Obe)
- #4817, handle more complex compound coordinate dystems (Paul Ramsey)
- #4842, Only do axis flips on CRS that have a “Lat” as the first column (Paul Ramsey)
- Support recent Proj versions that have removed pj_get_release (Paul Ramsey)
- #4835, Adjust tolerance for geodetic calculations (Paul Ramsey)
- #4840, Improper conversion of negative geographic azimuth to positive (Paul Ramsey)
- #4853, DBSCAN cluster not formed when recordset length equal to minPoints (Dan Baston)
- #4863, Update bboxes after scale/affine coordinate changes (Paul Ramsey)
- #4876, Fix raster issues related to PostgreSQL 14 tablefunc changes (Paul Ramsey, Regina Obe)
- #4877, mingw64 PostGIS / PostgreSQL 14 compile (Regina Obe, Tom Lane)
- #4838, Update to support Tiger 2020 (Regina Obe)
- #4890, Change Proj cache lifetime to last as long as connection (Paul Ramsey)
- #4845, Add Pg14 build support (Paul Ramsey)
The PostGIS Team is pleased to release the release of PostGIS 3.1.1!
This release is a bug fix release, addressing issues found in the previous 3.1 release.
- #4814, Crash passing collection with only empty components to ST_MakeValid
- #4818, Make the VSICURL synthetic driver work as documented
- #4825, Unstable results from ST_MakeValid
- #4823, Avoid listing the same geometry in different collections
The PostGIS Team is pleased to release the release of PostGIS 3.1.0!
This version exposes the new features of GEOS 3.9 as well as numerous core performance enhancements for spatial joins, large object access, text format output and more.
Performance is a key feature of this release, with improvements to spatial joins, text outputs, large object reads, vector tile output, and a host of smaller tweaks.
The k-means clustering code has been enhanced to support weighting and higher dimensional clusters.
Geometry generators to create hexagonal and square tilings have been added, for simpler in-the-database summarization queries.
Finally, PostGIS exposes the latest enhancements in the GEOS geometry library 3.9 version. The new overlay engine (aka “OverlayNG”) provides more robust handling of difficult input geometries, using a set of new noding strategies to process geometry. For the end user, this should mean no more “topology exceptions” when using the union, difference, intersection or symmetric difference functions. PostGIS also exposes the new fixed precision overlay capability via an additional grid-size parameter on ST_Intersection and the other overlay functions.
The PostGIS Team is pleased to release the release candidate of the upcoming PostGIS 3.1.0 release. This version is exposes some of the new performance and feature enhancements in GEOS 3.9 as well as numerous speed enhancements not requiring newer GEOS.
Best served with:
The PostGIS Team is pleased to release the first beta of the upcoming PostGIS
3.1.0 release. This version is exposes some of
the new performance and feature enhancements in not yet relesed GEOS 3.9 as well as numerous speed enhancements not requiring newer GEOS.
Requires GEOS 3.6+ and PostgreSQL 9.6+. To use MVT you will need protobuf-c 1.1. or higher.
Best served with:
The PostGIS Team is pleased to release the third alpha of upcoming PostGIS
3.1.0 release. This version is exposes some of
the new performance and feature enhancements in not yet relesed GEOS 3.9 as well as numerous speed enhancements not requiring newer GEOS.
Requires GEOS 3.6+ and PostgreSQL 9.6+. To use MVT you will need protobuf-c 1.1. or higher.
Best served with
PostgreSQL 13.1,
GEOS 3.7 or higher is recommended.
pgRouting 3.1.1
The PostGIS development team is pleased to provide
bug fix and performance enhancements
3.0.2, 2.5.5, 2.4.9 for the 3.0, 2.5, and 2.4 stable branches.
The PostGIS Team is pleased to release the second alpha of upcoming PostGIS
3.1.0 release.
Best served with
PostgreSQL 13beta2,
GEOS 3.7 or higher is recommended.
ST_MaximumInscribedCircle requires compilation with GEOS 3.9.0 in development to be enabled.
pgRouting 3.1.0 which will also be released soon.
The PostGIS Team is pleased to release PostGIS 2.3.11.
This is the last bug fix release of the PostGIS 2.3 series.
Please upgrade to 2.4 or higher if you want to continue receiving bug fixes.
If you come across any issues, feel free to report via our ticket tracker
https://trac.osgeo.org/postgis or mailing list with details as described
here. For security issues, send reports to
security@postgis.net.
