The PostGIS development team is happy to release patch for PostGIS 2.2, the 2.2.1 release. As befits a patch release, the focus is on bugs, breakages, and performance issues. This release includes many fixes for topology, so topology users should give this release special focus.
Bug Fixes and Improvements
- #2232, avoid accumulated error in SVG rounding
- #3321, Fix performance regression in topology loading
- #3329, Fix robustness regression in TopoGeo_addPoint
- #3349, Fix installation path of
postgis_topology scripts
- #3351, set endnodes isolation on
ST_RemoveIsoEdge
(and lwt_RemIsoEdge)
- #3355, geography
ST_Segmentize has geometry bbox
- #3359, Fix toTopoGeom loss of low-id primitives from
TopoGeometry definition
- #3360,
_raster_constraint_info_scale invalid input syntax
- #3375, crash in repeated point removal for collection(point)
- #3378, Fix handling of hierarchical TopoGeometries
in presence of multiple topologies
- #3380, #3402, Decimate lines on topology load
- #3388, #3410, Fix missing end-points in
ST_RemoveRepeatedPoints
- #3389, Buffer overflow in
lwgeom_to_geojson
- #3390, Compilation under Alpine Linux 3.2
gives an error when compiling the postgis and
postgis_topology extension
- #3393, ST_Area NaN for some polygons
- #3401, Improve
ST_Split robustness on 32bit systems
- #3404,
ST_ClusterWithin crashes backend
- #3407, Fix crash on splitting a face or an edge
defining multiple TopoGeometry objects
- #3411, Clustering functions not using spatial index
- #3412, Improve robustness of snapping step in
TopoGeo_addLinestring
- #3415, Fix OSX 10.9 build under pkgsrc
- Fix memory leak in
lwt_ChangeEdgeGeom [liblwgeom]
See the full list of changes in the news file and please report bugs that you find in the release.
PostGIS 2.2.0 is released! Over the last two years a number of interesting new features have been added, such as:
See the full list of changes in the news file and please report bugs that you find in the release.
This is it, PostGIS 2.2 is almost out the door, so we’re looking for testing and feedback! Please give the release candidate a try and report back any issues you encounter.
View all [closed tickets for 2.2.0][1].
[1]:http://trac.osgeo.org/postgis/query?status=closed&groupdesc=1&group=priority&milestone=PostGIS+2.2.0&order=priority
Due to a number of bugs capable of crashing a back-end, we have released 2.1.8. If you are running an earlier version on a public site, we recommend that you update as soon as possible.
View all [closed tickets for 2.1.8][1].
[1]:http://trac.osgeo.org/postgis/query?status=closed&groupdesc=1&group=priority&milestone=PostGIS+2.1.8&order=priority
Due to a critical bug in GeoJSON ingestion we have made an early release of versions 2.0.7 and 2.1.7. If you are running an earlier version on a public site and accepting incoming GeoJSON, we recommend that you update as soon as possible.
View all closed tickets for 2.0.7.
The 2.1.6 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.6 release. As befits a patch release, the focus is on bugs, breakages, and performance issues. Users with large tables of points will want to priorize this patch, for substantial (~50%) disk space savings.
The last couple weeks have seen two interesting updates in the world of PostgreSQL “foreign data wrappers” (FDW). Foreign data wrappers allow you to access remote data inside your database, exactly like other tables. PostgreSQL ships with two example implementations, one for accessing text files, and the other for accessing remote PostgreSQL servers.
The two updates of interest to PostGIS users are:
- The Oracle FDW implementation was recently enhanced to support spatial columns, so an Oracle table with SDO_GEOMETRY columns can be exposed in PostgreSQL as a table with PostGIS geometry columns.
- A new OGR FDW implementation was released that supports exposing any OGR data source as a table with PostGIS geometry columns.
Now you can access your PostGIS data without even going to the trouble of importing it first!
The 2.1.5 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.5 release. As befits a patch release, the focus is on bugs, breakages, and performance issues
<https://download.osgeo.org/postgis/source/postgis-2.1.5.tar.gz>
The 2.1.4 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.4 release. As befits a patch release, the focus is on bugs, breakages, and performance issues
<https://download.osgeo.org/postgis/source/postgis-2.1.4.tar.gz>
It has come to our attention that the PostGIS Raster support
may give more privileges to users than an administrator is
willing to grant. These include reading files from the filesystem
and opening connections to network hosts.