Description
Calculate usableArea=grossOpenSpace-excludedArea and areaPerPerson=usableArea/population.
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 usableArea=grossOpenSpace-excludedArea and areaPerPerson=usableArea/population.
When to use this tool
Use Public Open Space Per Person 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 grossOpenSpace, excludedArea, population. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read usableArea, areaPerPerson. Use the output convention below.
Calculate usableArea=grossOpenSpace-excludedArea and areaPerPerson=usableArea/population. Require positive integer population and nonnegative excluded area no larger than grossOpenSpace.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| grossOpenSpace | Gross Open Space | Required. Finite number. |
| excludedArea | Excluded Area | Required. Finite number; minimum 0. |
| population | Population | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| usableArea | Usable Area | Required. Finite number. |
| areaPerPerson | Area Per Person | Required. Finite number. |
{
"input": {
"grossOpenSpace": 12000,
"excludedArea": 2000,
"population": 1000
},
"output": {
"usableArea": 10000,
"areaPerPerson": 10
}
}Limitations and assumptions
- AreaPerPerson uses the supplied area unit per person. Public accessibility, quality, population catchment, legal open-space definitions, and adequate provision are not determined.
- 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.
- Parking Space Access Aisle Area
Rectangular perpendicular bays and a linear aisle allocation, excluding turning ends.