Move assets between eLandfill and a GIS as a GeoPackage (.gpkg) file: export the site's
assets to work on them in QGIS, or import a prepared dataset into the asset register.
Not to be confused with the Import module, which brings in drone
orthophoto rasters. This page is about the site's assets — points, lines and polygons
in the asset register.
Open the Assets module and choose Import / Export. Both directions live on one page:
pick the direction at the top. Importing requires the Asset management and Import data
permissions; exporting requires Asset management and Export data.
Everything happens on the site currently selected in the site switcher — check it before you
start, because an import writes into that site.
A GeoPackage holds up to three tables, one per geometry type:
| Table | Holds |
|---|---|
assets_points |
Point assets — wells, sampling points, poles |
assets_line |
Line assets — pipes, roads, fences |
assets_polygons |
Polygon assets — cells, phases, areas |
Each feature carries the asset's attributes as columns, including the name of its
interface — the asset type. An exported file has exactly the shape an import expects, so a
round trip (export → edit in QGIS → import) works without reshaping anything.
Import files are limited to 100 MB.
.gpkg when it is ready.Exporting never changes anything on the site; it is always safe to run.
Importing is deliberately a two-step operation, so nothing is written before you have seen
what would happen.
Drop a .gpkg on the page (or click to browse). The file is uploaded and inspected, and you
get back a preview before anything is written:
If the preview looks right, run the import. Progress is shown feature by feature, and the
result reports three numbers: how many assets were imported, how many were skipped,
and how many raised an error (with the details, per feature).
Each feature is matched to one of the site's asset interfaces by the interface name in the
file. Features whose interface does not exist on this site are skipped, never guessed —
this is the single most common reason for a smaller import than expected, and it is why the
unknown interfaces are listed before you commit.
If every layer in a file maps to an unknown interface, the import is blocked outright:
nothing would be written.
To fix unknown interfaces, either rename them in the source data to match the site's
interfaces, or create the missing interface on the site first (see
Asset management).