Edit parcel drafts outside LandWeave¶
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¶
- Open the parcel workflow task list and select the drafts you want to edit.
- Optionally select confirmed parcels on the map as surrounding context.
- Choose Export drafts for editing.
- Save the
.gpkgfile.
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¶
- Open the GeoPackage in QGIS.
- Edit polygon geometry only in
drafts_to_edit. - Use
selected_confirmed_contextto see surrounding confirmed boundaries. - 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. LandWeave transforms it to the authoritative parcel storage CRS before validation.
Import edited drafts¶
- Open Import edited drafts from the workflow task list.
- Upload the edited
.gpkgfile. - Submit it once and review the result.
LandWeave 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.
Select and export for checking¶
Select ordinary drafts on the workflow task list, including manual drafts and drafts from different uploads. Selection persists across pages, sorting and Show all matching drafts. Changing the dataset or filters clears it with a notice. The optional Upload ID filter narrows the list to one accessible upload. Topology proposals retain their individual links and cannot be selected.
Select all selects eligible ordinary drafts across all matching pages for the chosen purpose. Deselect all clears the whole selection. Show all loads rows progressively without selecting them; an interrupted load is labelled incomplete. Return to paginated view preserves the selection.
An exact Editor, Reviewer or Approver grant permits Export for checking.
This downloads only selected, accessible proposals, with no surrounding confirmed
parcels. The drafts_for_inspection layer contains every retained business
attribute and the proposed geometry in the installation's storage CRS. It also
records draft/dataset/parcel identities, state, revision, export time and available
source/approved version identities. Values come from the proposal, without filling
missing values from an approved parcel.
Text remains Unicode; null and empty text remain distinct. Tags are ordered JSON
array text ([] differs from null), decimal values are exact text, dates use ISO
text, and booleans are integers 0/1. inspection_metadata documents the encodings;
lmstool_manifest records the storage SRID and snapshot identity/time.
The download feedback reports included/excluded totals and reason counts.
inspection_exclusions lists requested IDs and safe reasons for inaccessible,
missing or invalid polygon proposals. No file is returned if none are inspectable.
Export does not acknowledge examination or change workflow state. The snapshot
cannot be imported as an editing package.
The default inspection limits are 2,000 selected drafts, 20 MiB of serialized input and 50 MiB for the completed file. Requests exceeding a limit are refused with a narrower-selection instruction, without truncation. Inspection has separate settings from editing, whose 100-draft limit is unchanged. The inspection bound was measured with complete attributes, five-vertex polygons and a quarter of polygons containing 257 vertices. Denser polygons or longer attributes may reach the byte guards first. These are resource bounds, not a promised download time.
File and safety limits¶
- Draft exchange import accepts
.gpkgonly, up to 50 MiB. - One editing 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.