Skip to content

Main content

Household Trip Chain Shared Leg Term Tool

Remove duplicated distance for one explicitly shared vehicle leg; supplied traveler distances include that leg for every sharer.

Loading tool…

Description

Sum nonnegative travelerLegDistances for personDistance.

Spatial models compare distances, travel intervals, activity areas, or supplied interaction functions. Coordinates and model parameters must share a compatible basis, and a local term does not establish observed behavior.

Sum nonnegative travelerLegDistances for personDistance.

When to use this tool

Use Household Trip Chain Shared Leg Term when you need one explicit spatial or travel-model component.

How to use the tool and how it works

  1. Enter travelerLegDistances, sharedLegDistance, sharedTravelers. 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 personDistance, vehicleDistance, sharedDistanceSaving. Use the output convention below.

Sum nonnegative travelerLegDistances for personDistance. Subtract sharedLegDistance times sharedTravelers-1 for vehicleDistance, validating a positive traveler count and enough aggregate distance.1

Input fieldMeaning and unitsAccepted input
travelerLegDistancesTraveler Leg DistancesRequired. Array of finite number; maximum items 256.
sharedLegDistanceShared Leg DistanceRequired. Finite number; minimum 0.
sharedTravelersShared TravelersRequired. Safe integer; minimum 1.
Output fieldInterpretationReturned shape
personDistancePerson DistanceRequired. Finite number.
vehicleDistanceVehicle DistanceRequired. Finite number.
sharedDistanceSavingShared Distance SavingRequired. Finite number.
json
{
  "input": {
    "travelerLegDistances": [
      10,
      12,
      8
    ],
    "sharedLegDistance": 4,
    "sharedTravelers": 3
  },
  "output": {
    "personDistance": 30,
    "vehicleDistance": 22,
    "sharedDistanceSaving": 8
  }
}

Limitations and assumptions

  • All distances share units; aggregate validation does not prove each traveler covered the shared leg or that the residual represents actual vehicle travel.
  • 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

Check projection, route definitions, calibration, and the complete model before interpreting access or predicted flows.

References

  1. Calculation and input contract: human-geography/household-trip-chain-shared-leg-term — tool.io

Similar or alternative tools