namespace | http://www.fixm.aero/app/ffice/1.0 | ||||||||||||||||||
type | restriction of xs:string | ||||||||||||||||||
properties |
|
||||||||||||||||||
used by |
|
||||||||||||||||||
facets |
|
||||||||||||||||||
annotation |
|
||||||||||||||||||
source | <xs:simpleType name="PlanningStatusValueType"> <xs:annotation> <xs:documentation>The applicable planning status values (CONCUR, NON_CONCUR, NEGOTIATE) of the route and trajectory, as submitted. [FF-ICE]</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="CONCUR"> <xs:annotation> <xs:documentation>The flight plan and in particular the route and trajectory is acceptable without the need for modification. This should mean that if the flight plan were to be filed, it would be accepted. [FF-ICE]</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="NON_CONCUR"> <xs:annotation> <xs:documentation>The flight plan does not comply with published airspace/route availability or published restrictions and would result in a rejection or an unacceptable status if the flight plan were to be filed. [FF-ICE]</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="NEGOTIATE"> <xs:annotation> <xs:documentation>The flight plan and in particular the route and trajectory is acceptable and would be accepted if filed. However the trajectory determined by the eASP has included additional constraints and/or has applied ATM configuration factors such as runway-in-use or Met data which may have resulted in a different trajectory. The operator is expected to assess the feedback and determine whether or not it wishes to amend it's Desired trajectory. [FF-ICE]</xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> |