Skip to content

Main content

Historical Rail Fare Distance Unit

Normalize an explicitly transcribed rail fare by distance converted with a caller-supplied historical unit factor.

Loading tool…

Description

Convert a recorded journey distance and calculate fare per reference distance.

Historical economic records depend on archival wording, accounting signs, local units, assigned values, denominations and date precision. A wage-day ratio is a comparison of supplied amounts rather than actual labor time. Preserving an account-year label or unit factor does not authenticate a historical price, practice or legal obligation.

Convert a recorded journey distance and calculate fare per reference distance.

When to use this tool

Use Historical Rail Fare Distance Unit when you already have recordedDistance, referenceDistancePerRecordedUnit, recordedFare and need to convert a recorded journey distance and calculate fare per reference distance.

How to use the tool and how it works

  1. Enter recordedDistance, referenceDistancePerRecordedUnit, recordedFare. 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 referenceDistance, farePerReferenceDistance. Use the output convention below.

Require recorded distance and reference-distance-per-recorded-unit factor>0 and fare>=0; distance=recorded*factor, unitFare=fare/distance.1

Input fieldMeaning and unitsAccepted input
recordedDistanceRecorded DistanceRequired. Finite number; strictly above 0.
referenceDistancePerRecordedUnitReference Distance Per Recorded UnitRequired. Finite number; strictly above 0.
recordedFareRecorded FareRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
referenceDistanceReference DistanceRequired. Finite number.
farePerReferenceDistanceFare Per Reference DistanceRequired. Finite number.
json
{
  "input": {
    "recordedDistance": 20,
    "referenceDistancePerRecordedUnit": 1.5,
    "recordedFare": 6
  },
  "output": {
    "referenceDistance": 30,
    "farePerReferenceDistance": 0.2
  }
}

Limitations and assumptions

  • Definitions, geography, currency and ticket basis are supplied. No historical route, unit standard, tariff or price comparability is verified.
  • 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 ledger, archive and historical unit or monetary definitions when reconstructing an account. Reconcile period, commodity quality, currency and source corrections before comparing values; local labels and supplied conversions preserve only their declared assumptions.

References

  1. Calculation and input contract: economic-history/historical-rail-fare-distance-unit — tool.io

Similar or alternative tools