CLI GuideChannel: geopackage → postgis sql

GeoPackage to PostGIS SQL Converter

Import GeoPackage layers into PostGIS server setups.

Migrate spatial layers from localized projects back to central database systems. This guide shows how to import GeoPackage tables into active Postgres databases, complete with spatial attributes.

Indirect Mapping Execution Required

Because database connection attributes or local attributes parsing is required, direct web streams are disabled. Use the GDAL CLI script below for precise terminal conversions.

Specification Rules

Consolidate field survey results from GeoPackage files into central databases
Publish regional map layers on high-concurrency database web apps
Integrate local mapping data with cloud databases
Requires active destination database connections and credentials
Subject to database constraint restrictions during data imports
Target databases tables must support incoming geometric shapes

GDAL Direct Equivalent Terminal Command

sh — gdalready

$ogr2ogr -f PostgreSQL PG:"dbname=postgis_db user=postgres" input.gpkg

When to use this conversion

Use when a GeoPackage-based dataset needs to be imported into a server-side PostGIS database for multi-user editing, web GIS publication, or large-scale spatial analysis. This is the inverse of postgis-to-geopackage and uses the same tools in reverse.

Technical Details

ogr2ogr reads each GeoPackage layer and writes it to PostgreSQL as a new table with a geometry column. CRS is preserved via geometry_columns metadata. Spatial indexes (GiST) are created automatically. Schema names can be controlled with -lco SCHEMA, and existing tables can be appended to with -append or replaced with -overwrite.

Output file size

PostgreSQL database growth is typically 100–150% of the GeoPackage size. PostgreSQL has slightly higher per-row overhead than SQLite but the GiST index is smaller than GeoPackage's R*Tree.

Common Errors & Fixes

Table already exists error: target table has data. Fix: -overwrite to replace, -append to add rows.
Schema permission denied: user lacks CREATE privilege. Fix: grant the user permissions or use -lco SCHEMA to target an allowed schema.
Column name collision: GeoPackage has "user" as a column name, conflicting with PostgreSQL reserved word. Fix: rename with -sql "SELECT ... AS new_name".
No spatial index created: legacy PostGIS or wrong driver options. Fix: -lco SPATIAL_INDEX=GIST and run VACUUM ANALYZE after import.

Alternative Tools

QGIS: drag the .gpkg into a PostGIS connection in the Browser panel
ogr2ogr CLI: ogr2ogr -f PostgreSQL PG:"dbname=mydb user=admin" input.gpkg
FME for complex schema mapping during import
pg_restore plus pgsql2shp for legacy workflows (slower and less feature-complete)

Frequently Asked Questions

How do I deal with column name conflicts?

Use mapping tools or command flags to rename conflicting database fields and match existing tables.

Are spatial coordinate indexes built automatically?

Yes, our processing scripts build GIST spatial indexes automatically during the import.

Which database geometries are supported?

All standard models (point, multi-point, line, polygon) are fully supported during the migration.

Related Transformations Map

Postgis To Geopackage Geojson To Postgis Geopackage To Geojson