-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Use Case
ADAPT currently uses a fixed list of common/anticipated Field Operation Types. This fixed list is not detailed/flexible enough for all use cases. #155 in particular cites a need for classifying an operation specifically as "sowing" vs. "sowing and planting."
Current Processes
In my experience, there is little standardization in this area. Every system has its own opinion of whether planting and seeding mean two different things, whether planting is a subtype of application or if application specifically means spraying/spreading after planting, etc. Systems are of course opinionated in their vocabularies based on the problems they are solving.
Other than the current ADAPT Standard Types, there are the ADAPT Framework types that largely follow ISO11783-11 DDI # 179. @aferreyra has shared another vocabulary from an ISO effort here although I am not aware if anyone is actively using this vocabulary. There is also AGROVOC and likely a number of other international classification systems that may or may not relate well to ADAPT.
@Jp-rice it is also no accident this topic came up in the context of mapping ADAPT to AAO. Looking at AAO in detail today, it appears you have already approached a lot of these same questions, and in many ways done what I'm proposing here to a far greater detail. I would appreciate your thoughts on how ADAPT might leverage AAO in this effort.
Touchpoints
The current ADAPT Types are as follows:
- UNKNOWN
- APPLICATION_GENERAL: Applying input(s) to a Field for purposes not otherwise specified in this list, or involving individual product mixes that cross types. Examples include spreading lime, and applying a product mix with a liquid fertilizer carrier and crop protection ingredients. Seeds with crop protection treatments, however, should be classified as APPLICATION_SOWING_AND_PLANTING. Also note that where multiple products of different types are applied in a single pass, data should be configured in separate operations by type.
- APPLICATION_FERTILIZING: Applying crop nutrition input(s) to a Field.
- APPLICATION_SOWING_AND_PLANTING: Introducing the seeds or other plant material into a field.
- APPLICATION_CROP_PROTECTION: Applying crop protection input(s) to a Field.
- APPLICATION_IRRIGATION: Applying water to a Field for the purpose of irrigation.
- FIELD_PREPARATION_GENERAL: Non-tillage activities to prepare a field for cultivation including chopping stover, picking rocks, leveling a field, building borders in flood-irrigated fields, shaping beds, etc.
- FIELD_PREPARATION_TILLAGE: Ground engaging operation to size and incorporate residue or alter the soil structure for future cultivation.
- HARVEST_PRE_HARVEST: In-field activities in preparation of harvest that are tracked separately, usually involving separate passes over the field from the harvest itself. Examples include swathing grain, mowing, raking and tedding hay, and removing foliage from or turning over root crops.
- HARVEST: The specific activity of gathering the cultivated crop from its growing location converting it into a product. Examples include combining grain, chopping forage, baling hay, picking cotton or fruit.
- HARVEST_POST_HARVEST: In-field activities following the actual harvest that are tracked separately, usually involving separate passes over the field from the harvest itself. Examples include carting grain, wrapping and hauling bales.
- OBSERVATION_GENERAL: A Field Observation activity such as scouting or soil testing.
- VEHICLE_DATA_COLLECTION_GENERAL: The activity of collecting data from the tractor or other vehicle, often alongside another Operation Type or in transport between Fields. Examples include fuel level and oil pressure.
Proposed Object Model
In discussions with @strhea, @dubnemo and others, we foresee a compound system of field operation type classification, where individual details can be assembled into compound types with or without their own names and/or mappings to external vocabularies. E.g., using the pending types from #155 as an example, we would likely retain "PADDY_MANAGEMENT_PUDDLING," but also define it in terms of other standard types, perhaps "FIELD_PREPARATION" + "FLOODED FIELD" + "PULVERIZING SOIL."
Similarly, we would break "SOWING_AND_PLANTING" into concepts of broadcasting seed vs. placing seed with additional levels of granularly in each case as may be deemed useful.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status