Skip to content

Main content

Public Map Name Period Gap Tool

Compare supplied public-map/name-vintage intervals, not a territorial or naming claim.

Loading tool…

Description

Check a map day against a closed place-name validity interval.

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.

Check a map day against a closed place-name validity interval.

When to use this tool

Use Public Map Name Period Gap when checking the stated regional record, period, hierarchy or text convention.

How to use the tool and how it works

  1. Enter mapDay, nameValidFrom, nameValidUntil. 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 withinPeriod, earlierGap, laterGap. Inspect withinPeriod before interpreting the associated values.

Check a map day against a closed place-name validity interval. Require whole ordered validity days; withinPeriod includes endpoints, earlier/later gaps are nonnegative distance outside them.1

Input fieldMeaning and unitsAccepted input
mapDayMap DayRequired. Safe integer.
nameValidFromName Valid FromRequired. Safe integer.
nameValidUntilInclusive end of the supplied place-name period.Required. Safe integer.
Output fieldInterpretationReturned shape
withinPeriodWithin PeriodRequired. Boolean.
earlierGapEarlier GapRequired. Safe integer.
laterGapLater GapRequired. Safe integer.
json
{
  "input": {
    "mapDay": 50,
    "nameValidFrom": 40,
    "nameValidUntil": 60
  },
  "output": {
    "withinPeriod": true,
    "earlierGap": 0,
    "laterGap": 0
  }
}

Limitations and assumptions

  • The validity period and day basis are supplied; no historical naming claim, geographic identity or calendar conversion is 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

  1. Calculation and input contract: area-studies/public-map-name-period-gap — tool.io

Similar or alternative tools