Skip to content

Main content

Regnal Year Era Token Tool

Apply an explicitly supplied first-year anchor and one-based regnal index; no accession/calendar convention is inferred.

Loading tool…

Description

Return suppliedFirstYear+regnalYear-1 and a JSON-array key retaining source, era, and regnal year.

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.

Return suppliedFirstYear+regnalYear-1 and a JSON-array key retaining source, era, and regnal year.

When to use this tool

Use Regnal Year Era Token when you need a documented calendar convention or source-coordinate comparison.

How to use the tool and how it works

  1. Enter era, source, regnalYear, suppliedFirstYear. 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 nominalYear, sourceKey. Use the output convention below.

Require positive integer regnalYear. Return suppliedFirstYear+regnalYear-1 and a JSON-array key retaining source, era, and regnal year.1

Input fieldMeaning and unitsAccepted input
eraEraRequired. Text; maximum UTF-16 length 8192.
sourceCaller-supplied source label; not independently verified.Required. Text; maximum UTF-16 length 8192.
regnalYearRegnal YearRequired. Safe integer; minimum 1.
suppliedFirstYearSupplied First YearRequired. Safe integer.
Output fieldInterpretationReturned shape
nominalYearNominal YearRequired. Safe integer.
sourceKeyJSON-array serialization retaining the supplied source and identifying components.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "era": "era-A",
    "source": "register-2",
    "regnalYear": 5,
    "suppliedFirstYear": 1700
  },
  "output": {
    "nominalYear": 1704,
    "sourceKey": "[\"register-2\",\"era-A\",5]"
  }
}

Limitations and assumptions

  • This is a nominal supplied-origin mapping without accession-day boundaries, calendar conversion, source authentication, or historical dating verification.
  • 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: history/regnal-year-era-token — tool.io

Similar or alternative tools