Satellite Data Requirements and Regional Planning

Transcription

1 WORLD METEOROLOGICAL ORGANIZATION COMMISSION FOR BASIC SYSTEMS OPEN PROGRAMME AREA GROUP ON INTEGRATED OBSERVING SYSTEMS INTER-PROGRAMME EXPERT TEAM ON SATELLITE UTILIZATION AND PRODUCTS FIRST SESSION GENEVA, SWITZERLAND, MARCH 2015 IPET-SUP-1/Doc (10.III.2015) ITEM: Original: ENGLISH Regional Satellite User Group in RA III/IV (Submitted by Luiz Machado and Diego Souza) Summary and Purpose of Document Formulating Region-based requirements for satellite data access and exchange has been recognized by WMO as a priority (see WMO Executive Council Resolution 12 (EC-65, 2013)). A preparatory meeting of the Coordination Group on Satellite Data Requirements in Region III and Region IV was held in the US during the 2013 NOAA Satellite Conference. Subsequently, the Group was endorsed by RA IV and by RA III. The Group has met by teleconference twelve times since October 2013, the last meeting held on 18 February This document describes the initiatives and actions taken in the last meetings in , as well the activities and mechanisms that are being developed to create an operational, sustained Regionbased satellite data distribution plan that is endorsed and supported by all Region Members. ACTION PROPOSED The first IPET-SUP session is invited to: (a) Take note of the progress in the Coordination Group on Satellite Data Requirements (SDR) for RA III/IV; (b) Discuss and criticize the steps done, next steps, and options to improve a sustainable satellite data dissemination system in the Region; (c) Discuss how to improve regional participation in the SDR and proposed committees. Appendix A: Agreed option for positioning GOES-13 imager scan frames during Rapid Scan Operations Appendix B: GEONETCast-Americas Bandwidth Management Appendix C: Draft of the GeonetCast-Americas Terms of Reference and the Subcommittees Appendix D: Terms of Reference and Nominees of the Coordination Group on Satellite Data Requirements for Region III and Region IV.

