PostGIS Development Blog

PostGIS 2.3.0 Released

Regina Obe — 2016-09-26T00:00:00+00:00

The PostGIS development team is pleased to announce the release of PostGIS 2.3.0.
This is the first version to utilize the parallel support functionality introduced in PostgreSQL 9.6. As such, if you are using PostgreSQL 9.6, we strongly encourage you to use this version.

Parallel support will make many queries using PostGIS relationship operators and functions faster. In order to take advantage of parallel query support, make sure to set max_parallel_workers_per_gather to something greater than 0 as noted in max_parallel_workers_per_gather PostgreSQL runtime configs

Best served with [PostgreSQL 9.6+] which is due out this week and pgRouting 2.3.0 which also just got released.

Packages from maintainers will be out in the coming days and weeks.

Continue Reading by clicking title hyperlink ..

PostGIS 2.3.0rc1 Released

Regina Obe — 2016-09-19T00:00:00+00:00

PostGIS 2.3.0rc1 is feature complete, so we’re looking for testing and feedback! Best served with PostgreSQL 9.6rc1 and pgRouting 2.3.0-rc1

Please give this release candidate a try and report back any issues you encounter. New things since 2.3.0beta1 release

Please report bugs that you find in this release.

Important / Breaking Changes

3466, Casting from box3d to geometry now returns a 3D geometry (Julien Rouhaud of Dalibo)
3604, pgcommon/Makefile.in orders CFLAGS incorrectly leading to wrong liblwgeom.h (Greg Troxel)
3396, ST_EstimatedExtent, now throws WARNING instead of ERROR (Regina Obe)

New Features and Performance Enhancements
Add support for custom TOC in postgis_restore.pl (Christoph Moench-Tegeder)
Add support for negative indexing in STPointN and STSetPoint (Rémi Cura)
Numerous new function additions and enhancements: New Functions and Enhancements
3549, Support PgSQL 9.6 parallel query mode, as far as possible (Paul Ramsey, Regina Obe)
3557, Geometry function costs based on query stats (Paul Norman)
3591, Add support for BRIN indexes (Giuseppe Broccolo of 2nd Quadrant, Julien Rouhaud and Ronan Dunklau of Dalibo)
3496, Make postgis non-relocateable (for extension install), schema qualify calls in functions (Regina Obe) Should resolve once and for all for extensions #3494, #3486, #3076
3547, Update tiger geocoder to support TIGER 2016 and use http or ftp (Regina Obe)

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.3.0.

PostGIS 2.3.0beta1 Released

Regina Obe — 2016-09-06T00:00:00+00:00

PostGIS 2.3 is feature complete, so we’re looking for testing and feedback! Best served with PostgreSQL 9.6.

Please give this beta a try and report back any issues you encounter.

Please report bugs that you find in this release.

** Important / Breaking Changes **

3466, Casting from box3d to geometry now returns a 3D geometry (Julien Rouhaud of Dalibo)
3604, pgcommon/Makefile.in orders CFLAGS incorrectly leading to wrong liblwgeom.h (Greg Troxel)

** New Features and Performance Enhancements **
Add support for custom TOC in postgis_restore.pl (Christoph Moench-Tegeder)
Add support for negative indexing in STPointN and STSetPoint (Rémi Cura)
Numerous new function additions and enhancements: New Functions and Enhancements
3549, Support PgSQL 9.6 parallel query mode, as far as possible (Paul Ramsey, Regina Obe)
3557, Geometry function costs based on query stats (Paul Norman)
3591, Add support for BRIN indexes (Giuseppe Broccolo of 2nd Quadrant, Julien Rouhaud and Ronan Dunklau of Dalibo)
3496, Make postgis non-relocateable (for extension install), schema qualify calls in functions (Regina Obe) Should resolve once and for all for extensions #3494, #3486, #3076
3547, Update tiger geocoder to support TIGER 2016 and use http or ftp (Regina Obe)

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.3.0.

Nautilytics Case Study

Christopher Lanoue — 2016-04-05T00:00:00+00:00

Nautilytics is a small data visualization and GIS startup based out of Boston, MA. We use PostGIS and PostgreSQL, among other open-source tools to build powerful web applications for US government organizations, public, and private sector companies.

Continue Reading by clicking title hyperlink ..

PostGIS for fast prototyping and Research

Rémi Cura — 2016-04-04T00:00:00+00:00

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?).

Continue Reading by clicking title hyperlink ..

Plenario (Univeristy of Chicago)

William Engler — 2016-03-29T00:00:00+00:00

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.

Continue Reading by clicking title hyperlink ..

PostGIS 2.2.2 Released

Paul Ramsey — 2016-03-22T00:00:00+00:00

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 ptarrayclonedeep
#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.

Binary packages will appear in repositories over the coming weeks as packagers roll out builds.

View all closed tickets for 2.2.2.

Vanguard Appraisals

Andy Colson — 2016-03-17T00:00:00+00:00

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).

Continue Reading by clicking title hyperlink ..

Clever Maps

Michal Zimmermann — 2016-03-17T00:00:00+00:00

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

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

Continue Reading by clicking title hyperlink ..

Selecting only pixels of particular range of values with ST_Reclass

Regina Obe — 2016-03-13T00:00:00+00:00

This raster question comes up quite a bit on PostGIS mailing lists and stack overflow and the best answer often involves the often forgotten ST_Reclass function that has existed since PostGIS 2.0.
People often resort to the much slower though more flexible ST_MapAlgebra or dumping out their rasters as Pixel valued polygons they then filter with WHERE val > 90, where ST_Reclass does the same thing but orders of magnitude faster.

Continue Reading by clicking title hyperlink ..