Field data collection: design a form, send collectors out with their phones — offline included — and get clean GeoJSON back, or write approved records straight into an editable layer.
Open Hyz FieldHyz 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.
Design the form before activating: once records exist, field keys are locked — renaming one would silently change the meaning of data already collected.
| 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".
Collectors open the survey's collect page on a phone. It is built offline-first:
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).
At size, the review list is narrowed and paged by the server — by review status, by a word in an answer or a note, by source — 25 records at a time; the counts beside it (by status, by collector, in the layer) are the server's; and Approve selected or Reject selected reviews up to 200 records in one call, each answered on its own.
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.
Dashboard for this campaign, on the campaign page, makes a dashboard already reading it — records, approved, waiting for review, from other systems, per day, by collector and by review status — which you then arrange and share like any other.
Managers can also publish a polygon layer as collection zones (up to 500 features) to structure a campaign into assignments.
When the form asks for a photo, the campaign's page has a Photos section: every picture collected, newest first, as a gallery. Narrow it by question, by review state, by a word in an answer, by an answer's value, or by a number's or a date's range, and click a picture to see its record: the picture large, the answers, who collected it, when, where, and its state. The gallery says where the pictures are stored. Download all gives the pictures the filter leaves as one ZIP with a list of what is in it, five hundred at most at a time.
A task sends a collector to one existing feature of an editable layer — inspect this hydrant, visit this pump — and what they record there changes that feature when it is approved.
Records do not have to come from a phone. Another system — an export from a monitoring system, a ticketing tool, a script over a spreadsheet — can send them into a campaign with the campaign's own key.
POST …/surveys/<id>/ingest, with Authorization: Bearer hyzin_… and a body of up to 500 records:{ "records": [
{ "clientId": "row-1", "collectedAt": "2026-09-30T08:00:00Z",
"location": [46.6753, 24.7136],
"data": { "site": "Malqa", "towers": 3, "working": true } }
] }
A line or area campaign sends geometry (a GeoJSON LineString or Polygon) instead of location. The section shows a ready request and the table of keys with what each takes.
clientId again changes nothing, so a retry is safe) or refused, with the reason and the field — a key the form does not have, a number outside its range, a value that is not one of a choice's options, a missing required answer, a position outside the collection area.The records enter the same review as a collector's, marked Via , and the review list filters by source. On an auto-approving campaign with a target layer they go straight into the layer. The campaign must be active; photos cannot be sent this way yet. Up to 60 calls a minute per campaign, and your plan sets how many records a day (Plans and limits). An approval can also be told to your enterprise's own systems as the survey.record.approved webhook.
Hyz Field opens on the week at a glance, over every campaign you own or manage: records today and over the last seven days, records awaiting review, open tasks, overdue tasks, and how many collectors were active. Under the tiles, the tasks across campaigns — overdue first, each with its campaign, its assignee and its due date, opening straight on the collect page — narrowed to open, overdue or done, or to only mine; beside them, the week's records on a map. Each campaign's row below says how many records await review and how many tasks are open or overdue.
A collector who runs no campaign sees their own: their open and overdue tasks (theirs or unclaimed) and their records this week. A task's overdue notification opens the task itself.
