PostGIS 2.1.9 Released

Author: Paul Ramsey 2017/09/19 in news ( release, 2.1, 2.1.9 )

The PostGIS development team has uploaded the final release of the PostGIS 2.1 branch. The 2.1 branch is now end-of-life. As befits a patch release, the focus is on bugs and breakages.

Please report bugs that you find in this release.

Bug Fixes and Improvements

2232, avoid accumulated error in SVG rounding
2283, Import nested holey multipolygons correctly
3222, Fix uninitialized stddev in stats computation
3196, do not let DropTopology drop non-topology schemes
3198, ST_AddEdgeModFace docs report wrong side of new face
3245, Ensure lwgeom/geos returns are fully owned
3280, Fix topology import of almost collinear linestrings
3281, Do not export liblwgeom symbols from the PostgreSQL module
3351, Set endnodes isolation on ST_RemoveIsoEdge
3355, Fix geography ST_Segmentize() does not add geodetic box ST_Intersects and other relationship functions always return false as result.
3359, Fix toTopoGeom loss of low-id primitives from TopoGeometry definition
3375, crash in repeated point removal for collection(point)
3378, Fix handling of hierarchical TopoGeometries with of multiple topologies
3389, Buffer overflow in lwgeom_to_geojson
3393, ST_Area NaN for some polygons
3436, memory handling mistake in ptarray_clone_deep
3461, ST_GeomFromKML crashes Postgres when there are innerBoundaryIs and no outerBoundaryIs
3429, upgrading to 2.2 or 2.3 can cause crash/hang on some platforms
3565, ST_SetPoint can crash backend
3579, Crash in LWGEOM2GEOS
3583, Crash in ST_GeomFromGeoJSON on malformed multipolygon
3607, Fix inconsistency with multilinestring in ST_LocateBetweenElevations (Artur Zakirov)
3608, Fix crash passing -W UTF-8 to shp2pgsql (Matt Amos)
3644, Deadlock on interrupt
3774, Trigonometric length for CompoundCurves
3731, Crash on very small table of homogenous data

See the full list of changes in the news file and please report bugs that you find in the release. Binary packages will appear in repositories over the coming weeks as packagers roll out builds.

View all closed tickets for 2.1.9.

PostGIS 2.5.0rc1

The PostGIS development team is pleased to release PostGIS 2.5.0rc1.

This release is a work in progress. Remaining time will be focused on bug fixes and documentation until PostGIS 2.5.0 release. Although this release will work for PostgreSQL 9.4 and above, to take full advantage of what PostGIS 2.5 offers, you should be running PostgreSQL 11beta3+ and GEOS 3.7.0rc1 which were released recently.

Best served with PostgreSQL 11beta3 which was recently released.

Changes since PostGIS 2.5.0beta2 release are as follows:

4146, Fix compilation error against Postgres 12 (Raúl Marín).
4147, 4148, Honor SOURCEDATEEPOCH when present (Christoph Berg).

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.

2.5.0rc1

PostGIS 2.5.0beta2

The PostGIS development team is pleased to release PostGIS 2.5.0beta2.

Best served with PostgreSQL 11beta3 which was recently released.

Changes since PostGIS 2.5.0beta1 release are as follows:

4115, Fix a bug that created MVTs with incorrect property values under parallel plans (Raúl Marín).
4120, ST_AsMVTGeom: Clip using tile coordinates (Raúl Marín).
4132, ST_Intersection on Raster now works without throwing TopologyException (Vinícius A.B. Schmidt, Darafei Praliaskouski)
4109, Fix WKT parser accepting and interpreting numbers with multiple dots (Raúl Marín, Paul Ramsey)
4140, Use user-provided CFLAGS in address standardizer and the topology module (Raúl Marín)
4143, Fix backend crash when ST_OffsetCurve fails (Dan Baston)
4145, Speedup MVT column parsing (Raúl Marín)

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.

2.5.0beta2

PostGIS 2.5.0beta1

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.

2.5.0beta1

PostGIS

Spatial and Geographic objects for PostgreSQL

PostGIS 2.1.9 Released

More Posts

PostGIS 2.5.0rc1

PostGIS 2.5.0beta2

PostGIS 2.5.0beta1

Site Map

PostGIS Project Steering Committee (PSC)