Description
Multiply longitude minus reference longitude by 240 to return the mean local-solar-time offset in seconds inside result.
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.
Multiply longitude minus reference longitude by 240 to return the mean local-solar-time offset in seconds inside result.
When to use this tool
Use Geography: Longitude Offset To Local Solar Time when you need a longitude normalization, interval, or seam-policy calculation.
How to use the tool and how it works
- Enter longitudeDegrees, referenceMeridianDegrees. 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 both longitudes within [-180, 180]. Multiply longitude minus reference longitude by 240 to return the mean local-solar-time offset in seconds inside result.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| longitudeDegrees | Longitude Degrees Unit: deg. | Required. Finite number. |
| referenceMeridianDegrees | Reference Meridian 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.solarTimeOffsetSeconds | Unwrapped mean-solar longitude offset in seconds; may reach ±86400. | Calculated result member: number. |
{
"input": {
"longitudeDegrees": 15,
"referenceMeridianDegrees": 0
},
"output": {
"result": {
"solarTimeOffsetSeconds": 3600
}
}
}Limitations and assumptions
- The difference is not wrapped, so opposite seam spellings can yield ±86400 seconds. This is mean solar longitude arithmetic, not civil time, time zones, daylight saving, or the equation of time.
- 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
- Longitude Halfturn Tie Direction Label
Wrap to minus from modulo 360.
- Geography: Longitude Seam Endpoint Policy
Normalize modulo 360, mapping the seam to +180 under positive policy or -180 otherwise.