Description
Round units*requiredFraction upward to integer required and return additional=max(0,required-existingAccessible).
A planning scenario combines parcel dimensions, frontage, service space, and explicitly supplied rules. Gross, excluded, and counted areas can use different bases. A geometric result describes the chosen model while site conditions and the governing requirements need separate verification.
Round units*requiredFraction upward to integer required and return additional=max(0,required-existingAccessible).
When to use this tool
Use Housing Unit Accessible Share Rounding when you need the stated geometric or planning-indicator term under supplied site dimensions and rule choices.
How to use the tool and how it works
- Enter units, requiredFraction, existingAccessible. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read required, additional. Use the output convention below.
Round units*requiredFraction upward to integer required and return additional=max(0,required-existingAccessible). Require nonnegative integer units, existing count within units, and fraction within zero through one.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| units | Units | Required. Safe integer; minimum 0. |
| requiredFraction | Supplied required unit fraction, rounded upward after multiplication. | Required. Finite number; minimum 0; maximum 1. |
| existingAccessible | Existing Accessible | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| required | Required | Required. Safe integer. |
| additional | Additional | Required. Safe integer. |
{
"input": {
"units": 37,
"requiredFraction": 0.1,
"existingAccessible": 2
},
"output": {
"required": 4,
"additional": 2
}
}Limitations and assumptions
- The fraction and existing accessible count are supplied. This rounding does not select an accessibility requirement or establish that any unit meets a legal design standard.
- 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
Use measured site geometry and the applicable authoritative definitions when a planning decision needs more than this supplied term. A complete layout, access, or structural review can require additional models.
References
Similar or alternative tools
- Bicycle Parking Rack Clearance Budget
Calculate requiredWidth=racks*rackWidth+(racks-1)*gap+2*endClearance and margin=availableWidth-requiredWidth.
- Block Perimeter Access Share
Calculate accessibleLength=sum(accessibleSegments)-suppliedOverlap and accessShare=accessibleLength/perimeter.