Fork me on GitHub
Visit the
                OGC
GeoPackage

An Open Format for Geospatial Information

GeoPackage is the modern alternative to formats like SDTS and Shapefile. Its SQLite-based format efficiently stores and transfers geographic vector features and image tiles.

GeoPackage is the modern alternative to formats like SDTS and Shapefile. At its core, GeoPackage is simply a SQLite database schema. If you know SQLite, you are close to knowing GeoPackage. Install Spatialite – the premiere spatial extention to SQLite – and you get all the performance of a spatial database along with the convenience of a file-based data set that can be emailed, shared on a USB drive or burned to a DVD.

GeoPackage was carefully designed this way to facilitate widespread adoption and use of a single simple file format by both commercial and open-source software applications — on enterprise production platforms as well as mobile hand-held devices. GeoPackage is a standard from the Open Geospatial Consortium. It was designed and prototyped following a multi-year, open process of requirements testing and public input. It is designed for extension. So if you need more than the core GeoPackage feature set, join OGC's open process to standardize community-tested enhancements.

View the Webinar given recently by Directions Magazine in collaboration with OGC!

Official Standards Information
For all official, normative information on the GeoPackage standard, including PDF format download, see the OGC standards program GeoPackage page.


 

Implementations

Luciad's libgpkg

  • libgpkg is a small C library that allows developers to easily read/write GeoPackage compliant SQLite files. The library only depends on SQLite. Luciad is pleased to announce they are making this base geopackage library available to the entire community as an open-source library. Our hope is that by releasing this library we can help in making geopackage a widely adopted format within the geo community.
  • libgpk developers discussion group

Luciad GeoPackage Viewer

  • To support the OGC OWS-9 and OWS-10 testbeds, Luciad has developed a viewer for Android that enables visualization of data following the OGC GeoPackage standard. The Luciad OGC GeoPackage Viewer is made available free of charge.

GDAL: the Swiss Army knife of open source geodata file formats

OpenJUMP PLUS reads GeoPackages

GeoTools

Esri ArcGIS

  • ArcGIS 10.2.2 for Desktop and Server support the 1.0 vector spec
  • Summer 2014: ArcGIS 10.3 for Desktop will add vector and tiled raster support, and ArcGIS Runtime 10.2.4 for Android and Java will also support GeoPackage!

SpatiaLite

GeoServer

  • GeoPackage Extension plugin brings in the ability to read and write GeoPackage files both as Vector Data Stores as well as Raster Data Stores. GeoPackage can be used as an output format for WFS GetFeature (creating one vector data layer) as well as WMS GetMap (creating one raster data layer). The GeoServer GeoPackage extension also allows to create a completely custom made GeoPackage with multiple layers, using the GeoPackage process.

 Sample Data

 

Land Information New Zealand LINZ Data Service (LDS)

  • "There are over half a billion features of New Zealand topography, hydrography, place name and cadastral data that can be downloaded in the GeoPackage format. Our testing has shown the format to be very good at handling large datasets."
  • press release

Technology Test Data Set

  • generated with GDAL (with -dev version to include spatial index support) thanks to Even Rouault
  • includes all geometry types supported by OGR (2d and 3d), all data types supported by OGR & GPKG, null properties, null geometries, a SRS different from the 3 required ones
  • also available is a Python script to generate this GeoPackage

Simple Sewers test data set

Haiti OpenStreetMap tiles and point features

Geonames data for Belgium

 

 
 
 

FAQ


Q How are GeoPackage files shared between apps on iOS and Android devices?

A OGC does not yet have a methodology or best practice for sharing files between apps on mobile devices. On Android there are a couple of different options. With some of the newer updates, Android has some interesting security constraints. There could be a nice solution using the ContentProvider API.

On the iPhone, the security issues of the device cause a lot of problems for cross-app file sharing. Inherently, the device does not want applications to share data except in very narrowly defined ways. So data sharing between apps is not feasible at this time.


Q What were the reasons to go with SQLite, when OGC has invested heavily in PostGIS?

A I wouldn't say OGC has invested in PostGIS. PostGIS implements OGC standards, but OGC as an organization hasn't put any time or effort into PostGIS. To us it's just like any other RDBMS implementation of the Simple Features spec. The primary use case for designing GeoPackage was mobile device use, and that's why SQLite was chosen as a platform. In this case OGC as an organization IS investing in a technology. This is unusual for us and we did not make the decision lightly, but practicality and ease of implementation won out over standards purity. And I'm happy to say we have yet to get any negative feedback on this decision -- probably because SQLite is considered more like a library than a standalone application.