Kuleana · commons reports · Toolkit Document 4 · baseline use case · ArcGIS Survey123

Direct entry for geospatial field reporting — a prototypical method

A steward at a place reports what they see, and the record lands where the map reads it. This page is a prototype of that method for geospatial data: a plain web page, with no Survey123 license, account, or app, carrying the registry's own field names, domains, and validation, writing to a hosted feature layer through the ArcGIS REST API — so the layer the map reads is the standard field dataset, and every record passes the same intake pipeline and the same human-held publication gate. The same method — survey to hosted feature layer to map, a printed marker code as the join key, a steward gate between the private layer and the public view — is currently being applied at the Magoon Maker Lab (Hui Koʻe ʻĀina, UH Mānoa): the site-asset survey, the hosted layer in Mokunet Org, and the site map that reads from it.

Status note, 2026-10-12: this page is the Green Fee shape of the method — the form a Green Fee project lead would use — shown against the fictional FY2026 fixture so that no entry can touch a real record. The Green Fee report itself lists the real FY2027 projects. At the Magoon Maker Lab the method is in use at its honest stage: the site-asset survey is built and the site map renders a dated snapshot; the hosted layer's public view is the next step, and the map says so.
Demonstration only: every project in this form is a fictional sample — no real award, awardee, or organization is represented, and no government adoption, endorsement, partnership, or deployment is claimed. Entries go nowhere: the page validates them and shows the REST calls it would make.
Demonstration mode No feature service is configured, so submitting shows the exact REST calls this page would make. Set CONFIG.featureServiceUrl to the hosted feature layer and the same entry submits live. In deployment this page sits behind maintainer sign-in and opens already bound to the maintainer's project (try ?project=GF-2026-HI-001); the public demonstration stays public, with fictional data only.
Who is reporting

Name and email are required on every submission for accountability and follow-up. They are never published.

Project

e.g. 2027-Q1, FY2027 to date, Summer 2027

About the project (first report, or when it changes)

What the project does, in plain language. Required before the project can publish; at least 20 characters if provided.

The Department approves the final alignment; this is the project lead's view.

Where the work is

Division-zone-section-plat-parcel, e.g. 1-3-6-012-001; separate several with ;

Required if there is no parcel (reef, stream reach, trail corridor…)

Reported outcomes

One entry per measure, from the approved indicator dictionary. Photo evidence is attached by the review team in this demonstration (the layer's addAttachment endpoint carries it in the production form).

What the project intends next (optional, public when approved)

In your own words, shown on the project's timeline as a dated intention marker. Revising an intention later is normal — the form will ask what changed, and a change explained is never a mark against the project. (Proposed schema v1.1 fields, demonstrating the framework's intention timeline.)

e.g. by June 2027, next dry season

Story and community context (optional, public when approved)

At least 50 characters if provided.

Attribute if you can (name/role) and only with their consent.

Funding status (optional — the Department provides official figures)

What this page would send

Two REST calls against the hosted feature layer — the report, then one outcome row per measure joined by parentglobalid: