Skip to content

Main content

Public Cultural Event Date Precision Tool

Format a public cultural-event date at supplied year, month or day precision. Unknown lower fields must be zero rather than fabricated.

Loading tool…

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

  1. Enter year, month, day, precision. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. 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 fieldMeaning and unitsAccepted input
yearYear under the stated calendar and supported numeric bounds.Required. Safe integer; minimum 1; maximum 9999.
monthMonthRequired. Safe integer; minimum 0; maximum 12.
dayDayRequired. Safe integer; minimum 0; maximum 31.
precisionRecorded precision category; not a measurement-uncertainty estimate.Required. Text; one of "year", "month", "day"; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
labelFormatted label for the supplied components under the convention above.Required. Text; maximum UTF-16 length 8192.
json
{
  "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

  1. Calculation and input contract: cultural-studies/public-cultural-event-date-precision — tool.io

Similar or alternative tools