Description
Measure overlap between a supplied visit interval and service opening interval.
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.
Measure overlap between a supplied visit interval and service opening interval.
When to use this tool
Use Service Access Opening Hour Overlap when you already have arrivalMinutes, departureMinutes, openingMinutes, closingMinutes and need to measure overlap between a supplied visit interval and service opening interval.
How to use the tool and how it works
- Enter arrivalMinutes, departureMinutes, openingMinutes, closingMinutes. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlapMinutes. Use the output convention below.
Require departure>=arrival and closing>=opening; return max(0,min(ends)-max(starts)) in minutes.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| arrivalMinutes | Arrival Minutes | Required. Finite number. |
| departureMinutes | Departure Minutes | Required. Finite number. |
| openingMinutes | Opening Minutes | Required. Finite number. |
| closingMinutes | Closing Minutes | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlapMinutes | Duration of the intersection of two supplied intervals; a shared endpoint has zero duration. | Required. Finite number. |
{
"input": {
"arrivalMinutes": 500,
"departureMinutes": 600,
"openingMinutes": 540,
"closingMinutes": 1020
},
"output": {
"overlapMinutes": 60
}
}Limitations and assumptions
- Touching boundaries give zero duration; no timezone, actual hours, service availability or suitable access 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
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
Similar or alternative tools
- Service Catchment Edge Travel Gap
Compare observed travel time with a supplied catchment-edge limit.
- Residential Move Date Precision
Label a residential move-date transcription and declared precision.