Description
Qualify an explicit field-boundary reference by version.
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 field-boundary reference by version.
When to use this tool
Use Field Boundary Version Label when you already have fieldId, boundaryRecordId, version and need to qualify an explicit field-boundary reference by version.
How to use the tool and how it works
- Enter fieldId, boundaryRecordId, version. 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 fieldId, boundaryRecordId, version 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 |
|---|---|---|
| fieldId | Field Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| boundaryRecordId | Boundary Record Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| version | Version | 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": {
"fieldId": "F17",
"boundaryRecordId": "BOUND2",
"version": "v2"
},
"output": {
"token": "[\"F17\",\"BOUND2\",\"v2\"]"
}
}Limitations and assumptions
- The result records supplied values without editing geometry. 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
- Field ID Split Parent Reference
Qualify an explicit field-parent split reference.
- Task Data Device Element ID
Qualify an explicit task-data device element.