Description
Intersect supplied half-open absolute-day trip and ticket windows 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.
Intersect supplied half-open absolute-day trip and ticket windows without inferring ticket terms.
When to use this tool
Use Attraction Ticket Validity Overlap Days 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 tripStart, tripEnd, ticketStart, ticketEnd. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlapDays. Use the output convention below.
Return overlapDays=max(0,min(tripEnd,ticketEnd)-max(tripStart,ticketStart)) for ordered numeric day intervals.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| tripStart | Trip Start | Required. Safe integer. |
| tripEnd | Trip End | Required. Safe integer. |
| ticketStart | Ticket Start | Required. Safe integer. |
| ticketEnd | Ticket End | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlapDays | Overlap Days | Required. Safe integer. |
{
"input": {
"tripStart": 10,
"tripEnd": 20,
"ticketStart": 15,
"ticketEnd": 25
},
"output": {
"overlapDays": 5
}
}Limitations and assumptions
- This measures interval length without an inclusive-day addition; touching or zero-length intervals overlap by zero. No calendar dates, ticket conditions, local-day boundaries, or operator policy are parsed.
- 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.
- Ticket Valid Day Count
Count supplied UTC civil dates with explicit end inclusion, without inferring ticket terms.