Description
Orthogonal crossing legs and a separate signed median stagger; excludes waiting time.
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.
Orthogonal crossing legs and a separate signed median stagger; excludes waiting time.
When to use this tool
Use Pedestrian Refuge Staggered Crossing Offset 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
- Enter firstHalf, secondHalf, stagger, speed. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read crossingDistance, walkingSeconds. Use the output convention below.
Calculate crossingDistance=firstHalf+secondHalf+abs(stagger) and walkingSeconds=crossingDistance/speed. Require nonnegative half-crossing lengths and positive speed.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstHalf | First Half | Required. Finite number; minimum 0. |
| secondHalf | Second Half | Required. Finite number; minimum 0. |
| stagger | Stagger | Required. Finite number. |
| speed | Positive walking speed in the supplied length unit per second. | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| crossingDistance | Crossing Distance | Required. Finite number. |
| walkingSeconds | Walking Seconds | Required. Finite number. |
{
"input": {
"firstHalf": 6,
"secondHalf": 7,
"stagger": 3,
"speed": 1
},
"output": {
"crossingDistance": 16,
"walkingSeconds": 16
}
}Limitations and assumptions
- Speed must use the supplied length unit per second. This assumes an additive stagger path and omits waiting, signal phases, accessibility needs, traffic conditions, and safety design requirements.
- 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
Similar or alternative tools
- Mixed Use Floor Share Balance
Return housingShare=housingArea/totalArea, commercialShare=commercialArea/totalArea, and otherArea=totalArea-housingArea-commercialArea.
- Mixed Use Parking Shared Peak Term
Apply caller-supplied concurrent peak fractions without choosing parking requirements.