Coding examples
EX 1: H24
Usual formulation in AIS documents
H24
Remark
See also Common coding patterns.
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTil | ANY |
startTime | 00:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 00:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
EX 2: Daily period adjusted for daylight saving
Usual formulation in AIS documents
0500-2200 (0400-2100)
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTil | |
startTime | 05:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 22:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | YES |
excluded | NO |
EX 3: Periods during the week, except legal holidays
Usual formulation in AIS documents
MON-THU 0700-1530 (MON-THU 0600-1430)
FRI 0700-1130 (FRI 0600-1030)
except legal holidays
Remark
Note that the 'excluded legal holidays' is coded with Timesheet (6) that uses local time and 00:00 of the next day as 'end of day' time
Timesheet (1) | Timesheet (2) | Timesheet (3) | Timesheet (4) | Timesheet (5) | Timesheet (6) | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC+1 |
startDate | startDate | startDate | startDate | startDate | startDate | ||||||
endDate | endDate | endDate | endDate | endDate | endDate | ||||||
day | MON | day | TUE | day | WED | day | THU | day | FRI | day | HOL |
dayTil | dayTil | dayTil | dayTil | dayTil | dayTil | AFT_HOL | |||||
startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 00:00 |
startEvent | startEvent | startEvent | startEvent | startEvent | startEvent | ||||||
startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | ||||||
startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | ||||||
endTime | 15:30 | endTime | 15:30 | endTime | 15:30 | endTime | 15:30 | endTime | 11:30 | endTime | 00:00 |
endEvent | endEvent | endEvent | endEvent | endEvent | endEvent | ||||||
endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | ||||||
endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | ||||||
dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | NO |
excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | YES |
EX 4: Sunset or 20:00, if earlier
Usual formulation in AIS documents
0800-SS or 2000 if earlier (0700-SS or 1900 if earlier)
Remark
In some European States SR is interpreted as BCMT (Begin of civil morning twilight) and SS as ECET (End of civil evening twilight). The definition is slightly different than for SS/SR. See also page Common coding patterns.
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTil | |
startTime | 08:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 20:00 |
endEvent | SS |
endTimeRelativeEvent | |
endEventInterpretation | EARLIEST |
dailightSavingAdjust | YES |
excluded | NO |
EX 5: Continuous from Monday to Saturday in local time
Usual formulation in AIS documents
Timesheet (1) | Timesheet (2) | ||
---|---|---|---|
timeReference | UTC+1 | timeReference | UTC+1 |
startDate | startDate | ||
endDate | endDate | ||
day | MON | day | HOL |
dayTil | SUN | dayTil | AFT_HOL |
startTime | 00:00 | startTime | 00:00 |
startEvent | startEvent | ||
startTimeRelativeEvent | startTimeRelativeEvent | ||
startEventInterpretation | startEventInterpretation | ||
endTime | 00:00 | endTime | 00:00 |
endEvent | endEvent | ||
endTimeRelativeEvent | endTimeRelativeEvent | ||
endEventInterpretation | endEventInterpretation | ||
dailightSavingAdjust | NO | dailightSavingAdjust | NO |
excluded | NO | excluded | YES |
EX 6: Continuous from October to July
Usual formulation in AIS documents
Remark
Remark: There are no times mentioned, which typically means that local time is assumed for the start and end dates.
Timesheet (1) | |
---|---|
timeReference | UTC+1 |
startDate | 01-10 |
endDate | 31-07 |
day | ANY |
dayTil | ANY |
startTime | 00:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 00:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
EX 7: Announced by NOTAM
Usual formulation in AIS documents
Up to 2500 FT AMSL: MON – FRI 0800-1700 local time except legal holidays.
Above 2500 FT AMSL effectiveness will be announced by NOTAM.
MON–FRI 1700-0800 local time as well as SAT and SUN 0000-2400 local time effectiveness will be announced by NOTAM.
Remark
This has to be coded as two different schedules each concerning a level band (e.g. as AirspaceActivation with corresponding AirspaceLayer or as RouteAvailabiliy elements). The times when the effectiveness is announced by NOTAM shall not be encoded as Timesheet. They should be just a Note. Otherwise, the schedule would be misunderstood as if the airspace or route is effective, even in the absence of a NOTAM.
Timesheet (1) | Timesheet (2) | Timesheet (3) | Timesheet (4) | Timesheet (5) | Timesheet (6) | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|
timeReference | UTC+1 | timeReference | UTC+1 | timeReference | UTC+1 | timeReference | UTC+1 | timeReference | UTC+1 | timeReference | UTC+1 |
startDate | startDate | startDate | startDate | startDate | startDate | ||||||
endDate | endDate | endDate | endDate | endDate | endDate | ||||||
day | MON | day | TUE | day | WED | day | THU | day | FRI | day | HOL |
dayTil | dayTil | dayTil | dayTil | dayTil | dayTil | AFT_HOL | |||||
startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 00:00 |
startEvent | startEvent | startEvent | startEvent | startEvent | startEvent | ||||||
startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | ||||||
startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | ||||||
endTime | 17:00 | endTime | 17:00 | endTime | 17:00 | endTime | 17:00 | endTime | 17:00 | endTime | 00:00 |
endEvent | endEvent | endEvent | endEvent | endEvent | endEvent | ||||||
endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | ||||||
endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | ||||||
dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO |
excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | YES |
EX 8: Outside OPS HR
Usual formulation in AIS documents
Remark
I am lost here. Of course it would be easy to exclude the time sheets of the MIL OPS office from a 00:00-24:00 time sheet, but as the office hours are often extended by NOTAM the time sheet would not fit anymore and it would also be necessary to change the times of this airspace by NOTAM which is not practicable. I fear that this will be an example of what will still only be possible to distribute by using a note only.
EX 9: Daily from SR - SS
Usual formulation in AIS documents
daily SR - SS
Remark
Note: is the same as HJ.
In some European States SR is interpreted as BCMT (Begin of civil morning twilight) and SS as ECET (End of civil evening twilight). The definition is slightly different than for SS/SR. See also page Common coding patterns for coding.
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTil | |
startTime | |
startEvent | SR |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | |
endEvent | SS |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
EX 10: Legal Holiday
Usual formulation in AIS documents
SAT, SUN 1000-1600 (0900-1500)
Legal holiday 1200-1400 (1100-1300)
Remark
Note: Legal holiday automatically overrules a "normal" day, e.g if the legal holiday is a Wednesday 1200-1400 does apply. See also page General coding rules for schedules.
Timesheet (1) | Timesheet (2) | Timesheet (3) | Timesheet (4) | Timesheet (5) | Timesheet (6) | Timesheet (7) | Timesheet (8) | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC |
startDate | startDate | startDate | startDate | startDate | startDate | startDate | startDate | ||||||||
endDate | endDate | endDate | endDate | endDate | endDate | endDate | endDate | ||||||||
day | MON | day | TUE | day | WED | day | THU | day | FRI | day | SAT | day | SUN | day | HOL |
dayTil | dayTil | dayTil | dayTil | dayTil | dayTil | dayTil | dayTil | ||||||||
startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 10:00 | startTime | 10:00 | startTime | 12:00 |
startEvent | startEvent | startEvent | startEvent | startEvent | startEvent | startEvent | startEvent | ||||||||
startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | ||||||||
startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | ||||||||
endTime | 16:00 | endTime | 16:00 | endTime | 16:00 | endTime | 16:00 | endTime | 16:00 | endTime | 16:00 | endTime | 1600 | endTime | 14:00 |
endEvent | endEvent | endEvent | endEvent | endEvent | endEvent | endEvent | endEvent | ||||||||
endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | ||||||||
endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | ||||||||
dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES | dailightSavingAdjust | YES |
excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO |
EX 11: Mixture of UTC and local time & daylight saving time and non daylight saving time
Usual formulation in AIS documents
MON-FRI H24
SAT 0001-1300 (2301 - 1200)
HOL excluded
(in order to avoid confusions, some States indicate explicitly the start day for the summer time, such as SAT 0001-1300 (FRI 2301 - SAT 1200)
Remark
This example refers to LI R53/A. Seems to be an overlap between SAT ( when the daylightsavingAdjust is applied) and WORK_DAY. Moreover what happen when Friday is a Legal Holiday? Does the Hol exclusion ( in this case on Friday between 23:00 and 23:59) overrule a workday, doesn't it?I would like to focus also on the "meaning" of UTC, UTC+1,... and so on. From my point of view it is not clear. From my understanding it seems to be the "Code indicating the time reference system" for the place you live in. As per the smartphones. During the setup I always set it as UTC+1. Should it be the same for aeronautical data?
Timesheet (1) | Timesheet (2) | Timesheet (3) | |||
---|---|---|---|---|---|
timeReference | UTC | timeReference | UTC | timeReference | UTC+1 |
startDate | startDate | startDate | |||
endDate | endDate | endDate | |||
day | WORK_DAY | day | SAT | day | HOL |
dayTil | AFT_WORK_DAY | dayTil | dayTil | AFT_HOL | |
startTime | 00:00 | startTime | 00:00 | startTime | 00:00 |
startEvent | startEvent | startEvent | |||
startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | |||
startEventInterpretation | startEventInterpretation | startEventInterpretation | |||
endTime | 00:00 | endTime | 13:00 | endTime | 00:00 |
endEvent | endEvent | endEvent | |||
endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | |||
endEventInterpretation | endEventInterpretation | endEventInterpretation | |||
dailightSavingAdjust | NO | dailightSavingAdjust | YES | dailightSavingAdjust | NO |
excluded | NO | excluded | NO | excluded | YES |
Ex 12: Mixture of UTC and local time & daylight saving time and non daylight saving time & active by NOTAM
Usual formulation in AIS documents
From SUN 2300(2200) to SAT 1200(1100)
HOL excluded
Moreover SAT 1200-2300(1100-2200) and HOL: active by NOTAM and with upper vertical limit reduced to FL200 only.
Remark
"Moreover SAT 1200-2300(1100-2200) and HOL: active by NOTAM and with upper vertical limit reduced to FL200 only." shall be encoded as a Note associated with the class that owns this schedule and having propertyName="timeInterval". See also page Common coding patterns.
Timesheet (1) | Timesheet (2) | ||
---|---|---|---|
timeReference | UTC | timeReference | UTC+1 |
startDate | startDate | ||
endDate | endDate | ||
day | SUN | day | HOL |
dayTil | SAT | dayTil | AFT_HOL |
startTime | 23:00 | startTime | 00:00 |
startEvent | startEvent | ||
startTimeRelativeEvent | startTimeRelativeEvent | ||
startEventInterpretation | startEventInterpretation | ||
endTime | 12:00 | endTime | 00:00 |
endEvent | endEvent | ||
endTimeRelativeEvent | endTimeRelativeEvent | ||
endEventInterpretation | endEventInterpretation | ||
dailightSavingAdjust | YES | dailightSavingAdjust | NO |
excluded | NO | excluded | YES |
Ex 13 NOTAM schedule - individual dates and date range
NOTAM item D text
11 14 0930-1100 1600-2300, 21-25 0300-0430
It is assumed that the schedule is for October.
Timesheet (1) | Timesheet (2) | Timesheet (3) | Timesheet (4) | Timesheet (5) | |||||
---|---|---|---|---|---|---|---|---|---|
timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC | timeReference | UTC |
startDate | 11-10 | startDate | 11-10 | startDate | 14-10 | startDate | 14-10 | startDate | 21-10 |
endDate | 11-10 | endDate | 11-10 | endDate | endDate | endDate | 25-10 | ||
day | ANY | day | ANY | day | ANY | day | ANY | day | ANY |
dayTil | dayTil | dayTil | dayTil | dayTil | |||||
startTime | 09:30 | startTime | 16:00 | startTime | 09:30 | startTime | 16:00 | startTime | 03:00 |
startEvent | startEvent | startEvent | startEvent | startEvent | |||||
startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | startTimeRelativeEvent | |||||
startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | startEventInterpretation | |||||
endTime | 11:00 | endTime | 23:00 | endTime | 11:00 | endTime | 23:00 | endTime | 04:30 |
endEvent | endEvent | endEvent | endEvent | endEvent | |||||
endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | endTimeRelativeEvent | |||||
endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | endEventInterpretation | |||||
dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO | dailightSavingAdjust | NO |
excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO |