About PostGIS

PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

SELECT superhero.name
FROM city, superhero
WHERE ST_Contains(city.geom, superhero.geom)
AND city.name = 'Gotham';

In addition to basic location awareness, PostGIS offers many features rarely found in other competing spatial databases such as Oracle Locator/Spatial and SQL Server. Refer to PostGIS Feature List for more details.

License

PostGIS is released under the GNU General Public License (GPLv2). Refer to License FAQ for more information. PostGIS is developed by a group of contributors led by a Project Steering Committee.

News

What's happening right now

Blogs, Tweets and more…

Follow @postgis

PostGIS 2.3.0 Released

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.

PostGIS 2.3.0rc1 Released

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

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.

PostGIS 2.2.2 Released

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.

More News…

Upcoming Events

PostgreSQL Sessions, 22 Sept 2016, Lyon France

PgCon Silicon Valley, California, US November 14-16 2016

PGConf US March 28-31st, 2017 in Jersey City, NJ, USA

FOSS4G 2017, Boston, MA, USA, August 14th - 18th 2017

Recent past events

PostgresOpen 2016
Sep 13-15 2016 Dallas, TX, US

PGConf US April 18-20, 2016 in NYC

Tips

Selecting only pixels of particular range of values with ST_Reclass

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.

More Tips…

Case Studies

Nautilytics Case Study

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.

PostGIS for fast prototyping and Research

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

More Case Studies…

PostGIS

Spatial and Geographic objects for PostgreSQL

About PostGIS

License

News

What's happening right now

PostGIS 2.3.0 Released

PostGIS 2.3.0rc1 Released

PostGIS 2.3.0beta1 Released

PostGIS 2.2.2 Released

Upcoming Events

Recent past events

Tips

Selecting only pixels of particular range of values with ST_Reclass

Case Studies

Nautilytics Case Study

PostGIS for fast prototyping and Research

Site Map

PostGIS Project Steering Committee (PSC)