Feeding a layer from Hyz Field — approved records become features

What the bridge does¶

A Hyz Field campaign collects records on phones: a GPS point and the answers to a form. Normally those records stay with the campaign, reviewable and exportable as GeoJSON. With a target layer set, an approved record also becomes a feature of an editable hosted layer, created through the same checks every other edit passes, with the collector recorded as its creator.

The bridge is one-way and explicit: nothing reaches the layer until a reviewer approves the record, and the record keeps a note of what happened (applied with the feature's identity, or the reason it was refused).

What the target layer must be¶

Requirement	Why
a Hyz Layer in the ready state, with editing switched on	only editable layers accept edits
a point layer	a record is one GPS point; lines and polygons cannot be collected on the form
the person setting the target holds the create permission on the layer	the target is a promise to write there
every mapped field exists on the layer	answers land in real columns

A campaign page offers as targets only items that are editable; the server checks the rest when you save, and its message shows in place: the layer is not a point layer, editing is switched off for this layer, you do not have permission.

Setting it up¶

1. Open the layer's item and switch editing on for the point layer; consider the rules New features start unlocked off and operations create only if the layer is an inbox that a manager reviews.
2. Open the campaign at /field as its owner or a manager. In the Feed a layer row, pick the layer. No editable layer yet means none of your items has editing on for a point layer.
3. Match the campaign's form keys to the layer's fields. An answer lands in the field with the same name; answers without a matching field are dropped. When the names differ, a field map on the campaign's target (set through the API) renames them.
4. Collect as usual. Records queue offline on the phone and sync to the campaign when online.

Approving a record¶

Review sets a record to approved, rejected or flagged, with an optional note and corrected answers. Review is a campaign action, taken through the campaign's review endpoint by an owner or a manager; Hyz Desktop's Field pane shows every record with its review state and imports campaigns with that state on each feature.

On approved, the platform creates the feature:

• the record's location becomes the point; its answers, mapped to the layer's fields, become the attributes;
• the feature's creator is the collector, not the reviewer, so a rule Editors change only their own features later treats it as the collector's;
• the reviewer's permission to create records on the layer is checked at that moment;
• the layer's rules apply: the point must fall inside the editing area if there is one, required fields must be filled, values must fit their fields;
• the record remembers the feature's identity; approving the same record twice never creates a second feature.

If the layer refuses, the review still succeeds and the record keeps the reason (for example outside the editing area or a required field is empty). Fix the cause, or correct the record's answers, and approve again.

Rejecting or flagging a record writes nothing to the layer. Approving a record that was already bridged updates the existing feature's attributes rather than creating another.

What the collector sees¶

Nothing changes for collectors. They need no permission on the layer: the bridge writes with the reviewer's permission and records the collector as creator. If collectors should also correct their own features afterwards, give them the editor role on the item and switch on Editors change only their own features.

A review queue built from three settings¶

Setting	Where	Effect
operations: create only	the layer's rules	nobody edits existing features on the layer directly
New features start unlocked off	the layer's rules	every bridged feature is born locked
a manager unlocks by filter	the layer's Locks tab	approved and checked features are released together

The result is a layer that only ever grows from the field, in which nothing is live until a manager has looked at it, with the full trail (collector, reviewer, unlock) in the layer's history.

Good to know¶

• The campaign's export is unchanged. GeoJSON export still gives every record, whatever the target does.
• Deleting the campaign does not delete the features it wrote into the layer; deleting a feature does not touch the record.
• A target you can no longer see stays shown by its identifier on the campaign page rather than being dropped silently.
• Edits per month. Every bridged feature is one applied edit against the layer owner's allowance.