Simple Features
Simple Features (officially Simple Feature Access) is both an Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO) standard ISO 19125 that specifies a common storage and access model of mostly two-dimensional geographical data (point, line, polygon, multi-point, multi-line, etc.)
The ISO 19125 standard comes in two parts. Part one, ISO 19125-1 (SFA-CA for "common architecture"), defines a model for two-dimensional simple features, with linear interpolation between vertices. The data model defined in SFA-CA is a hierarchy of classes. This part also defines representation using Well-Known Text (and Binary). Part 2 of the standard, ISO 19125-2 (SFA-SQL), defines an implementation using SQL.[1] The OpenGIS standard(s) cover implementations in CORBA and OLE/COM as well, although these have lagged behind the SQL one and are not standardized by ISO.
The ISO/IEC 13249-3 SQL/MM Spatial extends the Simple Features data model mainly with circular interpolations (e.g. circular arcs) and adds other features like coordinate transformations and methods for validating geometries as well as Geography Markup Language support.[1]
Standard documents
- ISO/IEC:
- OpenGIS
- OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture (05-126, 06-103r3, 06-103r4), current version 1.2.1
- OpenGIS Simple Feature Access - Part 2: SQL Option (99-054, 05-134, 06-104r3, 06-104r4), current version 1.2.1, formerly OpenGIS Simple Features [Implementation Specification] for SQL
- OpenGIS Simple Features Implementation Specification for CORBA (99-054), current version 1.0
- OpenGIS Simple Features Implementation Specification for OLE/COM (99-050), current version 1.1
Part 1 details
![[icon]](/wiki/File:Wiki_letter_w_cropped.svg){kind=small} | This section needs expansion. You can help by adding to it. (November 2012) |
The geometries are also associated with spatial reference systems. The standard also specifies attributes, methods and assertions with the geometries. In general, a 2D geometry is simple if it contains no self-intersection. The specification defines DE-9IM spatial predicates and several spatial operators that can be used to generate new geometries from existing geometries.
Implementations
| This section needs expansion. You can help by adding to it. (November 2012) |
Part 2 of Simple Feature Access is implemented to varying degrees in:
- MySQL Spatial Extensions.[2] Up to MySQL 5.5, all of the functions that calculate relations between geometries are implemented using bounding boxes not the actual geometries.[3] Starting from version 5.6, MySQL offers support for precise object shapes.[4]
- MonetDB/GIS extension for MonetDB.[5]
- PostGIS extension for PostgreSQL, also supporting some of the SQL/MM Spatial features.[6]
- SpatiaLite extension for SQLite[7]
- Oracle Spatial, which also implements some of the advanced features from SQL/MM Spatial.[8]
- IBM DB2 Spatial Extender and IBM Informix Spatial DataBlade.[6]
- Microsoft SQL Server since version 2008,[6] with significant additions in the 2012 version.[9]
- SAP Sybase IQ.[10]
- SAP HANA as of 1.0 SPS6.[11]
The GDAL library (sometimes described as a Spatial ETL because it can convert between various proprietary storage models) implements the Simple Features data model in its OGR component.[12] The Java-based deegree framework implements SFA (part 1) and various other OGC standards.[13]
GeoSPARQL is an OGC standard that is intended to allow geospatially-linked data representation and querying based on RDF and SPARQL by defining an ontology for geospatial reasoning supporting a small Simple Features (as well as DE-9IM and RCC8) RDFS/OWL vocabulary for GML and WKT literals.[14]
Alternatives
As of 2012, various NoSQL databases have very limited support for "anything more complex than a bounding box or proximity search".[3]
See also
References
- ^ a b Wolfgang Kresse; David M. Danko (2011). Springer Handbook of Geographic Information. Springer. pp. 81–83. ISBN 978-3-540-72678-4.
- ^ MySQL 5.1 documentation on Spatial extensions
- ^ a b Frank Hardisty (Fall 2012). "Penn State Geography 583: Geospatial System Analysis and Design. Databases".
- ^ MySQL 5.6 documentation on Spatial extensions
- ^ "GeoSpatial - MonetDB". 4 March 2014.
- ^ a b c Wolfgang Kresse; David M. Danko (2011). Springer Handbook of Geographic Information. Springer. pp. 105–106. ISBN 978-3-540-72678-4.
- ^ SpatiaLite Simple Features implementation for SQLite
- ^ Ravikanth V. Kothuri; Euro Beinat; Albert Godfrind (2004). Pro Oracle Spatial. Apress. p. 65. ISBN 978-1-59059-383-7.
- ^ Alastair Aitchison (2012). Pro Spatial with SQL Server 2012. Apress. pp. 21–23. ISBN 978-1-4302-3491-3.
- ^ http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01964.1602/doc/html/saiq-standards-compatibility-spatial.html SAP Sybase IQ support for spatial data
- ^ http://help.sap.com/saphelp_hanaplatform/helpdata/en/7a/2f4266787c1014a9b6ab6cf937f8ac/content.htm?frameset=/en/7a/2d11d7787c1014ac3a8663250814c2/frameset.htm¤t_toc=/en/99/d10e4fdaaf41588480a43478e840d5/plain.htm&node_id=12 SAP HANA Spatial Reference: Supported Import and Export Formats for Spatial Data
- ^ http://www.gdal.org/ogr/
- ^ Shashi Shekhar; Hui Xiong (2007). Encyclopedia of GIS. Springer. pp. 235–236. ISBN 978-0-387-30858-6.
- ^ Battle, Robert; Kolas, Dave (2012). "Enabling the Geospatial Semantic Web with Parliament and GeoSPARQL" (PDF). Semantic Web. 3 (4). IOS Press: 355–370. doi:10.3233/SW-2012-0065. Retrieved 21 November 2012.
