diff --git a/gpdb-doc/dita/ref_guide/extensions/postGIS.xml b/gpdb-doc/dita/ref_guide/extensions/postGIS.xml index 2fc098eec1a8b0c4d14da76121f28d6d093a8044..1d24cb7b84b338c232842897bb6f5402a8c12117 100644 --- a/gpdb-doc/dita/ref_guide/extensions/postGIS.xml +++ b/gpdb-doc/dita/ref_guide/extensions/postGIS.xml @@ -15,12 +15,7 @@
    • -
  • - -
    • -
  • - -
    • +
    • @@ -36,44 +31,52 @@ Information Systems) objects to be stored in the database. The Greenplum Database PostGIS extension includes support for GiST-based R-Tree spatial indexes and functions for analysis and processing of GIS objects.

    -

    Go to - http://postgis.refractions.net/ for more information about PostGIS.

    +

    The Greenplum Database PostGIS extension supports the optional PostGIS + raster data type and most PostGIS Raster functions. With the PostGIS + Raster objects, PostGIS geometry data type offers a single set of overlay + SQL functions (such as ST_Intersects) operating seamlessly on vector and + raster geospatial data. PostGIS Raster uses the GDAL (Geospatial Data Abstraction Library) + translator library for raster geospatial data formats that presents a single + raster abstract data model to a calling application.

    For information about Greenplum Database PostGIS extension support, see .

    +

    For information about PostGIS, see http://postgis.refractions.net/ +

    +

    For information about GDAL, see http://www.gdal.org.

    Greenplum PostGIS Extension -

    The Greenplum Database PostGIS extension is available from The Greenplum Database PostGIS extension package is available from Pivotal - Network. You can install it using the Greenplum Package Manager + Network. You can install the package using the Greenplum Package Manager (gppkg). For details, see gppkg in the Greenplum Database Utility Guide.

    -

    For the information about supported extension packages and software versions see the - Greenplum Database Release Notes.

    -

    Major enhancements and changes in 2.0.3 from 1.4.2 include:

    - -

    See the PostGIS documentation for a list of changes: http://postgis.net/docs/manual-2.0/release_notes.html

    - PostGIS 2.0 removed many functions that were deprecated but available - in PostGIS 1.4. Functions and applications written with functions that were deprecated in - PostGIS 1.4 might need to be rewritten. See the PostGIS documentation for a list of new, - enhanced, or changed functions: http://postgis.net/docs/manual-2.0/PostGIS_Special_Functions_Index.html - #NewFunctions +

    Greenplum Database supports the PostGIS extension with these component versions.

    +

    For the information about supported extension packages and software + versions see the Greenplum Database Release Notes.

    +

    Major enhancements and changes in PostGIS 2.1.5 from 2.0.3 include new PostGIS Raster + functions. For a list of new and enhanced functions in PostGIS 2.1, see the PostGIS + documentation PostGIS Functions new or enhanced in 2.1.

    +

    For a list of breaking changes in PostGIS 2.1, see PostGIS functions breaking changes in 2.1.

    +

    For a comprehensive list of PostGIS changes in PostGIS 2.1.5 and earlier, see PostGIS 2.1 + Appendix A Release 2.1.5.

    Greenplum Database PostGIS Limitations @@ -81,7 +84,6 @@

    The Greenplum Database PostGIS extension does not support the following features:

    +

    For a list of PostGIS data types, operators, and functions, see the PostGIS reference documentation.

    + +     + + Supported PostGIS Raster Data Types + +

    Greenplum Database PostGIS supports these PostGIS Raster data types.

    + +

    For information about PostGIS Raster data Management, queries, and applications http://postgis.net/docs/manual-2.1/using_raster_dataman.html

    +

    For a list of PostGIS Raster data types, operators, and functions, see the PostGIS Raster reference documentation.

     @@ -230,17 +300,15 @@ USING GIST ( geometryfield ); PostGIS Extension Limitations -

    This section lists the Greenplum Database PostGIS extension limitations for user defined - functions (UDFs), data types and aggregates.

    +

    This section lists the Greenplum Database PostGIS extension limitations for user-defined + functions (UDFs), data types, and aggregates.

      -
    • Data types and functions related to PostGIS topology or raster functionality, such as - TopoGeometry and ST_AsRaster are not supported - by Greenplum Database.
      • -
    • ST_Estimated_Extent function is not supported. The function - requires table column statistics for user defined data types that are not available with - Greenplum Database.
      • -
    • ST_GeomFromGeoJSON function is not supported. The function requires - JSON support. JSON is not supported in Greenplum Database.
      • +
    • Data types and functions related to PostGIS topology functionality, such as + TopoGeometry, are not supported by Greenplum Database.
      • +
    • Functions that perform ANALYZE operations for user-defined data + types are not supported. For example, the ST_Estimated_Extent + function is not supported. The function requires table column statistics for user + defined data types that are not available with Greenplum Database.
    • These PostGIS aggregates are not supported by Greenplum Database:
      • ST_MemCollect
        • @@ -249,10 +317,11 @@ USING GIST ( geometryfield ); different answers if it is called several times repeatedly.

      • Greenplum Database does not support PostGIS long transactions.

        -

        PostGIS relies on triggers and the PostGIS table public.authorization_table - for long transaction support. When PostGIS attempts to acquire locks for long - transactions, Greenplum Database reports errors citing that the function cannot access - the relation, authorization_table.

        +

        PostGIS relies on triggers and the PostGIS table + public.authorization_table for long transaction support. When + PostGIS attempts to acquire locks for long transactions, Greenplum Database reports + errors citing that the function cannot access the relation, + authorization_table.

      • Greenplum Database does not support type modifiers for user defined types.

        The work around is to use the AddGeometryColumn function for PostGIS geometry.