Skip to content

Main content

Bbox Longitude Wrap Interpretation Token Tool

Compute bbox longitude wrap interpretation token from explicit bounded inputs.

Loading tool…

Description

Mark crossing when east is below west and compute width as east minus west plus 360 only for that case.

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.

Mark crossing when east is below west and compute width as east minus west plus 360 only for that case.

When to use this tool

Use Bbox Longitude Wrap Interpretation Token when you need a bounding-box dimension, order, or span diagnostic.

How to use the tool and how it works

  1. Enter west, east. 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 crossesAntimeridian, width. Inspect crossesAntimeridian before interpreting the associated values.

Require west and east longitudes within [-180, 180]. Mark crossing when east is below west and compute width as east minus west plus 360 only for that case.1

Input fieldMeaning and unitsAccepted input
westWestRequired. Finite number.
eastEastRequired. Finite number.
Output fieldInterpretationReturned shape
crossesAntimeridianCrosses AntimeridianRequired. Boolean.
widthWidth or interval span on the measurement basis above.Required. Finite number.
json
{
  "input": {
    "west": 170,
    "east": -170
  },
  "output": {
    "crossesAntimeridian": true,
    "width": 20
  }
}

Limitations and assumptions

  • Equal endpoints mean zero width; seam representations can yield either zero or 360. No actual geometry, enclosure, or latitude extent is inspected.
  • 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

  1. Calculation and input contract: geojson/bbox-longitude-wrap-interpretation-token — tool.io

Similar or alternative tools