GeoPackage
Sign in to saveAlso known as GeoPackage Encoding Standard, GPKG, .gpkg, OGC GeoPackage
GeoPackage (GPKG) is an open, non-proprietary, platform-independent and standards-based data format for geographic information systems built as a set of conventions over a SQLite database. Defined by the Open Geospatial Consortium (OGC) with the backing of the US military and published in 2014, GeoPackage has seen widespread support from various government, commercial, and open source organizations.
Described at
GeoPackage Standard – Open SQLite Format for Geospatial Data
Discover the GeoPackage standard, an open SQLite-based format for storing and exchanging vector data, raster maps, tiles, and metadata across GIS platforms.
opengeospatial.org →This encoding standard describes a set of rules and conventions for storing vector features, imagery tile matrix sets, raster map tile matrix sets and non-spatial tabular data in a SQLite database. The standard also describes rules for extending the capabilities of a GeoPackage. (Hover over Type for full description) Document title Version OGC Doc No. Type A GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. The GeoPackage standard describes a set of conventions for storing the following within a SQLite database: To be clear, a GeoPackage is the SQLite container and the GeoPackage Encoding Standard governs the rules and requirements of content stored in a GeoPackage container. The GeoPackage standard defines the schema for a GeoPackage, including table definitions, integrity assertions, format limitations, and content constraints. The required and supported content of a GeoPackage is entirely defined in the standard. Since a GeoPackage is a database container, it supports direct use. This means that data in a GeoPackage can be accessed and updated in a “native” storage format without intermediate format translations. GeoPackages that comply with the requirements in the standard and do not implement vendor-specific extensions are interoperable across all enterprise and personal computing environments. GeoPackages are particularly useful on mobile devices such as cell phones and tablets in communications environments where there is limited connectivity and bandwidth. Public Site For more information on GeoPackage including developer resources and information on in-progress work, please visit . For the official OGC member approved versions of the standard, see the Download information below. Members of the public can review draft standards and share feedback to ensure they are practical and widely applicable. OGC Seeks Public Comment on Proposed 3D Tiles 2.0 Community Standard Work Item The Open Geospatial Consortium (OGC) Federated Maritime Spatial Data Infrastructure (FMSDI) Pilot is... Earlier in this series, I introduced four common challenges that I frequently encounter... Artificial Intelligence (AI) is reshaping how we understand our world. From disaster response...
Excerpt from a page describing this subject · 9,971 chars · not written by Vinony
~2 min read
Encyclopedic overview
4 sectionsContents
- Origin
- Format
- References
- External links
GeoPackage (GPKG) is an open, non-proprietary, platform-independent and standards-based data format for geographic information systems built as a set of conventions over a SQLite database. Defined by the Open Geospatial Consortium (OGC) with the backing of the US military and published in 2014, GeoPackage has seen widespread support from various government, commercial, and open source organizations.
==Origin== Despite dozens of file formats and services for exchanging geospatial data, there was not an open format which could support both raster and vector data, while being efficiently decodable by software, particularly in mobile devices. This need was formally expressed at the OGC in 2012. The candidate standard was approved by the OGC in February 2014.
Excerpted from Wikipedia’s “GeoPackage” article, available under the CC BY-SA 4.0 licence.