Description
Return region-label source age and a source key.
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 region-label source age and a source key.
When to use this tool
Use Region Label Source Vintage when checking the stated regional record, period, hierarchy or text convention.
How to use the tool and how it works
- Enter regionLabel, source, sourceYear, observationYear. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read ageYears, sourceKey. Use the output convention below.
Return region-label source age and a source key. Require whole years; ageYears = observationYear-sourceYear, key serializes [source,sourceYear,regionLabel].1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| regionLabel | Region Label | Required. Text; maximum UTF-16 length 8192. |
| source | Source | Required. Text; maximum UTF-16 length 8192. |
| sourceYear | Source Year | Required. Safe integer. |
| observationYear | Observation Year | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ageYears | Age Years | Required. Safe integer. |
| sourceKey | Source Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"regionLabel": "region-A",
"source": "atlas-2",
"sourceYear": 1980,
"observationYear": 2026
},
"output": {
"ageYears": 46,
"sourceKey": "[\"atlas-2\",1980,\"region-A\"]"
}
}Limitations and assumptions
- Negative age is retained; names, source currency and historical/regional validity are not authenticated.
- 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
Similar or alternative tools
- Public Region Code Era Depth
Return region-path depth and supplied edition support.
- Place Hierarchy Level Count
Return place-path level count under a root policy.