Skip to content

Main content

Accessibility Trip Return Deadline Slack Tool

Compare supplied trip return and inclusive deadline timestamps without predicting travel or accessibility.

Loading tool…

Description

Calculate slack to a supplied trip-return deadline.

Geographic activity records depend on location precision, boundary vintage, observation time, population denominator and access-window conventions. A travel-time budget differs from actual accessibility, and rectangular cell area does not establish privacy. Local shares and labels need the original survey and spatial definitions.

Calculate slack to a supplied trip-return deadline.

When to use this tool

Use Accessibility Trip Return Deadline Slack when you already have returnTime, suppliedDeadline and need to calculate slack to a supplied trip-return deadline.

How to use the tool and how it works

  1. Enter returnTime, suppliedDeadline. 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 slack, onTime. Inspect onTime before interpreting the associated values.

Return deadline-returnTime and flag returnTime<=deadline as onTime.1

Input fieldMeaning and unitsAccepted input
returnTimeReturn TimeRequired. Finite number.
suppliedDeadlineSupplied DeadlineRequired. Finite number.
Output fieldInterpretationReturned shape
slackSlackRequired. Finite number.
onTimeTrue at equality with the deadline as well as earlier returns.Required. Boolean.
json
{
  "input": {
    "returnTime": 15,
    "suppliedDeadline": 20
  },
  "output": {
    "slack": 5,
    "onTime": true
  }
}

Limitations and assumptions

  • Equality is on time; no route, actual deadline, accessibility, travel uncertainty or service entitlement 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

Use the actual route, service schedule, survey frame and boundary source when assessing mobility or access. Review disclosure across the full spatial dataset and linked records; a location label or cell-size product is not a complete privacy method.

References

  1. Calculation and input contract: human-geography/accessibility-trip-return-deadline-slack — tool.io

Similar or alternative tools