11
Filename.ppt 1 NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements NOAA WP-13

NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements NOAA WP-13

  • Upload
    lot

  • View
    27

  • Download
    1

Embed Size (px)

DESCRIPTION

NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements NOAA WP-13. Responsive to CGMS Action. - PowerPoint PPT Presentation

Citation preview

Page 1: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 1

NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements

NOAA WP-13

Page 2: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 2

Responsive to CGMS Action

● Action 40.18: CGMS Agencies to support fast delivery initiatives using direct broadcast with extensions wherever possible (e.g., IASI, METOP-B, NPP), including on future polar orbiting satellites.

Page 3: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 3

Any latency requests less than total system latency for JPSS (103 minutes) are captured as objective latencies for each respective product3

• NOAA operational Line Offices have provided true latency values for their respective critical products (focusing on the near-real time requirements)

30 minutes

60 minutes

NWS:ATMS SDR TDRCrIS SDR VIIRS Imagery EDR (Alaska Region)

80 minutesNWS: VIIRS SDRAMSR-2 SDR

NESDIS:ADCS Data

NOS:VIIRS Imagery EDR

NESDIS:SARSAT Data

12 hours – During Event

24 hours – Normal Monitoring

NOS:VIIRS Ocean Color/Chlorophyll Sea Surface Temperature Aerosol Optical ThicknessAMSR-2 Sea Surface Temperature

NMFS:ADCS DataVIIRS SDR Aerosol Optical ThicknessSea Surface TemperatureOMPS SDRCERES SDRAMSR-2 Sea Surface Temperature

120 minutes

NMFS:VIIRS Ocean Color/Chlorophyll

NOAA User Latency Requests

140 90 80 60 45 30 150.0

10.0

20.0

30.0

40.0

50.0

60.0

70.0

80.0

90.0

100.0

Data Latency and Percent of Data Used in Operational NWP

NAM

GFS

Hourly

Latency (Minutes)

Pe

rce

nt

Us

ed

S-NPP JPSS

Page 4: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 4

Community Supported Processing Package (CSPP) demonstrates the value of 15- 30 minute latency for nowcasting and regional forecast model applications by establishing a network of direct readout stations - includes METOP and All Polar Orbiting Satellites with DB

Future JPSS Proving Ground DB DemoCSPP sites

Guam

Page 5: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 5

Scope

● Gap mitigation for NPP/JPSS-1 or JPSS-1/JPSS-2 by securing all existing satellite sounder data with direct broadcast with significantly improved latency – goal of 15 minutes, threshold of 30.

● Sounder data are relayed back to NSOF and CIMSS (UW) for distribution to NCEP Central Operations.

● Existing NOAA priority sites: WI, AK, HI

● Expand to: Guam, Miami, Puerto Rico, and Suitland. >> connect to EUMETSAT sites

● Access to Japan site (JMA)

● Sounder data from all METOP, POES, JPSS.

● Add GCOM capabilities

● Potential to include Russian Meteor-M and Chinese FY-3 series.

● Additional benefits – local use of DB by local NWS office and other customers.

Page 6: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 6

Execution

● Kickoff meeting in April 2013

● Identified POC/hosts in Miami and PR

● CIMSS/UW - acquire and install Miami and PR antennas

● OSPO – contract to install Monterrey, with options for remaining antennas.

● Communication analysis by OSD confirmed all sites with exception of Guam will not need additional comm support.

● Use CSPP and include call home feature for data exploitation from external sites.

Page 7: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

CSPP Users 23 January 2013

More than 250 people have registered to downloaded some part of the CSPP suite of products representing 33 different countries, including all 7 continents.

Page 8: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Who is Using CSPP?Here is a sample

• EUMETSAT for EARS-NPP EUMETCast distribution

• UK Met Office• Météo-France• CSIR South Africa• Swedish Met Service• DWD – German Met Service• Australia Bureau of Meteorology• Taiwan Central Weather Bureau• Belarus National Academy of Science• Indonesia Government Space Agency

(LAPAN)• German Aerospace Center• CONABIO Mexico• EURAC Remote Sensing Institute

Italy

• China National Satellite Meteorological Center

• Brazil INPE• Danish Meteorological Institute• Japanese Meteorological Agency• Norwegian Meteorological Institute• Swedish Met Institute• Kazakhstan Space Investigation

Institute• UK Plymouth Marine Lab• Naval Research Lab• Vendors SeaSpace, ScanEx, Spacetec

and others.• In addition, CSPP DB products are

being used in the US NWS in HI, Alaska and CONUS

Page 9: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

EARS – Current Status

Services

EARS-ATOVS L1

EARS-ASCAT L2 Winds

EARS-AVHRR L0

EARS-IASI L1C

EARS-NWC L2 Clouds

Satellites: NOAA POES

Metop

Page 10: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

NPP Regional Services - Conclusion

Kangerlussuaq (Q4)

Svalbard (Q3)

Athens (Q3)

Lannion (Q3)

Moscow (TBC)

Maspalomas (Q3)

• Preparations well underway at all Stations. Expected Operational Readiness indicated as Quarter in 2012.

• New EARS Suomi NPP Services to start during 2012.

• The contributions from the:• Station Partners• NWP-SAF • CSPP Team• Users

are essential for the successful implementation of the new services and are highly appreciated!

Page 11: NOAA Direct Broadcast Data Initiative to Meet NWP Latency Requirements  NOAA WP-13

Filename.ppt 11

Recommendations

● Work with WMO to fully engage NOAA Direct Readout Initiative

● NOAA welcomes the participation of other CGMS agencies. We would like to include FY3 and Russian satellites and would encourage open access to level 0 and level 1 processing code to convert satellite data packets to calibrated sensor observations.