2 IPET-SUP-1/Doc , p. 2 DISCUSSION 1. Introduction A Satellite Data Requirements Task Team for Region III and IV was established in June 2009 by the Secretary General of WMO. The Task Team prepared an inventory of dissemination systems available in Regions III and IV with details on their coverage, data rate, and provisions for sustainability of these systems. The Task Team on Satellite Data Requirements completed its work in In its report, the Team prepared an inventory of dissemination systems available in Regions III and IV with details on their coverage, data rate, and provisions for sustainability of these systems. The inventory list as well all related documentation is available on line in the following URL In November 2012, the WMO Secretary General asked all Members in RA III and RA IV to nominate candidates for a standing Regional Coordination Group on Satellite Data Requirements as a follow-up step from the successively concluded work of the Task Team. On 8 April 2013, in the US National Center for Weather and Climate Prediction, College Park MD, USA, the Preparatory Meeting of the Coordination Group on Satellite Data Requirements for RAIII and RA IV was held. After this meeting, twelve teleconferences were held and several actions were taken. Among these actions the group discussed an optimized schedule for GOES-13 (mitigating the loss of GOES-South America in August 2013), reported in the ET-SUP-8, the organization of a regional survey (see IPET-SUP-1/Doc.13.1). In this document we present the main achievements obtained by the teleconferences in 2014 and 2015, the GEONETCast-Americas organization as a possible model for user-data provider interaction, the complementary information provided by the data providers to the Data Requirements tables, and the procedures established to improve product documentation, bandwidth management and capacity building. This document mainly describes the initiatives related to the GNC-A, however a broader view on data dissemination mechanisms in the Region can provide a more objective analysis of gaps and solutions. Therefore, an update of the table II presented in the SATELLITE DATA REQUIREMENTS WORKSHOP FOR RA III and RA IV would help to have a general view of the dissemination system in the region. 2. Main achievements obtained in the teleconferences WMO secretariat coordinated all teleconferences, and the minutes are available ( Seven teleconferences were conducted since ET-SUP-8 (the last one in 18 February 2015), with participation from data providers (NOAA and EUMETSAT) and users. Several subjects were discussed and implemented, such as: (i) refined detail in the data requirements table (user requirements, and input from data providers on how to match these requirements), (ii) agree opton for optimized schedule for GOES 13 (see Appendix A), (iii) conclusion of a regional user survey, (iv) preparation for the 2015 NOAA Conference and SDR meeting, (v) generation of a GEO-LEO image mosaic to complement the new GOES schedule in southern South America, (vi) providing updates on GOES-R to users, and (vii) planning further activities for SDR and resolve issues about operational satellites and products. Basically, several achievements described in the next section are related to actions defined during the teleconferences. 3. Data Requirements Table (complemented by Data Providers) Substantial progress has been made in the second half of 2014, and the requirements table now contains comprehensive user requirements and matching products by EUMETSAT, INPE, and NOAA- NESDIS. In September 2014 we reached 395 products listed covering 49 out of the 58 proposed datasets. All remaining datasets are expected to be filled in 2015.

3 IPET-SUP-1/Doc , p. 3 Also, the Specific Application and Societal Benefit Areas columns were added to the Table, containing the general dataset applications and the GEOSS SBAs involved. This will help the preparation of the data directories to be accessed by visualization software and thematic organization of the data. Actually, data in GeonetCast are organized from the data providers point of view, i.e., by data provider. However, from the user point of view, the data should be organized by application facilitating the access and analyses. Figure 1 shows an example of the new table of the data requirements. Figure 1: Satellite Data Requirements for Region III / IV: Table Sample 4. GEONETCast-Americas Product Documentation and bandwidth control The Coordination Group recognizes that the GEONETCast-Americas (GNC-A) System is a key element of satellite data dissemination in the Region. Providing detailed information on how to read and employ the broadcasted data is one the recommendations to optimize Regional data distribution. To achieve this objective is mandatory to maintain the broadcasted products flow and their metadata constantly updated and properly documented. The first measure adopted was the development of the GNC-A Product Datasheets, a comprehensive and user friendly set of documents describing the product category, the Data Provider, the related Satellite Data Requirements dataset, format, average size, frequency, maximum number of files received a day, the pixel information, the satellite, instrument, channel, wavelength, type of the product, the projection, the resolution, the naming convention, a general description of that product, the applications and considerations and the GEOSS Societal Benefit Areas related to the product. These datasheets represent a major upgrade to the user's ability to access the broadcasted products, having a global view of the possible applications. Figure 2 illustrate an example of these GNC-A Product Datasheets.

4 IPET-SUP-1/Doc , p. 4 Figure 2: Example of GNC-A Product datasheet for GOES-12 Visible channel. Another effort toward the organization of the system was the development of a method for accounting for products and tools to manage bandwidth has been developed through the GNC-A Broadcast Operations sub-committee (see Appendix B). 5. GEONETCast-Americas Capacity Building One of the greatest needs of an operational, sustained Region-based satellite data distribution plan is the Capacity Building activities involved. Currently the following product formats are being broadcasted in GNC-A: GeoTIFF, BUFR, HDF, GRIB, BINARY, ASCII, CSV, SHAPEFILE, IMAGE (JPEG, BMP, PNG, GIF, etc), TEXT and PDF. The User Sub-Committee of GNC-A is expected to create tutorials regarding all the processing formats in the next months. The first format covered in this series will be the GeoTIFF format. NOAA is making a considerable effort to deliver GOES images in GeoTIFF format, as a first effort to decrease the number of formats. On 9 November 2014, a first Hands-On GEONETClass was provided by INPE regarding GeoTIFF manipulation. The students used a 50 pages tutorial written by the User Sub-Committee and had the theory given by two researchers from INPE. In a five hours course, the students were able to import, manipulate, visualize and interpret a set of GOES-13 images covering South America. The students feedbacks were fairly positive. Another training in the region was held in Mexico in 11 September 2014, dedicated to the use of GeoTIFF images in GNC-A. Capacity building in the new satellite generation specifically in the broadcast procedures and instrumentations and the hardware - software required is essential to promote the use of these satellites in the region.

5 IPET-SUP-1/Doc , p. 5 Figure 3 Example of GNC-A Capacity Building GeoTIFF Tutorial Sample Figure 4: GNC-A Capacity Building Session Slide Presented at LAGF Mexico Geonetcast Americas Term of Reference Besides the SDR teleconferences, the GEONETCast-Americas Coordination Group also had several telecons including data providers and data users. As a result of these telecons the following Terms of References of the coordination group were drafted and sub committees were created in order to facilitate the effective management of the GEONETCast Americas (GNC-A) system. The following subcommittees to the GNC-A Coordination Group have been formed. Broadcast Operations Ground Receive Systems Content Users See the full text describing these actions in Appendix C. 7. The Brazilian Test-bed project for SIGMACAST. Brazil has a project called SigmaCast that has the goal to prepare operational softwares based in JAVA and geospatial technologies that allow the user to visualize, analyse across several level of geographical layers and data from Geonetcast. This is a desktop based GIS, developed specifically to

6 IPET-SUP-1/Doc , p. 6 the Geonetcast users. The project consist in the development of this tool and training specifically to: a) the operation and manager of Geonetcast station, b) data content in Geonetcast and user data requirements, c) structure of Geonetcast and how to contribute as data provider and users to the system and d) SigmaCast training. The project has the budget to install 23 stations in Brazil in the regional centres (agreement already signed with the centers). The stations are being specified to run in Linux, with hardware based for operational use. The schedule is to install all stations in 2014 including the full database software and SigmaCast. This project can be a test-bed for the implementation in others countries and regions. 8. Coordination Group on Satellite Data Requirements for Region III and Region IV - Terms of Reference The terms of reference of the Group on Satellite Data Requirements was prepared by the team during the telecom meetings, and endorsed by the Regional Associations. This document, as well the actual composition (nominations) is presented in the Appendix D.

