Walkthrough

Interactive sketch editing with terra-draw

terra-draw draw modes drive the edit-sketch workflow: undo/redo, snapping, and applyEdits submission.

Task walkthrough

Complete the workflow.

Initialize the map's sketch and editing controls against the configured feature source.
Create or modify a geometry using the sample's editing interaction.
Inspect the resulting feature state and the visual evidence emitted by the sample.

Expected outcomeA visible geometry edit completed through the SDK interaction and reflected in application state.

CODE FIRSTFinding the primary source file…Expand source

Loading source from honua-sdk-js…

This preview and the runnable browser bundle are bound to the same immutable producer commit.

Producer provenance and lifecycle

Projected from honua-sdk-js's versioned site-consumer handoff. Code is not vendored here. This gallery-only evidence is not counted in this repository's samples coverage.

Capabilities

FeatureServer Editing (editing.featureserver-edits)

Support tier: experimental Track: recipe Protocols: geoservices-feature-service, geoservices-geometry-service, geoservices-gp-service, geoservices-image-service, geoservices-map-service Renderers: maplibre Lifecycle: active — Retain as the focused terra-draw drawing, snapping, undo, and edit-submission recipe; the planning journey owns the end-to-end planning workflow. Qualification: experimental

Provenance & evidence

Runnable bytes and inline source are bound to producer commit 8f9d6a4fcde9aa78582fb12395ea5b9ef6d9f964.
Fixture lane: fixture / executed. Committed deterministic harbor-parcel fixture.
Live lane: public-live / planned.
Expected degradation: Sketch tools report unsupported capabilities when terra-draw is not installed; the SDK works without the optional peer.

View source on GitHub ↗ · Docs ↗