Skip to content

Main content

Parcel Access Easement Width Margin

Compare explicit easement width with a supplied requirement without deciding legal access or accessibility compliance.

Loading tool…

Description

Compare an easement width with a supplied required width.

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.

Compare an easement width with a supplied required width.

When to use this tool

Use Parcel Access Easement Width Margin when you already have recordedWidth, suppliedRequiredWidth and need to compare an easement width with a supplied required width.

How to use the tool and how it works

  1. Enter recordedWidth, suppliedRequiredWidth. 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 margin, meetsSuppliedWidth. Inspect meetsSuppliedWidth before interpreting the associated values.

Require nonnegative widths; return recorded-required margin and recorded>=required, including equality.1

Input fieldMeaning and unitsAccepted input
recordedWidthRecorded WidthRequired. Finite number; minimum 0.
suppliedRequiredWidthSupplied Required WidthRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
marginMarginRequired. Finite number.
meetsSuppliedWidthInclusive recorded>=required comparison, not proof of legal compliance.Required. Boolean.
json
{
  "input": {
    "recordedWidth": 6,
    "suppliedRequiredWidth": 4
  },
  "output": {
    "margin": 2,
    "meetsSuppliedWidth": true
  }
}

Limitations and assumptions

  • The required width is assumed; no easement rights, survey boundaries or applicable access standard is verified.
  • 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/parcel-access-easement-width-margin — tool.io

Similar or alternative tools