Skip to content

Main content

Position Dimension Count Tool

Inspect supplied position ordinate count without assigning meaning to ordinates beyond the optional third.

Loading tool…

Description

Return its length, presence of a third entry, and the count 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 its length, presence of a third entry, and the count beyond three.

When to use this tool

Use Position Dimension Count 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 dimensions, hasThirdOrdinate, extraOrdinateCount. Inspect hasThirdOrdinate before interpreting the associated values.

Require position with at least two numeric entries. Return its length, presence of a third entry, and the count beyond three.1

Input fieldMeaning and unitsAccepted input
positionPositionRequired. Array of finite number; maximum items 256.
Output fieldInterpretationReturned shape
dimensionsNumber of supplied ordinates, including extras beyond a third value.Required. Safe integer.
hasThirdOrdinateHas Third OrdinateRequired. Boolean.
extraOrdinateCountExtra Ordinate CountRequired. Safe integer.
json
{
  "input": {
    "position": [
      10,
      20,
      5
    ]
  },
  "output": {
    "dimensions": 3,
    "hasThirdOrdinate": true,
    "extraOrdinateCount": 0
  }
}

Limitations and assumptions

  • This counts dimensions without validating longitude/latitude bounds, altitude interpretation, coordinate reference, or full GeoJSON position conformance.
  • 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/position-dimension-count — tool.io

Similar or alternative tools