Hyz Field

What it is¶

Hyz Field turns a form and a set of phones into a data-collection campaign. You design the form, invite collectors, and every record they capture comes back as a GPS point with its answers — reviewable, exportable as GeoJSON, ready to drop onto a map, or written straight into an editable layer when a record is approved.

Your surveys live at /field. Each survey has a management page and a separate, mobile-first collect page for the people in the field.

Setting up a survey¶

1. Create it at /field with a bilingual title.
2. Build the form. Five field types — text, number, select, yes/no, date — each with an Arabic and English label, a required flag, and per-type options (choice chips for selects; min/max/step and an optional slider for numbers). A live preview shows exactly what collectors will see. Up to 60 fields.
3. Add collector instructions and, optionally, a collection area: upload a polygon and collectors are warned when they capture outside it.
4. Point it at a layer (optional). In Feed a layer, pick an editable point layer; approved records then become its features. See Feeding a layer from Hyz Field.
5. Invite people by username or email (up to 200 members).
6. Set the survey Active. A survey that is not active refuses new records.

Design the form before activating: once records exist, field keys are locked — renaming one would silently change the meaning of data already collected.

Roles¶

Role	Can
collector	Read the form, submit records, see their own records
manager	Edit the form and status, invite members, review every record, export
owner	Everything, including deleting the survey

A survey you have no role on answers "not found".

Collecting in the field¶

Collectors open the survey's collect page on a phone. It is built offline-first:

• The form definition is cached on the device — open the page once while online and it keeps working without coverage.
• Records queue locally before any network attempt, with live GPS (including a continuous "track" mode), accuracy in meters, and an inside/outside warning against the collection area.
• Syncing is an idempotent batch: each record carries a device-generated id, so retrying a sync can never create duplicates. Up to 500 records per batch.

Reviewing and exporting¶

Managers see every submission on the survey page; collectors see only their own. Each record can be reviewed — pending, approved, rejected, or flagged — with a note, and managers can correct answers (the collector's original data is preserved the first time a record is corrected).

Export is one click: GeoJSON with every record as a point feature carrying its answers, GPS accuracy, and capture time — ready for the Workspace or any GIS.

A campaign can also feed a layer: with an editable point layer set as its target, approving a record creates a feature in that layer, with the collector recorded as its creator and the layer's rules applied. A refusal is kept on the record and never blocks the review. See Feeding a layer from Hyz Field.

Managers can also publish a polygon layer as collection zones (up to 500 features) to structure a campaign into assignments.

Good to know¶

• A campaign can belong to a project. Filing it into a project keeps it with the maps and dashboards of the same work, and its page then says which projects hold it. A campaign is reference-only there: it cannot be shared through a project, because its least-privileged role can submit records and sharing must never turn a read into a write.
• Hyz Field is included in plans from Basic upward — see pricing.
• Deleting a survey permanently deletes every collected record. Features already written into a target layer stay in the layer.
• Structural limits: 60 form fields, 200 members, 500 records per sync batch.