==== Basic selection criteria area ==== All selection criteria specifications are logically connected with an AND-operator to one requirement on the flight plan data selection. When a flight meets this requirement it is included in the new flight-set. Within one selection criterion specification, multiple data values are logically connected with an OR-operator. Often, it is possible to exclude (instead of include) certain values using the NOT-button. Within the basic selection criteria area, 3 parts can be distinguished: * Time/day selection entries where the time/day criteria must be specified. [[Image:QueryPanel_timeselect.png|left]] With the option button, the time zone can be selected. Values are LT and UTC. Default value is UTC. This option defines only the date and time fields within the query panel. So if LT is selected, the flights will be selected within the LT range from LT start till LT end time. How date and time values are shown in the GUI as well as print-outs is determined by the Fanomos Preferences. The 4 input fields contain the specification of the required period of time; i.e. the starting date/time and the end date/time using the date- and time-input fields. Default period: ‘Today’ 00:00:00 to ‘Today’ 23:59:59. The example in the above picture depicts the UTC time period between 00 and 23 hour on August 9, 2009. * Time-of-day sub-selection entries, where a part of a day can be included (or excluded) in the selection. [[Image:QueryPanel_subtimeofdayselect.png|left]] The option button indicates whether the time-range specified must be excluded ([[Image:delete.png|16px]] option) or included (([[Image:add.png|16px]] option). Two time-input fields can be used to specify the time range that is involved in the sub-selection. The default is ‘No sub-selection at all’ depicted at time 00:00:00 TO 23:59:59 and a blank option menu entry. The example before shows the exclusion of all flights between 0 and 6 hour. * Logic expression In almost all field it is allowed to use logical expression (NOT,AND,OR). For example a callsign field entry, ''(DLH* OR LOT*) AND NOT DLH07*'' Please note there some exceptions; * Runway and Route fields: These fields don't support the NOT operator due to database constrains, in the advanced parameters panel there are four fields "Arr. Runway" (Arrival runway), "Dep. Runway" (Departure runway), "Arr. Route" (Arrival route) and "Dep. Route" (Depature route). With these fields the same effect can be reached. * Basic parameter entries. [[Image:BasicParameters4Q2012.png|left]] All entries relate to the flight plan data of a flight. The entries are character type input fields and sometimes supported via drop-down lists (e.g. routes, runways). Some of the entries contain a NOT-button to exclude the values. For all entries applies ALL as default value. '''Restrictions:''' The meaning of the Airport-entry depends on the chosen option in the FlightType entry. When FlightType is Departure, the Airport refers to the origin airport of the flight. FlightType is Arrival means that the Airport is considered to be the destination airport of the flight. The same applies for Runway and Route. The Airport entry is a single value input field. Next to the basic selection criteria as described in this paragraph, an additional set of selection criteria can be used.
Edit Comment:
Minor Edit
