185
edits
AI Traffic: Difference between revisions
m
→Tools: capitalize proper names
(→Tools: time examples with UTC offsets) |
m (→Tools: capitalize proper names) |
||
| Line 264: | Line 264: | ||
Note that the flight information laid out above resembles that of a standard airline schedule table as close as possible, with a few known exceptions: | Note that the flight information laid out above resembles that of a standard airline schedule table as close as possible, with a few known exceptions: | ||
- Weekdays are in the range 0 to 6, but do follow standard airline conventions (0 = | - Weekdays are in the range 0 to 6, but do follow standard airline conventions (0 = Monday; 6 is Sunday) | ||
- All times in the table are in UTC; to convert from local time, as given in the airline table, subtract the airport in question's UTC offset. eg: KJFK is UTC-0400 so a flight leaving at 20:00 local New York time is written as 00:00 UTC. EHAM is UTC+1 so a flight leaving EHAM at 20:00 local Amsterdam time is written as 21:00 UTC. | - All times in the table are in UTC; to convert from local time, as given in the airline table, subtract the airport in question's UTC offset. eg: KJFK is UTC-0400 so a flight leaving at 20:00 local New York time is written as 00:00 UTC. EHAM is UTC+1 so a flight leaving EHAM at 20:00 local Amsterdam time is written as 21:00 UTC. | ||
- The last entry in each line (A/C type) should correspond to the ''combination'' of the '''TypeCode''' and '''Airline''' entries in the aircraft sections. | - The last entry in each line (A/C type) should correspond to the ''combination'' of the '''TypeCode''' and '''Airline''' entries in the aircraft sections. | ||