Description
Report every positive-length UTC span overlap with unequal offset evidence; touching or identical offsets are not conflicts.
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.
Report every positive-length UTC span overlap with unequal offset evidence; touching or identical offsets are not conflicts.
When to use this tool
Use this tool to report every positive-length UTC span overlap with unequal offset evidence; touching or identical offsets are not conflicts.
How to use the tool and how it works
- Enter spansJson 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.conflicts, using the stated boundary, ordering, sign and absence conventions.
Compare every distinct source pair. Report its positive-length UTC overlap only when the exact offsets differ, including source indexes, intersection endpoints and both offsets.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. |
These decoded structures show the examples inside JSON text fields. Supply their serialized JSON strings as input.
{
"spansJson": [
{
"start": 0,
"end": 2,
"offset": 0
},
{
"start": 1,
"end": 3,
"offset": 2
}
]
}| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.conflicts | Overlapping unequal-offset source pairs with their positive-length intersection. |
{
"input": {
"spansJson": "[{\"start\":0,\"end\":2,\"offset\":0},{\"start\":1,\"end\":3,\"offset\":2}]"
},
"output": {
"result": {
"conflicts": [
{
"left": 0,
"right": 1,
"start": 1,
"end": 2,
"leftOffset": 0,
"rightOffset": 2
}
]
}
}
}Limitations and assumptions
- Equal-offset overlaps are not conflicts here; this does not prove global span coverage or choose a winner.
- 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 Offset Span Adjacent Compactor
Compact only adjacent ordered touching spans with exactly equal offsets, rejecting reversed/overlapping input rather than hiding conflicts.
- Time Zone Offset Span Coverage Gaps
Audit uncovered portions of a finite UTC window after unioning all supplied coverage regardless of offsets; not a claim of timezone rule completeness.