Description
Qualify an explicit farm-machine counter by supplied unit wording.
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 farm-machine counter by supplied unit wording.
When to use this tool
Use Farm Machine Counter Unit when you already have deviceId, counterName, unitText and need to qualify an explicit farm-machine counter by supplied unit wording.
How to use the tool and how it works
- Enter deviceId, counterName, unitText. 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 deviceId, counterName, unitText 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 |
|---|---|---|
| deviceId | Device Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| counterName | Counter Name | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| unitText | Unit Text | 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": {
"deviceId": "DEV17",
"counterName": "engine time",
"unitText": "h"
},
"output": {
"token": "[\"DEV17\",\"engine time\",\"h\"]"
}
}Limitations and assumptions
- The result records supplied values without reading the counter. 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
- Farm Log Crop Season Key
Build an unambiguous key from explicit farm, crop, and season labels.
- Farm Data Source Permission Tag
Record explicit farm-data source and purpose-specific permission metadata.