Description
Record a coordinate-order label without changing a geometry's coordinates.
GeoJSON separates a Feature’s identifier, geometry and properties. Null geometry, an explicit null property and an omitted property are distinct states. Coordinate-order labels do not transform positions, and stringifying a value already entered as a number cannot restore lost identifier precision or spelling.
Record a coordinate-order label without changing a geometry's coordinates.
When to use this tool
Use Geometry Coordinate Order Token when checking the stated restricted GeoJSON construction, property or identifier convention.
How to use the tool and how it works
- Enter recordId, axisOrder. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read label. Use the output convention below.
Require nonempty record ID and axisOrder longitude-latitude or latitude-longitude. Format recordId [axisOrder].1
GeoJSON specifies longitude/latitude order. Recording a lat-long label here neither reorders coordinates nor makes that ordering conform to GeoJSON.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordId | Nonempty caller-supplied record label; not independently resolved. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| axisOrder | Declared order only; latitude-longitude is accepted as a label without converting it to GeoJSON order. | Required. Text; one of "longitude-latitude", "latitude-longitude"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| label | Formatted supplied record wording; no independent validation of its substantive meaning. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordId": "R17",
"axisOrder": "longitude-latitude"
},
"output": {
"label": "R17 [longitude-latitude]"
}
}Limitations and assumptions
- This labels a supplied convention without swapping coordinates or validating GeoJSON; standard GeoJSON position order must be checked separately.
- 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.
Alternative or Complementary methods
Validate the complete Feature against the intended GeoJSON contract and use verified longitude/latitude and datum conventions for actual geographic data exchange.
References
Similar or alternative tools
- Line Two Position Endpoint Feature
Construct a GeoJSON LineString Feature from two matching-width positions.
- Coordinate Axis Authority Tag
Record the stated authority of a coordinate-axis convention.