Description
Return share=allocatedWidth/totalWidth, requiring positive totalWidth and allocatedWidth within zero and totalWidth.
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.
Return share=allocatedWidth/totalWidth, requiring positive totalWidth and allocatedWidth within zero and totalWidth.
When to use this tool
Use Street Section Allocation Share 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 allocatedWidth, totalWidth. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read share. Use the output convention below.
Return share=allocatedWidth/totalWidth, requiring positive totalWidth and allocatedWidth within zero and totalWidth.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| allocatedWidth | Allocated Width | Required. Finite number; minimum 0. |
| totalWidth | Total Width | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| share | Dimensionless fraction using the denominator stated in the mechanics; not a percentage numeral. | Required. Finite number. |
{
"input": {
"allocatedWidth": 3,
"totalWidth": 12
},
"output": {
"share": 0.25
}
}Limitations and assumptions
- Both widths need a common length unit and section basis. The fraction does not identify street uses or establish traffic, accessibility, drainage, or design-standard compliance.
- 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
- Street Frontage Build To Gap
Calculate actualFraction=occupiedFrontage/frontage, requiredLength=frontage*requiredFraction, and gap=occupiedFrontage-requiredLength.
- Street Tree Canopy Gap At Maturity
One-dimensional mature canopy extents along the street axis.