Description
Count supplied UTC civil dates with explicit end inclusion, without inferring ticket terms.
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.
Count supplied UTC civil dates with explicit end inclusion, without inferring ticket terms.
When to use this tool
Use Ticket Valid Day Count 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 startDate, endDate, inclusiveEnd. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read days. Use the output convention below.
Parse startDate and endDate as exact valid YYYY-MM-DD dates at UTC midnight and count their day difference, adding one only when inclusiveEnd is true. Require end no earlier than start.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| startDate | Start Date | Required. Text; maximum UTF-16 length 8192. |
| endDate | End Date | Required. Text; maximum UTF-16 length 8192. |
| inclusiveEnd | Inclusive End | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| days | Days | Required. Safe integer. |
{
"input": {
"startDate": "2024-02-28",
"endDate": "2024-03-01",
"inclusiveEnd": true
},
"output": {
"days": 3
}
}Limitations and assumptions
- A same-date interval counts zero with an exclusive end and one with an inclusive end. Ticket rules, local times, time zones, and whether either endpoint is legally valid are not determined.
- 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 Ticket Validity Overlap Days
Intersect supplied half-open absolute-day trip and ticket windows 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.