These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Precision Agriculture Platform
- Features
- Fields and boundaries
Fields and boundaries
Keep field identity, surveyed geometry and measured area together.
OverviewSurveyed field boundaries×
Precision Agriculture Platform · Fields and boundaries
New
Surveyed field boundaries
Field boundaries
| Id | Field | Survey date | Area hectares | Geo JSON | |
|---|---|---|---|---|---|
| IDD-618 | FLD-2896 | 03 Oct | 560 | GJ-640 | |
| IDD-818 | FLD-2482 | 11 Oct | 70 | GJ-495 | |
| IDD-119 | FLD-7240 | 13 Oct | 480 | GJ-519 | |
| IDD-588 | FLD-6516 | 15 Oct | 120 | GJ-772 | |
| IDD-968 | FLD-5267 | 12 Oct | 120 | GJ-847 |
6 of 6 records
IDD-618Field boundaries · FB-92184
FieldFLD-2896
Survey date03 Oct
Area hectares560
Geo JSONGJ-640
What you can do
Start with an identifiable field
Each plot has a field name, code, location, area and availability status. The Farm Manager uses that record as the anchor for a crop cycle, observation, task and input application. A field marked Restricted deserves a review before anyone plans new work there. A field marked Available is a candidate for the next cycle, while Planted and Fallow distinguish different operating states.
Surveyed boundaries belong to a field rather than to a crop cycle. The Field Surveyor records the survey date, measured area and geo JSON geometry. That means a later crop change does not erase the surveyed footprint. The boundary page lets the team filter by field and survey date, inspect the geometry and measured area, and open the underlying boundary record.
How the work is organized
- Field identity. Keep one name and field code for each plot so operators select the right place for a task.
- Survey history. Associate each boundary capture with its field and survey date; review the area when a newer survey arrives.
- Operating status. Use Available, Planted, Fallow and Restricted to make the next planning decision visible.
What to agree during setup
Agree how field codes are assigned, who can change a field’s status, and which survey source supplies geometry. Check the area unit used in field and boundary records before bringing in old data. A field may have more than one surveyed boundary record over time. Decide which dated survey the team uses for a current planning decision, while preserving earlier entries for comparison.
For a newly leased plot, the manager first creates the field with a recognizable name and location. The surveyor then captures its outline and measured area. The manager can inspect the boundary page before assigning the first crop cycle. The field remains the common reference even if the crop, operator or input plan changes later.
Check the handoff on an actual case
Take a field marked Available and capture a dated boundary. Confirm that its geometry and area appear under the correct field on the Field Boundaries page. Open the exact source record from that page. Then create a crop cycle for the same field and verify that the manager can trace from the cycle back to the field. Repeat with a second survey date to ensure the older record remains identifiable.
If the survey points to another plot, correct the link before using its area for planning. The manager should also check whether a Restricted field appears in planning discussions; the status is a decision cue, not a replacement for the manager’s review.
What your team sees
- Surveyed field boundaries — Review captured geometry, survey date and area for each mapped field.
- Fields ready for planting — Find plots marked Available before assigning a new cycle.
- Field status board — Compare available, planted, fallow and restricted plots without mixing in dated work.
Follow the work through
See field planning and field work.
What it keeps track of
Data model- Fields
- Farm fields and plots with area, location and availability status
- Field boundaries
- Surveyed field boundary geometry with survey date and area
- Crop cycles
- Crop cycles per field from planned planting through growing, harvesting and close
Who uses it
Permissions- Field Surveyor
- , Farm Manager and Admin maintain the field and its survey history.
- Field Operator
- Reads the field identity while carrying out assigned work.
Set up Precision Agriculture Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.