Skip to content

Main content

Point Third Ordinate Presence Token Tool

Inspect presence of a third ordinate; zero is a flagged placeholder when absent.

Loading tool…

Description

Return hasThird by length, the third value when present or zero placeholder, and count entries beyond three.

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.

Return hasThird by length, the third value when present or zero placeholder, and count entries beyond three.

When to use this tool

Use Point Third Ordinate Presence Token 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 hasThird, third, extraOrdinates. Inspect hasThird before interpreting the associated values.

Require position with at least two numeric entries. Return hasThird by length, the third value when present or zero placeholder, and count entries beyond three.1

Input fieldMeaning and unitsAccepted input
positionPositionRequired. Array of finite number; maximum items 256.
Output fieldInterpretationReturned shape
hasThirdHas ThirdRequired. Boolean.
thirdThird value or zero placeholder; inspect hasThird.Required. Finite number.
extraOrdinatesExtra OrdinatesRequired. Safe integer.
json
{
  "input": {
    "position": [
      10,
      20,
      30
    ]
  },
  "output": {
    "hasThird": true,
    "third": 30,
    "extraOrdinates": 0
  }
}

Limitations and assumptions

  • Read hasThird before using zero; no longitude/latitude bounds, altitude unit or reference, or full position validity is inferred.
  • 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/point-third-ordinate-presence-token — tool.io

Similar or alternative tools