Panel | ||
---|---|---|
| ||
|
Warning | ||
---|---|---|
| ||
These examples were initially provided by Steffen Siegl (Austrocontrol) in the form of an Excel sheet. They need to be reviewed and checked for compliance with the latest version of the coding rules for schedules. Also, the table needs to be re-formatted in order to fit better in Confluence. A new table structure is proposed above the original table. Proposal:
|
Info | ||
---|---|---|
| ||
See also Common coding patterns |
EX 1: H24
Tip | ||
---|---|---|
| ||
H24 |
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTill | ANY |
startTime | 00:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 00:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- H24 encoding --> <aixm:Timesheet gml:id="EX1-1"> <aixm:timeReference>UTC</aixm:timeReference> <aixm:day>ANY</aixm:day> <aixm:dayTil>ANY</aixm:dayTil> <aixm:startTime>00:00</aixm:startTime> <aixm:endTime>00:00</aixm:endTime> <aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust> <aixm:excluded>NO</aixm:excluded> </aixm:Timesheet> |
EX 2: Time period for daily & daylight saving applied
Tip | ||
---|---|---|
| ||
0500-2200 (0400-2100) |
Timesheet (1) | |
---|---|
timeReference | UTC |
startDate | |
endDate | |
day | ANY |
dayTill | |
startTime | 05:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 22:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | YES |
excluded | NO |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- 0500-2200 (0400-2100) -->
<aixm:Timesheet gml:id="EX2-1">
<aixm:timeReference>UTC</aixm:timeReference>
<aixm:day>ANY</aixm:day>
<aixm:startTime>05:00</aixm:startTime>
<aixm:endTime>22:00</aixm:endTime>
<aixm:daylightSavingAdjust>YES</aixm:daylightSavingAdjust>
<aixm:excluded>NO</aixm:excluded>
</aixm:Timesheet> |
EX 3: Except legal holidays
Tip | ||
---|---|---|
| ||
MON-THU 0700-1530 (MON-THU 0600-1430) |
Info | ||
---|---|---|
| ||
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 |
dayTill | dayTill | dayTill | dayTill | dayTill | dayTill | AFT_HOL | |||||
startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 07:00 | startTime | 0700: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 | 1500:3000 |
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 | YESNO |
excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO | excluded | NO |
EX 4: If earlier
Tip | ||
---|---|---|
| ||
0800-ECET or 2000 if earlier (0700-ECET or 1900 if earlier) |
Info | ||
---|---|---|
| ||
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. But the times are published for all 6 major Aerodromes. |
timeReference
UTC
startDate
endDate
day
ANY
dayTill
startTime
08:00
startEvent
startTimeRelativeEvent
startEventInterpretation
endTime
20:00
endEvent
endTimeRelativeEvent
endEventInterpretation
dailightSavingAdjust
YES
excluded
NO
language | xml |
---|---|
title | XML Snippet |
collapse | true |
YES |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- MON-THU 0700-1530 (MON-THU 0600-1430), FRI 0700-1130 (FRI 0600-1030), except legal holidays --> <aixm:Timesheet gml:id="EX3-1"> <aixm:timeReference>UTC</aixm:timeReference> <aixm:day>ANY<day>MON</aixm:day> <aixm:startTime>08startTime>07:00</aixm:startTime> <aixm:endTime>20endTime>15:00<30</aixm:endTime> <aixm:endEvent>SS<daylightSavingAdjust>YES</aixm:endEvent>daylightSavingAdjust> <aixm.endEventInterpretation>EARLIEST<:excluded>NO</aixm.endEventInterpretation>:excluded> <aixm:daylightSavingAdjust>YES<</aixm:daylightSavingAdjust>Timesheet> <aixm:Timesheet gml:id="EX3-2"> <aixm:excluded>NO<timeReference>UTC</aixm:excluded>timeReference> <<aixm:day>TUE</aixm:Timesheet> |
EX 5: Continuous from Monday to Saturday & local time
Tip | ||
---|---|---|
| ||
MON 00:00 - SAT 24:00 local time, except legal holidays. |
timeReference
UTC+1
timeReference
UTC+1
startDate
startDate
endDate
endDate
day
MON
day
HOL
dayTill
SUN
dayTill
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
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- MON 00:00 - SAT 24:00; local time; except legal holiday -->day> <aixm:startTime>07:00</aixm:startTime> <aixm:endTime>15:30</aixm:endTime> <aixm:daylightSavingAdjust>YES</aixm:daylightSavingAdjust> <aixm:excluded>NO</aixm:excluded> </aixm:Timesheet> <aixm:Timesheet gml:id="id03EX3-13"> <aixm:timeReference>UTC+1<timeReference>UTC</aixm:timeReference> <aixm:startDate>01-01<day>WED</aixm:startDate>day> <aixm:endDate>31-12<startTime>07:00</aixm:endDate>startTime> <aixm:endTime>15:day>MON<30</aixm:day>endTime> <aixm:dayTil>SUN<daylightSavingAdjust>YES</aixm:dayTil>daylightSavingAdjust> <aixm:startTime>00:00<excluded>NO</aixm:startTime>excluded> <aixm:endTime>00:00<</aixm:endTime>Timesheet> <aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust><aixm:Timesheet gml:id="EX3-4"> <aixm:excluded>NO<timeReference>UTC</aixm:excluded>timeReference> </aixm:Timesheet> <aixm:Timesheet gml:id="id03-2">day>THU</aixm:day> <aixm:timeReference>UTC+1<startTime>07:00</aixm:timeReference>startTime> <aixm:endTime>15:startDate>01-01<30</aixm:startDate>endTime> <aixm:endDate>31-12<daylightSavingAdjust>YES</aixm:endDate>daylightSavingAdjust> <aixm:day>HOL<excluded>NO</aixm:day>excluded> <aixm:dayTil>AFT_HOL<</aixm:dayTil>Timesheet> <aixm:Timesheet gml:id="EX3-5"> <aixm:startTime>00 <aixm:timeReference>UTC</aixm:timeReference> <aixm:day>FRI</aixm:day> <aixm:startTime>07:00</aixm:startTime> <aixm:endTime>00endTime>11:00<30</aixm:endTime> <aixm:daylightSavingAdjust>NO<daylightSavingAdjust>YES</aixm:daylightSavingAdjust> <aixm:excluded>YES<excluded>NO</aixm:excluded> </aixm:Timesheet> |
EX 6: Continuos between date period
Tip | ||
---|---|---|
| ||
Active from 1 OCT - 31 JUL |
Info | ||
---|---|---|
| ||
Remark: 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! |
timeReference
UTC+1
startDate
endDate
day
ANY
dayTill
ANY
startTime
00:00
startEvent
startTimeRelativeEvent
startEventInterpretation
endTime
00:00
endEvent
endTimeRelativeEvent
endEventInterpretation
dailightSavingAdjust
NO
excluded
NO
EX 7: Announced by NOTAM
Tip | ||
---|---|---|
| ||
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. |
Info | ||
---|---|---|
| ||
Remark: 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. Does an exception for a legal holiday always have to be from 00:00-24:00 or can this be limited like in this case from 08:00-17:00? |
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
timeReference
UTC+1
startDate
startDate
startDate
startDate
startDate
startDate
startDate
startDate
startDate
startDate
startDate
endDate
endDate
endDate
endDate
endDate
endDate
endDate
endDate
endDate
endDate
endDate
day
MON
day
TUE
day
WED
day
THU
day
FRI
day
HOL
day
MON
day
TUE
day
WED
day
THU
day
SAT
dayTill
dayTill
dayTill
dayTill
dayTill
dayTill
dayTill
TUE
dayTill
WED
dayTill
THU
dayTill
FRI
dayTill
MON
startTime
08:00
startTime
08:00
startTime
08:00
startTime
08:00
startTime
08:00
startTime
08:00
startTime
17:00
startTime
17:00
startTime
17:00
startTime
17:00
startTime
00:00
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startTimeRelativeEvent
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
startEventInterpretation
endTime
17:00
endTime
17:00
endTime
17:00
endTime
17:00
endTime
17:00
endTime
17:00
endTime
08:00
endTime
08:00
endTime
08:00
endTime
08:00
endTime
00:00
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endTimeRelativeEvent
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
endEventInterpretation
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
dailightSavingAdjust
NO
excluded
NO
excluded
NO
excluded
NO
excluded
NO
excluded
NO
excluded
YES
excluded
NO
excluded
NO
excluded
NO
excluded
NO
excluded
NO
EX 8: Outside OPS HR
Tip | ||
---|---|---|
| ||
Outside of OPS HR of military flight operation office Zeltweg |
Info | ||
---|---|---|
| ||
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. |
timeReference
???
startDate
endDate
day
???
dayTill
???
startTime
???
startEvent
startTimeRelativeEvent
startEventInterpretation
endTime
???
endEvent
endTimeRelativeEvent
endEventInterpretation
dailightSavingAdjust
???
excluded
???
office Zeltweg.
EX 9: Daily from SR (BCMT) - SS (ECET)
Tip | ||
---|---|---|
| ||
daily BCMT - ECET |
timeReference
UTC
startDate
endDate
day
dayTill
ANY
startTime
startEvent
startTimeRelativeEvent
startEventInterpretation
endTime
endEvent
endTimeRelativeEvent
endEventInterpretation
dailightSavingAdjust
excluded
<aixm:Timesheet gml:id="EX3-6">
<aixm:timeReference>UTC+1</aixm:timeReference>
<aixm:day>HOL</aixm:day>
<aixm:daTill>AFT_HOL</aixm:daTill>
<aixm:startTime>00:00</aixm:startTime>
<aixm:endTime>00:00</aixm:endTime>
<aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust>
<aixm:excluded>YES</aixm:excluded>
</aixm:Timesheet> |
EX 4: If earlier
Tip | ||
---|---|---|
| ||
0800-SS or 2000 if earlier (0700-SS or 1900 if earlier) |
Info | ||
---|---|---|
| ||
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 |
dayTill | |
startTime | 08:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 20:00 |
endEvent | SS |
endTimeRelativeEvent | |
endEventInterpretation | EARLIEST |
dailightSavingAdjust | YES |
excluded | NO |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<aixm:Timesheet gml:id="EX4-1">
<aixm:timeReference>UTC</aixm:timeReference>
<aixm:day>ANY</aixm:day>
<aixm:startTime>08:00</aixm:startTime>
<aixm:endTime>20:00</aixm:endTime>
<aixm:endEvent>SS</aixm:endEvent>
<aixm:endEventInterpretation>EARLIEST</aixm:endEventInterpretation>
<aixm:daylightSavingAdjust>YES</aixm:daylightSavingAdjust>
<aixm:excluded>NO</aixm:excluded>
</aixm:Timesheet> |
EX 5: Continuous from Monday to Saturday & local time
Tip | ||
---|---|---|
| ||
MON 00:00 - SAT 24:00 local time, except legal holidays. |
Timesheet (1) | Timesheet (2) | ||
---|---|---|---|
timeReference | UTC+1 | timeReference | UTC+1 |
startDate | startDate | ||
endDate | endDate | ||
day | MON | day | HOL |
dayTill | SUN | dayTill | 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 |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- MON 00:00 - SAT 24:00; local time; except legal holiday -->
<aixm:Timesheet gml:id="EX5-1">
<aixm:timeReference>UTC+1</aixm:timeReference>
<aixm:day>MON</aixm:day>
<aixm:dayTil>SUN</aixm:dayTil>
<aixm:startTime>00:00</aixm:startTime>
<aixm:endTime>00:00</aixm:endTime>
<aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust>
<aixm:excluded>NO</aixm:excluded>
</aixm:Timesheet>
<aixm:Timesheet gml:id="EX5-2">
<aixm:timeReference>UTC+1</aixm:timeReference>
<aixm:day>HOL</aixm:day>
<aixm:dayTil>AFT_HOL</aixm:dayTil>
<aixm:startTime>00:00</aixm:startTime>
<aixm:endTime>00:00</aixm:endTime>
<aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust>
<aixm:excluded>YES</aixm:excluded>
</aixm:Timesheet> |
EX 6: Continuos between date period
Tip | ||
---|---|---|
| ||
Active from 1 OCT - 31 JUL |
Info | ||
---|---|---|
| ||
Remark: 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! |
Timesheet (1) | |
---|---|
timeReference | UTC+1 |
startDate | 01-OCT |
endDate | 31-JUL |
day | ANY |
dayTill | ANY |
startTime | 00:00 |
startEvent | |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | 00:00 |
endEvent | |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- Active from 1 OCT - 31 JUL -->
<aixm:Timesheet gml:id="EX6-1">
<aixm:timeReference>UTC</aixm:timeReference>
<aixm:startDate>01-10</aixm:startDate>
<aixm:endDate>31-07</aixm:endDate>
<aixm:day>ANY</aixm:day>
<aixm:dayTil>ANY</aixm:dayTil>
<aixm:startTime>00:00</aixm:startTime>
<aixm:endTime>00:00</aixm:endTime>
<aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust>
<aixm:excluded>NO</aixm:excluded>
</aixm:Timesheet> |
EX 7: Announced by NOTAM
Tip | ||
---|---|---|
| ||
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. |
Info | ||
---|---|---|
| ||
This has to be coded as two different schedules each concerning a level band (e.g. as AirspaceActivation for 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 |
dayTill | dayTill | dayTill | dayTill | dayTill | dayTill | ||||||
startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08:00 | startTime | 08: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 | 17: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
Tip | ||
---|---|---|
| ||
Outside of OPS HR of military flight operation office Zeltweg |
Info | ||
---|---|---|
| ||
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. |
Timesheet (1) | |
---|---|
timeReference | ??? |
startDate | ??? |
endDate | ??? |
day | ??? |
dayTill | ??? |
startTime | ??? |
startEvent | ??? |
startTimeRelativeEvent | ??? |
startEventInterpretation | ??? |
endTime | ??? |
endEvent | ??? |
endTimeRelativeEvent | ??? |
endEventInterpretation | ??? |
dailightSavingAdjust | ??? |
excluded | ??? |
Note.purpose | REMARK |
Note//note | Outside of OPS HR of military flight operation office Zeltweg. |
EX 9: Daily from SR - SS
Tip | ||
---|---|---|
| ||
daily SR - SS |
Info | ||
---|---|---|
| ||
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 | |
dayTill | ANY |
startTime | |
startEvent | SR |
startTimeRelativeEvent | |
startEventInterpretation | |
endTime | |
endEvent | SS |
endTimeRelativeEvent | |
endEventInterpretation | |
dailightSavingAdjust | NO |
excluded | NO |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<aixm:Timesheet gml:id="EX-9-1">
<aixm:timeReference>UTC</aixm:timeReference>
<aixm:day>ANY</aixm:day>
<aixm:startEvent>SR</aixm:startEvent>
<aixm:endEvent>SS</aixm:endEvent>
<aixm:daylightSavingAdjust>NO</aixm:daylightSavingAdjust>
<aixm:excluded>NO</aixm:excluded>
</aixm:Timesheet> |
EX 10: Legal Holiday
Tip | ||
---|---|---|
| ||
MON-FRI 0800-1600 (0700-1500) SAT, SUN 1000-1600 (0900-1500) Legal holiday 1200-1400 (1100-1300) |
Info | ||
---|---|---|
| ||
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? |
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 |
dayTill | dayTill | dayTill | dayTill | dayTill | dayTill | dayTill | dayTill | ||||||||
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 | YES | excluded | NO | excluded | NO |
EX 11: Mixture of UTC and local time & daylight saving time and non daylight saving time
Tip | ||
---|---|---|
| ||
MON-FRI H24 SAT 0001-1300 (2301 - 1200); HOL excluded |
Info | ||
---|---|---|
| ||
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 |
dayTill | AFT_WORK_DAY | dayTill | dayTill | AFT_HOL | |
startTime | 00:00 | startTime | 00:01 | 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
Tip | ||
---|---|---|
| ||
From SUN 2300(2200) to SAT 1200(1100) |
Info | ||
---|---|---|
| ||
"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" |
Timesheet (1) | Timesheet (2) | ||
---|---|---|---|
timeReference | UTC | timeReference | UTC+1 |
startDate | startDate | ||
endDate | endDate | ||
day | SUN | day | HOL |
dayTill | SAT | dayTill | 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 |
AIP Text | timeReference | startDate | endDate | day | dayTil | startTime | startEvent | startTimeRelativeEvent | startEventInterpretation | endTime | endEvent | endTimeRelativeEvent | endEventInterpretation | daylightSavingAdjust | excluded | note purpose | note | Remarks | Encoding rule violations |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 |