Honua

Capability journeys — choose an outcome, then inspect the evidence

Honua JavaScript SDK

What are you trying to accomplish?

Connect existing services, build a decision workflow, analyze large spatial data, operate on a live feed, move into imagery and 3D, migrate ArcGIS code, or automate safely. The gallery now leads with those outcomes—not a checklist of SDK features.

SDK provenanceThese samples track trunk development @ 2ff3aff4aa37. Latest published package: @honua/sdk-js 0.1.0-beta.0.

Loading evidence Reading the current SDK artifact and sample state…

Filter by goal

Flagship journeys

A small set of beginning-to-outcome paths. Supported previews are runnable today; experimental paths say exactly what is not yet productized.

Loading…

Loading capability journeys…

Read the state before the claim

Data mode and fallback are separate. A page can begin on a live service and later report a fixture replay or a degraded capability; it should never silently turn one into the other.

Live is observed

Public and demo-live lanes identify the source at runtime. Reachability is not inferred from a static badge.

Fixture is deterministic

Fixtures keep a workflow usable and testable, but are labeled replayed or synthetic rather than current.

Degradation is structured

Missing data, auth, or server capability reduces only the affected lane and leaves visible recovery guidance.

Focused recipes

Use these when you already know the concept you need. Recipes support a journey; they no longer compete with flagship applications.

Loading…

Loading recipes…

Every old sample received a disposition

The machine-readable audit covers all 21 site samples and 27 SDK examples with a keep, rework, merge, replace, or retire decision, rationale, target journey, and owner.

Open audit JSON