PostGIS
Developer(s) | Refractions Research, Paul Ramsey, Dave Blasby, Kevin Neufeld, Mark Cave-Ayland, Regina Obe, Sandro Santilli, Olivier Courtin, Nicklas Avén, Bborie Park, Pierre Racine, Jeff Lounsbury, Chris Hodgson, Jorge Arévalo, Mateusz Loskot, Norman Vine, Carl Anderson, Ralph Mason, Klaus Foerster, Bruno Wolff III, Markus Schaber |
---|---|
Initial release | April 19, 2005 |
Stable release | 1.5.3
/ June 25, 2011 |
Repository | |
Operating system | GNU/Linux, MS-Windows, Mac OS X, POSIX compliant systems |
Type | Geographic information system |
License | GPL |
Website | http://www.postgis.org |
PostGIS (/post'-jis/) is an open source software program that adds support for geographic objects to the PostgreSQL object-relational database. PostGIS follows the Simple Features for SQL specification from the Open Geospatial Consortium (OGC).
History
The first version was released in 2001 by Refractions Research under the GNU General Public License. A stable "1.0" version was released on April 19, 2005, which followed 6 release candidates. In 2006, PostGIS was registered as "implements the specified standard" for "Simple Features for SQL" by the OGC.[1]
Features
- Geometry types for points, linestrings, polygons, multipoints, multilinestrings, multipolygons and geometrycollections.
- Spatial predicates for determining the interactions of geometries using the 3x3 Egenhofer matrix (provided by the GEOS software library).
- Spatial operators for determining geospatial measurements like area, distance, length and perimeter.
- Spatial operators for determining geospatial set operations, like union, difference, symmetric difference and buffers (provided by GEOS).
- R-tree-over-GiST (Generalised Search Tree) spatial indexes for high speed spatial querying.
- Index selectivity support, to provide high performance query plans for mixed spatial/non-spatial queries.
- For raster data, under development PostGIS WKT Raster (now integrated into PostGIS 2.0 and renamed PostGIS Raster)
The PostGIS implementation is based on "light-weight" geometries and indexes optimized to reduce disk and memory footprint. Using light-weight geometries helps servers increase the amount of data migrated up from physical disk storage into RAM, improving query performance substantially.
PostGIS is registered as "implements the specified standard" for "Simple Features for SQL" by the OGC.[2] PostGIS has not been certified as compliant by the OGC. For the OGC's definition of compliant, see What does "Compliant" mean?.
Users
There are a large number of software products that can use PostGIS as a database backend, including:
- ST-Links PgMap
- Cadcorp SIS
- Everest GIS
- Feature Manipulation Engine
- GeoMedia (via 3rd party connectors)
- GeoServer
- GRASS GIS (GPL)
- gvSIG (GPL)
- ERDAS APOLLO
- Interoperability Extension from ESRI
- Ionic Red Spider
- Kosmo (GPL)
- Manifold System
- MapInfo Professional
- Mapnik (LGPL)
- MapDotNet Server
- MapServer (BSD)
- MapGuide (LGPL)
- MezoGIS
- OpenJUMP (GPL)
- Quantum GIS (GPL)
- TerraLib (LGPL)
- TerraView (GPL)
- uDig (LGPL)
- ArcGIS (via ST-Links PgMap, ZigGIS, ArcSDE and other 3rd party connectors)
- CitySurf Globe
See also
- Well-known text and binary, descriptions of geospatial objects used within PostGIS
References
- ^ http://www.refractions.net/products/postgis/history/
- ^ OGC Implementing Product Details Open Geospatial Consortium