Map Edit Mode and Inline Editing

Primary page: /parcels/map/?mode=edit

Access

  • Dataset Editors can open map edit mode.
  • Viewer access does not gain parcel drawing or snapping authority.

Edit-Mode Capabilities

  • Draw/create parcel polygons on map
  • Submit create form embedded under map
  • Open side panel editing for existing parcels
  • Inline attribute/geometry updates via API
  • Set effective_at timestamp for inline edits

Inline Update API

Endpoint: POST /parcels/api/inline-update/<uuid:pk>/

Editable payload fields include:

  • name, parcel_type, status, priority
  • address, description, is_public
  • geometry_wkt
  • effective_at (optional datetime; defaults to now)

Validation behavior:

  • unsupported fields rejected
  • choice values normalized and validated
  • polygon WKT parsed and validated

Versioning behavior:

  • inline save does not overwrite in place
  • current row is superseded (valid_to = effective_at)
  • new row is created as active version

Boundary Snapping Operations

The main map's Map Settings is the only place users edit snapping preferences. Settings are personal, not dataset-wide, and staff status does not bypass dataset Editor checks. Parcel create and update pages consume the same settings as read-only runtime configuration.

Supported polygon editors are /parcels/map/?mode=edit, /parcels/create/ (including reopened drafts), and /parcels/<uuid>/update/.

Point and edge candidates are previewed from the current authorized viewport payload. The server resolves the referenced current parcel version and uses PostGIS in the parcel storage CRS to confirm an exact vertex, edge point, or exterior-ring path. Target geometry is never updated by snapping.

Saved drafts retain versioned snap provenance. Draft update, submit, review, and final approval replay it under deterministic target-row locks. Stale, retired, inaccessible, cross-dataset, or source-self targets are rejected without disclosing inaccessible parcel details. A geometry update submitted without snap context clears older provenance.

For stale-target reports, confirm whether the adjacent parcel received a newer official version, then ask the Editor to reload and place the snap again. Do not edit draft JSON to replace target identifiers.