The new v5.5 of TEAM Engine on the OGC Validator
TEAM Engine is the open source software used for validating compliance to OGC Standards. Version 5.5 of TEAM Engine brings some exciting improvements.
GeoPackage Encoding Standard
Overview
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:
- vector features
- tile matrix sets of imagery and raster maps at various scales
- extensions
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.
Additional Resources
- Public Site For more information on GeoPackage including developer resources and information on in-progress work, please visit http://www.geopackage.org/ . For the official OGC member approved versions of the standard, see the Download information below.
- Media Type https://www.iana.org/assignments/media-types/application/geopackage+sqlite3
Downloads
Official model files and encoding schemas
Working Groups
With Version 1.1, the GeoPackage standard is stable. However, the GeoPackage Standards Working Group (SWG) is actively addressing issues and possible extensions. The GeoPackage SWG group has a public page at:
Submit a Change Request, Requirement, or Comment for this OGC standard.
Related links
No Results Found.
OGC Standards
- 3D Tiles
- 3dP
- ARML2.0
- Cat: ebRIM App Profile: Earth Observation Products
- Catalogue Service
- CDB
- CityGML
- CityJSON
- Coordinate Transformation
- EO-GeoJSON
- Filter Encoding
- GML in JPEG 2000
- GeoAPI
- GeoPackage
- GeoPose
- GeoSciML
- GeoSPARQL
- Geography Markup Language
- GeoRSS
- Geospatial eXtensible Access Control Markup Language (GeoXACML)
- Geospatial User Feedback (GUF)
- GeoTiff
- GroundwaterML
- HDF5
- I3S
- Indoor Mapping Data Format (IMDF)
- IndoorGML
- KML
- LandInfra/InfraGML
- LAS
- Location Services (OpenLS)
- Moving Features
- NetCDF
- Observations and Measurements
- OGC API – EDR
- OGC API – Features
- OGC API – Processes
- OGC API – Tiles
- Open GeoSMS
- OpenMI
- OpenSearch
- Ordering Services Framework for Earth Observation Products
- OWS Context
- OWS Security
- PipelineML
- PubSub
- PUCK
- SWE Common Data Model
- SWE Service Model
- Sensor Model Language
- Sensor Observation Service
- Sensor Planning Service
- SensorThings
- Semantic Sensor Network (SSN)
- Symbology Core
- Simple Features
- Simple Features CORBA
- Simple Features OLE/COM
- Simple Features SQL
- Styled Layer Descriptor
- Symbology Encoding
- Table Joining Service
- Time Ontology in OWL
- TimeseriesML (tsml)
- Two Dimensional Tile Matrix Set
- WaterML
- Web Coverage Processing Service
- Web Coverage Service
- Web Feature Service
- Web Map Context
- Web Map Service
- Web Map Tile Service
- Web Processing Service
- Web Service Common
- WKT CRS
