Description
Rectangular perpendicular bays and a linear aisle allocation, excluding turning ends.
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.
Rectangular perpendicular bays and a linear aisle allocation, excluding turning ends.
When to use this tool
Use Parking Space Access Aisle Area 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 spaceWidth, spaceLength, aisleWidth, spaces, aisleSharedSides. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read spaceArea, allocatedAisleArea, totalArea. Use the output convention below.
Calculate spaceArea=spaces*spaceWidth*spaceLength and allocatedAisleArea=spaces*spaceWidth*aisleWidth/aisleSharedSides, then return their sum. Require nonnegative dimensions and integer space count, with aisleSharedSides one or two.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| spaceWidth | Space Width | Required. Finite number; minimum 0. |
| spaceLength | Space Length | Required. Finite number; minimum 0. |
| aisleWidth | Aisle Width | Required. Finite number; minimum 0. |
| spaces | Spaces | Required. Safe integer; minimum 0. |
| aisleSharedSides | One or two sides sharing the allocated aisle area. | Required. Safe integer; minimum 1; maximum 2. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| spaceArea | Space Area | Required. Finite number. |
| allocatedAisleArea | Allocated Aisle Area | Required. Finite number. |
| totalArea | Total Area | Required. Finite number. |
{
"input": {
"spaceWidth": 2.5,
"spaceLength": 5,
"aisleWidth": 6,
"spaces": 10,
"aisleSharedSides": 2
},
"output": {
"spaceArea": 125,
"allocatedAisleArea": 75,
"totalArea": 200
}
}Limitations and assumptions
- The shared-side count is a cost or area allocation convention, not a layout design. Turning geometry, setbacks, accessible bays, obstructions, traffic operation, and parking-code compliance are not checked.
- 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
- Public Space Frontage Access Share
Calculate the share of supplied frontage length marked both accessible and in public use.
- Mixed Use Parking Shared Peak Term
Apply caller-supplied concurrent peak fractions without choosing parking requirements.