Description
Enumerate every offset-span UTC solution for a supplied local-second coordinate, retaining duplicates and overlapping evidence.
An offset maps a supplied UTC coordinate to local civil coordinates by local = UTC + offset. Half-open spans include their start and exclude their end. A forward offset jump can leave local coordinates uncovered; a backward jump can give several UTC interpretations of one local value. These tools use explicit synthetic civil-second observations rather than a named-zone database.
Enumerate every offset-span UTC solution for a supplied local-second coordinate, retaining duplicates and overlapping evidence.
When to use this tool
Use this tool to enumerate every offset-span UTC solution for a supplied local-second coordinate, retaining duplicates and overlapping evidence.
How to use the tool and how it works
- Enter spansJson, local using the definitions below. Serialize JSON text fields in the decoded shape shown below.
- Run the operation. Resolve input-format errors before interpreting an output.
- Read result.candidates, using the stated boundary, ordering, sign and absence conventions.
For each span compute utc=local−offset and retain it exactly when span.start≤utc<span.end. Return every candidate with its original span index and offset.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| spansJson | JSON array of {start,end,offset}: half-open UTC spans with local=UTC+offset, all in seconds. | Text, at most 8,192 UTF-16 code units; narrower grammar/range rules also apply. |
| local | Local civil-second coordinate within ±10¹². | Finite numeric value satisfying the stated comparisons. |
These decoded structures show the examples inside JSON text fields. Supply their serialized JSON strings as input.
{
"spansJson": [
{
"start": 0,
"end": 10,
"offset": 0
},
{
"start": 10,
"end": 20,
"offset": 2
},
{
"start": 20,
"end": 30,
"offset": 0
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.candidates | Every valid original-span {index,utc,offset} interpretation, without deduplication. |
{
"input": {
"spansJson": "[{\"start\": 0, \"end\": 10, \"offset\": 0}, {\"start\": 10, \"end\": 20, \"offset\": 2}, {\"start\": 20, \"end\": 30, \"offset\": 0}]",
"local": 21
},
"output": {
"result": {
"candidates": [
{
"index": 1,
"utc": 19,
"offset": 2
},
{
"index": 2,
"utc": 21,
"offset": 0
}
]
}
}
}Limitations and assumptions
- A missing candidate may mean an actual local gap or simply incomplete supplied coverage; duplicates are not removed.
- Span/transition coordinates are finite seconds within ±10¹² and offsets within ±86,400 seconds. Spans require start<end. No IANA database, calendar parsing, daylight-saving inference or leap seconds are included.
- Every declared outer field is required and unknown outer fields are rejected. Strings and JSON text have size limits, lists are bounded to 128 entries, and JSON nesting/node counts are bounded. Tighter operation-specific bounds stated above take precedence.
- Ordinary numeric outputs must be finite and within safe-integer magnitude. Exact large lengths/counts use decimal strings. Original record indexes and code-unit positions are zero-based; span ends are exclusive unless stated otherwise.
Alternative or Complementary methods
Keep all timestamps on one origin and in seconds, and retain gaps or competing observations. Use a maintained time-zone library when real dates, named zones or historical rules are required.
References
Similar or alternative tools
- Time Zone Local Candidate Policy Selector
Choose earliest/latest UTC candidate or unique-only under an explicit policy; empty or unresolved evidence returns null.
- Time Zone Local Window UTC Span List
Invert a local half-open window against every observed offset span, preserving multiple UTC solutions and source span indexes.