Description
Calculate the share of supplied frontage length marked both accessible and in public use.
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.
Calculate the share of supplied frontage length marked both accessible and in public use.
When to use this tool
Use Public Space Frontage Access 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 frontageLengths, accessible, publicUse. 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 totalFrontage, accessiblePublicFrontage, share, defined. Inspect defined before interpreting the associated values.
Require aligned nonnegative frontageLengths and accessible and publicUse flags. Sum totalFrontage and lengths with both flags true as accessiblePublicFrontage, then divide by total when positive.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| frontageLengths | Frontage Lengths | Required. Array of Finite number; minimum 0.; maximum items 256. |
| accessible | Accessible | Required. Array of Boolean.; maximum items 256. |
| publicUse | Public Use | Required. Array of Boolean.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| totalFrontage | Total Frontage | Required. Finite number. |
| accessiblePublicFrontage | Accessible Public Frontage | Required. Finite number. |
| share | Dimensionless fraction using the denominator stated in the mechanics; not a percentage numeral. | Required. Finite number. |
| defined | Whether the associated denominator or quantity is defined; inspect before interpreting a placeholder. | Required. Boolean. |
{
"input": {
"frontageLengths": [
10,
20,
30
],
"accessible": [
true,
true,
false
],
"publicUse": [
true,
false,
true
]
},
"output": {
"totalFrontage": 60,
"accessiblePublicFrontage": 10,
"share": 0.16666666666666666,
"defined": true
}
}Limitations and assumptions
- An empty or zero-length base returns share zero with defined false. Supplied booleans do not establish legal public access, accessible-route compliance, or actual conditions on site.
- 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
- Parking Space Access Aisle Area
Rectangular perpendicular bays and a linear aisle allocation, excluding turning ends.
- Public Open Space Per Person Term
Calculate usableArea=grossOpenSpace-excludedArea and areaPerPerson=usableArea/population.