Edit parcel drafts outside LMSTool

This feature lets you take existing parcel drafts into a desktop GIS, edit their geometry, and import the geometry back into the same drafts. It does not create drafts, change workflow states, or update confirmed parcels.

Use ordinary parcel download and import for confirmed parcel datasets. Draft editing packages are a separate, controlled GeoPackage format.

Export drafts for editing

  1. Open the parcel workflow task list and select the drafts you want to edit.
  2. Optionally select confirmed parcels on the map as surrounding context.
  3. Choose Export drafts for editing.
  4. Save the .gpkg file.

The drafts_to_edit layer contains the editable draft geometry. The selected_confirmed_context layer is a visual reference only. Do not copy new features into the editable layer or change its identifier, revision, or dataset fields.

Editing export and import require an exact Editor grant. Reviewer or Approver access alone is not editing authority. Their workflow task page shows inspection export only; editing export and the import form are omitted. Direct access to the import URL is also denied before any uploaded file is inspected. An export is refused when no selected draft is currently editable. Records that you cannot access are excluded without exposing their parcel details.

Edit in QGIS

  1. Open the GeoPackage in QGIS.
  2. Edit polygon geometry only in drafts_to_edit.
  3. Use selected_confirmed_context to see surrounding confirmed boundaries.
  4. Save edits back to the same GeoPackage. Keep the layer names, CRS, fields, identifiers, and revision values unchanged.

Version 1 accepts Polygon geometry in a projected CRS with known linear units. LMSTool transforms it to the authoritative parcel storage CRS before validation.

Import edited drafts

  1. Open Import edited drafts from the workflow task list.
  2. Upload the edited .gpkg file.
  3. Submit it once and review the result.

LMSTool checks the current user, active dataset, draft state, revision, geometry, and current neighbouring parcels. The importer may be a different editor from the person who exported the package, but they must currently be allowed to edit every included draft.

The import is atomic. If one draft fails, none of the drafts in that package is changed. A successful import changes geometry only, leaves each draft in DRAFT, and records an offline_import audit event.

If a draft changed after export, the package is stale. Export a fresh package, repeat the edit, and import the new package. Reimporting the same successful package is rejected because the successful import advances each draft revision.

Export for inspection

Dataset readers can use Export drafts for inspection when their current read role permits viewing the selected drafts. The drafts_for_inspection layer has no editable revision contract. An inspection package cannot be imported as an editing package.

File and safety limits

  • Draft exchange import accepts .gpkg only, up to 50 MiB.
  • One package may contain at most 100 drafts and 1,000 selected context parcels.
  • Shapefile, GeoJSON, KML, ordinary parcel GeoPackages, inspection packages, and corrupt or unsupported packages are rejected.
  • Exported context is never authoritative. Validation always uses current server data.