# Presentation: 516428

## Surface ObservationData Flowvia GOES

- In Support
- Of
- Wildland Fire

## Primary real-time 

**25,000 + Reporting Stations**
- USDA – FS
- USDI – BLM, NPS, FWS, BIA,
- States
- USGS
- USACE
- National Buoy Center
- Other Governments
- NOAA – NWS, NESDIS
- Climate Reference Network

- Primary real-time
- hydro/met data collection system for all of these agencies.

## DAPS is a Data General System.

- There is no off-site backup.

## Slide 4

## Slide 5

## The Single Point of Failure

**NOAA/NESDIS**
- DAPS – NO Backup to System
- Pilot Signal – Backup @ NASA Goddard
- Command / Control GOES East – B/U @ NASA Goddard
- Backup for GOES West in AK - *Maybe*

**Sufficient....per NOAA/NESDIS COOP Plan developed **
**pre-9/11 and pre-Katrina****.**

- Not identified as a primary system per NOAA.

## Where are Wallops & Goddard?

**MAPQUEST:  Total Est. Time:** 3 hours, 7 minutes     **Total Est. Distance:** 154.66 miles

- Technicians from Wallops
- are to drive to Goddard in the event
- of failure at Wallops.

- High Winds

- Heavy Traffic

## Emergency Data Distribution Network

- STIWG Members w/Support from NOAA/NESDIS
- (in development now)

## No observations / imagery to 

**No observations / imagery to **
**DOMSAT users, AWIPS, HADS, NOAAPORT, EMWIN**

## Specific Problems

- Insufficient Backup to Wallops
- Pilot Signal Backup Uncertainties
- Command/Control Backup Uncertainties

## Specific Problems

- The DCS is not a designated primary system by NOAA.
- Primary Systems Failure
- New satellite moved into operation.
- Or launch as soon as possible.
- Non Primary System Failure
- No such resolution.

- DO WITHOUT

## Specific Problems

- Satellite Telemetry Interagency Working Group (STIWG)
- Unable to find anything in writing that mandates the operation of the GOES DCS.
- Members feel that backup at NASA Goddard not sufficient due to lack of geographic separation.

## Specific Problems

- Membership believes that backup at NASA Goddard and AK not sufficient to operate GOES DCS.
- STIWG has not been advised of any verification or testing of this system to satisfy our concerns.

## Specific Problems

- STIWG has been told by NESDIS that NASA could take control of spacecraft in emergency.
- This has not been confirmed.
- Would it be a NASA priority in event of National Emergency?
- Transponders would not be active.
- therefore still no data...

## What Has STIWG Done?

- Recently briefed the Subcommittee on Hydrology on situation.

- Requested elevation of problem and appropriate response from NOAA Management / Strategic Planning Activity.

## Inside the Wildland Fire Community

- Once Data is
- Received from GOES

## 1

- 2

- 2

- 3 – ROMAN ID

- 4

- Metadata
- By Dispatcher

**Notes:**
WIMS – Weather Information Management System – Stores Data/Metadata by WIMS ID
ROMAN – Real-Time Observation Monitor and Analysis Network – Gets Data and Metadata from ASCADS, assigns own number.
WFMI – Wildland Fire Management Information – Gets data from ASCADS
WRCC – Western Regional Climate Center – Gets data and metadata from ASCADS and WIMS stored by both NESSID and WIMS ID (two separate sets of data) AND stores the data that has been developed for Fire Program Analysis (FPA).

## NFDRS

- Snapshot

**Notes:**
National Interagency Fire Management Integrated Database (NIFMID)

## is all from one place on earth.

- Which periodically fails
- Sends Metadata to DAPS
- DAPS has no Backup
- DAPS sends metadata and data to AWIPS/NWS

**ASCADS**** Sends Data to ****WIMS**
- WIMS Sends Data and Metadata
- to NWS and WRCC by WIMS#

**ASCADS Sends ****Data and Metadata**** to**
- WRCC, ROMAN
- By NESSID

- WRCC and NWS
- Receive same data from two systems
- Identified by different numbers
- Metadata does not always match

- WRCC has “cleaned data” for the Wildland Fire Community’s FPA project.
- This is also stored at WRCC.

- We potentially have three datasets, all *sl**i**g**h**t**l**y* different, for the **same** point on earth *and* period of record.

- However, the data
- is all from one place on earth.