Description
Compute Euclidean separation of the two planar coordinates.
Spatial models compare distances, travel intervals, activity areas, or supplied interaction functions. Coordinates and model parameters must share a compatible basis, and a local term does not establish observed behavior.
Compute Euclidean separation of the two planar coordinates.
When to use this tool
Use Activity Space Two Location Span when you need one explicit spatial or travel-model component.
How to use the tool and how it works
- Enter firstX, firstY, secondX, secondY, bufferRadius. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read distance, boundingWidth, boundingHeight, capsuleArea. Use the output convention below.
Compute Euclidean separation of the two planar coordinates. Add twice nonnegative bufferRadius to each axis span and return capsule area 2 × radius × distance + π × radius squared.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstX | First X | Required. Finite number. |
| firstY | First Y | Required. Finite number. |
| secondX | Second X | Required. Finite number. |
| secondY | Second Y | Required. Finite number. |
| bufferRadius | Buffer Radius | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| distance | Distance | Required. Finite number. |
| boundingWidth | Bounding Width | Required. Finite number. |
| boundingHeight | Bounding Height | Required. Finite number. |
| capsuleArea | Capsule Area | Required. Finite number. |
{
"input": {
"firstX": 0,
"firstY": 0,
"secondX": 3,
"secondY": 4,
"bufferRadius": 1
},
"output": {
"distance": 5,
"boundingWidth": 5,
"boundingHeight": 6,
"capsuleArea": 13.141592653589793
}
}Limitations and assumptions
- Coordinates and radius share a planar length unit; this is an ideal buffered line segment, not geographic geodesy or a measured activity-space polygon.
- 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
Check projection, route definitions, calibration, and the complete model before interpreting access or predicted flows.
References
Similar or alternative tools
- Urban Trip Detour Factor
Return both totals and routeTotal/directTotal.
- Turtle Shell Photo Area Factor
Convert nonnegative pixelArea using squared scaleLength/scalePixels, then divide projectedArea by cosine(obliquityRadians), with angle strictly within ±π/2.