Understanding Fields and Subfields in FarmCommand
In FarmCommand, **fields** and **subfields** are how your operation’s data is organized and managed. Here's how it works:
---
#### What is a Field?
A **field** represents the total boundary of a physical piece of land.
#### What is a Subfield?
A **subfield** is a working unit within a field—this is where your **zone maps, soil test data, and variable rate (VR) prescriptions** are created and stored.
---
### Key Rules for Subfields
- **Every field must contain at least one subfield.**
- A field can have **multiple subfields**, but together their boundaries must **match the field boundary exactly**—no gaps or overlaps.
- **Each subfield should contain only one crop type.**
- All **zoning, soil testing, and prescriptions** are done at the **subfield level**.
---
### Farmers Edge Recommendation
**Farmers Edge strongly recommends using *one subfield per field* whenever possible.**\
This approach simplifies record keeping, ensures clean data, and allows for more accurate year-over-year comparisons.
However, if a field has been split in the past—or is likely to be split again in the future—you may use **multiple subfields** to reflect those different crop areas. Just remember: the combined subfield boundaries must still match the field boundary exactly.