I used extensively postgis (+ecosystem) for my phd thesis, in several ways. The first is that PostGIS is a good steady horse (elephant?): a database is the perfect place to store a lot of very different information in the same place and put them in relation. For geospatial data, postgis means you always have a way to put data in relation (are they at the same place?).

The Urban Center for Computation and Data (UrbanCCD) is a research initiative of Argonne National Laboratory and the Computation Institute of the University of Chicago. We create computational tools to better understand cities. One of these is Plenario, our hub for open geospatial data. PostGIS makes the spatial operations at the heart of Plenario possible.

The PostGIS development team is happy to release patch for PostGIS 2.2, the 2.2.2 release. As befits a patch release, the focus is on bugs and breakages.

Bug Fixes and Improvements

• #3463, Fix crash on face-collapsing edge change
• #3422, Improve ST_Split robustness on standard precision double systems (arm64, ppc64el, s390c, powerpc, …)
• #3427, Update spatial_ref_sys to EPSG version 8.8
• #3433, ST_ClusterIntersecting incorrect for MultiPoints
• #3435, ST_AsX3D fix rendering of concave geometries
• #3436, memory handling mistake in ptarray_clone_deep
• #3437, ST_Intersects incorrect for MultiPoints
• #3461, ST_GeomFromKML crashes Postgres when there are innerBoundaryIs and no outerBoundaryIs
• #3429, upgrading to 2.3 or from 2.1 can cause loop/hang on some platforms
• #3460, ST_ClusterWithin “Tolerance not defined” error after upgrade
• #3490, Raster data restore issues, materialized views. Added scripts postgis_proc_set_search_path.sql, rtpostgis_proc_set_search_path.sql
• #3426, failing POINT EMPTY tests on fun architectures

See the full list of changes in the news file and please report bugs that you find in the release.

Clever°Maps’ is a three years old startup based in the Czech Republic. We create web apps for four distinct market segments:

1. business/location inteligence - helping companies to make decisions based on data, not on feelings
2. farming - simplifying agenda and everyday work
3. road infrastructure administration - settlement of land property rights, treaty evidence, speeding up the whole administrative process
4. assets administration - treaty management, land purchases

There is an Updated versionof this case

Vanguard Appraisals is new to the GIS world. In fact, we aren’t really in the GIS world; we just kind of brush up against it. We do mass property appraisal for entire county and city jurisdictions, and we develop software to collect, price and maintain values. We also host assessment data online so that homeowners can search and find property information much simpler from the comfort of their own home. Our software and websites are used in 7 states (IA, IL, MN, MO, NE, ND, SD).

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:

• True nearest-neighbor searching for all geometry and geography types
• New volumetric geometry support, including ST_3DDifference, ST_3DUnion and more
• Temporal data model support and functions like ST_ClosestPointOfApproach to support temporal query
• Spatial clustering functions ST_ClusterIntersecting and ST_ClusterWithin
• Subdividing large geometries with ST_Subdivide
• Fast box clipping with ST_ClipByBox2D
• In-database raster processing with ST_Retile and ST_CreateOverview.html
• New high-speed native code address standardizer
• Visvalingam-Whyatt geometry simplification with ST_SimplifyVW
• Support for compressed “tiny well-known binary” format with ST_AsTWKB and ST_GeomFromTWKB

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.

• Download
• Changelog

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.

• Download
• Changelog

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.

• Download 2.1.7
• Download 2.0.7

View all closed tickets for 2.0.7.