7 IPET-SUP-1/Doc , p. 7 Appendix A: Agreed option for positioning GOES-13 imager scan frames during Rapid Scan Operations The multi-channel imager onboard the geostationary GOES-13 satellite positioned at 75 W is at a unique vantage position for providing imagery in support of nowcasting and many other weather services for the Americas. An overview of its field-of-view is given in the Figure below. During normal operations, the Southern Hemisphere is covered every 30 minutes. During Rapid Scan Operations of the imager, which are invoked for example during the hurricane season, the CONUS and N. Hemisphere areas (see Figure) are covered more frequently. As a consequence, the other areas, i.e. most of the South American continent, are scanned by the imager only every three hours, which is insufficient for many user applications. In a letter to WMO, NOAA proposed to add two additional scan frames to the operations schedule of GOES-13 imager during Rapid Scan Operations. The areas within these frames will be scanned once every hour rather than only every three hours, thus significantly improving coverage. The Coordination Group on Satellite User Requirements for Region III and Region IV, with assistance by WMO Secretariat, developed a preferred option for positioning the scan frames (black boxes in the Figure). It took into account user requirements and the availability of satellite imagery from other providers such as EUMETSAT. This option has been recommended to NOAA for implementation. This work is critical for many user applications and mitigates the loss of GOES-12 endured in 2013; it is an example for the value of the Group as a coordinated satellite data user community.

8 IPET-SUP-1/Doc , p. 8 Appendix B: GEONETCast-Americas Bandwidth Management by Diego Souza A method for accounting for products and tools to manage bandwidth has been developed through the GNC-A Broadcast Operations sub-committee. The first tool developed was the GEONETCast- Americas Real Time Bandwidth Monitor Windows application. The main objective of this tool was to analyze how the GNC-A broadcast works by means of bandwidth (the application plots the used bandwidth as a function of time). At the time of development, the Broadcast Operations Sub-Committee was not sure if the broadcast system used the whole bandwidth when transmitting high volume files or if it divided the bandwidth equally between transmissions. The first results showed clearly that the system always works at full bandwidth. In order to develop this plotting software, a FAZZT (Datacast software) script was developed, which sums the bandwidth used by each channel second by second. A custom Windows application read this data and plots it for a better visualization. Figure A1: GEONETCast-Americas Real Time Bandwidth Monitor and the FAZZT receiving files log. After understanding how the broadcast system works, the Committee developed the GNC-A Bandwidth Management Spreadsheet, containing all the information required to keep track of what is being broadcasted in the System, enabling the Broadcast Operations Sub-Committee and the Content Sub-Committee to determine the broadcast usage of each product, to know in advance the impact of future product additions to the System, determining the priority of products and accepting recommendations on products and formats by the Users Sub-Committee. The spreadsheet was developed using information from GNC-A stations databases.

