Skip to content

TT AvData Teleconference 2023 Aug 17

Jump to bottom
BL Choy edited this page Jan 23, 2024 · 9 revisions

Details

2023-Aug-17, 12:00-13:00 UTC, Webex

Agenda

  1. Development of IWXXM schemas for VONA and QVA:
  2. Consolidate initial thoughts on the overall layout of future WxObjects.

Notes

  • Some initial consensus with regard to future implementation of WxObject based on MeteorologicalFeature Class:
    • Element PhenomenonProperty:
      • For a single-valued data point simple GML type gml:MeasureType together with schematron rule to mandate the content of attribute uom should be adequate. This is also the current practice in legacy IWXXM reports.
      • The element can also be used to represent a multi-valued data point, or an aggregation of values of the data point with time (i.e. time series) and may be space too. The latter will be useful in future use cases involving high fidelity data, especially under situations where it will be more appropriate to aggregate data into a single MeteorologicalFeature instead of multiple MeteorologicalFeature each with a single value data point.
    • Element originatingCentre:
      • For the scope of IWXXM there may be a need to formalize the representation.
  • With regard to using the MeteorologicalFeature Class to represent a volcano, we may want to start developing such representation based on those elements in VONA and invite Paula to comment before putting it in use in IWXXM VONA and QVA. There is no need for the representation to be comprehensive at the moment, as we can always add new (optional) descriptions at a latter stage.
  • The was also a discussion on BoM's borrowing of the TAC METAR format for reporting MET parameters at waypoints. Both made a note that while the MeteorologicalFeature Class is already flexible in certain aspects, the use of a single format for reporting under different situations may cause confusions. For example, it is possible to use the same MeteorologicalFeature Class specialized for reporting wind to report winds at an aerodrome or aloft over a waypoint, but the consumers may be confused as the latter is not an observation made at surface level with conventional equipment. Therefore while the reporting format could be 'recycled' (to safe implementation cost for example), additional metadata should be included to make sure that the consumers know what the data is actually representing and hence it proper use. This should be revisited in the development of IWXXM-SX.
  • The need to deal with 'holes' in 2D surfaces and 2.5D volumes was discussed. It was noticed that the current 2.5D representation only supports holes that extends from the top to the bottom of the 2.5D volume (or slab). If a hole doesn't get through the slab, there will be a need to make it into two horizontal slabs, one on top of the other, and one with through hole but not the other.

Actions

  • Choy to finalize IWXXM VONA and QVA based on those prepared by Mark and let him review.
  • Mark to provide some insight into possible representation of element phenomenonProperty as well as their use case, like the representation of a time series with TimeseriesML.
  • All to post use cases on the reporting of observational/forecast meteorological parameters to broaden the view of those involved in the design of IWXXM-SX.

Attendees

  • BL Choy
  • Mark Oberfield

Post meeting notes

Timeseries can be represented as below. The gc:rangeType can be as simple or multi-valued as needed.

   <phenomenonProperty>
        <tsml:TimeseriesDomainRange gml:id="uuid.2177b59e-f149-4c32-964c-4e4ea89324c4">
            <gml:domainSet>
                <tsml:TimePositionList gml:id="uuid.dd4b6365-5703-47ca-af2e-831824f3afa2">
                    <tsml:timePositionList>2023-08-18T21:17:00 2023-08-18T21:18:00 2023-08-18T21:19:00 2023-08-18T21:20:00 2023-08-18T21:21:00 2023-08-18T21:22:00
                       2023-08-18T21:23:00 2023-08-18T21:24:00 2023-08-18T21:25:00 2023-08-18T21:26:00 2023-08-18T21:27:00</tsml:timePositionList>
                </tsml:TimePositionList>
            </gml:domainSet>
            <gml:rangeSet>
                <gml:QuantityList uom="deg">123 127 125 122 124 128 127 125 132 124</gml:QuantityList>
                <gml:QuantityList uom="m/s">5.1 6.0 5.9 6.7 6.6 8.0 4.5 4.3 5.1 5.2</gml:QuantityList>
                <!-- 
                     etc. etc.
                   -->
            </gml:rangeSet>
            <!-- gc:rangeType can refer to a external resource that describes this time series, OR
                 use swe:DataRecord to describe the TS inline as shown here -->
            <gc:rangeType>
                <swe:DataRecord>
                    <swe:field name="windDirection">
                        <swe:Text>
                            <swe:description>Instantaneous wind direction at 10 metres AGL</swe:description>
                        </swe:Text>
                    </swe:field>
                    <swe:field name="windSpeed">
                        <swe:Text>
                            <swe:description>Instantaneous wind speed at 10 metres AGL</swe:description>
                        </swe:Text>                        
                    </swe:field>
                </swe:DataRecord>
            </gc:rangeType>
        </tsml:TimeseriesDomainRange>
    </phenomenonProperty>

... go to TT-AvData Homepage on WMO Community website

Clone this wiki locally