Copyright © 2012 Envitia
Copyright © 2012 Luciad
Copyright © 2012 Sigma Bravo
Copyright © 2012 The Carbon Project
Copyright © 2012 U.S. Army Geospatial Center
Copyright © 2012 U.S. National Geospatial Intelligence Agency
The companies listed above have granted the Open Geospatial Consortium, Inc. (OGC) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/.
Warning
This document is not an OGC Standard. It is distributed for review and comment and to evaluate use of github for public comments in addition to the PDF document format that was provided by the OGC RFC at http://www.opengeospatial.org/standards/requests/105. The formal public comment period for that RFC has closed. This document is subject to change without notice and SHALL NOT be referred to as an OGC Standard. The GeoPackage SWG is about to complete a final draft for consideration by the OGC Technical Committee for adoption as an OGC Standard. If your comments are not reflected in the final SWG draft, you may submit an OGC Change Request for the adopted GeoPackage Standard at http://www.opengeospatial.org/standards/cr.
Document type: OGC® Publicly Available Standard
Document subtype: Encoding Standard
Document stage: Draft
Document language: English
Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.
Mobile device users who require map/geospatial application services and operate in disconnected or limited network connectivity environments are challenged by limited storage capacity and the lack of open format geospatial data to support these applications. The current situation is that each map/geospatial application requires its own potentially proprietary geospatial data store. These separate application-specific data stores may contain the same geospatial data, wasting the limited storage available, and requiring custom applications for data translation, replication, and synchronization to enable different map/geospatial applications to share the same world view. In addition, many existing geospatial data stores are platform-specific, which means that users with different platforms must translate data to share it.
An open, standards-based, application-independent, platform-independent, portable, interoperable, self-describing, GeoPackage (GPKG) data container, API and manifest are needed to overcome these challenges and to effectively support multiple map/geospatial applications such as fixed product distribution, local data collection, and geospatially enabled analytics. This standard is intended to facilitate widespread adoption and use of GeoPackages by both COTS and open-source software applications on enterprise production platforms as well as mobile hand-held devices, given that mobile hand held devices do not yet have the processing power or battery life to effectively tackle difficult geospatial product production and analysis tasks. An application that accesses a GPKG will make use of the GPKG capabilities it requires; few if any such applications will make use of all GPKG capabilities.
This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications.
A GeoPackage is a platform-independent SQLite database file that contains GeoPackage data and metadata tables shown in GeoPackage Tables, with specified definitions, integrity assertions, format limitations and content constraints. The allowable content of a GeoPackage is entirely defined in this specification.
An Extended GeoPackage is a GeoPackage that contains any additional data elements (tables or columns) or SQL constructs (data types, indexes, constraints or triggers) that are not specified in this encoding standard.
A GeoPackage MAY be “empty” (contain user data table(s) for vector features and/or tile matrix pyramids with no row record content) ) or contain one or many vector feature type records and /or one or many tile matrix pyramid tile images. GeoPackage metadata can describe GeoPackage data contents and identify external data synchronization sources and targets. A GeoPackage MAY contain spatial indexes on feature geometries and SQL triggers to maintain indexes and enforce content constraints.
A GeoPackage SQLite Configuration consists of the SQLite 3 software library and a set of compile- and runtime configurations options.
A GeoPackage SQLite Extension is a SQLite loadable extension that MAY provide SQL functions to support spatial indexes and SQL triggers linked to a SQLite library with specified configuration requirements to provide SQL API access to a GeoPackage file. This specification does not address the issues listed in the [_potential_future_work] clause in [background_and_context], which MAY be addressed in a subsequent version of this specification or by other specifications.
Attention is drawn to the possibility that some of the elements of this document MAY be the subject of patent rights. Open Geospatial Consortium Inc. SHALL not be held responsible for identifying any or all such patent rights. However, to date, no such rights have been claimed or identified.
Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they MAY be aware that might be infringed by any implementation of the specification set forth in this document, and to provide supporting documentation.