Description
Return values at the requested indexes in order.
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 values at the requested indexes in order.
When to use this tool
Use Coordinate Position Ordinate Projection when you need a coordinate-tuple shape check or explicit ordinate operation.
How to use the tool and how it works
- Enter position, indexes. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read position. Use the output convention below.
Require a numeric position with at least two values and at least two integer indexes, each within that position. Return values at the requested indexes in order.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| position | Position | Required. Array of finite number; maximum items 256. |
| indexes | Indexes | Required. Array of safe integer; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| position | Position | Required. Array of finite number; maximum items 256. |
{
"input": {
"position": [
12,
34,
5
],
"indexes": [
0,
1
]
},
"output": {
"position": [
12,
34
]
}
} Limitations and assumptions
- Indexes may repeat or reorder axes, so the result need not be a valid GeoJSON position. This is an ordinate projection, not a coordinate-reference transformation.
- 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
Similar or alternative tools
- Point Coordinate Extra Ordinate Policy
Keep the first two, or at most the first three when keepAltitude, and report removed count.
- GeoJSON: Geometry Coordinate Z Presence Check
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.