TAF::MeteorologicalAerodromeForecastRecord

: Public Class

Created:	23/05/2012 12:49:11 PM
Modified:	22/06/2015 1:23:06 AM

Project:
Author:	braeckel
Version:	1.0
Phase:	1.0
Status:	Proposed
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{456C95F3-4639-4f2e-89D8-EE24B07C594F}
Appears In:	Context Diagram: MeteorologicalAerodromeForecast

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. 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. Note that the TAC representations for "FM", "TL", and "AT" are represented by the phenomenonTime on the change forecast (MeteorologicalAerodromeForecast): FM and TL - a phenomenonTime with a TimePeriod (start is FM and end is TL) TL - a phenomenonTime with a TimePeriod (start is beginning of forecast validity and end is TL) FM - a phenomenonTime with a TimePeriod (start is FM and end is end of forecast validity) AT - a phenomenonTime with a TimeInstant

Attributes
Associations To
Associations From
Constraints

Attribute

Public AerodromeForecastChangeIndicator
changeIndicator

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

sequenceNumber=1
xsdAsAttribute=true

Notes:

The type of change being reported (FROM, BECOMING, TEMPORARY, etc.).#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;A change indicator is required for all MeteorologicalAerodromeForecastRecords excepting reported base conditions.#lt;br /#gt;#lt;/p#gt;

Public Boolean
cloudAndVisibilityOK

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:
Transient:	False
Derived:	False
IsID:	False

sequenceNumber=2
xsdAsAttribute=true

Notes:

When true, indicates that the observed cloud ceiling, horizontal visibility, and weather conditions are of no operational significance. See ICAO Annex 3 / WMO No. 49-2 Section 2.2. Also known as "CAVOK"#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;When CAVOK conditions are observed, no other information on visibility, runway visual range, present weather, cloud amount, or cloud type is reported#lt;br /#gt;#lt;/p#gt;

Public Distance
prevailingVisibility

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

quantity=http://codes.wmo.int/common/quantity-kind/aeronauticalPrevailingHorizontalVisibility
sequenceNumber=4

Notes:

The prevailing horizontal visibility, mandatory except when ceiling and visibility is reported as OK

Public RelationalOperator
prevailingVisibilityOperator

Details:

Alias:
Initial:
Stereotype:
Ordered:
Range:	Range:0 to 1
Transient:	False
Derived:	False
IsID:	False

Notes:

The reported relational operator for the prevailing horizontal visibility. When reported, this operator is reported in conjunction with prevailing visibility.#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;To report a prevailing visibility of at least 10000 meters, prevailing visibility is reported as 10000 meters and the operator is reported as "above". #lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;When no operator is reported, prevailing visibility represents an exact value with identical semantics to other measured quantities#lt;br /#gt;#lt;/p#gt;

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, are 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") is 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 ) prevailingVisibility == NULL	Invariant	Approved
Details:
if( cloudAndVisibilityOK ) cloud == NULL	Invariant	Approved
Details:
if( cloudAndVisibilityOK ) weather == NULL	Invariant	Approved
Details: