| Table of Contents |
|---|
...
| Data Item | Description | AIXM mapping |
|---|---|---|
| daily | An indication that the time schedule defined further applies every day. | Timesheet.day with the value "ANY" |
| start time | The time of the day (hour and minute) when the period included in the schedule starts. | Timesheet.startTime |
| start event | An event (like sunset or sunrise), the occurrence of which indicates when the period included in the schedule starts. | Timesheet.startEvent with this list of valuesCodeTimeEventType |
| rel. start | A number of minutes indicating the start of the period included in the schedule, relative to the event. | Timesheet.startTimeRelativeEvent and Timesheet.startEventInterpretation |
| end time | The time of the day (hour and minute) when the period included in the schedule ends. | Timesheet.endTime |
| end event | An event (like sunset or sunrise), the occurrence of which indicates when the period included in the schedule ends. | Timesheet.endEvent with this list of valuesCodeTimeEventType |
| rel. end | A number of minutes indicating the end of the period included in the schedule, relative to the event. | Timesheet.endTimeRelativeEvent and Timesheet.endEventInterpretation |
| on date | A specified date of a month that is included in the schedule, such as 02 FEB, 30 JUN, etc. | Timesheet.startDate and Timesheet.endDate Note that both startDate and endDate get the same value. |
| date range | A series of consecutive days of a year that are included in the schedule, such as 02-15 FEB, 23 MAR - 04 APR, etc. | Timesheet.startDate and Timesheet.endDate |
| on weekday | A specified day of the week that is included in the schedule, such as MON, TUE, etc. | Timesheet.day with this list of valuesCodeDayType |
| from weekday | A day of a week that, combined with a start time or event, indicates the start of the period included in the schedule. For example, "From MON 09:00...", etc. | Timesheet.day with this list of valuesCodeDayType |
| to weekday | A day of a week that, combined with an end time or event, indicates the end of the period included in the schedule. For example, "...till FRI 17:00", etc. | Timesheet.day with this list of valuesCodeDayType |
| exc. date | A specified date of a month that is fully excluded from the schedule. | Timesheet.startDate and Timesheet.endDate;in addition, theTimesheet.excluded shall get the value "YES". Note that both startDate and endDate get the same value (see also further data encoding rules). |
| exc. weekday | A specified day of the week that is fully excluded from the schedule. | Timesheet.day with this list of valuesCodeDayType;in addition, theTimesheet.excluded shall get the value "YES". |
...
The TEMPDELTA shall contain the complete definition of the activity times, including any eventual time ranges that are recuperated from the BASELINE schedules. Note that according to the OPADD, notification of a schedule modification by NOTAM shall be done by including the new schedule in item E, not in item D. Therefore, the list of Event Scenarios has to include separate scenarios for such situations.
End of day format
According to ICAO Annex 15, Appendix 6, NOTAM Format, “the end of a day shall be indicated by ‘2359’”. However, in static data (AIP) the end of the day is usually indicated by “2400”. In addition, feedback from developers having used the AIXM Temporality Concept show that using “23:59” as end of day in digital data is problematic because it requires a special interpretation for comparison operators: 23:59:01 is numerically higher than 23:59 and therefore is numerically after the end time. However, in the NOTAM practice, 23:59:01 is still considered inside a time interval that ends at 23:59.
...
.
Data encoding rules
...
The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. The compliance with some of these encoding rules can be checked with automatic data validation rules (see next section).
...