Description
Explicit piecewise plane starts rising beyond the supplied setback; no zoning rule is selected.
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.
Explicit piecewise plane starts rising beyond the supplied setback; no zoning rule is selected.
When to use this tool
Use Setback Plane Height At Distance 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 baseHeight, distance, setback, risePerRun. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read allowedHeight. Use the output convention below.
Calculate allowedHeight=baseHeight+max(0,distance-setback)*risePerRun, requiring all inputs nonnegative.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| baseHeight | Base Height | Required. Finite number; minimum 0. |
| distance | Distance | Required. Finite number; minimum 0. |
| setback | Setback | Required. Finite number; minimum 0. |
| risePerRun | Nonnegative height increase per unit run beyond the supplied setback. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| allowedHeight | Allowed Height | Required. Finite number. |
{
"input": {
"baseHeight": 10,
"distance": 8,
"setback": 3,
"risePerRun": 2
},
"output": {
"allowedHeight": 20
}
}Limitations and assumptions
- RisePerRun is dimensionless and lengths share one unit. AllowedHeight is conditional on the supplied plane rule, not a verified planning permission, jurisdictional limit, or buildable-height determination.
- 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 Setback Area Term
Compute one rectangular setback strip from supplied dimensions without accounting for corner overlaps or zoning rules.
- Setback Corner Lot Frontage Token
Resolve supplied corner-lot frontage names without deciding a statutory front-yard designation.