Description
Reflect a latitude beyond a pole once, add 180 degrees of longitude when reflected, and normalize longitude into [-180, 180).
Longitude is an angular coordinate with a seam and equivalent values separated by full turns. Interval direction, endpoint inclusion, and half-turn policy must be fixed before comparing or averaging longitudes.
Reflect a latitude beyond a pole once, add 180 degrees of longitude when reflected, and normalize longitude into [-180, 180).
When to use this tool
Use Geography: Latitude Pole Reflection Step when you need a longitude normalization, interval, or seam-policy calculation.
How to use the tool and how it works
- Enter latitudeDegrees, longitudeDegrees. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Require latitudeDegrees within [-270, 270] and longitudeDegrees within [-180, 180]. Reflect a latitude beyond a pole once, add 180 degrees of longitude when reflected, and normalize longitude into [-180, 180).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| latitudeDegrees | Latitude Degrees Unit: deg. | Required. Finite number. |
| longitudeDegrees | Longitude Degrees Unit: deg. | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Object containing the calculated members; expand to inspect the fields below. | Required. Object. |
| result.latitudeDegrees | Latitude Degrees | Calculated result member: number. |
| result.longitudeDegrees | Longitude Degrees | Calculated result member: number. |
| result.poleReflected | Pole Reflected | Calculated result member: boolean. |
{
"input": {
"latitudeDegrees": 100,
"longitudeDegrees": 10
},
"output": {
"result": {
"latitudeDegrees": 80,
"longitudeDegrees": -170,
"poleReflected": true
}
}
}Limitations and assumptions
- A single reflection is sufficient for the bounded input interval. Exact ±90 is not reflected, and this coordinate identity does not track a physical path or perform a datum conversion.
- Outputs are nested inside result. 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
Use a full spherical or ellipsoidal geometry method for routes and areas. Retain an explicit seam and endpoint policy when splitting, sorting, or averaging geographic data.
References
Similar or alternative tools
- Geography: Geographic Cell Angular Center
Compute the eastward wrapped longitude span, take its halfway point, and normalize into [-180, 180).
- Geographic Point Antimeridian Alias Pair
Return west [-180, latitude] and east [180, latitude] as longitude-first pairs.