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.

Should you upgrade now?

Not sure if you are running the best possible PostGIS for your PostgreSQL? Refer to our Version compatibility and EOL Policy.

License

PostGIS is released under the GNU General Public License (GPLv2 or later). 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.5.0rc2

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

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.0 which were released recently.

Best served with PostgreSQL 11beta3.

WARNING: If compiling with PostgreSQL 11+JIT, LLVM >= 6 is required

2.5.0rc2

source download
NEWS
PDF docs en, de
html doc download
epub doc download
pgsql help files for non-english languages: de, ja,kr, br, es
Changelog

Changes since PostGIS 2.5.0rc1 release are as follows:

4162, ST_DWithin documentation examples for storing geometry and radius in table (Darafei Praliaskouski, github user Boscop).
4163, MVT: Fix resource leak when the first geometry is NULL (Raúl Marín)
4172, Fix memory leak in lwgeom_offsetcurve (Raúl Marín)
4164, Parse error on incorrectly nested GeoJSON input (Paul Ramsey)
4176, ST_Intersects supports GEOMETRYCOLLECTION (Darafei Praliaskouski)
4177, Postgres 12 disallows variable length arrays in C (Laurenz Albe)
4160, Use qualified names in topology extension install (Raúl Marín)
4180, installed liblwgeom includes sometimes getting used instead of source ones (Regina Obe)

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.

PostGIS Patch Release 2.4.5

The PostGIS development team is pleased to provide bug fix 2.4.5 for the 2.4 stable branch.

View all closed tickets for 2.4.5.

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

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

More News…

Upcoming Events

PGCONF.EU
Oct 23rd-26th 2018 Lisbon, Portugal

Recent past events

PostgresOpen SV 2018
Sep 5th-7th 2018, San Franciso, CA, USA

FOSS4G 2018, August 27- September 2nd Dar es Salam, Tanzania

Aug 27th- Sep 2nd 2018 Dar es Salam, Tanzania

July 16th-21th 2018, Portugal

POSTGRES VISION 2018, June 5th-6th, Boston MA

Jun 5-6th 2018 Boston, MA USA

May 15th-17th 2018 Paris, France

May 14th-16th 2018 St. Louis, MO, USA

PostgresConf US: April 16th-20th, 2018
in Jersey City, NJ, USA

Boston, MA, USA, August 14th-19th 2017

Tips

Move PostGIS extension to a different schema

As of PostGIS 2.3, the postgis extension was changed to no longer allow relocation. All function calls within the extension are now schema qualified.

While this change fixed some issues with database restore, it created the issue of if you installed PostGIS in a schema other than the one you wanted to it is not intuitive how to move it to a different schema. Luckily there is a way to do this.

For this exercise, I will install PostGIS in the default schema and then demonstrate how to move it into another schema location.

You can run these steps using psql or pgAdmin or any other PostgreSQL tool you want.

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

PostGIS

Spatial and Geographic objects for PostgreSQL

About PostGIS

Should you upgrade now?

License

News

What's happening right now

PostGIS 2.5.0rc2

PostGIS Patch Release 2.4.5

PostGIS 2.5.0rc1

PostGIS 2.5.0beta2

Upcoming Events

Recent past events

Tips

Move PostGIS extension to a different schema

Case Studies

Nautilytics Case Study

PostGIS for fast prototyping and Research

Site Map

PostGIS Project Steering Committee (PSC)