Description
Split it into minimum and maximum halves, compare corresponding axes, and optionally permit first-axis reversal for antimeridian crossing.
A bounding box groups lower axis bounds followed by upper axis bounds. Longitude can cross the antimeridian under a specific convention, so numeric ordering and coordinate span need to be interpreted separately from actual geometry enclosure.
Split it into minimum and maximum halves, compare corresponding axes, and optionally permit first-axis reversal for antimeridian crossing.
When to use this tool
Use Bbox Coordinate Pair Order Check when you need a bounding-box dimension, order, or span diagnostic.
How to use the tool and how it works
- Enter bbox, allowAntimeridian. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read ordered, crossing. Inspect ordered, crossing before interpreting the associated values.
Require an even-length numeric bbox with at least four values. Split it into minimum and maximum halves, compare corresponding axes, and optionally permit first-axis reversal for antimeridian crossing.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| bbox | Bbox | Required. Array of finite number; maximum items 256. |
| allowAntimeridian | Allow Antimeridian | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ordered | Ordered | Required. Boolean. |
| crossing | Crossing | Required. Boolean. |
{
"input": {
"bbox": [
170,
-10,
-170,
10
],
"allowAntimeridian": true
},
"output": {
"ordered": true,
"crossing": true
}
} Limitations and assumptions
- The crossing flag records first-axis reversal independently of whether that policy is allowed. Higher dimensions are accepted; coordinate ranges, ordinary GeoJSON dimension limits, and enclosure are not validated.
- 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
Compute bounds from the actual geometry with the intended seam policy. Validate dimensionality, coordinate ranges, and enclosure separately before using a box for spatial filtering.
References
Similar or alternative tools
- GeoJSON: Feature Bbox Dimension Label
Return dimensions equal to half its length and a 2D or 3D label inside result.
- Bbox Six Value Axis Budget
Compute wrapped longitude span, latitude span, and Z span.