Skip to content

Main content

Street Intersection Accessible Arm Flag

Partition explicit intersection arm identifiers by supplied accessibility flags without evaluating design compliance.

Loading tool…

Description

Partition intersection arms by supplied accessibility flags.

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.

Partition intersection arms by supplied accessibility flags.

When to use this tool

Use Street Intersection Accessible Arm Flag when you already have armIds, recordedAccessible and need to partition intersection arms by supplied accessibility flags.

How to use the tool and how it works

  1. Enter armIds, recordedAccessible. Follow any array-alignment requirements below. 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 accessibleArmIds, inaccessibleArmIds, allRecordedAccessible. Inspect allRecordedAccessible before interpreting the associated values.

Require aligned arrays and unique arm IDs; filter true/false flags into separate ID lists and return every(flag) as allRecordedAccessible.1

Input fieldMeaning and unitsAccepted input
armIdsArm IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
recordedAccessibleRecorded AccessibleRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
accessibleArmIdsAccessible Arm IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
inaccessibleArmIdsInaccessible Arm IdsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
allRecordedAccessibleEvery supplied flag is true; an empty list also returns true.Required. Boolean.
json
{
  "input": {
    "armIds": [
      "N",
      "E",
      "S"
    ],
    "recordedAccessible": [
      true,
      false,
      true
    ]
  },
  "output": {
    "accessibleArmIds": [
      "N",
      "S"
    ],
    "inaccessibleArmIds": [
      "E"
    ],
    "allRecordedAccessible": false
  }
}

Limitations and assumptions

  • An empty list returns true by vacuous convention; recorded flags do not establish actual accessibility or regulatory 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.

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/street-intersection-accessible-arm-flag — tool.io

Similar or alternative tools