Description
Add supplied integer source/target origins to their whole year coordinates using exact arithmetic.
Historical and regional records connect source vintages, era coordinates, folio sides, time coverage and locally defined units. Literal tokens and supplied offsets can organize metadata without authenticating an archive or establishing historical calendar equivalence. Preserve the original source and its conventions.
Add supplied integer source/target origins to their whole year coordinates using exact arithmetic.
When to use this tool
Use Public African Era Year Gap when checking the stated regional archival, chronology, coverage or unit convention.
How to use the tool and how it works
- Enter sourceYear, targetYear, suppliedSourceOrigin, suppliedTargetOrigin. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read normalizedSourceDecimal, normalizedTargetDecimal, gapDecimal. Use the output convention below.
Add supplied integer source/target origins to their whole year coordinates using exact arithmetic. Export both normalized coordinates and target-minus-source gap as decimal-integer text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sourceYear | Source Year | Required. Safe integer. |
| targetYear | Target Year | Required. Safe integer. |
| suppliedSourceOrigin | Supplied Source Origin | Required. Safe integer. |
| suppliedTargetOrigin | Supplied Target Origin | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| normalizedSourceDecimal | Normalized Source Decimal | Required. Text; maximum UTF-16 length 8192. |
| normalizedTargetDecimal | Normalized Target Decimal | Required. Text; maximum UTF-16 length 8192. |
| gapDecimal | Exact normalized target coordinate minus normalized source coordinate, as decimal-integer text. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"sourceYear": 10,
"targetYear": 12,
"suppliedSourceOrigin": 1900,
"suppliedTargetOrigin": 1900
},
"output": {
"normalizedSourceDecimal": "1910",
"normalizedTargetDecimal": "1912",
"gapDecimal": "2"
}
}Limitations and assumptions
- Origins and era alignment are supplied; this does not handle nonlinear calendars, month/day boundaries or historical year-zero conventions automatically.
- 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 archive and appropriate historical/calendar/unit authorities for provenance and substantive interpretation.
References
Similar or alternative tools
- Public Calendar Era Offset
Return yearCoordinate+suppliedOffset, allowing signed real coordinates and offsets.
- African Archive Dual Date Token
Compare them literally and JSON-encode [firstCalendar,firstDate,secondCalendar,secondDate] as key.