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)[2] with the backing of the US military[3] and published in 2014, GeoPackage has seen widespread support from various government, commercial, and open source organizations.[4]
| Filename extension |
.gpkg |
|---|---|
| Internet media type |
application/geopackage+sqlite3[1] |
| Developed by | Open Geospatial Consortium |
| Initial release | 13 February 2014 |
| Latest release | 1.3 26 November 2020 |
| Type of format | Geographic information system |
| Contained by | SQLite |
| Standard | OGC GeoPackage Encoding Standard |
| Open format? | Yes |
| Website | OGC GeoPackage Standard Working Group |
Origin
editDespite 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.[5][6] This need was formally expressed at the OGC in 2012.[7] The candidate standard was approved by the OGC in February 2014.[8]
Format
editA GeoPackage is defined as a SQLite 3 database file with a specific database schema and with filename extension .gpkg.[9] The schema defines data and metadata tables with specified definitions, integrity assertions, format limitations and content constraints.[9]
The GeoPackage standard describes a set of conventions (requirements) for storing vector features, tile matrix sets of imagery and raster maps at various scales, schema and metadata.
A GeoPackage can be extended by using the extension rules as defined in clause 2.3 of the standard. The OGC GeoPackage standard specifies a set of OGC member approved extensions in Annex F. Additional (vendor-specific) extensions may also be added by following the rules for GeoPackage extensions, however doing so can impact interoperability.
GeoPackage was designed to be as lightweight as possible and be contained in one ready-to-use single file. This makes it suitable for mobile applications in disconnected mode[10] and rapid sharing on cloud storage, USB drives, etc. The GeoPackage extension F.3 RTree Spatial Indexes specifies how to use SQLite spatial indexes in order to speed up performance on spatial queries compared to traditional geospatial files formats.
References
edit- ^ Scott Simmons (10 August 2018). "GeoPackage". IANA Media Types. Retrieved 23 April 2021.
- ^ "GeoPackage Encoding Standard". Open Geospatial Consortium. Retrieved 2024-05-15.
- ^ Yasin, Rutrell (2015-08-17). "At the edge: Pushing geo data to "disadvantaged" troops". C4ISRNet. Retrieved 2024-05-15.
- ^ "Implementations Listed by Specification". Open Geospatial Consortium. Retrieved 2024-05-15.
- ^ "GeoPackage as Future Ubiquitous GIS Data Format: A Review". www.jurnalteknologi.utm.my. Archived from the original on 2015-12-22. Retrieved 2015-12-20.
- ^ Singh, R.; Bermudez, L. E. (2013-12-01). "Emerging Geospatial Sharing Technologies in Earth and Space Science Informatics". AGU Fall Meeting Abstracts. 33: 08. Bibcode:2013AGUFMIN33C..08S.
- ^ "The OGC Forms GeoPackage Standards Working Group". Open Geospatial Consortium. 2012-10-25. Retrieved 2024-05-15.
- ^ "PR: OGC Adopts Important GeoPackage Standard for Mobile". GIS Resources. 2014-02-14. Retrieved 2024-05-15.
- ^ a b "OGC® GeoPackage Encoding Standard".
- ^ "The OGC agrees on a standard for mobile exchange of geospatial data | UN-SPIDER Knowledge Portal". www.un-spider.org. Retrieved 2024-05-15.
External links
edit- Geopackage website - Containing implementation guidelines, sample data, etc.
- Geopackage format description on digitalpreservation