Description
Subtract accessWidth once from frontage for totalUsable and divide by positive integer parcels for equalFrontage.
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.
Subtract accessWidth once from frontage for totalUsable and divide by positive integer parcels for equalFrontage.
When to use this tool
Use Parcel Split Frontage Width Budget 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 frontage, accessWidth, parcels. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read equalFrontage, totalUsable. Use the output convention below.
Subtract accessWidth once from frontage for totalUsable and divide by positive integer parcels for equalFrontage. Require nonnegative access width no larger than frontage.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| frontage | Frontage | Required. Finite number. |
| accessWidth | Access Width | Required. Finite number; minimum 0. |
| parcels | Parcels | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| equalFrontage | Equal Frontage | Required. Finite number. |
| totalUsable | Total Usable | Required. Finite number. |
{
"input": {
"frontage": 100,
"accessWidth": 10,
"parcels": 3
},
"output": {
"equalFrontage": 30,
"totalUsable": 90
}
}Limitations and assumptions
- This assumes one shared access deduction and equal distribution of the remainder. Minimum frontages, parcel shapes, access rights, subdivision rules, and actual boundaries 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
- Parcel Frontage Depth Ratio
Supplied parcel-dimension ratio without zoning or buildability interpretation.
- Parcel Setback Area Term
Compute one rectangular setback strip from supplied dimensions without accounting for corner overlaps or zoning rules.