Description
Independently check allowed-code membership and exact equality of version with expectedVersion.
Farm data records connect field, event, sensor and source identifiers with observation and verification flags. Literal keys and supported-record shares help reconcile those records without authenticating a source, identifying a physical object or establishing measurement quality. Repeated IDs may need a different denominator from repeated rows.
Independently check allowed-code membership and exact equality of version with expectedVersion.
When to use this tool
Use Agricultural Survey Option Code Version when checking the stated agricultural source, identity or record-support convention.
How to use the tool and how it works
- Enter code, version, allowedCodes, expectedVersion. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read codeKnown, versionMatches. Inspect codeKnown, versionMatches before interpreting the associated values.
Independently check allowed-code membership and exact equality of version with expectedVersion.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| code | Literal supplied code; no external registry lookup. | Required. Text; maximum UTF-16 length 8192. |
| version | Literal supplied version token; no semantic-version comparison unless explicitly stated. | Required. Text; maximum UTF-16 length 8192. |
| allowedCodes | Allowed Codes | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| expectedVersion | Expected Version | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| codeKnown | Code Known | Required. Boolean. |
| versionMatches | Version Matches | Required. Boolean. |
{
"input": {
"code": "02",
"version": "v2",
"allowedCodes": [
"01",
"02"
],
"expectedVersion": "v2"
},
"output": {
"codeKnown": true,
"versionMatches": true
}
}Limitations and assumptions
- A code may be known while its version differs; no survey schema or meaning is retrieved.
- 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
Inspect original records, authoritative identifier schemes and calibrated measurements before merging data or drawing agricultural conclusions.
References
Similar or alternative tools
- Agricultural Unit Code Source Gap
Check literal membership of code in knownCodes and equality of actualSource with expectedSource.
- Agricultural Map Crs Authority Pair
Require nonempty authority and code, compare both with expected values and encode [authority,code] as JSON text.