9 IPET-SUP-1/Doc , p. 9 Figure A2: GNC-A Bandwidth Management Table Sample For each product twenty characteristics are given in the spreadsheet, described as follows: Product ID number: A unique identification number for each product, enabling different committees to reference them easily and efficiently while discussing strategies. Provider: The Data Provider for each product. Grouping the products by Data Providers sequentially simplifies the analysis and makes possible to determine the exact bandwidth used by each agency / channel. File Description: A simplified description of the physical parameters that can be retrieved using a given product and / or the sensor used to make the data acquisition. The geographic region covered by the product is also described. File Name Example: An example of the naming convention adopted by the Data Provider. Format: The file format for all the products. This information will define the development of training courses. Frequency (minutes): The interval of reception for each product. This information is used to calculate the required data rate. Files a Day: Maximum number of files a day, as declared by the provider. Minimum Size (kb): Considering a GNC-A station five months database, the minimum file size encountered for each product. Used to predict the broadcast behavior when the product size is typically reduced (e.g. visible imagery without sunlight). Average Size (kb): Considering a GNC-A station five months database, the mean file size calculated for each product. This, along with the frequency, is the value used to estimate the required data rate for each product. Maximum Size (kb): Considering a GNC-A station five months database, the maximum file size encountered for each product. Used to predict the broadcast behavior when the product size is typically increased (e.g. visible imagery when the satellite footprint is completely covered by sunlight). Bytes Per Day and Megabits Per Day: Considering the datacast client log, the real number of bytes broadcasted in a day. Used to corroborate the average estimates and check possible errors. Time Required to Broadcast (seconds and minutes): Calculated based on the product average size and the system maximum bandwidth. Very important information to schedule future product entries. Required Data Rate (kb/s): The overall bandwidth used to broadcast a given product in a given frequency. Calculated using the average file sizes. Percentage of 2 Mbps / Day - Average: Main information used to know the effective impact of the product in the broadcast. Being color scaled, it s the immediate indicative of broadcast viability.

10 IPET-SUP-1/Doc , p. 10 Figure A3 : GNC-A Bandwidth Management Table Sample Accumulated Percentage Average: The cumulative sum of the bandwidth impact for all products. Used to estimate the total broadcast capacity used. To verify the efficiency of this estimation, the second by second spreadsheet described in the next topic is used. Figure A4: GNC-A Bandwidth Management Table Sample Percentage of 2 Mbps / Day - Real: Considering the datacast client log, calculates the effective impact of the product in the broadcast. Used to corroborate the average estimates and check possible errors. Accumulated Real Average: The cumulative sum of the bandwidth impact for all products considering the datacast client log. Comments: Additional information, containing the exact time of broadcast for a given product based on a GNC-A data base. The bandwidth usage by each channel is also shown in the spreadsheet, based on the average bandwidth usage percentage. Figure A5: GNC-A Bandwidth Usage by Channel Being able to monitor the used bandwidth every second made possible the creation of a Second by Second Bandwidth Usage Spreadsheet in order to detect the broadcast Rush Hours, enabling the Broadcast Operations Sub-Committee to schedule the uploads so that the system bandwidth is used efficiently. This mechanism is still under development, but the first results already enabled a better understanding of the upload system.

11 IPET-SUP-1/Doc , p. 11 Figure A6: GNC-A Second by Second Table Sample This mechanism also enabled the Broadcast Operations Sub-Committee to know the real percentage of bandwidth used every day, with a small margin of error. Figure A7: GNC-A Second by Second Table Sample Using this table we can compare the system behavior between days to check possible disparities:

12 IPET-SUP-1/Doc , p. 12 Figure A8: GNC-A Second by Second Graph Sample GEONETCast-Americas Product Management: One of the main suggestions from users was the creation of an intuitive data organization mechanism. Figure A9: GNC-A standard ingestion incoming folder With the product suite properly documented by the Broadcast Operations Sub-Committee, the Ground Receive Systems Sub-Committee developed a flexible Data Manager Script which is scheduled by the FAZZT Datacast Client. Figure A10: GNC-A Data Manager Script Scheduled in the Datacast Client The script s data management is completely configurable by the user and has a simple syntax, described as follows: [Application Area] Provider:Identifier1,Identifier2,IdentifierN :Folder:Format;

