Description
Apply caller-supplied concurrent peak fractions without choosing parking requirements.
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.
Apply caller-supplied concurrent peak fractions without choosing parking requirements.
When to use this tool
Use Mixed Use Parking Shared Peak Term 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 demandByUse, coincidentFractions, suppliedSpaces. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read coincidentDemand, margin. Use the output convention below.
Require aligned nonnegative demandByUse and coincidentFractions within zero through one, and nonnegative integer suppliedSpaces. Return coincidentDemand=sum(demand*fraction) and margin=suppliedSpaces-coincidentDemand.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| demandByUse | Demand By Use | Required. Array of Finite number.; maximum items 256. |
| coincidentFractions | Coincident Fractions | Required. Array of Finite number.; maximum items 256. |
| suppliedSpaces | Supplied Spaces | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| coincidentDemand | Coincident Demand | Required. Finite number. |
| margin | Margin | Required. Finite number. |
{
"input": {
"demandByUse": [
100,
50
],
"coincidentFractions": [
0.5,
0.8
],
"suppliedSpaces": 100
},
"output": {
"coincidentDemand": 90,
"margin": 10
}
}Limitations and assumptions
- Demand may be fractional and is not rounded to spaces. Coincidence factors are supplied scenarios, not observed joint peaks, a demand forecast, or a legal shared-parking approval.
- 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.
- Parking Space Access Aisle Area
Rectangular perpendicular bays and a linear aisle allocation, excluding turning ends.