The GeoPackage is the database. This is its studio.

One OGC-standard SQLite file carries your utility data — pole inventories, feeder maps, inspection records — and VoltGrid gives it a full workbench: design tables and schemas, import five vector formats, edit features (with real Z elevations) through native ArcGIS Editor widgets, read ESRI mobile geodatabases alongside, and export clean GeoJSON or CSV. All offline, all on your disk — ready for air-gapped OT networks and storm ops alike.

GeoPackage ManagerSchema editor.gpkg .geojson .shp .fgb .parquet POINT Z / POLYGON ZEditor widget.geodatabase / .mmpk

Manage

Design it, fill it, ship it

The GeoPackage Manager treats a .gpkg as what it is — a portable spatial database you can author, not just a file you receive.

Design tables — create layers and edit schemas from the built-in schema editor.
Import broadly — pull in .gpkg, .geojson, .shp, .fgb, and .parquet.
Export cleanly — GeoJSON or CSV per table for downstream tools and reports.
Attribute workflows — the native Layers dock pairs each layer with an attribute table and Edit/Select mode toggles, so inspection and correction stay one click from the map.

/api/featureserver/edit3d

// GPKG served as an ESRI FeatureServer — Z-aware
GET  /api/featureserver/{ds}                → service metadata
GET  /api/featureserver/{ds}/{layer}        → schema (hasZ/hasM)
GET  /api/featureserver/{ds}/{layer}/query?returnZ=true
POST /api/featureserver/{ds}/{layer}/applyEdits
     { adds, updates, deletes, rollbackOnFailure }

// ESRI mobile geodatabase, read offline
GET  /api/geodatabase/packages/{gdb}/{table}/query?f=geojson

● round-trip  z 1500.5 → blob → 1500.5  · exact

In-App Screenshots

GeoPackage Studio & Data Engineering

VoltGrid desktop — GeoPackage Manager child window displaying open databases and feature tables — GeoPackage Manager child window with connected database layers, tables, and attribute inspection

VoltGrid desktop — GeoPackage Manager Data Engineering tab for schema design and spatial indexing — Data Engineering tab for schema design, field type modification, spatial indexing, and table properties

VoltGrid desktop — Saved magic_wand.gpkg layer inspected in GeoPackage Manager — Saved `magic_wand.gpkg` layer inspected in the manager showing live MULTIPOLYGON feature records

Edit — in three dimensions

Real Z editing over standard GPKG blobs

The embedded local server serves your GeoPackage as an ESRI-compatible FeatureServer with full Z + M ordinate round-tripping — so the native ArcGIS Editor widget edits 3D features directly in the SceneView.

🏔️

Z + M, preserved exactly

ESRI JSON ↔ NTS geometry ↔ standard OGC GPKG blobs with full Z and M ordinates. Verified round trip: a 3D point at z = 1500.5 survives the full pipeline bit-exact.

🧬

Schema-driven 3D

hasZ / hasM are read from gpkg_geometry_columns — not hardcoded — and honored via a returnZ query parameter, so 2D and 3D layers coexist in one file.

✏️

Native Editor widget

A Z-aware FeatureLayer with elevationInfo: absolute-height mounts the stock Editor widget for create/update/delete workflows — each vertex renders at its stored elevation above the ellipsoid.

📦

Ready out of the box

A Z-enabled edit3d.gpkg (POINT Z points, POLYGON Z polygons) is seeded on first run, so the Editor has working 3D layers before you import a thing.

🔁

Transactional applyEdits

Adds, updates, and deletes post as one batch with rollback-on-failure — plus offline edit queuing, change tracking, and conflict-resolution strategies for disconnected field work.

🧊

The 3D editing deep-dive

Vertical editing, extrusion, elevation snapping, and the full 3D pipeline get their own page — see the 3D GPKG Editor.

Interop

ESRI mobile geodatabases, read without ArcGIS

Field crews hand you .geodatabase files and Mobile Map Packages. VoltGrid reads them fully offline — no network, no infrastructure.

Official decoder, clean output — proprietary ST_Geometry blobs are converted through Esri's bundled stgeometry_sqlite.dll into RFC 7946 GeoJSON, ESRI FeatureSet, or spec-clean OGC WKB.
.mmpk aware — upload a Mobile Map Package and every embedded geodatabase is extracted and registered.
Reference in place — point at a large on-disk file by path; nothing is copied, and sources open strictly read-only.
Query like a service — where clauses, bbox filters, field selection, pagination, and on-the-fly reprojection to WGS84.
Self-testing — GET /api/geodatabase/selftest round-trips point, line, and polygon before you trust it with real data.

field data → map

# reference a survey geodatabase in place — no copy
curl -X POST /api/geodatabase/reference \
  -d '{ "path": "C:\\data\\MySurvey.geodatabase" }'

# query a feature class as GeoJSON, reprojected to 4326
GET /api/geodatabase/packages/mysurvey/Parcels
    /query?f=geojson&resultRecordCount=100

● read-only  source never mutated  · offline

Mobile geodatabase access is read-only by design; tile and raster content inside an .mmpk is handled by the Tile Package converter rather than this reader. FeatureServer editing applies to GeoPackage sources.