Skip to content

Main content

Zoning Lot Coverage Excluded Area

Normalize explicit footprint after supplied exclusions to lot area without deciding zoning coverage rules.

Loading tool…

Description

Calculate lot-coverage fraction after a supplied footprint exclusion.

Planning measurements depend on lot boundaries, excluded area, frontage, ground datum and the unit or person being served. A footprint fraction and a width margin answer different geometric questions. Accessibility, easement rights and zoning compliance depend on verified conditions and applicable requirements beyond a supplied flag or numerical comparison.

Calculate lot-coverage fraction after a supplied footprint exclusion.

When to use this tool

Use Zoning Lot Coverage Excluded Area when you already have grossFootprintArea, explicitlyExcludedArea, lotArea and need to calculate lot-coverage fraction after a supplied footprint exclusion.

How to use the tool and how it works

  1. Enter grossFootprintArea, explicitlyExcludedArea, lotArea. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read countedFootprintArea, coverageFraction. Use the output convention below.

Require grossFootprintArea>=0, excluded area within gross and lotArea>0; return gross-excluded and that counted area/lot area.1

Input fieldMeaning and unitsAccepted input
grossFootprintAreaGross Footprint AreaRequired. Finite number; minimum 0.
explicitlyExcludedAreaCaller-declared excluded footprint, within [0,gross footprint].Required. Finite number; minimum 0.
lotAreaLot AreaRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
countedFootprintAreaCounted Footprint AreaRequired. Finite number.
coverageFractionCounted footprint/lot area; may exceed one.Required. Finite number.
json
{
  "input": {
    "grossFootprintArea": 200,
    "explicitlyExcludedArea": 20,
    "lotArea": 600
  },
  "output": {
    "countedFootprintArea": 180,
    "coverageFraction": 0.3
  }
}

Limitations and assumptions

  • Exclusions are caller assumptions; coverage may exceed one and the calculation does not determine applicable zoning or compliance.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • 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. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use a verified survey, route inspection and the applicable planning definitions for actual coverage, access or height questions. Separate a supplied geometric margin from the documentation needed to establish an easement or accessibility condition.

References

  1. Calculation and input contract: urban-planning/zoning-lot-coverage-excluded-area — tool.io

Similar or alternative tools