Description
Compare supplied ordered dimensions with explicit axis limits without rotating bags or selecting carrier rules.
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.
Compare supplied ordered dimensions with explicit axis limits without rotating bags or selecting carrier rules.
When to use this tool
Use Baggage Size Envelope Excess 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 dimensions, suppliedLimits. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read axisExcess, exceeds. Inspect exceeds before interpreting the associated values.
Compare aligned nonempty dimensions and suppliedLimits, returning per-axis positive excess and exceeds when any dimension is strictly above its limit. Require nonnegative entries.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| dimensions | Dimensions | Required. Array of finite number; maximum items 256. |
| suppliedLimits | Supplied Limits | Required. Array of finite number; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| axisExcess | Axis Excess | Required. Array of finite number; maximum items 256. |
| exceeds | Exceeds | Required. Boolean. |
{
"input": {
"dimensions": [
55,
40,
25
],
"suppliedLimits": [
55,
40,
20
]
},
"output": {
"axisExcess": [
0,
0,
5
],
"exceeds": true
}
}Limitations and assumptions
- Equality passes the supplied axis check. Axis order is fixed without trying rotations, and dimensions alone do not establish baggage acceptance, weight compliance, packing feasibility, or operator policy.
- 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.
- Attraction Ticket Validity Overlap Days
Intersect supplied half-open absolute-day trip and ticket windows without inferring ticket terms.