Sidewalk Clear Width Residual Tool

Description

Subtract explicit additive obstruction widths and compare with a supplied requirement.

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 explicit additive obstruction widths and compare with a supplied requirement.

When to use this tool

Use Sidewalk Clear Width Residual 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 totalWidth, obstructionWidths, requiredClearWidth. Keep parallel arrays aligned. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read clearWidth, residual. Use the output convention below.

Subtract the sum of nonnegative obstructionWidths from nonnegative totalWidth for clearWidth, then subtract requiredClearWidth for residual.^[1]

Input field	Meaning and units	Accepted input
totalWidth	Total Width	Required. Finite number; minimum 0.
obstructionWidths	Obstruction Widths	Required. Array of Finite number; minimum 0.; maximum items 256.
requiredClearWidth	Required Clear Width	Required. Finite number; minimum 0.

Output field	Interpretation	Returned shape
clearWidth	Clear Width	Required. Finite number.
residual	Residual	Required. Finite number.

json

{
  "input": {
    "totalWidth": 4,
    "obstructionWidths": [
      0.5,
      1
    ],
    "requiredClearWidth": 2
  },
  "output": {
    "clearWidth": 2.5,
    "residual": 0.5
  }
}

Limitations and assumptions

ClearWidth can be negative. Obstructions must be supplied as additive width deductions without double counting; actual placement, accessible routing, legal minimums, and pedestrian safety are not evaluated.
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

Calculation and input contract: urban-planning/sidewalk-clear-width-residual — tool.io

Similar or alternative tools

Parcel Split Frontage Width Budget
Subtract accessWidth once from frontage for totalUsable and divide by positive integer parcels for equalFrontage.
Mixed Use Floor Share Balance
Return housingShare=housingArea/totalArea, commercialShare=commercialArea/totalArea, and otherArea=totalArea-housingArea-commercialArea.