Description
Require nonnegative magnitude and prefix its numeric string with minus or plus according to negative, returning text, magnitude, and the flag.
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.
Require nonnegative magnitude and prefix its numeric string with minus or plus according to negative, returning text, magnitude, and the flag.
When to use this tool
Use Geodetic Coordinate Signed Zero Roundtrip when you need a supplied geographic label or coordinate-convention diagnostic.
How to use the tool and how it works
- Enter magnitude, negative. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read text, magnitude, negative. Inspect negative before interpreting the associated values.
Require nonnegative magnitude and prefix its numeric string with minus or plus according to negative, returning text, magnitude, and the flag.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| magnitude | Magnitude | Required. Finite number; minimum 0. |
| negative | Negative | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| text | Text | Required. Text; maximum UTF-16 length 8192. |
| magnitude | Magnitude | Required. Finite number. |
| negative | Negative | Required. Boolean. |
{
"input": {
"magnitude": 0,
"negative": true
},
"output": {
"text": "-0",
"magnitude": 0,
"negative": true
}
}Limitations and assumptions
- Text and the flag preserve the requested sign even at zero; numeric signed zero is not a distinct geographic location. No degree bounds, fixed decimal precision, or input lexical spelling are enforced.
- 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
- Coordinate Order Ambiguity Count
Test whether first and second satisfy longitude/latitude bounds in each possible order, count valid orders, and set ambiguous when both orders pass.
- Geodetic Longitude Rotation Sense Token
Keep or negate longitude accordingly, then label the resulting sign east, west, or none.