Skip to content

Main content

Block Perimeter Access Share Tool

Calculate block perimeter access share from explicit caller-supplied inputs.

Loading tool…

Description

Calculate accessibleLength=sum(accessibleSegments)-suppliedOverlap and accessShare=accessibleLength/perimeter.

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.

Calculate accessibleLength=sum(accessibleSegments)-suppliedOverlap and accessShare=accessibleLength/perimeter.

When to use this tool

Use Block Perimeter Access Share 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

  1. Enter perimeter, accessibleSegments, suppliedOverlap. 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 accessibleLength, accessShare. Use the output convention below.

Calculate accessibleLength=sum(accessibleSegments)-suppliedOverlap and accessShare=accessibleLength/perimeter. Require positive perimeter and a feasible nonnegative union length within it.1

Input fieldMeaning and unitsAccepted input
perimeterPerimeterRequired. Finite number; strictly above 0.
accessibleSegmentsAccessible SegmentsRequired. Array of finite number; maximum items 256.
suppliedOverlapSupplied OverlapRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
accessibleLengthAccessible LengthRequired. Finite number.
accessShareAccess ShareRequired. Finite number.
json
{
  "input": {
    "perimeter": 100,
    "accessibleSegments": [
      30,
      20
    ],
    "suppliedOverlap": 10
  },
  "output": {
    "accessibleLength": 40,
    "accessShare": 0.4
  }
}

Limitations and assumptions

  • Overlap is supplied rather than derived geometrically. Length membership does not establish legal access, a continuous accessible route, or accessibility compliance.
  • 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

  1. Calculation and input contract: urban-planning/block-perimeter-access-share — tool.io

Similar or alternative tools