AMOIS and AMFIS Discussion 2026 09 16 - team-sx/iwxxm-sx GitHub Wiki

Details

2026-Sep-16, 11:00-12:00 UTC, Webex

Agenda

  1. Recap of last discussion:

    • Updated iwxxm:MeteorologicalFeature making reference to a ROI: 
      <iwxxm:MeteorologicalFeature>
   <gml:identifier ... />
   <iwxxm:phenomenonCategory />
   <iwxxm:phenomenonTime />
   <iwxxm:phenomenon />
   <iwxxm:phenomenonRegionOfInterest />
   <iwxxm:phenomenonProperty />
</iwxxm:MeteorologicalFeature>
    • ROI should refer to the location (or more specifically the observed coverage) where the observation is being made
    • Consumers are expected to decide which of these observations are applicable to their use case, but hints on the locations an observation is applicable (e.g. TDZ) may be useful?
    • AMOIS for an aerodrome is essentially a cluster of observations made at or in the vicinity of (i.e. having a close relationship with) an aerodrome. Ditto for AMFIS.
    • There exist use cases where it is required to report a cluster of observations at a location at a significant distance from an aerodrome, but this cluster of observations are also related (but not so closely) to an aerodrome because "flight crews make key operational decisions before continuing to one or more destination aerodromes"

  2. Possible representation (focus on the information, not the structure or naming)

    • Example 1: Wind observed near TDZ of a runway 
      <iwxxm:MeteorologicalFeature>
   <iwxxm:phenomenonRegionOfInterest>   
      <iwxxm:phenomenonROICommonName />   <-- Name/handle of observation
      <iwxxm:phenomenonROIGeometry />   <-- Location of observation/measuring coverage of observation
   </iwxxm:phenomenonRegoinOfInterest>
   <iwxxm:phenomenonProperty />   <-- Actual observation
   <iwxxm:Reference />   <-- Reference aerodrome
   <iwxxm:AeronauticalFeature />   <-- Hints on application aeronautical features like runway section, etc.
</iwxxm:MeteorologicalFeature>
    • Example 2: Ashwin's remote observation 
      <iwxxm:MeteorologicalFeature>
   <iwxxm:phenomenonRegionOfInterest>   
      <iwxxm:phenomenonROICommonName />   <-- Name/handle of observation
      <iwxxm:phenomenonROIGeometry />   <-- Location of observation/measuring coverage of observation
   </iwxxm:phenomenonRegoinOfInterest>
   <iwxxm:phenomenonProperty />   <-- Actual observation
   <iwxxm:Reference />   <-- Reference location
   <iwxxm:Related />   <-- Related aerodrome
</iwxxm:MeteorologicalFeature>

  3. Checking with real-life example

    • Example 3: Wind observed at the centre of the aerodrome 
      <iwxxm:MeteorologicalFeature>
   <iwxxm:phenomenonRegionOfInterest>   
      <iwxxm:phenomenonROICommonName>R2C</iwxxm:phenomenonROICommonName>
      <iwxxm:phenomenonROIGeometry>
         <iwxxm:ElevatedPoint />
      </iwxxm:phenomenonROIGeometry>
   </iwxxm:phenomenonRegoinOfInterest>
   <iwxxm:phenomenonProperty />   <-- Actual observation
   <iwxxm:Reference>VHHH</iwxxm:Reference>
   <iwxxm:AeronauticalFeature>VHHH, VHHH-RWY09C-MID, VHHH-RWY27C-MID</iwxxm:AeronauticalFeature>
</iwxxm:MeteorologicalFeature>
    • Example 4: Wind observed at the upper right hand corner of the aerodrome (also served as the third in the list of aerodromes for VHHH) 
      <iwxxm:MeteorologicalFeature>
   <iwxxm:phenomenonRegionOfInterest>   
      <iwxxm:phenomenonROICommonName>R3E</iwxxm:phenomenonROICommonName>
      <iwxxm:phenomenonROIGeometry>
         <iwxxm:ElevatedPoint />
      </iwxxm:phenomenonROIGeometry>
   </iwxxm:phenomenonRegoinOfInterest>
   <iwxxm:phenomenonProperty />   <-- Actual observation
   <iwxxm:Reference>VHHH</iwxxm:Reference>
   <iwxxm:AeronauticalFeature>VHHH (Priority 3), VHHH-RWY09L-END, VHHH-RWY27R-TDZ</iwxxm:AeronauticalFeature>
</iwxxm:MeteorologicalFeature>

  4. Discussion points:

    • Need for a name/handle for the observation
    • The way the aerodrome involved is referenced
    • The need to mention a related aerodrome (Ashwin's wish)
    • The need to give hints on applicable locations, and priority (if available)

Notes

  • For AMOIS, participants noted that "Region of Interest" or ROI will now be the location/coverage where the observation is made, albeit they have reservation whether the phrase "Region Of Interest" is the most appropriate one to use.
  • For AMFIS, the ROI will continue to be the location/coverage where consumers want to know its weather conditions.
  • While the intention is to let the consumer choose the most suitable observations to infer the weather conditions at a target location/coverage, it may be useful for the producer to give hints to each observation applicable target locations/coverages which are most likely to be aeronautical features like TDZ. Since participants have no reaction on this arrangement, we may want to continue its development to showcase its usefulness.
  • Since each WxObject (no matter an observation in AMOIS or a forecast in AMFIS) now has a tag referencing an aerodrome, this tag (together with others like time and location/coverage) can be used as a key to retrieve all observations and/or forecasts for that aerodrome.
  • For AMOIS and AMFIS this tag should naturally be an AIXM AirportHeliport object. If this could be relaxed to allow for use with other geophysical objects (for example a significant point) the same format may be reused for other use case like BoM's. Yet more discussion will have to be made (e.g. can the resulting object be treated as AMOIS or AMFIS?)

Decision and Action

To kick start the discussion on property presentation of observations in the next meeting.

Next Meeting

30 Sep 2026

Attendees

Attendees from TT-AvData, WG-MIE and WG-MRAD

Name (Affiliation) Attendance
Rosalind Lapsley (EUROCONTROL) X
Dirk Zinkhan (DWD) X
Svenja Koos (DWD)
Joonas Eklund (FMI) X
Anu Lång (FMI)
Rauhala Mikko (FMI)
Ilkka Rinne (FMI) X
Terhi Nikkanen (FMI)
Ashwin Naidu (BoM) X
Patrick Desgagnes (NAVCAN) X
Tom Helms (FAA) X
Michiko Ikeda (JMA) X
Jan Korosi (IBL) X
JJ Biel-Goebel (WISK) X
Paul Hershberg (NOAA)
BL Choy (HKO) X