: Public Class
Created: 23/05/2012 12:49:11 PM
Modified: 27/03/2013 3:22:54 PM
Project:
Advanced:
A specialized Record type containing meteorological conditions forecast at an aerodrome.  This class is also related but not identical to MeteorologicalAerodromeTrendForecastRecord, which is reported on a METAR/SPECI - conditions reported in trend forecasts in METAR/SPECI differ from forecast groups in a TAF.<br /></p><p><br /></p><p>When no clouds of operational significance or no weather of operational significance is predicted, the nothingOfOperationalSignificance nilReason should be used for the cloud or presentWeather association.  <br /></p><p><br /></p><p>Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast):<br /></p><p>    FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL)<br /></p><p>    TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL)<br /></p><p>    FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity)<br /></p><p>    AT - a phenomenonTime with a TimeInstant<br /></p>
Element Source Role Target Role
«DataType» AerodromeAirTemperatureForecast
Class   		Name:  
  		Name: temperature
 
Details:
Minimum and maximum temperatures observed at specific times, consisting of up to a maximum of four temperatures (two maximum temperatures and two minimum temperatures).<br /></p><p><br /></p><p>Due to Note 9 on Table A5-1: "consisting of up to a maximum of four temperatures (two maximum temperatures and two minimum temperatures)", there can be up to two temperature groups on each MeteorologicalAerodromeForecastRecord.  It is possible that Annex 3 instead specifies four temperatures for the entire TAF but no more than one for each Record, in which case this association would need to be corrected to be 0..1 and a constraint on TAF would need to be put in place to ensure that no more than two temperature forecast groups exist on any single TAF.<br /></p>
«CodeList» AerodromeForecastWeather
Class   		Name:  
  		Name: weather
 
Details:
Weather phenomenon: characteristics and type.  To be included whenever applicable.<br /></p><p><br /></p><p>One or more, up to a maximum of three weather phenomena or combinations thereof, together with their characteristics and, where appropriate, intensity, shall be forecast if they are expected to occur at the aerodrome<br /></p><p><br /></p><p>The expected end of occurrence of weather phenomena ("NSW") shall be indicated by a change forecast with a missing weather group with a nil reason of nothingOfOperationalSignificance<br /></p>
AerodromeCloudForecast
Class   		Name:  
  		Name: cloud
 
Details:
Cloud phenomenon of operational significance, including cloud type and cloud layers.  To be included whenever applicable, so as to convey a complete description of the clouds of significance to flight operations.<br /></p><p><br /></p><p>When no clouds of operational significance are forecast and “CAVOK” is not appropriate ("NSC") it should be indicated by a missing cloud group with a nil reason of nothingOfOperationalSignificance<br /></p>
AerodromeSurfaceWindForecast
Class   		Name:  
  		Name: surfaceWind
 
Details:
 
Element Source Role Target Role
«FeatureType» MeteorologicalAerodromeForecast
Class   		Name:  
  		Name: result
 
Details:
 
Constraint Type Status
if( cloudAndVisibilityOK ) prevailingHorizontalVisibility == NULL Invariant Approved
Details:
 
if( cloudAndVisibilityOK ) cloud == NULL Invariant Approved
Details:
 
if( cloudAndVisibilityOK ) weather == NULL Invariant Approved
Details: