Skip to content

Main content

Regional Dualera Year Token Tool

Year-offset bookkeeping only for a caller-asserted compatible era mapping.

Loading tool…

Description

Return a year conversion only when offset is known.

Regional records connect place labels, language coverage, source vintages, calendar offsets and historical units. A literal label or supplied year offset can organize metadata without resolving changes in borders, calendar systems or naming authority. Unknown and ambiguous values must retain their explicit flags.

Return a year conversion only when offset is known.

When to use this tool

Use Regional Dualera Year Token when checking the stated regional record, period, hierarchy or text convention.

How to use the tool and how it works

  1. Enter recordedYear, suppliedOffset, offsetKnown. 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 convertedKnown, convertedYear. Inspect convertedKnown before interpreting the associated values.

Return a year conversion only when offset is known. Require whole recordedYear/suppliedOffset; convertedYear = year+offset when offsetKnown, otherwise zero with convertedKnown false.1

Input fieldMeaning and unitsAccepted input
recordedYearRecorded YearRequired. Safe integer.
suppliedOffsetSupplied OffsetRequired. Safe integer.
offsetKnownOffset KnownRequired. Boolean.
Output fieldInterpretationReturned shape
convertedKnownConverted KnownRequired. Boolean.
convertedYearrecordedYear+suppliedOffset when offsetKnown; zero placeholder otherwise.Required. Safe integer.
json
{
  "input": {
    "recordedYear": 1400,
    "suppliedOffset": 600,
    "offsetKnown": true
  },
  "output": {
    "convertedKnown": true,
    "convertedYear": 2000
  }
}

Limitations and assumptions

  • The zero output is a placeholder for unknown conversion, not year zero; no historical calendar mapping 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 original sources, applicable calendar and historical naming/measurement authorities for geographic or historical interpretation.

References

  1. Calculation and input contract: area-studies/regional-dualera-year-token — tool.io

Similar or alternative tools