THE FILE FIELD GUIDE

.gpkg

GeoPackage Geospatial Data

Maps & GPS

GPKG is the OGC GeoPackage container, based on SQLite and capable of holding multiple feature layers/tiles. One file need not mean one layer; inspect tables, CRS and attributes in compatible GIS.

Main use: Store spatial layers, attributes and tiles in SQLite
Data type: Binary data

All sections, questions and sources

Content reviewed：2026-10-19 · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

QGIS / GDAL / GeoPackage-compatible GIS

Preserve the original and inspect a working copy in a compatible application.

Select a copy as a data source in QGIS or compatible GIS.
Choose required layers from the contained layer list.
Inspect CRS, attributes and spatial extent.

Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

Inventory layer names, feature counts and geometry types.
Establish CRS and required fields.
Complete writes before copying rather than copying an actively edited database blindly.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

Only one layer visible: inspect the other tables.
Map misalignment: inspect declared CRS and actual coordinate values.
Not editable: inspect file permissions and concurrent locks.
Fields lost on export: inspect names, types and target-format limitations.

GPKG → GeoJSON / SHP / another GPKG

Select layers/fields and export separately with agreed CRS/field requirements.
Verify required layers/counts, attribute types, CRS and extent.

Exporting one layer does not transfer all other layers, styles and tiles.

Separate data from project configuration

GPKG stores data, while map appearance and external-layer configuration can belong to a GIS project. A GPKG alone need not reproduce the original map layout.

Source for these steps：OGC · GeoPackage / GDAL project · GeoPackage vector driver

Worked example: checks before handoff

Example: verify both boundary and facility layers/counts, providing a separate display project if the map layout is also required.

Source for these steps：OGC · GeoPackage / GDAL project · GeoPackage vector driver

Related-format differences

Related-format differences
Format / method	Purpose and preserved information
.gpkg	Store spatial layers, attributes and tiles in SQLite
SHP / QGZ	SHP uses a companion file set; QGZ mainly stores a map project.
GPKG → GeoJSON / SHP / another GPKG	Exporting one layer does not transfer all other layers, styles and tiles.

Handling and security

Review distribution conditions for locations and personal/facility attributes.

Questions and answers

Can I edit it like arbitrary SQLite?

Spatial metadata must remain consistent; normally use GeoPackage-aware tools.

Does it always replace every dependency?

It can consolidate datasets, but project/external dependencies still need inspection.

Can one GPKG hold multiple layers?

Yes; inspect layer inventory/counts rather than assuming one layer.

Format facts: name, steward and MIME type

Formal name: GeoPackage Geospatial Data
Steward / specification: OGC
MIME type: Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources

StandardGeoPackage
Standardized SQLite-based geospatial container.
OGC · Link checked：2026-10-16
Software documentationGeoPackage vector driver
GeoPackage tables, attributes and read/write support.
GDAL project · Link checked：2026-10-16