Description
For a non-January season, end-year labels add one at/after seasonStartMonth; start-year labels subtract one before it.
Agricultural time series depend on clock origins, reporting intervals, source vintage and crop-season labeling. A supplied clock offset can reconcile timestamps, while matching source labels alone cannot prove clock synchronization. Calendar-year labels and start-year/end-year crop-season labels use different boundary conventions.
For a non-January season, end-year labels add one at/after seasonStartMonth; start-year labels subtract one before it.
When to use this tool
Use Crop Season Year Explicit Anchor when checking the stated clock, period, reporting-support or season-label convention.
How to use the tool and how it works
- Enter calendarYear, month, seasonStartMonth, labelByEndYear. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read seasonYear. Use the output convention below.
Require whole calendarYear and months 1..12. For a non-January season, end-year labels add one at/after seasonStartMonth; start-year labels subtract one before it. January seasons keep calendarYear.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| calendarYear | Calendar Year | Required. Safe integer. |
| month | Month | Required. Safe integer; minimum 1; maximum 12. |
| seasonStartMonth | Season Start Month | Required. Safe integer; minimum 1; maximum 12. |
| labelByEndYear | True uses the ending calendar year for a non-January season; false uses the starting year. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| seasonYear | Season Year | Required. Safe integer. |
{
"input": {
"calendarYear": 2026,
"month": 10,
"seasonStartMonth": 9,
"labelByEndYear": false
},
"output": {
"seasonYear": 2026
}
} Limitations and assumptions
- The season boundary and labeling policy are supplied; no crop calendar or geographical growing season is inferred.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use verified time metadata, calibrated clocks and the relevant complete crop/calendar conventions for actual temporal alignment and interpretation.
References
Similar or alternative tools
- Agricultural Tariff Season Window Gap
Include both window endpoints, wrapping across cycle end when start>end; return nonnegative modular days to start.
- Agri Environment Contract Year Proration
Return eligible/reference fraction and annualAmount times that fraction.