Skip to content

Main content

Transit Service Gap Duration Tool

Calculate transit service gap duration from explicit caller-supplied inputs.

Loading tool…

Description

Return gap=nextDeparture-previousDeparture, requiring nextDeparture>=previousDeparture.

Planning indicators combine supplied counts, time intervals, distances, and area definitions. The denominator, geometric envelope, and category boundaries affect a reported density or share. A scenario calculation follows those assumptions while the governing rules and actual site conditions require separate verification.

Return gap=nextDeparture-previousDeparture, requiring nextDeparture>=previousDeparture.

When to use this tool

Use Transit Service Gap Duration when you need an explicit scenario indicator from supplied site dimensions, service records, or policy assumptions.

How to use the tool and how it works

  1. Enter previousDeparture, nextDeparture. 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 gap. Use the output convention below.

Return gap=nextDeparture-previousDeparture, requiring nextDeparture>=previousDeparture.1

Input fieldMeaning and unitsAccepted input
previousDeparturePrevious DepartureRequired. Finite number.
nextDepartureNext DepartureRequired. Finite number.
Output fieldInterpretationReturned shape
gapGapRequired. Finite number.
json
{
  "input": {
    "previousDeparture": 10,
    "nextDeparture": 25
  },
  "output": {
    "gap": 15
  }
}

Limitations and assumptions

  • Both departure values need one numeric time axis, including any overnight adjustment. This is a supplied service interval, not a timetable lookup, passenger wait estimate, reliability measure, or service recommendation.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
  • 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. Signed zero is exported as zero.

Alternative or Complementary methods

Check measured site data and the applicable authoritative definitions before using a scenario in a planning decision. Geographic analysis, transport modeling, or a complete design review may be needed beyond the stated term.

References

  1. Calculation and input contract: urban-planning/transit-service-gap-duration — tool.io

Similar or alternative tools