Skip to content

Getting Started

Pick the path that matches what you want to do. Each one assumes you already have the tool on the left-hand column installed; no Nix, no dev shell, no compilation.

Direct downloads (latest release)

Asset Stable URL
GeoPackage (everything) KartozaInfrastructureMapper-latest.gpkg
PostgreSQL schema (everything) pg-schema-latest.sql
PG migrations pg-migrations-latest.tar.gz
GPKG migrations gpkg-migrations-latest.tar.gz
Per-domain slices Pattern: pg-schema-NN-name-latest.sql and KartozaInfrastructureMapper-NN-name-latest.gpkg — full list on the Releases page

  • Open the GeoPackage in QGIS

    Download a single .gpkg file from the latest release. Drag it onto a QGIS canvas. Every capture domain registers automatically. Best for desktop GIS and one-machine workflows.

    GeoPackage in QGIS

  • Load the schema into Postgres

    Download the released SQL bundle and apply it to your own PostgreSQL + PostGIS database. Then connect from QGIS, web maps, or anything that speaks Postgres.

    Load into Postgres

  • Take it to the field

    The GeoPackage is field-portable in QField and Mergin Maps. UUIDs and last_update timestamps make a clean sync path back to the source Postgres after a capture trip.

    Field workflow

I want to…

Goal Path
Look at the data in QGIS on my laptop GeoPackage in QGIS
Run a server my team and tools can query Load into Postgres
Wire QGIS to that server Connect QGIS to Postgres
Take data into the field on my phone or tablet Field workflow
Browse what the schema actually captures Data Model
Work on the schema itself (not just use it) Developer Guide

Schema versions

The current schema version is on the GitHub Releases page. Every released GeoPackage and SQL tarball is tagged with a vX.Y.Z semver and carries its own current_schema_version view so consumers can read which migrations are baked in. See Schema Lifecycle for what bumps a major / minor / patch.

Need help?