-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List of Application Areas #438
Comments
As discussed in my previous message, the current list of ESACs and AAs is available here: Evolved RRR Process 2022 - Lit of ESACs and AAs - post INFCOM-2-v1.0.docx |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@amilan17 @echarpent
|
@echarpent Do you have a mapping of the old to new application areas? |
initial mapping exercise: |
https://github.com/wmo-im/tt-wigosmd/wiki/2023.02.16-TT-WIGOSMD notes: discussion: Superseding current codes by mapping is difficult, because there one to many, many to one, many to many mappings. It may be more efficient to replace the entire list with a new one. Kruno will collaborate with us on this. |
@amilan17 : Please set up meeting with Etienne, Kruno, Tom Kralidis (because of WIS topic hierarchy) and myself to discuss this and agree a way forward. Suggestions: 28 March or 30 March. Thanks. |
The list of approved application areas is now online: https://space.oscar.wmo.int/applicationareas |
@amilan17 @joergklausen |
The list of ESACs and AAs is a part of the Manual on WIGOS, recently approved by EC. INFCOM-MG is supposed to approve ESAC/AAs owners, together with the proposed PoCs, at their meeting in 2 weeks. Then the owners/PoCs should work on the population of AAs (description, variables, requirements, etc). |
@kpremec @joergklausen @amilan17 |
https://github.com/wmo-im/tt-wigosmd/wiki/2023-03-17-TT-WIGOSMD notes: |
@joergklausen I will look at setting up a meeting next week, because this week is very busy. |
|
@amilan17 Thanks for sharing this table. I understand our role here to make sure that we have an unambigous notation for each of the 'New Application Areas' (column 3). The (now) existing ambiguities therefore need to be removed and a few new notations are needed to supersede some of the existing ones (example; cryosphere). It seems, some of our existing notations also need to be combined. I have the following comments wrt the mapping between columns 2 and 3:
My personal perception is Global NWP goes beyond Atmospheric Applicaions, hence, I would propose to list this under "6. Integrated Earth System Applications"
I would propose to list this under "3. Oceanic Applications" Please confirm the status of columns 2 and 3 in this table (approved?, under discussion?) We can then begin to work on the notations. |
@joergklausen @amilan17 . Global NWP is an atmospheric application because the focus is on APPLICATION - the principle aim of global NWP is to forecast the weather. In order to do so, it needs to model and use observations from several areas of the Earth System (="Domains" in our language). But this is true of most Application Areas. So my criticism is the opposite - I have questioned the need for an Application Area called Earth System Forecasting and Monitoring, because I do not recognise this as an application - it is a method, and an increasingly common method, for many Application Areas. Other Application Areas should be understood from the same perspective - what is the APPLICATION? - it is only through understanding the APPLICATION that you can understand the requirements for observations - some Application Areas that use common Earth System models have different requirements for observations because their applications are different. |
Hi @JREyre Indeed, I can share this perspective on things. With that in mind, I step back from my earlier suggestion for GNWP. However, I can also see Earth System Forecasting and Monitoring as an application, an integration of the other more domain-focused applications, and where the focus is more on the interface, i.e., the energy and material fluxes. |
These code values are not used in OSCAR/Surface interface for filtering and searching and there isn't an input field for this code in the metadata forms. @fstuerzl Do you know if there are XML records with applicationarea element populated? |
@amilan17 I would not expect observing system owners to understand all the Application Areas in which their observations were used or might be used. Ideally they should, if they have gone through the WIGOS-recommended network design process, but in practice they won't. In fact you could argue that one of the main purposes of WIGOS is to make observations from all observing systems potentially available for all WMO applications. I don't see any value in the observation data themselves varying this information. |
@joergklausen -regarding the proposal to list Sea Ice Forecasting and Monitoring under Ocean, since the structure was approved by INFCOM2, it may be useful to not make changes outside a similar process. of course, other groupings are possible. The specific application as a "primary" use of observations, is focused on generating information for navigation in polar/subpolar waters. |
Perhaps we can generalize the definitions by referring to OSCAR/Requirements instead. For example, |
sent Kruno an email |
New proposal: Deprecate old version of table and add new version using the application categories.
|
Proposal for mapping in codes registry or just for OSCAR/Surface
|
https://github.com/wmo-im/tt-wigosmd/wiki/2024.06.20%E2%80%90TT%E2%80%90WIGOSMD notes: DECISION: |
|
We were asked to defer this proposal until the relevant teams in SC-ON can review and consider the options for WIGOS implementation tools. |
update branch with new List of Application Areas #438
feedback from ET-WTR for OSCAR/Surface:
|
Test codes registry is unstable and these links need to be rebuilt. |
|
https://github.com/wmo-im/tt-wigosmd/wiki/Meeting.2025.01.16 notes:
|
Initial request
I refer to the Application Areas Codes list in the WMDR.
INFCOM-2 recommended changes to WIGOS Manual in relation to the evolved Rolling Review of Requirements process per WMO's Earth System Approach. In doing so, it introduced the concept of Earth System Application Category (ESAC), which is effectively a grouping of Application Areas into 1. Space Weather, 2. Atmospheric, 3. Oceanic, 4. Hydrological & Terrestrial, 5. Cryospheric, and 6. Integrated Earth System Applications. It also expanded the list of Application Areas, which are now grouped into ESACs. See related INFCOM-2 INF 6.1(3) and its Annex 1.
Some further changes were then also proposed by SERCOM and its ET-MOR with regard to the Oceanic Applications ESAC. These will have to be considered (I will provide the table in a next message).
OSCAR Requirements web page of Application Categories and Areas:
Amendment details
updated 16 January 2025
NEW codes
notation | name | description-- | -- | --
Mapping
no mapping available
cryosphere
energy
health
hydrology
oceanApplications
spaceWeather
terrestrialEcology
transport
Comments
Requestor(s)
Etienne Charpentier (WMO)
Stakeholder(s)
Publication(s)
Manual on Codes (WMO-No. 306), Volume I.3 and WMO Codes Registry
Expected impact of change
HIGH, the OSCAR/Surface editor will need to be updated and there is not a direct mapping between old and new
Collaborators
References
Validation
The text was updated successfully, but these errors were encountered: