Description
Qualify an explicit agricultural operation code by source.
Farm data records preserve task, device, field-boundary, source-permission and unit identifiers. A supplied area-unit label is not a conversion, while a sensor/reference clock gap is not synchronization. Version and permission references record assertions rather than validating a complete device or agricultural data standard.
Qualify an explicit agricultural operation code by source.
When to use this tool
Use Agricultural Operation Type Code when you already have taskId, operationCode, codeSource and need to qualify an explicit agricultural operation code by source.
How to use the tool and how it works
- Enter taskId, operationCode, codeSource. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter taskId, operationCode, codeSource using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| taskId | Task Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| operationCode | Operation Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| codeSource | Code Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"taskId": "TASK17",
"operationCode": "OP2",
"codeSource": "Farm key A"
},
"output": {
"token": "[\"TASK17\",\"OP2\",\"Farm key A\"]"
}
}Limitations and assumptions
- The result records supplied values without identifying an operation from telemetry. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Check actual device, task, boundary and source records with the full format and controlled vocabulary. Verify calibration, time alignment and permissions before relying on local keys or labels in an operational workflow.
References
Similar or alternative tools
- Agricultural Area Unit Tag
Preserve explicit field area and unit text.
- Farm Data Source Permission Tag
Record explicit farm-data source and purpose-specific permission metadata.