Description
Compare supplied fixed UTC-offset civil-day indices without choosing time zones or daylight rules.
Travel records use explicit dates, time axes, offsets, operating-day boundaries, durations, and capacity assumptions. A scheduling or validity term is meaningful only under those conventions. Actual operator rules, bookings, local conditions, and availability require separate information.
Compare supplied fixed UTC-offset civil-day indices without choosing time zones or daylight rules.
When to use this tool
Use Reservation Localday Origin Gap when you need the stated date, clock, scheduling, language, or capacity check from already supplied travel records.
How to use the tool and how it works
- Enter utcEpochSeconds, firstOffsetSeconds, secondOffsetSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read firstLocalDay, secondLocalDay, dayGap. Use the output convention below.
Add firstOffsetSeconds and secondOffsetSeconds separately to utcEpochSeconds, divide each by 86400, and floor for two local-day indexes and return dayGap=secondLocalDay-firstLocalDay.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| utcEpochSeconds | Shared UTC epoch-second coordinate. | Required. Finite number. |
| firstOffsetSeconds | First Offset Seconds | Required. Finite number. |
| secondOffsetSeconds | Second Offset Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| firstLocalDay | Floor local-day index on an 86400-second grid. | Required. Safe integer. |
| secondLocalDay | Floor local-day index under the second offset. | Required. Safe integer. |
| dayGap | Day Gap | Required. Safe integer. |
{
"input": {
"utcEpochSeconds": 0,
"firstOffsetSeconds": 0,
"secondOffsetSeconds": -3600
},
"output": {
"firstLocalDay": 0,
"secondLocalDay": -1,
"dayGap": -1
}
}Limitations and assumptions
- Offsets are supplied fixed local-minus-UTC seconds. Day indexes use an epoch-based 86400-second grid, not a time-zone database or date-dependent reservation policy.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- 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. Signed zero is exported as zero.
Alternative or Complementary methods
Use the actual schedule, calendar, booking record, and operator conditions for a real travel decision. Keep numeric clock conventions explicit when comparing this term with another method.
References
Similar or alternative tools
- Attraction Slot Buffer Share
Return usableDuration=slotDuration-bufferDuration and bufferShare=bufferDuration/slotDuration.
- Attraction Ticket Validity Overlap Days
Intersect supplied half-open absolute-day trip and ticket windows without inferring ticket terms.