The functions given below are spatial aggregate functions provided with PostGIS that can be used just like any other sql aggregate function such as sum, average.
The functions given below are spatial window functions provided with PostGIS that can be used just like any other sql window function such as row_numer(), lead(), lag(). All these require an SQL OVER() clause.
The functions given below are PostGIS functions that conform to the SQL/MM 3 standard
![]() | |
SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1. |
The functions and operators given below are PostGIS functions/operators that take as input or return as output a geography data type object.
![]() | |
Functions with a (T) are not native geodetic functions, and use a ST_Transform call to and from geometry to do the operation. As a result, they may not behave as expected when going over dateline, poles, and for large geometries or geometry pairs that cover more than one UTM zone. Basic transform - (favoring UTM, Lambert Azimuthal (North/South), and falling back on mercator in worst case scenario) |
The functions and operators given below are PostGIS functions/operators that take as input or return as output a 栅格 data type object. Listed in alphabetical order.
The functions given below are PostGIS functions that take as input or return as output a set of or single geometry_dump or geomval data type object.
The functions given below are PostGIS functions that take as input or return as output the box* family of PostGIS spatial types. The box family of types consists of box2d, and box3d
The functions given below are PostGIS functions that do not throw away the Z-Index.
The functions given below are PostGIS functions that can use CIRCULARSTRING, CURVEPOLYGON, and other curved geometry types
The functions given below are PostGIS functions that can use POLYHEDRALSURFACE, POLYHEDRALSURFACEM geometries
Below is an alphabetical listing of spatial specific functions in PostGIS and the kinds of spatial types they work with or OGC/SQL compliance they try to conform to.
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 3.3
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 3.2
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 3.1
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 3.0
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 2.5
The functions given below are PostGIS functions that were added or enhanced.
Functions changed in PostGIS 2.4
All PostGIS aggregates now marked as parallel safe. This will force a drop and recreate of aggregates during upgrade which may fail if any user views or sql functions rely on PostGIS aggregates.
The functions given below are PostGIS functions that were added or enhanced.
![]() | |
PostGIS 2.3.0: PostgreSQL 9.6+ support for parallel queries. |
![]() | |
PostGIS 2.3.0: PostGIS extension, all functions schema qualified to reduce issues in database restore. |
![]() | |
PostGIS 2.3.0: PostgreSQL 9.4+ support for BRIN indexes. Refer to Section 4.9.2, “Brin指数”. |
![]() | |
PostGIS 2.3.0: Tiger Geocoder upgraded to work with TIGER 2016 data. |
The functions given below are PostGIS functions that were added or enhanced.
![]() | |
postgis_sfcgal now can be installed as an extension using CREATE EXTENSION postgis_sfcgal; |
![]() | |
PostGIS 2.2.0: Tiger Geocoder upgraded to work with TIGER 2015 data. |
![]() | |
address_standardizer, address_standardizer_data_us extensions for standardizing address data refer to Section 14.1, “地址标准器” for details. |
![]() | |
Many functions in topology rewritten as C functions for increased performance. |
The functions given below are PostGIS functions that were added or enhanced.
![]() | |
More Topology performance Improvements. Please refer to Chapter 10, 拓扑学 for more details. |
![]() | |
Bug fixes (particularly with handling of out-of-band rasters), many new functions (often shortening code you have to write to accomplish a common task) and massive speed improvements to raster functionality. Refer to Chapter 12, 栅格参考 for more details. |
![]() | |
PostGIS 2.1.0: Tiger Geocoder upgraded to work with TIGER 2012 census data. |
The functions given below are PostGIS functions that were added, enhanced, or have Section 15.12.11, “PostGIS Functions changed behavior in 2.0” breaking changes in 2.0 releases.
New geometry types: TIN and Polyhedral surfaces was introduced in 2.0
![]() | |
Greatly improved support for Topology. Please refer to Chapter 10, 拓扑学 for more details. |
![]() | |
In PostGIS 2.0, raster type and raster functionality has been integrated. There are way too many new raster functions to list here and all are new so
please refer to Chapter 12, 栅格参考 for more details of the raster functions available. Earlier pre-2.0 versions had raster_columns/raster_overviews as real tables. These were changed to views before release. Functions such as |
![]() | |
Tiger Geocoder upgraded to work with TIGER 2010 census data and now included in the core PostGIS documentation. A reverse geocoder function was also added. Please refer to Section 14.2, “TIGER地理编码器” for more details. |
The functions given below are PostGIS functions that have changed behavior in PostGIS 2.0 and may require application changes.
![]() | |
Most deprecated functions have been removed. These are functions that haven't been documented since 1.2 or some internal functions that were never documented. If you are using a function that you don't see documented, it's probably deprecated, about to be deprecated, or internal and should be avoided. If you have applications or tools that rely on deprecated functions, please refer to Q: 9.2 for more details. |
![]() | |
Bounding boxes of geometries have been changed from float4 to double precision (float8). This has an impact on answers you get using bounding box operators and casting of bounding boxes to geometries. E.g ST_SetSRID(abbox) will often return a different more accurate answer in PostGIS 2.0+ than it did in prior versions which may very well slightly change answers to view port queries. |
![]() | |
The arguments hasnodata was replaced with exclude_nodata_value which has the same meaning as the older hasnodata but clearer in purpose. |
The functions given below are PostGIS functions that were introduced or enhanced in the 1.4 release.