Skip to content

Main content

GeoJSON: Geometry Coordinate Z Presence Check Tool

Check whether one RFC7946-style position has a third altitude coordinate, rejecting ambiguous extra dimensions; not an altitude-datum validator.

Loading tool…

Description

Require a numeric position of length two or three, longitude in [-180, 180], and latitude in [-90, 90]; return whether a third ordinate is present inside result.

A GeoJSON position is an ordered coordinate tuple. Its dimension and individual ordinates are structural information; the presence of a third value alone does not establish a usable altitude or a valid coordinate reference.

Require a numeric position of length two or three, longitude in [-180, 180], and latitude in [-90, 90]; return whether a third ordinate is present inside result.

When to use this tool

Use GeoJSON: Geometry Coordinate Z Presence Check when you need a coordinate-tuple shape check or explicit ordinate operation.

How to use the tool and how it works

  1. Enter position. 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 result. Expand result to inspect the returned fields.

Require a numeric position of length two or three, longitude in [-180, 180], and latitude in [-90, 90]; return whether a third ordinate is present inside result.1

Input fieldMeaning and unitsAccepted input
positionPositionRequired. Array of finite number. Implementation limit: 128 items.
Output fieldInterpretationReturned shape
resultObject containing the calculated members; expand to inspect the fields below.Required. Object.
result.hasZHas ZCalculated result member: boolean.
json
{
  "input": {
    "position": [
      1,
      2,
      3
    ]
  },
  "output": {
    "result": {
      "hasZ": true
    }
  }
}

Limitations and assumptions

  • The third value is treated as Z by position alone. Its vertical datum, meaning, and suitability are not verified, and no coordinate transformation is performed.
  • Outputs are nested inside result. 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

Validate the complete coordinate convention and geometry before geospatial use. For actual coordinate conversion, use a transformation with the source and target reference systems explicitly specified.

References

  1. Calculation and input contract: geojson/geometry-coordinate-z-presence-check — tool.io

Similar or alternative tools