GeoPackage Encoding Standard

1) Overview
2) Public Site
3) Downloads
4) Working Groups

1) Overview

A GeoPackage is a platform-independent SQLite database file that may contain:

  • vector geospatial features
  • tile matrix sets of imagery and raster maps at various scales
  • metadata

Since a GeoPackage is a database, it supports direct use, meaning that its data can be accessed and updated in a "native" storage format without intermediate format translations. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. This OGC® Encoding Standard defines the schema for a GeoPackage, including table definitions, integrity assertions, format limitations, and content constraints. The allowable content of a GeoPackage is entirely defined in this specification.

 


 

OGC GeoPackage reference implementation

The ERDC Whitehorse Geopackage Download (134MB)

The OGC GeoPackage reference implementation used for the Plugfest was created by the US Army Engineer Research and Development Center (ERDC). This raster tile pyramid GeoPackage was created with free imagery obtained from Geomatics Yukon, and covers an approximately 30 square-kilometer area centered on the City of Whitehorse. The OGC GeoPackage Plugfest reference implementation uses the Web Mercator (EPSG:3857) coordinate reference system, 256x256 pixel tiles, contains zoom levels 11-18, and is 135.25MB in size. The Python scripts used to create this GeoPackage can be found at https://github.com/GitHubRGI/geopackage-python.

2) Public Site

For the online version of the standard and the developer resources, visit http://www.geopackage.org/

3) Downloads

Version Document Title (click to download) Document # Type
1.0.1 OGC Geopackage Encoding Standard - With Corregendum 12-128r11 ISc
1.0 OGC® GeoPackage Encoding Standard 12-128r10 IS

 

4) Working Groups

This specification is currently stable, however, Working Groups are put in place to actively address future changes.The GeoPackage SWG group has a public page at: http://www.opengeospatial.org/projects/groups/geopackageswg

Submit a Change Request, Requirement, or Comment for this OGC standard.

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” storage 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.  GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth.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” storage 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.  GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth.