Description
Shift a supplied local clock hour using explicit UTC offsets; no time-zone database or daylight-saving inference.
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.
Shift a supplied local clock hour using explicit UTC offsets; no time-zone database or daylight-saving inference.
When to use this tool
Use Trip Day Timezone Offset 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 localHour, sourceOffsetHours, targetOffsetHours. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read targetHour, dayShift. Use the output convention below.
Calculate targetHour modulo 24 from localHour-sourceOffsetHours+targetOffsetHours and dayShift as its floor-divided day carry. Require local hour within zero inclusive and 24 exclusive and offsets within plus or minus 24 hours.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| localHour | Hour from zero inclusive through 24 exclusive; fractional hours allowed. | Required. Finite number; minimum 0; strictly below 24. |
| sourceOffsetHours | Fixed source local-minus-UTC offset in hours. | Required. Finite number; minimum -24; maximum 24. |
| targetOffsetHours | Fixed target local-minus-UTC offset in hours. | Required. Finite number; minimum -24; maximum 24. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| targetHour | Target Hour | Required. Finite number. |
| dayShift | Day Shift | Required. Safe integer. |
{
"input": {
"localHour": 23,
"sourceOffsetHours": -5,
"targetOffsetHours": 2
},
"output": {
"targetHour": 6,
"dayShift": 1
}
}Limitations and assumptions
- Offsets are fixed supplied local-minus-UTC values. Fractional hours are allowed; no date-specific time zone, daylight-saving rule, booking condition, or itinerary lookup is provided.
- 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
- Ticket Valid Day Count
Count supplied UTC civil dates with explicit end inclusion, without inferring ticket terms.
- Visitor Pass First Scan Day Carry
Assign an explicit minute index to an operating day with supplied UTC offset and day boundary.