CalendarWeb Class

Data contract Rental calendar and possible arrival/departure dates.

The primary goal of an arrival and departure calendar is to correctly identify on which days what vacation types (booking lengths) are available.

RentalObjectCalendarWeb.ArrivalDays and RentalObjectCalendarWeb.DepartureDays contains possible arrival and departure days for the following vacation types:

• Standard vacation (A): 7, 14, 21 or 28 days
• Optional Arrival (O): 7-28 days
• Multi Week Discount (M): 14-28 days
• Short Stay (S): 2-6 days

The calendar also contains the following vacancy details

• A: Free and available standard vacation arrival day (see above)
• a: Available
• b: blocked. Not available, but a blocked day should not count against the winter 13 week (max) rental rule
• B: Booked

To correctly parse the calendar the following steps should be taken: Start by identifying an arrival day of interest on the arrival calendar. To do this, use the offset date on the calendar and calculate how many groups (days) to skip to find the group of interest. Once found, the contents of the arrival day group can be used to calculate allowed arrival days. The goal is to find out what lengths between 2 and 28 days are possible for this specific arrival day.

Here are the possible values to help determine an allowed departure day:

• B or b: No arrival is possible on this date.

• Allowed length is 7, 14, 21 or 28 days.
• The arrival day must contain an A on the arrival calendar.
• The departure day must contain an A on the departure calendar.
• Every day in between must contain an uninterrupted A/a on either the arrival or departure calendar.*

• Allowed length is between 7-28 days.
• The arrival day must contain an O on the arrival calendar.
• The departure day must contain an O on the departure calendar.
• Every day in between must contain an uninterrupted O on either the arrival or departure calendar.*

• Allowed length is between 2-6 days.
• The arrival day must contain an S on the arrival calendar.
• The departure day must contain an S on the departure calendar.
• Every day in between must contain an uninterrupted S on either the arrival or departure calendar.*

• Allowed length is 14, 21 and 28 days.
• The arrival day must contain an M on the arrival calendar.
• The departure day must contain an M on the departure calendar.
• Every day in between must contain an uninterrupted M on either the arrival or departure calendar and A/a.*
• For lengths other than whole weeks (15-20 and 22-27 days) every day in between must contain an uninterrupted M on either the arrival or departure calendar and O. *

*When checking if a character is either on the arrival or departure calendar, start by looping the arrival calendar and check for that character. If a day is reached where the characters is no longer there, then continue from that day on the departure calendar, and continue checking for that character until the desired departure date is reached.

Please note
Please be aware that the calendar string format described above is obsolete and is only available to avoid breaking the contract with old client proxies.
Please use the new duration based format in stead. The description of this duration based format can be found in the comments to the field ArrivalDays
If the field IncludeCalendarDurations is set to true, a CalendarWeb instance containing the duration based format, will be returned in the field CalendarDurations. The field Calendar always contains the old obsolete format.