13 IPET-SUP-1/Doc , p. 13 [/Application Area] Where: Application Area: Name of the folder to which the product will be directed; Provider: Origin folder inside the incoming directory; Identifiers separated by commas: Piece of text inside the file names. MUST be unique. Informed by the Provider; Folder: Sub-folder to which the product will be directed; Format: Product format; Figure A11: GNC-A Data Manager Script Sample Let s consider the following example: [Radiation] INPE:INPE_UVI:Ultra Violet Index - South America:JPEG; [/Radiation] In this case, the products containing the INPE_UVI identifier will be redirected to a JPEG folder inside a Ultra Violet Index - South America folder inside a Radiation folder. Below another example: [Oceanography] NOAA-NESDIS:MODWCW,CB,.png:Sea Surface Chlorophyll - NOAA SWIR - Caribbean:PNG; NOAA-NESDIS:MODWCW,CB,.tif:Sea Surface Chlorophyll - NOAA SWIR - Caribbean:GEOTIFF; [/Oceanography] In this case, the products containing the MODWCW, CB and.png identifiers will be redirected to a PNG folder inside a Sea Surface Chlorophyll - NOAA SWIR - Caribbean folder inside a Oceanography folder and the products containing the MODWCW, CB and.tif identifiers will be

14 IPET-SUP-1/Doc , p. 14 redirected to a TIF folder inside a Sea Surface Chlorophyll - NOAA SWIR - Caribbean folder inside a Oceanography. Figure A12: GNC-A Data Manager Folder Example

15 IPET-SUP-1/Doc , p. 15 Appendix C: Draft of the GeonetCast Americas Terms of Reference and the Subcommittees (DRAFT) - GEONETCast Americas Coordination Group - Terms of Reference - (9/8/14) Definitions GEONETCast is a global, near-real-time, environmental data dissemination system developed in support of the Global Earth Observation System of Systems (GEOSS). GEONETCast Americas, supported and managed by the United States National Oceanic and Atmospheric Administration (NOAA) and other partners, is the Western Hemisphere component of the global system. GEONETCast Americas will serve North, Central, and South America and the Caribbean using inexpensive satellite receiver stations based on Digital Video Broadcast standards for the free dissemination of environmental data. Purpose The purpose of the GEONETCast Americas Coordination Group is to serve as a forum for regional partners, data providers and users to provide advice and coordinated input on the GEONETCast Americas data flow, including the identification of data and products, data acquisition, priorities, data utilization, system operation, and opportunities for capacity building. Objectives: Establish a link between partners, data providers and users. Normalize system operations and data requirements. Broaden regional understanding of the initiative, including reception requirements. Identify and recommend data and products for transmission through GEONETCast Americas, to support the needs identified by the GEO nine societal benefit areas. Identify strategic opportunities for installation of receivers throughout the region and for building capacity to utilize system data and products. Identify additional users and providers who might be able to use or provide data or products for transmission through the system. Provide advice and comment on the technical enhancement of the system and assistance to new users and providers. Approach and Functions The GNC-A Cooperation Group will develop the necessary committees in order to manage the GNC-A system in an efficient manner. Meet regularly via teleconference and in person as needed to review progress toward GNC-A objective.. Communicate with government agencies, NGOs, academia and the private sector, to explore the best utilization of GEONETCast Americas. Membership Membership in the GEONETCast Americas Coordination Group is comprised of those entities that are either partners, data provides or users of the service. Because of the different levels of participation in the GNC-A system three types of members have been identified. Partners are those that are directly involved in the management of the broadcast as well as assist with the administration of the system. Providers are those that provide data or products for the system. They may or may not use the system. Users typically have one or more ground stations, or otherwise receive and utilize content

