Description
Compare UTC-calendar and fixed-duration expiry times for a visitor pass.
Travel records distinguish a booking transcription, recorded party count and a caller-supplied time or cost allowance. Calendar-day validity can expire at a day boundary, whereas rolling validity preserves purchase time. Venue timezones, ticket terms, actual access and statutory taxes must be checked separately from a supplied arithmetic scenario.
Compare UTC-calendar and fixed-duration expiry times for a visitor pass.
When to use this tool
Use Visitor Pass Calendar Vs Rolling Day when you already have purchaseEpochSeconds, validityDays and need to compare UTC-calendar and fixed-duration expiry times for a visitor pass.
How to use the tool and how it works
- Enter purchaseEpochSeconds, validityDays. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read utcCalendarExpiryExclusiveSeconds, rollingExpiryExclusiveSeconds. Use the output convention below.
Require safe whole validityDays>=1. Convert purchase seconds to a valid Date, reset to UTC midnight and add validityDays for calendar expiry; rolling expiry=purchase+days*86400. Both endpoints are exclusive.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| purchaseEpochSeconds | Purchase Epoch Seconds | Required. Finite number. |
| validityDays | Positive whole count of UTC calendar days or fixed 86400-second durations. | Required. Safe integer; minimum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| utcCalendarExpiryExclusiveSeconds | UTC midnight at purchase-date plus validityDays; not venue-local midnight. | Required. Finite number. |
| rollingExpiryExclusiveSeconds | Purchase epoch seconds+validityDays*86400; exclusive boundary. | Required. Finite number. |
{
"input": {
"purchaseEpochSeconds": 43200,
"validityDays": 2
},
"output": {
"utcCalendarExpiryExclusiveSeconds": 172800,
"rollingExpiryExclusiveSeconds": 216000
}
}Limitations and assumptions
- Calendar counting uses UTC rather than a venue timezone; no local daylight-saving rules, ticket terms or entitlement are checked.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- 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. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Check venue-local ticket terms and verified booking dates for actual admission. Build a complete itinerary with travel and opening-hour constraints when planning a visit; use supplied count, tax and time terms as individual budget components.
References
Similar or alternative tools
- Attraction Ticket Entry Exit Date Tag
Preserve ticket entry and exit date transcriptions.
- Travel Booking Local Time Offset Field
Preserve booking-local time text and its supplied offset label.