Description
Remove both appearances of a supplied internal boundary from parcel perimeters.
When two parcel boundaries are combined, the shared interior edge disappears from the exterior perimeter. Adding the original perimeters counts that edge twice, so both copies must be subtracted. All supplied lengths need the same unit.
Remove both appearances of a supplied internal boundary from parcel perimeters.
When to use this tool
Use Lot Merge Common Boundary Deduction 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
- Enter perimeters, sharedBoundaryLength. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read mergedPerimeter. Use the output convention below.
Calculate mergedPerimeter=sum(perimeters)-2*sharedBoundaryLength. Require nonnegative lengths and twice the shared length no greater than the sum.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| perimeters | Original parcel perimeter lengths in one common length unit. | Required. Array of finite number; maximum items 256. |
| sharedBoundaryLength | Length counted once here and removed twice from summed parcel perimeters. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| mergedPerimeter | Remaining exterior perimeter in the same length unit. | Required. Finite number. |
{
"input": {
"perimeters": [
100,
80
],
"sharedBoundaryLength": 20
},
"output": {
"mergedPerimeter": 140
}
}Limitations and assumptions
- The shared boundary is counted once as an input but removed from both parcel perimeters. No parcel geometry, legal merger, or boundary survey is verified.
- 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
Similar or alternative tools
- Bicycle Parking Rack Clearance Budget
Calculate requiredWidth=racks*rackWidth+(racks-1)*gap+2*endClearance and margin=availableWidth-requiredWidth.
- Block Perimeter Access Share
Calculate accessibleLength=sum(accessibleSegments)-suppliedOverlap and accessShare=accessibleLength/perimeter.