16 IPET-SUP-1/Doc , p. 16 distributed by GEONETCast. system. Users may or may not send data or products over the GEONETCast Americas Coordination Group Sub-Committees In order to facilitate the effective management of the GEONETCast Americas (GNC-A) system, the following sub-committees to the GNC-A Coordination Group have been formed. Broadcast Operations Ground Receive Systems Content Users Broadcast Operations Sub-Committee The Broadcast Operations Sub-Committee will assist NOAA in managing the operation of the GNC-A system. Because this involves NOAA infrastructure and contracts, membership in this committee will be comprised of Partners or those that make a substantial contribution to system administration. The Broadcast Operations Sub-Committee function is to: 1. Manage the overall GNC-A broadcast infrastructure such as: a. Commercial system operation b. Kencast software administration c. broadcast quality 2. The Broadcast Operations sub-committee will provide expert advice on the effects of the decisions recommended by the other sub-committees on the GNC-A broadcast infrastructure. 3. Consult with the sub-committees before making changes to the GNC-A broadcast and report out decisions in a timely manner. Ground Receive Systems Sub-Committee The Ground Receive Systems Sub-Committee has three main functions. 1. Experiment with and track changes in equipment for the system, which might affect the operation of existing ground stations or affect the configuration of future deployments. 2. Track, as possible, the status of existing sites. 3. Create training manuals and a knowledge base that helps with initial site installation, maintenance, and troubleshooting. Content Sub-Committee The Content Sub-Committee will: 1. Accepts Recommendations on products and formats. 2. Determine the priority of products. 3. After consultation with the Coordination Group, approve new products, formats and priorities for the Broadcast Operations sub-committee to implement. A primary task of the Content sub-committee should be to develop guidelines for including data and products on the GNC-A broadcast. The 9 GEO Societal Benefit Areas is the primary corner stone for the guidelines. Along with other requirements, such as WMO RA III and IV satellite data requirements.

17 IPET-SUP-1/Doc , p. 17 Users Sub-Committee The Users Sub-Committee will: 1. Develop trainings and tutorials on how to use the data and products on the system and on what software packages work with the data and products. 2. Develop, as possible, a chat or blog or other to serve as a support system covering product usage, software questions, or other related issues. 3. Make recommendations to the Content Sub-Committee on possible new data or products and removal of unused data or products from the system.

18 IPET-SUP-1/Doc , p. 18 Appendix D Coordination Group on Satellite Data Requirements for Region III and Region IV Terms of Reference 1. The Group consists of a representative number of members from the satellite data user community in the Region, joined, as associate members, by satellite data providers and WMO. The Group is chaired by one or two representatives from key satellite data user organizations of the Region. 2. The Group maintains an updated list of satellite data and products available to the Region through existing dissemination services. Data and products shall be classified by categories of variables and derived products. 3. The Groups regularly reviews sources of regional needs and undertakes, as needed, further information gathering, such as surveys, to ensure that views of WMO Members in the Region are adequately represented. 4. The Group analyzes the requirements for each relevant category of product, and identifies which requirements are not adequately met by existing services. The unmet requirements are prioritized, taking into account: a. The applications supported and their impact b. The number and representativeness of the users c. The status of the required data or products d. The quality and suitability of the required data or products. 5. In summary the Group formulates recommendations pertaining to: a. Existing satellite data/products (with detailed references) to be included in existing distribution services, or moving a product from one service to another, or assigning lower priority to an existing product (or removing it if obsolete) b. Amendments of existing products or development of new products c. Evolution (upgrade, or consolidating) of data dissemination means, or other (e.g. training, tools, user equipment) d. Short-term action to implement these recommendations 6. The Group maintains a dialogue with satellite data providers of relevance to the Region, and other partners as needed, to ensure that its recommendations are implemented. 7. The Group uses the WMO Procedure for Documenting Regional Requirements for Satellite Data Access and Exchange, for guidance. 8. The Group meets in person at least every two years, and, to ensure continuity, works through collaborative tools during the intersessional period.

19 IPET-SUP-1/Doc , p. 19 Nominees to the Coordination Group on Satellite Data Requirements for Region III and Region IV (Status: November 2014) Name Institution Country Estela Collini Luiz Augusto Machado Wagner de Aragão Bezerra Servicio de Hidrografía Naval (SHN) and Servicio Meteorológico Nacional (SMN) Center for Weather Forecasting and Climate Studies (CPTEC), National Institute for Space Research (INPE) National Institute of Meteorology (INMET) Argentina Brazil Brazil David Bradley Meteorological Service of Canada Canada Miguel Egaña Dirección Meteorológica de Chile Chile Olga Gonzalez Luis Fernández Institute of Hydrology, Meteorology and Environmental Studies (IDEAM) National Meteorological and Hydrological Institute (INAMEH) Colombia Venezuela Bryan Thomas Meteorological Office Trinidad and Tobago Satellite operators Paul Seymour NOAA NESDIS USA Kelly Sponberg NOAA NWS and UCAR USA Sally Wannop EUMETSAT