See the Release 3 Milestone Summary page.
|Description||Capability extensions to index and query datasets by geospatial metadata beyond geospatial points supported in R2|
|Deliverable||Data Access Service|
|Development Team||Data Management|
|Req ID||Status||Requirement Text||Rationale and Description|
- Define key oceanographic geospatial search scenarios
- Dataset Metadata Indexing
- CIAD DM OV Discovery Service
- CIAD DM OV Index Management Service
- R2Cx Searches and Catalogs
- Evaluate GeoPortal for Externalization of Catalog and Discovery repository
- M166 PostgreSQL data store
- PostGIS Features
After our migration efforts for milestone M166 PostgreSQL data store, we should be able to leverage the featureset of PostGIS to provide OOIN and clients with geospatial awareness for all system resoures that have a geospatial identity. Once PostGIS is installed and the PostgreSQL database has the GIS extension installed then extended resources to include GIS aware objects is simple.
The GIS objects supported by PostGIS are a superset of the "Simple Features" defined by the OpenGIS Consortium (OGC). As of version 0.9, PostGIS supports all the objects and functions specified in the OGC "Simple Features for SQL" specification.
PostGIS extends the standard with support for 3DZ,3DM and 4D coordinates.
The OpenGIS specification defines two standard ways of expressing spatial objects: the Well-Known Text (WKT) form and the Well-Known Binary (WKB) form. Both WKT and WKB include information about the type of the object and the coordinates which form the object.
Examples of the text representations (WKT) of the spatial objects of the features are as follows:
- POINT(0 0)
- LINESTRING(0 0,1 1,1 2)
- POLYGON((0 0,4 0,4 4,0 4,0 0),(1 1, 2 1, 2 2, 1 2,1 1))
- MULTIPOINT(0 0,1 2)
- MULTILINESTRING((0 0,1 1,1 2),(2 3,3 2,5 4))
- MULTIPOLYGON(((0 0,4 0,4 4,0 4,0 0),(1 1,2 1,2 2,1 2,1 1)), ((-1 -1,-1 -2,-2 -2,-2 -1,-1 -1)))
- GEOMETRYCOLLECTION(POINT(2 3),LINESTRING(2 3,3 4))
The database provides the capability to query against spatial relationships. With standard geometrical relationships: contains, within, touches, etc.
Here is a quick SQL example of the geospatial capabilities:
PostGIS also supports parsers for standard industry shapefiles including KMZ, ESRI Shape files etc. This may play a role if we provide users with the capability of inputing system resources and defining shape boundaries for the resources.