Description
Assign an explicit minute index to an operating day with supplied UTC offset and day boundary.
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.
Assign an explicit minute index to an operating day with supplied UTC offset and day boundary.
When to use this tool
Use Visitor Pass First Scan Day Carry 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 scanMinute, offsetMinutes, dayBoundaryMinute. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read operatingDay, minuteIntoDay. Use the output convention below.
Shift scanMinute by offsetMinutes and subtract dayBoundaryMinute, then floor-divide by 1440 for operatingDay and normalize the remainder for minuteIntoDay. Require integer minutes, offset within plus or minus 1439, and boundary from zero through 1439.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| scanMinute | Integer minute coordinate on the caller’s numeric origin. | Required. Safe integer. |
| offsetMinutes | Offset Minutes | Required. Safe integer; minimum -1439; maximum 1439. |
| dayBoundaryMinute | Operating-day boundary within a 1440-minute grid. | Required. Safe integer; minimum 0; maximum 1439. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| operatingDay | Operating Day | Required. Safe integer. |
| minuteIntoDay | Minute Into Day | Required. Safe integer. |
{
"input": {
"scanMinute": 60,
"offsetMinutes": 0,
"dayBoundaryMinute": 240
},
"output": {
"operatingDay": -1,
"minuteIntoDay": 1260
}
}Limitations and assumptions
- This assumes fixed 1440-minute days on a supplied numeric origin. It does not select time zones, daylight-saving transitions, ticket policy, or actual first-scan history.
- 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.
- Trip Day Timezone Offset
Shift a supplied local clock hour using explicit UTC offsets; no time-zone database or daylight-saving inference.