Description
Encode [source,edition,cropCode,stageCode] as JSON text.
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.
Encode [source,edition,cropCode,stageCode] as JSON text.
When to use this tool
Use Crop Calendar Stage Source Key when checking the stated agricultural source, identity or record-support convention.
How to use the tool and how it works
- Enter cropCode, stageCode, source, edition. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read key. Use the output convention below.
Require nonempty cropCode, stageCode, source and edition. Encode [source,edition,cropCode,stageCode] as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| cropCode | Crop Code | Required. Text; maximum UTF-16 length 8192. |
| stageCode | Stage Code | Required. Text; maximum UTF-16 length 8192. |
| source | Caller-supplied source label, not independently authenticated. | Required. Text; maximum UTF-16 length 8192. |
| edition | Edition | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| key | Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"cropCode": "C1",
"stageCode": "02",
"source": "calendar-A",
"edition": "v1"
},
"output": {
"key": "[\"calendar-A\",\"v1\",\"C1\",\"02\"]"
}
}Limitations and assumptions
- A namespaced key does not establish that the crop/stage code exists or is compatible across sources.
- 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.
- Farm Sensor Channel Code Source Pair
Return exact channel-and-source concordance with supplied expected labels.