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
- Data model
The tables behind Precision Agriculture Platform
Precision Agriculture Platform ships with 11 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 11
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Land and crop
Fields anchors surveyed boundaries, observations and crop cycles.
Execution
Field operations links the field, cycle and team members owner.
Inputs
Input stocks holds lots; input usage links a lot to a task; input applications records field application and applicator.
Output
Harvests links measured quantity, unit and grade to the crop cycle and reviewer.
Every table, by feature
- Fields
Farm fields and plots with area, location and availability status
- Field boundaries
Surveyed field boundary geometry with survey date and area
Linked to Fields - Crop cycles
Crop cycles per field from planned planting through growing, harvesting and close
Linked to Fields
- Crop cycles
Crop cycles per field from planned planting through growing, harvesting and close
Linked to Fields - Fields
Farm fields and plots with area, location and availability status
- Field operations
Planned and executed field work assigned to a person for a specific cycle
Linked to Fields, Crop cycles, Team members - Harvests
Harvested quantities with unit and grade, accepted by a reviewer
Linked to Crop cycles, Team members
- Field observations
Field scouting observations with measured value, unit and notes
Linked to Fields - 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
Linked to Fields - Field operations
Planned and executed field work assigned to a person for a specific cycle
Linked to Fields, Crop cycles, Team members
- Field operations
Planned and executed field work assigned to a person for a specific cycle
Linked to Fields, Crop cycles, Team members - 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
Linked to Fields - Team members
Farm staff, operators, reviewers and managers with their authenticated user account and role title
Linked to Users - Input usage
Input quantities consumed against a field task
Linked to Input stocks, Field operations
- Input stocks
Agricultural input stock lots with quantity on hand, unit and expiry
- Input usage
Input quantities consumed against a field task
Linked to Input stocks, Field operations - Input applications
Recorded input applications to a field by a named applicator
Linked to Fields, Team members - Field operations
Planned and executed field work assigned to a person for a specific cycle
Linked to Fields, Crop cycles, Team members - Fields
Farm fields and plots with area, location and availability status
- Team members
Farm staff, operators, reviewers and managers with their authenticated user account and role title
Linked to Users
- Harvests
Harvested quantities with unit and grade, accepted by a reviewer
Linked to Crop cycles, Team members - Crop cycles
Crop cycles per field from planned planting through growing, harvesting and close
Linked to Fields - Field operations
Planned and executed field work assigned to a person for a specific cycle
Linked to Fields, Crop cycles, Team members - Fields
Farm fields and plots with area, location and availability status
- Team members
Farm staff, operators, reviewers and managers with their authenticated user account and role title
Linked to Users
Keys and references
Field codes and names help people select the right plot, while record references preserve the relationship between a task and its cycle. A harvest belongs to a cycle, not directly to a field. Team members.User connects named staff to Users; task Owner and harvest accepted by point to team members. Input usage.Input and input usage.Task keep consumed quantity tied to a lot and operation.
Migration order
- Import Users and team members, then Fields with stable names and codes.
- Add field boundaries and current crop cycles, followed by dated field observations.
- Bring in input stocks before field operations and input usage.
- Add input applications and Harvests after their field, cycle and person references resolve.
Set up Precision Agriculture Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.