From: Regina Obe Date: Sun, 23 Jul 2017 20:08:43 +0000 (+0000) Subject: Put in safeguards around availability, changes, enhances so if no match, then doesn... X-Git-Tag: 2.4.0alpha~26 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=46e8025334563eded4ac814e332d2e138731dcbf;p=postgis Put in safeguards around availability, changes, enhances so if no match, then doesn't break xml and latex validation git-svn-id: http://svn.osgeo.org/postgis/trunk@15502 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl index 6e8d5a3ca..5eab0ca07 100644 --- a/doc/xsl/postgis_aggs_mm.xml.xsl +++ b/doc/xsl/postgis_aggs_mm.xml.xsl @@ -44,7 +44,7 @@ - + PostGIS Window Functions 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. @@ -109,7 +109,7 @@ PostGIS Geography Support Functions 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, + 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) @@ -162,8 +162,8 @@ - - + + PostGIS Geometry / Geography / Raster Dump Functions 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. @@ -190,7 +190,7 @@ - + PostGIS Box Functions The functions given below are PostGIS functions that take as input or return as output the box* family of PostGIS spatial types. @@ -277,7 +277,7 @@ - + PostGIS Polyhedral Surface Support Functions The functions given below are PostGIS functions that can use POLYHEDRALSURFACE, POLYHEDRALSURFACEM geometries @@ -315,14 +315,14 @@ ]]> ]]> ]]> - + PostGIS Function Support Matrix 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. A means the function works with the type or subtype natively. - A means it works but with a transform cast built-in using cast to geometry, transform to a "best srid" spatial ref and then cast back. Results may not be as expected for large areas or areas at poles + A means it works but with a transform cast built-in using cast to geometry, transform to a "best srid" spatial ref and then cast back. Results may not be as expected for large areas or areas at poles and may accumulate floating point junk. A means the function works with the type because of a auto-cast to another such as to box3d rather than direct type support. A means the function only available if PostGIS compiled with SFCGAL support. @@ -334,7 +334,7 @@ T - Triangles and Triangulated Irregular Network surfaces (TIN) - + @@ -372,7 +372,7 @@ - + @@ -406,7 +406,7 @@ - + @@ -431,7 +431,7 @@ - + @@ -475,7 +475,7 @@ - + @@ -485,6 +485,7 @@ PostGIS Functions new or enhanced in 2.4 The functions given below are PostGIS functions that were added or enhanced. + Functions new in PostGIS 2.4 @@ -496,12 +497,12 @@ - + - - + + @@ -514,11 +515,12 @@ - + + TODO: Enhance some functions in 2.4 so this space isn't empty. - + - + PostGIS Functions new or enhanced in 2.3 The functions given below are PostGIS functions that were added or enhanced. @@ -526,6 +528,7 @@ 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 . PostGIS 2.3.0: Tiger Geocoder upgraded to work with TIGER 2016 data. + Functions new in PostGIS 2.3 @@ -537,12 +540,12 @@ - + - - + + @@ -555,7 +558,9 @@ - + + + The functions given below are PostGIS functions that are enhanced in PostGIS 2.3. @@ -564,7 +569,7 @@ - + @@ -579,18 +584,20 @@ - + + - + PostGIS Functions new or enhanced in 2.2 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 for details. Many functions in topology rewritten as C functions for increased performance. + Functions new in PostGIS 2.2 @@ -602,12 +609,12 @@ - + - - + + @@ -620,7 +627,9 @@ - + + + The functions given below are PostGIS functions that are enhanced in PostGIS 2.2. @@ -629,7 +638,7 @@ - + @@ -644,10 +653,12 @@ - + + - - PostGIS functions breaking changes in 2.2 + + + PostGIS functions breaking changes in 2.2 The functions given below are PostGIS functions that have possibly breaking changes in PostGIS 2.2. If you use any of these, you may need to check your existing code. @@ -656,7 +667,7 @@ - + @@ -673,17 +684,19 @@ + + - PostGIS Functions new or enhanced in 2.1 The functions given below are PostGIS functions that were added or enhanced. - + More Topology performance Improvements. Please refer to 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 for more details. - PostGIS 2.1.0: Tiger Geocoder upgraded to work with TIGER 2012 census data. geocode_settings added for debugging and tweaking rating preferences, loader made less greedy, now only downloads tables to be loaded. PostGIS 2.1.1: Tiger Geocoder upgraded to work with TIGER 2013 data. + PostGIS 2.1.0: Tiger Geocoder upgraded to work with TIGER 2012 census data. geocode_settings added for debugging and tweaking rating preferences, loader made less greedy, now only downloads tables to be loaded. PostGIS 2.1.1: Tiger Geocoder upgraded to work with TIGER 2013 data. Please refer to for more details. - + + Functions new in PostGIS 2.1 @@ -695,7 +708,7 @@ - + @@ -713,7 +726,9 @@ - + + + The functions given below are PostGIS functions that are enhanced in PostGIS 2.1. @@ -722,7 +737,7 @@ - + @@ -737,10 +752,12 @@ - - + + + - + + PostGIS functions breaking changes in 2.1 The functions given below are PostGIS functions that have possibly breaking changes in PostGIS 2.1. If you use any of these, you may need to check your existing code. @@ -750,7 +767,7 @@ - + @@ -767,17 +784,20 @@ + + - PostGIS Functions new, behavior changed, or enhanced in 2.0 The functions given below are PostGIS functions that were added, enhanced, or have 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 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 + 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 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 ST_AddRasterColumn were removed and replaced with , as a result some apps that created raster tables may need changing. 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 for more details. + + @@ -788,7 +808,7 @@ - + @@ -806,7 +826,9 @@ - + + + The functions given below are PostGIS functions that are enhanced in PostGIS 2.0. @@ -815,7 +837,7 @@ - + @@ -830,8 +852,10 @@ - + + + PostGIS Functions changed behavior in 2.0 The functions given below are PostGIS functions that have changed behavior in PostGIS 2.0 and may require application changes. @@ -844,6 +868,8 @@ 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. + + @@ -851,7 +877,7 @@ - + @@ -867,9 +893,12 @@ + + PostGIS Functions new, behavior changed, or enhanced in 1.5 + The functions given below are PostGIS functions that were introduced or enhanced in this minor release. @@ -881,7 +910,7 @@ - + @@ -899,10 +928,12 @@ + PostGIS Functions new, behavior changed, or enhanced in 1.4 The functions given below are PostGIS functions that were introduced or enhanced in the 1.4 release. + @@ -926,10 +957,12 @@ + PostGIS Functions new in 1.3 The functions given below are PostGIS functions that were introduced in the 1.3 release. + @@ -953,6 +986,7 @@ +