Description
Calculate actualFraction=occupiedFrontage/frontage, requiredLength=frontage*requiredFraction, and gap=occupiedFrontage-requiredLength.
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 actualFraction=occupiedFrontage/frontage, requiredLength=frontage*requiredFraction, and gap=occupiedFrontage-requiredLength.
When to use this tool
Use Street Frontage Build To Gap 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, occupiedFrontage, requiredFraction. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read actualFraction, requiredLength, gap. Use the output convention below.
Calculate actualFraction=occupiedFrontage/frontage, requiredLength=frontage*requiredFraction, and gap=occupiedFrontage-requiredLength. Require positive frontage, occupied frontage within it, and fraction within zero through one.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| frontage | Frontage | Required. Finite number; strictly above 0. |
| occupiedFrontage | Occupied Frontage | Required. Finite number; minimum 0. |
| requiredFraction | Required Fraction | Required. Finite number; minimum 0; maximum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| actualFraction | Actual Fraction | Required. Finite number. |
| requiredLength | Required Length | Required. Finite number. |
| gap | Gap | Required. Finite number. |
{
"input": {
"frontage": 100,
"occupiedFrontage": 70,
"requiredFraction": 0.6
},
"output": {
"actualFraction": 0.7,
"requiredLength": 60,
"gap": 10
}
}Limitations and assumptions
- Positive gap meets or exceeds the supplied length target arithmetically. The tool does not select a build-to rule, determine which frontage qualifies, or establish zoning 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
- Parcel Frontage Depth Ratio
Supplied parcel-dimension ratio without zoning or buildability interpretation.
- Parcel Split Frontage Width Budget
Subtract accessWidth once from frontage for totalUsable and divide by positive integer parcels for equalFrontage.