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.
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.
The PostGIS development team is pleased to announce the release of PostGIS 2.3.1. Best served with pgRouting 2.3.1 and PostgreSQL 9.6.1.
As befits a patch release, the focus is on bugs and breakages.
The PostGIS development team is pleased to announce the release of PostGIS 2.2.4 As befits a patch release, the focus is on bugs and breakages.
The PostGIS development team is pleased to announce the release of PostGIS 2.2.3 As befits a patch release, the focus is on bugs and breakages.
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.
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.
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.
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?).