Description
Validate year 1-9999 and precision year, month, or day.
Calendar coordinates depend on an era, origin, day-start rule, and sometimes an arithmetic rather than observational convention. A supplied coordinate difference does not resolve those choices.
Validate year 1-9999 and precision year, month, or day.
When to use this tool
Use Public Cultural Event Date Precision when you need a documented calendar convention or source-coordinate comparison.
How to use the tool and how it works
- Enter year, month, day, precision. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read label. Use the output convention below.
Validate year 1-9999 and precision year, month, or day. Year precision requires month/day zero; month precision validates month and requires day zero; day precision validates the complete Gregorian date.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| year | Year under the stated calendar and supported numeric bounds. | Required. Safe integer; minimum 1; maximum 9999. |
| month | Month | Required. Safe integer; minimum 0; maximum 12. |
| day | Day | Required. Safe integer; minimum 0; maximum 31. |
| precision | Recorded precision category; not a measurement-uncertainty estimate. | Required. Text; one of "year", "month", "day"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| label | Formatted label for the supplied components under the convention above. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"year": 2026,
"month": 10,
"day": 0,
"precision": "month"
},
"output": {
"label": "2026-10"
}
} Limitations and assumptions
- Unspecified components are explicit zero sentinels; precision is supplied and no event date, historical calendar, or uncertainty interval 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
Consult the source calendar and authoritative date information for actual observance, conversion, or historical dating.
References
Similar or alternative tools
- Historical Event Date Precision Token
Quote date text and append its declared precision.
- Ethnographic Date Precision Single Label
Validate four digits for year, YYYY-MM with valid month for month, and a real YYYY-MM-DD for day; approximate and unknown retain arbitrary nonempty text.