Skip to content

Main content

Ticket Age Band Boundary Policy Tool

Apply an explicit age band with inclusive lower edge and configurable upper edge; no ticket provider's age policy is assumed.

Loading tool…

Description

Include the lower bound and apply the selected inclusive or strict upper bound.

Eligibility windows and numeric limits use explicit endpoints. A supplied age band, pass duration, opening interval, or allowance may include one boundary and exclude another; the implemented comparison determines that narrow result.

Include the lower bound and apply the selected inclusive or strict upper bound.

When to use this tool

Use Ticket Age Band Boundary Policy when you need to apply a supplied travel-service window or allowance consistently.

How to use the tool and how it works

  1. Enter ageYears, lowerAge, upperAge, upperInclusive. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read inBand. Inspect inBand before interpreting the associated values.

Require nonnegative ageYears and ordered nonnegative age bounds. Include the lower bound and apply the selected inclusive or strict upper bound.1

Input fieldMeaning and unitsAccepted input
ageYearsAge YearsRequired. Finite number; minimum 0.
lowerAgeLower AgeRequired. Finite number; minimum 0.
upperAgeUpper AgeRequired. Finite number.
upperInclusiveUpper InclusiveRequired. Boolean.
Output fieldInterpretationReturned shape
inBandIn BandRequired. Boolean.
json
{
  "input": {
    "ageYears": 12,
    "lowerAge": 6,
    "upperAge": 12,
    "upperInclusive": false
  },
  "output": {
    "inBand": false
  }
}

Limitations and assumptions

  • Fractional ages are allowed; actual ticket rules, age-verification documents, and birth-date calculations are not supplied.
  • 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 the full provider policy and any exceptions that are not represented by the input fields.

References

  1. Calculation and input contract: tourism/ticket-age-band-boundary-policy — tool.io

Similar or alternative tools