Description
Test whether first and second satisfy longitude/latitude bounds in each possible order, count valid orders, and set ambiguous when both orders pass.
Coordinate labels and tokens encode an axis order, sign convention, or formatting policy. Numeric compatibility and text formatting can diagnose ambiguity, but neither establishes the actual coordinate reference or location.
Test whether first and second satisfy longitude/latitude bounds in each possible order, count valid orders, and set ambiguous when both orders pass.
When to use this tool
Use Coordinate Order Ambiguity Count when you need a supplied geographic label or coordinate-convention diagnostic.
How to use the tool and how it works
- Enter first, second. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read validOrders, ambiguous. Inspect ambiguous before interpreting the associated values.
Test whether first and second satisfy longitude/latitude bounds in each possible order, count valid orders, and set ambiguous when both orders pass.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| first | First | Required. Finite number. |
| second | Second | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| validOrders | Valid Orders | Required. Safe integer. |
| ambiguous | Ambiguous | Required. Boolean. |
{
"input": {
"first": 20,
"second": 30
},
"output": {
"validOrders": 2,
"ambiguous": true
}
}Limitations and assumptions
- A count of one establishes only numeric compatibility, not the actual axis convention; zero means neither bounded order fits. Coordinates use degrees and no metadata or geographic context is examined.
- 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
Read authoritative coordinate metadata when the actual axis order or reference system matters. Keep original numeric precision and explicit sign conventions rather than inferring them from a plausible label.
References
Similar or alternative tools
- Geography: Geographic Latlon Axis Order Swap
Return named coordinates and swappedPair [second, first].
- Latitude Longitude Signquadrant Token
Return axis if either coordinate is zero; otherwise concatenate N or S with E or W from the signs.