gpkg
What is a .gpkg file?
application/geopackage+sqlite3
GeoPackage is an OGC standard that stores vector features, raster tiles, and their metadata inside a single SQLite database. Required tables such as gpkg_contents, gpkg_spatial_ref_sys, and gpkg_geometry_columns describe what the file holds, and feature geometries are stored in a standard binary header followed by Well-Known Binary. Being one self-contained file with real SQL indexing, it is the modern replacement for the multi-file shapefile.
How to use a .gpkg file
Use an example .gpkg file to test GIS readers, SQLite-based spatial tooling, and shapefile-to-GeoPackage converters, checking the required metadata tables, the geometry header's SRS id and envelope flags, and attribute round-tripping.
Download example .gpkg files
- GeoPackage: Three Feature Layers in One SQLite ContainerThe territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.
- GeoPackage: Aspatial Attributes Table (no geometry column)A GeoPackage holding an `attributes` table with no geometry at all: the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.
- GeoPackage: Features Stored in Web Mercator (EPSG:3857)The same five towns stored as projected metres rather than degrees, with EPSG:3857 registered in gpkg_spatial_ref_sys and stamped into every geometry blob's header. Unlike GeoJSON, GeoPackage genuinely supports this, so it is the clean way to test that your reader honours the declared SRS instead of assuming 4326.