Skip to content

Main content

Commute Cost Unit Wedge Tool

Calculate commute cost unit wedge from explicit caller-supplied inputs.

Loading tool…

Description

Divide firstCost and secondCost by their positive trip counts and return firstPerTrip-secondPerTrip.

Generalized travel cost combines supplied cash charges with a monetary valuation of time. Its meaning depends on the time basis, wage or opportunity value, and which costs are included.

Divide firstCost and secondCost by their positive trip counts and return firstPerTrip-secondPerTrip.

When to use this tool

Use Commute Cost Unit Wedge when you need one stated travel-cost comparison or valuation component.

How to use the tool and how it works

  1. Enter firstCost, firstTrips, secondCost, secondTrips. 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 firstPerTrip, secondPerTrip, wedge. Use the output convention below.

Divide firstCost and secondCost by their positive trip counts and return firstPerTrip-secondPerTrip.1

Input fieldMeaning and unitsAccepted input
firstCostFirst CostRequired. Finite number.
firstTripsFirst TripsRequired. Finite number; strictly above 0.
secondCostSecond CostRequired. Finite number.
secondTripsSecond TripsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
firstPerTripFirst Per TripRequired. Finite number.
secondPerTripSecond Per TripRequired. Finite number.
wedgeWedgeRequired. Finite number.
json
{
  "input": {
    "firstCost": 30,
    "firstTrips": 10,
    "secondCost": 20,
    "secondTrips": 10
  },
  "output": {
    "firstPerTrip": 3,
    "secondPerTrip": 2,
    "wedge": 1
  }
}

Limitations and assumptions

  • Costs use one currency and compatible trip definitions; costs can be signed and no service quality, affordability, or causal comparison is 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.
  • 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

Keep actual payments separate from modeled time values and review the complete costing assumptions.

References

  1. Calculation and input contract: human-geography/commute-cost-unit-wedge — tool.io

Similar or alternative tools