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.
- Greenhouse Management
- Features
- Greenhouse zones
Greenhouse zones
Keep surveyed growing-area boundaries linked to the field they describe.
OverviewSurveyed greenhouse zones×
Greenhouse Management · Greenhouse zones
New
Surveyed greenhouse zones
Greenhouse zones
| Id | Field | Geo JSON | Survey date | Area hectares | |
|---|---|---|---|---|---|
| IDD-497 | FLD-3790 | GJ-258 | 05 Oct | 280 | |
| IDD-240 | FLD-5708 | GJ-711 | 05 Oct | 460 | |
| IDD-639 | FLD-5062 | GJ-322 | 09 Oct | 40 | |
| IDD-166 | FLD-8322 | GJ-621 | 12 Oct | 350 | |
| IDD-551 | FLD-4674 | GJ-238 | 15 Oct | 380 |
6 of 6 records
IDD-497Greenhouse zones · GZ-62905
FieldFLD-3790
Geo JSONGJ-258
Survey date05 Oct
Area hectares280
What you can do
Give mapped areas a field anchor
A greenhouse zone record contains boundary geometry, survey date, area and a link to a field. The field anchor lets a manager compare a mapped area with the crop cycles and field work recorded against that place. The zone is a surveyed boundary record; it is useful when people need a shared spatial reference for work or review.
Start with the field identity the team already uses. A surveyor should confirm the selected field before recording the shape. A copied boundary attached to the wrong field can send the team to the wrong growing area even when the geometry itself looks plausible.
How the work is organized
- Identify. Choose the field that owns the surveyed area.
- Capture. Record the boundary geometry, survey date and measured area.
- Review. Compare the zone’s field and area with the physical location before relying on it.
The zone record stores boundary geometry. Survey dates and area measurements belong with the shape, so a later revision can be understood in context. The manager can review surveyed zones alongside the field record’s area and location, while keeping the two area measurements distinct.
What to agree during setup
Agree how a physical greenhouse, bed or growing area maps to field records before surveying zones. The current field record supplies a name, code, location, area and availability status. Choose a consistent granularity so a zone does not refer to an entire site one day and a small plot the next. Decide who checks geometry and area before it becomes the team’s reference.
For imports or capture requests, establish a source identity and repeat-safe operation key in the integration design. Check the linked field, actor identity, geometry, survey date, area, unit and request identity before accepting data from an external capture source.
Check the handoff on an actual case
A field surveyor prepares a new mapped area for a named field. They verify the field code and location, collect the boundary geometry and survey date, and record the measured area. The greenhouse manager compares that area with the field’s broader area and confirms the zone is attached to the intended field. The next crop cycle uses the field link; growers can review the zone when coordinating work in that growing area.
Repeat with a boundary whose field reference is wrong. The surveyor corrects the field selection before the record is used. A second capture of the same source operation should be treated as the same operation during integration setup, so retries do not create extra zones.
What your team sees
- Surveyed greenhouse zones — Review mapped shapes, dates, areas and their fields.
- Available fields — Check field names, codes and location before a new survey.
- Active crop cycles — See current planting work associated with the linked fields.
Follow the work through
Review zone capture and the data model before importing existing maps.
What it keeps track of
Data model- Greenhouse zones
- Surveyed field boundary geometry with survey date and area
- Fields
- Farm fields and plots with area, location and availability status
- Crop cycles
- Crop cycles per field from planned planting through growing, harvesting and close
Who uses it
Permissions- Field Surveyor
- Records the geometry, Greenhouse Manager reviews the field relationship and Admin maintains access.
Set up Greenhouse Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.