...
| AIP text | Remarks | Timesheet [1] | Timesheet [2] | Timesheet [3] | Timesheet [4] | Timesheet [5] | Timesheet [6] | Timesheet [7] | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| H24 | see Common coding patterns |
| ||||||||||||||||||||||||||||||||||||
AIP Text | timeReference | startDate | endDate | day | dayTil | startTime | startEvent | startTimeRelativeEvent | startEventInterpretation | endTime | endEvent | endTimeRelativeEvent | endEventInterpretation | daylightSavingAdjust | excluded | note purpose | note | Remarks | Encoding rule violations |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0500-2200 (0400-2100) | UTC |
|
| ANY |
| 05:00 |
|
|
| 22:00 |
|
|
| YES | NO |
|
|
|
|
MON-THU 0700-1530 (MON-THU 0600-1430) | UTC | MON | 07:00 | 15:30 | YES | NO | The difference to AIXM 4.5 is, that it is now possible to exclude legal holidays. | ||||||||||||
UTC | TUE | 07:00 | 15:30 | YES | NO | ||||||||||||||
UTC | WED | 07:00 | 15:30 | YES | NO | ||||||||||||||
UTC | THU | 07:00 | 15:30 | YES | NO | ||||||||||||||
UTC | FRI | 07:00 | 11:30 | YES | NO | ||||||||||||||
UTC+1 | HOL | 00:00 | 24:00 | NO | YES | ||||||||||||||
0800-ECET or 2000 if earlier (0700-ECET or 1900 if earlier) | UTC |
|
| ANY |
| 08:00 |
|
|
| 20:00 | SS |
| EARLIEST | YES | NO |
|
| In Austria 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. But the times are published for all 6 major Aerodromes. |
|
MON 0000 - SAT 2400 local time | UTC+1 | MON | SAT | 00:00 | 24:00 | NO | NO | ||||||||||||
UTC+1 | HOL | 00:00 | 24:00 | NO | YES | ||||||||||||||
Active from 1 OCT - 31 JUL | UTC+1 | 01-OCT | 31-JUL | ANY |
| 00:00 |
|
|
| 24:00 |
|
|
| NO | NO |
|
| The problem here is, that there are no times mentioned. Of course it is active H24. But as this is defined by Austrian law the times would be in local time. See comment! |
|
Up to 2500 FT AMSL: MON–FRI 0800-1700 local time | UTC+1 | MON | 08:00 | 17:00 | NO | NO | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | This is a tough one which is not completely solvable because the exception of the legal holidays applies only to a part of the whole time sheet. In AIXM 4.5 I was able to circumvent certain problems using TXT_RMK_WORK_HR. In AIXM 5.1 this can only be solved using notes. I like to avoid notes as they are not supported well in our system, but again this is our problem. | ||||||||||
UTC+1 | TUE | 08:00 | 17:00 | NO | NO | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | ||||||||||||
UTC+1 | WED | 08:00 | 17:00 | NO | NO | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | ||||||||||||
UTC+1 | THU | 08:00 | 17:00 | NO | NO | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | ||||||||||||
UTC+1 | FRI | 08:00 | 17:00 | NO | NO | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | ||||||||||||
UTC+1 | HOL | 08:00 | 17:00 | NO | YES | REMARK | Up to 2500 FT AMSL. Above 2500 FT AMSL effectiveness will be announced by NOTAM. | ||||||||||||
UTC+1 | MON | TUE | 17:00 | 08:00 | NO | NO | REMARK | effectiveness will be announced by NOTAM. | |||||||||||
UTC+1 | TUE | WED | 17:00 | 08:00 | NO | NO | REMARK | effectiveness will be announced by NOTAM. | |||||||||||
UTC+1 | WED | THU | 17:00 | 08:00 | NO | NO | REMARK | effectiveness will be announced by NOTAM. | |||||||||||
UTC+1 | THU | FRI | 17:00 | 08:00 | NO | NO | REMARK | effectiveness will be announced by NOTAM. | |||||||||||
UTC+1 | SAT | SUN | 00:00 | 24:00 | NO | NO | REMARK | effectiveness will be announced by NOTAM. | |||||||||||
Outside of OPS HR of military flight operation office Zeltweg | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | ??? | Outside of OPS HR of military flight operation | 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. |
|
daily BCMT - ECET | UTC | ANY | SR | SS | NO | NO | |||||||||||||
MON-FRI 0800-1600 (0700-1500) | UTC |
|
| MON |
| 08:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| I actually made this one up, but I think that it is a legitimate example. Does a legal holiday automatically overrule a "normal" day? Which template does apply if the legal holiday is a Wednesday? 0800-1600 or 1200-1400? |
|
UTC |
|
| TUE |
| 08:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| WED |
| 08:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| THU |
| 08:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| FRI |
| 08:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| SAT |
| 10:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| SUN |
| 10:00 |
|
|
| 16:00 |
|
|
| YES | NO |
|
| |||
UTC |
|
| HOL |
| 12:00 |
|
|
| 14:00 |
|
|
| YES | NO |
|
| |||
MON-FRI H24 SAT 0001-1300 (2301 - 1200); HOL excluded | UTC | WORK_DAY | 00:00 | 24:00 | NO | NO | This esxample 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? | ||||||||||||
UTC | SAT | 00:01 | 13:00 | YES | NO | ||||||||||||||
UTC+1 | HOL | 00:00 | 24:00 | NO | YES | ||||||||||||||
From SUN 2300(2200) to SAT 1200(1100) | UTC | SUN | SAT | 23:00 | 12:00 | YES | NO | "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". | |||||||||||
UTC+1 | HOL | 00:00 | 24:00 | YES | YES | ||||||||||||||
...