Description
Check a supplied round-trip activity time budget.
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.
Check a supplied round-trip activity time budget.
When to use this tool
Use Travel Budget Time Constraint Margin when you already have availableMinutes, outboundMinutes, activityMinutes, returnMinutes and need to check a supplied round-trip activity time budget.
How to use the tool and how it works
- Enter availableMinutes, outboundMinutes, activityMinutes, returnMinutes. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read timeMarginMinutes, feasibleUnderInputs. Inspect feasibleUnderInputs before interpreting the associated values.
Require nonnegative available/outbound/activity/return minutes; margin=available-outbound-activity-return and feasibleUnderInputs means margin>=0.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| availableMinutes | Available Minutes | Required. Finite number; minimum 0. |
| outboundMinutes | Outbound Minutes | Required. Finite number; minimum 0. |
| activityMinutes | Activity Minutes | Required. Finite number; minimum 0. |
| returnMinutes | Return Minutes | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| timeMarginMinutes | Time Margin Minutes | Required. Finite number. |
| feasibleUnderInputs | Nonnegative time margin, including equality at zero; no real travel delay is predicted. | Required. Boolean. |
{
"input": {
"availableMinutes": 120,
"outboundMinutes": 20,
"activityMinutes": 60,
"returnMinutes": 25
},
"output": {
"timeMarginMinutes": 15,
"feasibleUnderInputs": true
}
}Limitations and assumptions
- No route, travel uncertainty, accessibility, actual opening times or appropriate activity duration is evaluated.
- 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.
- Public Space Observation Area Time
Calculate supplied public-space observation area-times-hours.