Skip to content

Main content

Historical Measure Unit Ambiguity Tool

Expose supplied historical-unit ambiguity without choosing a conversion from spelling alone.

Loading tool…

Description

Return supplied historical-unit ambiguity status.

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 supplied historical-unit ambiguity status.

When to use this tool

Use Historical Measure Unit Ambiguity when checking the stated regional record, period, hierarchy or text convention.

How to use the tool and how it works

  1. Enter token, candidateUnits, sourceUnitKnown. 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 ambiguous, candidateCount, resolvedUnit. Inspect ambiguous before interpreting the associated values.

Return supplied historical-unit ambiguity status. Require nonempty token; deduplicate candidates, ambiguous means unknown source unit and candidate count not one; resolvedUnit is token when known, the sole candidate otherwise, or empty.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
candidateUnitsCandidate UnitsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
sourceUnitKnownSource Unit KnownRequired. Boolean.
Output fieldInterpretationReturned shape
ambiguousTrue when the source unit is unknown and candidate count is not exactly one; zero candidates is ambiguous too.Required. Boolean.
candidateCountCandidate CountRequired. Safe integer.
resolvedUnitResolved UnitRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "token": "ton",
    "candidateUnits": [
      "short-ton",
      "long-ton"
    ],
    "sourceUnitKnown": false
  },
  "output": {
    "ambiguous": true,
    "candidateCount": 2,
    "resolvedUnit": ""
  }
}

Limitations and assumptions

  • A known token need not appear among candidates; actual unit identity, historical meaning and conversion factor are not established.
  • 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.

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/historical-measure-unit-ambiguity — tool.io

Similar or alternative tools