Release 5.1a/R5.1b RWP Requirements
[5.1a & 5.1b now called 5.1.1 & 5.1.2, respectively]

7/11/00 0:00

 
RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

1

0

 

 

 

Station Model Plot Configurability

 

 

 

 

 

 

 

1

1

 

 

 

AWIPS shall be able to display up to nine variables around an observation location in a plan view display. This set of variables around a sensor location is called a "station model".

X

X

X

 

 

 

 

1

2

 

 

 

AWIPS shall allow the user to select which variables will be displayed in the station model.

X

X

 

 

 

 

 

1

3

 

 

 

AWIPS shall allow the user to specify the relative position of each variable in relationship to the center point of the station model.

X

 

X

 

 

 

 

1

5

 

 

 

Data sources shall be surface or upper air observations stored on; however, a single plan view display will not display variables from different levels :

X

 

X

 

 

 

 

1

5

1

 

 

Metar;

X

 

X

 

 

 

 

1

5

2

 

 

Fixed and/or floating buoy or C-Man observations;

X

 

X

 

 

 

 

1

5

3

 

 

Ship;

X

 

X

 

 

 

 

1

5

4

 

 

RAWS;

X

 

X

 

 

 

 

1

5

5

 

 

Rawinsonde;

X

 

X

 

 

 

 

1

5

6

 

 

Mareps;

X

 

X

 

 

 

 

1

5

7

 

 

Aireps;

X

 

X

 

 

 

 

1

5

8

 

 

ACARS;

X

 

X

 

 

 

 

1

5

9

 

 

Dropwindsonde;

X

 

X

 

 

 

 

1

5

10

 

 

Local surface observations, including SHEF-encoded data;

X

 

X

 

 

 

 

1

5

11

 

 

Other surface or upper air data sources as identified

X

 

X

 

 

 

 

1

6

 

 

 

When a new point data source is added to AWIPS or a new element is added to an existing observation source, any new variables shall be available for positioning on a station model

X

 

X

 

 

 

 

1

14

 

 

 

AWIPS shall provide the capability to show derived parameters as well as observed parameters in locations around the station center

X

X

 

 

 

 

 

1

17

 

 

 

AWIPS shall be able to use station model definitions under all failover conditions. (Carl says this resides on the WS, so not an issue for failover)

X

 

X

 

 

 

 

2

0

 

 

 

Provide displays of wind and sea state guidance and marine observations

 

 

 

 

 

 

 

2

2

 

 

 

AWIPS shall provide the capability to ingest, decode, and display locally run gridded meso-scale marine model guidance such as the Great Lakes Environmental Research Labratory sea state forecasts.

 

X

X

 

 

 

 

2

3

 

 

 

AWIPS shall decode and display observational bouy data as a station plot on D2D for the following fields:

 

X

X

 

 

 

 

2

3

1

 

 

Wave Height (WVHT)

 

X

X

 

 

 

 

2

3

2

 

 

Swell Height (SwH)

 

X

X

 

 

 

 

2

3

3

 

 

Swell Direction (SwD)

 

X

X

 

 

 

 

2

3

4

 

 

Swell Period (SwP)

 

X

X

 

 

 

 

2

3

5

 

 

Wave Steepness (STP)

 

X

X

 

 

 

 

2

3

6

 

 

Significant Wave Height (HO)

 

X

X

 

 

 

 

2

3

7

 

 

Dominant Wave Period (DPD)

 

X

X

 

 

 

 

2

4

 

 

 

AWIPS shall decode and display gridded Ocean Modeling Branch Ice Analysis and the Vessel Ice Accretion guidance in D2D.

 

X

X

 

 

 

 

2

5

 

 

 

AWIPS shall decode and display gridded NESDIS Gulf Stream Analyses in D2D.

 

X

X

 

 

 

 

2

6

 

 

 

AWIPS shall decode and display gridded SSM/I analyses of wind in D2D.

 

X

X

 

 

 

 

2

7

 

 

 

AWIPS shall decode and display Canadian buoy observational data as well as U.S. buoy data as a station plot in D2D.

 

X

X

 

 

 

 

5

0

 

 

 

Provide User-Configurability of contours (intervals and limits) for generated graphics

 

 

 

 

 

 

 

5

1

 

 

 

AWIPS shall provide a GUI for the forecaster to control the way fields are displayed in D2D. This shall include the capability for the forecaster to set the following things:

X

 

X

 

 

 

 

5

1

1

 

 

a. Range of data for contours in physical units, e.g., -40F to +40F;

X

 

X

 

 

 

 

5

1

2

 

 

b. Intervals for contours in physical units, e.g., every 5 degrees F;

X

 

X

 

 

 

 

5

1

3

 

 

c. Thresholds for display of contours in physical units, e.g., contours greater than 50 knots or less than 100 knots;

X

 

X

 

 

 

 

5

3

 

 

 

This functionality shall work when a site is in failover mode.

X

X

 

 

 

 

 

7

0

 

 

 

Faster Availability New Products/Models Fields in AWIPS

 

 

 

 

 

 

 

7

1

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected grid parameters and time steps for existing grid projections to AWIPS ingest tables, template files, and purge parameters to allow storage of new grids

X

 

X

 

 

 

 

7

2

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected grid parameters and time steps for existing grid projections to the Volume Browser to allow display of new grids

X

 

X

 

 

 

 

7

3

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected redbook graphics (RBG) files for existing projections to AWIPS redbook data, depict key tables, and purge parameter files to allow storage and display of new RBGs

X

 

X

 

 

 

 

7

4

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected text bulletins to the Text Database to allow display of new text bulletins from the Text window and browser.

X

 

X

 

 

 

 

7

5

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected satellite imagery for existing satellite projections to AWIPS ingest tables, template files, and purge parameters to allow storage of new display

X

 

X

 

 

 

 

7

6

 

 

 

AWIPS shall have functionality to allow AWIPS System Managers to add selected satellite imagery for existing satellite projections to the D-2D menu to allow display of new satellite imagery

X

 

X

 

 

 

 

10

0

 

 

 

Image Tools - Cloud Height Computation

 

 

 

 

 

 

 

10

1

 

 

 

For Cloud Heights AWIPS shall display satellite/sounding derived cloud top information in D2D by utilizing the sampling function logic associated with satellite imagery to access temperature data.

 

X

X

 

 

 

 

10

2

 

 

 

AWIPS shall display the following output in text readout underneath the cursor when sampling is activated on IR Satellite Imagery: aaaaa/bbbbb feet (source status) where aaaaa represents the estimated cloud height in feet at the cursor, bbbbb represent

 

X

X

 

 

 

 

10

2

1

 

 

Source shall be the model or raob site used in the cloud height computation.

 

X

X

 

 

 

 

10

2

1

1

 

If raob data is used, the source shall be the 3-letter ID of the nearest sounding used in the computation.

 

X

X

 

 

 

 

10

2

1

2

 

If climatological data is used, the source shall be indicated as CLIMO.

 

X

X

 

 

 

 

10

2

2

 

 

Status is a one-letter indicator of the results of a cloud height computation. Status values shall be: W - Cloud Temp warmer than sounding-Top set to 0. C - Cloud Temp colder than sounding-Tops recomputed using parcel theory or by linear extrapolation.*

 

X

X

 

 

 

 

10

3

 

 

 

This functionality shall be available only when sampling a satellite IR image.

 

X

X

 

 

 

 

10

4

 

 

 

AWIPS shall be able to display satellite/sounding derived cloud top information on a satellite IR image when it is displayed alone and when it is displayed with other types of data in the a window.

 

X

X

 

 

 

 

10

5

 

 

 

AWIPS shall display cloud top information as the user moves a cursor over the IR satellite image.

 

X

X

 

 

 

 

10

6

 

 

 

AWIPS shall give the user the ability to turn on/off the sampling.

 

X

X

 

 

 

 

10

7

 

 

 

AWIPS shall use sounding data from either model, climatological and radiosonde sources. A suggested default is to use ETA model sounding data.

 

X

X

 

 

 

 

10

8

 

 

 

AWIPS shall give the user the ability to select the data source one at a time.

 

X

X

 

 

 

 

10

8

1

 

 

This functionality shall be turned on/off by pressing the right mouse button.

 

X

X

 

 

 

 

10

8

2

 

 

The option "Sample Cloud Heights" shall be incorporated into the AWIPS pop-up menu between the "Sampling" and "Lat/Lon Readout" options.

 

X

X

 

 

 

 

10

8

3

 

 

Once the "Sample Cloud Heights" option is activated a cascading menu with radio-button and check-button choices with the following options shall appear in D2D:

 

X

X

 

 

 

 

10

8

3

1

 

- No Sampling (radio-button)

 

X

X

 

 

 

 

10

8

3

2

 

- ETA (radio-button)

 

X

X

 

 

 

 

10

8

3

3

 

- RUC2 (radio-button)

 

X

X

 

 

 

 

10

8

3

4

 

AVN211 (radio-button)

 

X

X

 

 

 

 

10

8

3

5

 

- From Raobs (radio-button)

 

X

X

 

 

 

 

10

8

3

6

 

- SKEW-T (check button)

 

X

X

 

 

 

 

10

14

 

 

 

The Skew-T Log-P algorithm shall display either model or radiosonde sounding, from a time nearest to the time of the displayed satellite image.

 

X

X

 

 

 

 

10

15

 

 

 

Temperatures on the Skew-T Log-P diagram shall be labeled in C and F, heights in feet (to the nearest foot), and pressure in millibars.

 

X

X

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

22

0

 

 

 

Ingest, Store and Display Mesonet Data Received by LDAD at Maximum Temporal Resolution

 

 

 

 

 

 

 

22

1

 

 

 

LDAD shall ingest mesonet data at frequencies that match the cycle times of the mesonet.

 

X

X

 

 

 

 

22

2

 

 

 

AWIPS shall store mesonet data received from LDAD at frequencies that match the cycle times of the mesonet

 

X

X

 

 

 

 

22

3

 

 

 

AWIPS shall display mesonet data at frequencies that match the cycle times of the mesonet.

 

X

X

 

 

 

 

23

0

 

 

 

Time Series Of Observation Parameters

 

 

 

 

 

 

 

23

1

 

 

 

AWIPS shall have the ability to display a graphical representation of point data in a time series of various observation parameters. This shall include data sets such as METARs, buoys, LDAD ingested data, and others.

X

X

 

 

 

 

 

30

0

 

 

 

Ingest and Display of Model Soundings

 

 

 

 

 

 

 

30

1

 

 

 

AWIPS shall ingest and store all model soundings available on the SBN that fall within the:

 

X

X

 

 

 

 

30

1

1

 

 

Regional Scale at WFOs

 

X

X

 

 

 

 

30

1

2

 

 

RFC Scale at RFCs

 

X

X

 

 

 

 

30

1

3

 

 

Area of responsibility at NCEP National Centers (NC)

 

X

X

 

 

 

 

30

2

 

 

 

AWIPS shall allow display of model sounding parameters (individually or as a standard "SKEWT" package) using D-2D, Volume Browser, and Product Maker applications

 

X

X

 

 

 

 

30

3

 

 

 

AWIPS shall display model soundings using all vertical layers available in model

 

X

X

 

 

 

 

30

4

 

 

 

AWIPS shall display time projections using the model's full temporal resolution

 

X

X

 

 

 

 

30

5

 

 

 

When vertical sounding "SKEWT" display is selected from Volume Browser:

 

X

X

 

 

 

 

30

5

1

 

 

AWIPS shall depict model sounding stability indices the same as the RAOB display behavior

 

X

X

 

 

 

 

30

5

2

 

 

AWIPS shall display other parameters contained within the sounding file (centrally generated) within the same table as the calculated stability parameters (Haines, CAPE, WINDEX, etc)

 

X

X

 

 

 

 

30

6

 

 

 

AWIPS shall allow sounding data to be depicted in the following views:

 

X

X

 

 

 

 

30

6

1

 

 

Time/height cross sections

 

X

X

 

 

 

 

30

6

2

 

 

Planar depiction

 

X

X

 

 

 

 

30

6

3

 

 

Vertical "SKEWT" depictions

 

X

X

 

 

 

 

30

7

 

 

 

AWIPS shall allow display of all available parameters and independently toggled, to include:

 

X

X

 

 

 

 

30

7

1

 

 

Height

 

X

X

 

 

 

 

30

7

2

 

 

Temperature

 

X

X

 

 

 

 

30

7

3

 

 

Moisture (specific humidity, dew point, dew point depression, relative humidity, mixing ratio, wet bulb)

 

X

X

 

 

 

 

30

7

4

 

 

Winds (u, v)

 

X

X

 

 

 

 

30

7

5

 

 

Cloud amount

 

X

X

 

 

 

 

30

7

6

 

 

Omega

 

X

X

 

 

 

 

30

7

7

 

 

Freezing level

 

X

X

 

 

 

 

30

7

8

 

 

Tropopause level

 

X

X

 

 

 

 

30

7

9

 

 

Precipitation Type

 

X

X

 

 

 

 

30

7

10

 

 

Precipitation Intensity

 

X

X

 

 

 

 

30

7

11

 

 

Precipitation Amount (1, 3, 6, 12hr)

 

X

X

 

 

 

 

30

7

12

 

 

Snow Water Equivalent

 

X

X

 

 

 

 

30

7

13

 

 

Snow Accumulation (1hr)

 

X

X

 

 

 

 

30

7

14

 

 

Pressure

 

X

X

 

 

 

 

30

7

15

 

 

Catagorical Weather Type

 

X

X

 

 

 

 

30

7

16

 

 

Total Precipitable Water

 

X

X

 

 

 

 

30

7

17

 

 

Visibility

 

X

X

 

 

 

 

30

7

18

 

 

Stability Parameters (CAPE, CIN, LI)

 

X

X

 

 

 

 

30

7

19

 

 

Derived Parameters Calculable from the above Parameters

 

X

X

 

 

 

 

30

8

 

 

 

AWIPS shall allow users to select the beginning and ending loop times and data time step interval (ex. Build a loop of 1 hr sounding data from H+12 through H+36). This is particularly useful when the number of time steps in the model exceed the max number

 

X

X

 

 

 

 

30

9

 

 

 

AWIPS shall allow users to select model soundings using the "points" tools; AWIPS shall retrieve the closest available model sounding for the model requested (see also RWPxxxx - Geo-Referencing from "Points")

 

X

X

 

 

 

 

30

10

 

 

 

AWIPS shall display the location of the grid point retrieved in the planar view thumbnail when plotting a vertical profile (SKEWT view)

 

X

X

 

 

 

 

30

11

 

 

 

WFOs/RFCs/NCEP will require the ability to archive model sounding data and latter play back on AWIPS. Users should have the ability to select "all" forecast soundings in database or select individual forecast soundings during the archiving process.

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

 

X

X

 

 

 

 

31

0

 

 

 

Data Availability - Long range models

 

 

 

 

 

 

 

31

1

 

 

 

AWIPS shall disseminate, ingest, store and display on D-2D using the AWIPS Volume Browser the following gridded data:

X

 

X

 

 

 

 

31

1

1

 

 

NOGAPS (Refer to Table 1 in RWP)

X

 

X

 

 

 

 

31

1

2

 

 

UKMET (Refer to Table 2 in RWP)

X

 

X

 

 

 

 

31

1

3

 

 

Canadian GEM Model (Refer to Table 3 in RWP)

X

 

X

 

 

 

 

35

0

 

 

 

Satellite Data Products

 

 

 

 

 

 

 

35

1

 

 

 

AWIPS shall create New Products formats, projections, and resolutions in accordance with "Detailed Data Matrix" document specifications

X

X

 

 

 

 

 

35

3

 

 

 

New products shall be ingested into the AWIPS database

 

X

X

 

 

 

 

35

4

 

 

 

New products shall be integrated into AWIPS user interface in accordance with "AWIPS Operations Concept for New Satellite Products" document specification (5.0, 5.1, 5.2, and interim maintenance implementations as appropriate) ( see matrix and descriptio

 

X

X

 

 

 

 

35

4

1

1

 

*A.1.Geostationary Orbiting Earth Satellite (GOES) BUFR Soundings

 

X

X

 

 

 

 

35

4

1

2

 

*A.2. Polar Orbiting Earth Satellite (POES) BUFR Soundings

 

X

X

 

 

 

 

35

4

2

 

 

*B. GOES BUFR High Density Winds

 

X

X

 

 

 

 

35

4

3

 

 

C. GOES Sounder Derived Product Imagery (DPI) - Lifted Index (LI)

 

X

X

 

 

 

 

35

4

4

 

 

D. GOES Sounder DPI - Total Precipitable Water (TPW)

 

X

X

 

 

 

 

35

4

5

 

 

E. GOES Sounder DPI - Skin Temperature

 

X

X

 

 

 

 

35

4

6

 

 

F. GOES Sounder DPI - Cloud Top Pressure

 

X

X

 

 

 

 

35

4

7

 

 

GOES Satellite Precipitation Estimate (SPE) - Eastern Continental US (E. CONUS)

 

X

X

 

 

 

 

35

4

8

 

 

H. GOES SPE - Western CONUS

 

X

X

 

 

 

 

35

4

9

 

 

I. GOES SPE - Hawaii

 

X

X

 

 

 

 

35

4

10

 

 

GOES SPE - Puerto Rico (SJU)

 

X

X

 

 

 

 

35

4

11

 

 

European Geostationary Satellite (METEOSAT) /GOES- E Composite

 

X

X

 

 

 

 

35

4

12

 

 

Japanese Geostationary Meteorological Satellite (GMS) /GOES-W Composite - Honolulu (HFO) National Composite

 

X

X

 

 

 

 

35

4

13

 

 

GMS/GOES-Western Alaska Region (AR) National Composite -

 

X

X

 

 

 

 

35

4

14

 

 

GMS/GOES - W AR Regional Composite

 

X

X

 

 

 

 

35

4

15

 

 

POES/Defense Meteorological Satellite Program (DMSP) Blended Composite - Marine Surface Wind

 

X

X

 

 

 

 

35

4

16

 

 

POES/DMSP Blended Composite - Marine Precipitable Water

 

X

X

 

 

 

 

35

4

17

 

 

POES/DMSP Blended Composite - Rainfall Rate

 

X

X

 

 

 

 

35

4

18

 

 

POES/DMSP Blended Composite - Sea Surface Temperature

 

X

X

 

 

 

 

35

4

19

 

 

GOES Imager DPI - Hawaii Lifted Index

 

X

X

 

 

 

 

35

4

20

 

 

GOES Imager DPI - Puerto Rico Lifted Index

 

X

X

 

 

 

 

35

4

21

 

 

GOES Imager DPI - Hawaii Precipitable Water

 

X

X

 

 

 

 

35

4

22

 

 

GOES Imager DPI - Puerto Rico Precipitable Water

 

X

X

 

 

 

 

35

4

23

 

 

GOES Imager DPI - Hawaii Skin Temperature

 

X

X

 

 

 

 

35

4

24

 

 

GOES Imager DPI - Puerto Rico Skin Temperature

 

X

X

 

 

 

 

35

4

25

 

 

Scatterometer Marine Surface Winds (BUFR)

 

X

X

 

 

 

 

35

4

26

 

 

Composite GOES Sounder Imagery

 

X

X

 

 

 

 

35

4

27

 

 

POES/DMSP Composite imagery - CONUS National

 

X

X

 

 

 

 

35

4

28

 

 

POES/DMSP Composite imagery - HFO National

 

X

X

 

 

 

 

35

4

29

 

 

POES/DMSP Composite imagery - SJU National

 

X

X

 

 

 

 

35

4

30

 

 

POES/DMSP Blended Composite Soil Wetness

 

X

X

 

 

 

 

35

4

31

 

 

GOES Sounder DPI - Cloud Amount

 

X

X

 

 

 

 

35

4

32

 

 

Northern Hemisphere Four Satellite Composite - Complete (on channel 4) - on GOES-E/W channels

 

X

X

 

 

 

 

35

4

33

 

 

Volcanic Ash Graphic

 

X

X

 

 

 

 

35

4

34

 

 

Not included in Matrix - Satellite Status Text Messages

 

X

X

 

 

 

 

50

0

 

 

 

Improve Line Option in Warngen

 

 

 

 

 

 

 

50

1

 

 

 

AWIPS shall provide the capability to generate text warning products from WarnGen with the option of using either two or three vertices.

X

 

X

 

 

 

 

50

2

 

 

 

AWIPS shall provide the capability to allow users to locally configure the number of vertices desired for product generation with WarnGen, and to allow the user the option of using additional vertices.

X

 

X

 

 

 

 

50

3

 

 

 

AWIPS shall provide the capability to generate text warning products from WarnGen with either of the following user selected wording options:

 

X

X

 

 

 

 

50

3

1

 

 

-"A LINE OF SEVERE THUNDERSTORMS EXTENDED FROM ... TO ... TO ...";

 

X

X

 

 

 

 

50

3

2

 

 

-"SEVERE THUNDERSTORMS EXTENDING ALONG A LINE FROM ... TO ... TO ...."

 

X

X

 

 

 

 

50

4

 

 

 

AWIPS shall provide the capability to allow users to select the option of either a two or a three point line from WarnGen in the generated text warning products.

 

X

X

 

 

 

 

50

5

 

 

 

AWIPS shall provide the capability to include options for the following location designators in the text warning products describing a line of storms generated with WarnGen : -only the nearest towns; -only the reference cities; -both the nearest towns

X

X

 

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

51

0

 

 

 

WarGen Pathcast Improvements

 

 

 

 

 

 

 

51

6

 

 

 

AWIPS shall provide the capability in WarnGen to round Pathcast times down to the nearest 5 minutes, rather than providing a Pathcast with times at a specified minute.

X

 

X

 

 

 

 

51

7

 

 

 

AWIPS shall provide the capability in WarnGen to locally set the Pathcast times for a time window, and also provide the capability to locally set the duration of the time window.

 

X

X

 

 

 

 

51

8

 

 

 

AWIPS shall provide the capability in WarnGen the option to include any of the following conjunctions/prepositions in the text of the Pathcast :

 

X

X

 

 

 

 

51

8

1

 

 

-BEFORE [time];

 

X

X

 

 

 

 

51

8

2

 

 

-AFTER [time];

 

X

X

 

 

 

 

51

8

3

 

 

-BY [time];

 

X

X

 

 

 

 

51

8

4

 

 

-AROUND [time];

 

X

X

 

 

 

 

51

8

5

 

 

-NEAR [time];

 

X

X

 

 

 

 

51

8

6

 

 

-BETWEEN [time 1];

 

X

X

 

 

 

 

51

8

7

 

 

-AND [time 2]

 

X

X

 

 

 

 

51

9

 

 

 

AWIPS shall provide the capability to log both each warning product disseminated from WarnGen, and selected information from each of these disseminated warning products. (As is now done with the WISE program). For each warning product disseminated, the

 

X

X

 

 

 

 

51

9

1

 

 

-product type;

 

X

X

 

 

 

 

51

9

2

 

 

-issue time;

 

X

X

 

 

 

 

51

9

3

 

 

-UGC codes

 

X

X

 

 

 

 

60

0

 

 

 

CRS-Specific Formatter Changes from Build 4.2 and new CRS text formatters/functions to support NOAA Weather Radio

 

 

 

 

 

 

 

60

12

 

 

 

AWIPS shall provide a method for formatting of the W/W/A products for issuance by CRS, including the following: For WSW/NPW this includes:

X

 

 

X

 

 

 

60

12

1

 

 

Split segmented warnings into separate products based on VTEC phenomena and significance codes

X

 

 

X

 

 

 

60

12

2

 

 

Include expiration times from UGC and the effective times from VTEC -Remove old segments and overviews from the CRS

X

 

 

X

 

 

 

60

12

3

 

 

Include the option to send "what, where, when, call-to action", basis and pathcast form of a warning product created from a defined template in order to support concatenated voice capability on CRS

X

 

 

X

 

 

 

60

12

4

 

 

Include a "pipe" command in the CRS text prior to a Call-to-Action (CTA) which specifies the user-defined number of minutes which the message is to play

X

 

 

X

 

 

 

60

12

5

 

 

Provide an end pipe for any products where the CTA is not the end of the product

X

 

 

X

 

 

 

60

12

6

 

 

Provide the capability to designate certain warning products from nearby listening areas to transmit to nearby transmitters without the warning alarm tone activation

X

 

 

X

 

 

 

60

12

7

 

 

Provide the capability to the user to designate that specified products be transmitted to the CRS without activating the tone warning alarm

X

 

 

X

 

 

 

60

12

8

 

 

Provide option to include/not include headlines -Provide complete sentences in the NWR text generated from WarnGen

X

 

 

X

 

 

 

60

12

9

 

 

Limit the repetition of state names by reformatting in form of, "...is in effect for the following counties in Statename a: xxx,yyy and the following counties in Statename b: ppp,qqq,etc"

X

 

 

X

 

 

 

60

12

10

 

 

Limit repetition of full time zones in pathcast segment to only those where multiple time zones are actually listed. Minimally, provide CRS with spaced abbreviations after first reading, to limit length of time needed to broadcast warning, i.e. "Pacific

X

 

 

X

 

 

 

60

12

11

 

 

Add option to include the product issuance time

X

 

 

X

 

 

 

60

12

12

 

 

Add the option to remove the overview from hazards and send as a separate product

X

 

 

X

 

 

 

60

16

 

 

 

AWIPS shall provide a method for formatting the NOW product for issuance by CRS, including the following:

X

 

 

X

 

 

 

60

16

1

 

 

-Provide a method for summarizing NOWs in a similar fashion to that for W/W/As.

X

 

 

X

 

 

 

60

16

2

 

 

-Provide a user-selected option to delete NOWs

X

 

 

X

 

 

 

60

16

3

 

 

-Provide the option to broadcast the NOWcast without specifically listing all geographic areas for which the product covers

X

 

 

X

 

 

 

60

16

4

 

 

-Provide a method for tracking of the NOW products using the expiration time and removing them as they expire

X

 

 

X

 

 

 

60

16

5

 

 

-Provide option to include/not include headlines

X

 

 

X

 

 

 

60

16

6

 

 

-Provide the capability to either send all NOWs to any applicable towers, or to assign one county per tower

X

 

 

X

 

 

 

61

0

 

 

 

Local Storm Reports

 

 

 

 

 

 

 

61

1

 

 

 

AWIPS shall provide the capability for the user to save draft work versions of a Local Storm Report (LSR) and clearly display the status of each specific product as either submitted, archived, or draft.

 

X

 

X

 

 

 

61

2

 

 

 

AWIPS shall provide a Graphical User Interface (GUI) with the capability to graphically display the spotter location and spotter id over a map background of the WFO County Warning Area (CWA).

 

X

X

 

 

 

 

61

2

1

 

 

In addition, this GUI shall allow display of both the spotter name and phone number. REFER TO RWP167

 

X

X

 

 

 

 

61

3

 

 

 

AWIPS shall provide a database for storing data from all spotters, to provide storage of the name, phone number and location of spotter report.

 

X

 

 

 

 

 

61

3

1

 

 

The phone number and name shall not be included in any generated LSR product.

 

X

 

X

 

 

 

61

4

 

 

 

AWIPS shall provide the capability to generate a list of all spotter reports within a user defined time window for any user selected storm event, and to compile a summary total event LSR for each WFO, based upon user input starting and ending times and da

 

X

 

X

 

 

 

61

21

 

 

 

AWIPS shall automatically insert the County and State information from the city direction and distance data.

 

X

 

X

 

 

 

61

21

1

 

 

The capability for the user to edit the list of towns shall be provided in the LSR Product Generation GUI.

 

X

 

X

 

 

 

61

26

 

 

 

AWIPS shall provide a configuration file to allow all offices to turn on the LSR program simultaneously at a coordinated and announced time.

 

X

 

X

 

 

 

61

28

 

 

 

AWIPS shall automatically save the LSR product to the database when the official product is disseminated.

 

X

 

X

 

 

 

69

0

 

 

 

Aviation Terminal Forecast (TAF) Verification

 

 

 

 

 

 

 

69

1

 

 

 

AWIPS shall archive and verify all TAF forecasts issued by a WFO.

 

X

 

X

 

 

 

69

2

 

 

 

AWIPS shall provide an interactive graphical user interface which displays the TAF verification data at the WFO.

 

X

 

X

 

 

 

69

3

 

 

 

AWIPS shall provide verification data for each scheduled TAF issuance time (00Z, 06Z, 12Z, and 18Z) and each unscheduled, amended TAF issuance.

 

X

 

X

 

 

 

69

4

 

 

 

AWIPS shall provide the user display capability for verification data for combinations of issuance times.

 

X

 

X

 

 

 

69

5

 

 

 

AWIPS shall provide the capability to display verification data for user-specified periods, e.g., a day, multiple days, a month, multiple months, a season, multiple seasons, a year, multiple years.

 

X

 

X

 

 

 

69

6

 

 

 

AWIPS shall provide verification separately for each operational TAF location issued by the WFO.

 

X

 

X

 

 

 

69

7

 

 

 

AWIPS shall transmit all archived TAF verification data from the WFO to National Weather Service Headquarters.

 

X

 

X

 

 

 

69

8

 

 

 

AWIPS shall provide the user the capability to display data for a single TAF, multiple TAFs, or all the TAFs issued by the WFO.

 

X

 

X

 

 

 

69

9

 

 

 

AWIPS shall perform verification for the following forecast periods: 1. 0-24 hours; 2. 0-6 hours; 3. 6-12 hours; 4. 12-18 hours; 5. 18-24 hours

 

X

 

X

 

 

 

69

10

 

 

 

AWIPS shall allow verification of TAFs based on forecaster ID.

 

X

 

X

 

 

 

69

11

 

 

 

AWIPS shall provide verification of the automated TAFs which are produced by the TDL LAMP system.

 

X

 

X

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

75

0

 

 

 

IFPS Full Capability, Create marine forecast products

 

 

 

 

 

 

 

75

1

 

 

 

AWIPS shall provide the user the capability of generating the marine official text products, in format as specified in the NWS Operations Manuals C43, D51, D52, C11 with IFPS. These products shall include the following:

X

 

 

X

 

 

 

75

1

1

 

 

Routine Coastal Forecasts and Products:

X

 

 

X

 

 

 

75

1

1

1

 

Coastal Marine Forecast (CWF)

X

 

 

X

 

 

 

75

1

1

2

 

Offshore Forecast (OFF) [5.1 maintenance] issued by WFO ANC, MPC, TPC

X

 

 

X

 

 

 

75

1

1

3

 

Marine Verification Forecast (MVF)

X

 

 

X

 

 

 

75

1

1

4

 

Coast Guard Reports (CGR) - This is supposed to be for incoming reports from USCG stations. However, it appears that some offices are issuing these for the USCG and at least one is using it for something else.

X

 

 

X

 

 

 

75

1

1

5

 

Tide and Water Levels (TID)

X

 

 

X

 

 

 

75

1

1

6

 

High Seas Forecast issued by WFO Honolulu, MPC, TPC

X

 

 

X

 

 

 

75

1

2

 

 

2 Non-routine Forecasts and Products:

X

 

 

X

 

 

 

75

1

2

1

 

Alaska Ice Products (Seasonal)

X

 

 

X

 

 

 

75

1

2

2

 

Miscellaneous Marine Products (OSO) - [5.2] Only one office issues this.

X

 

 

X

 

 

 

75

1

2

3

 

Recreational Forecast (REC)

X

 

 

X

 

 

 

75

1

2

4

 

Other Marine Reports (OMR) - This is a routine product for some offices, but not for all.

X

 

 

X

 

 

 

75

1

2

5

 

Plain Language Ship Reports (PLS)

X

 

 

X

 

 

 

75

1

2

6

 

Special Tide Report (TID) - This is supposed to be a formatted message for specific data, however, some offices are using it for all sorts of other things.

X

 

 

X

 

 

 

75

2

 

 

 

AWIPS shall provide the user the ability to graphically underlay the Gulf Stream Analysis product over a map of the Marine Coastal Zones in the Graphical Forecast Editor (GFE) in IFPS to provide the user a visual guide for locations over which higher seas

X

 

 

X

 

 

 

75

3

 

 

 

AWIPS shall provide the user the capability of ingesting, decoding and displaying grids generated as output from local models into the IFPS, for use as initialization grids for the Great Lakes Forecast area.

X

 

 

X

 

 

 

75

4

 

 

 

AWIPS shall provide the capability to view and edit matrices and grids of marine elements in IFPS which have been derived from model grids for the marine zones.

X

 

 

X

 

 

 

75

5

 

 

 

AWIPS shall provide the user the ability to specify geographic areas in IFPS by choosing end points along a coastline.

X

 

 

X

 

 

 

75

6

 

 

 

AWIPS shall provide access to gridded model forecasts from the following models to be selected by the users as a sources for initialization of the grids within IFPS: AVN MRF NOAA Global Wavewatch III 100 km resolution NOAA Regional Alaskan Waters Wavewa

 

X

 

X

 

 

 

75

7

 

 

 

AWIPS shall provide the following model parameters required for use in the initialization of the gridded fields for use in IFPS: Seas (swell height + 1/3 wind wave height) Swell 10 meter winds temperature for ice accretion obstructions to vision such

 

X

 

X

 

 

 

75

8

 

 

 

AWIPS shall provide the capability to include the Valid Time Event Code (VTEC) within the generated official text products. VTEC shall be added to the Coastal Waters Forecast, Offshore Forecast, Nearshore Forecast, and the Open Lake Forecast. New codes w

 

X

 

X

 

 

 

89

0

 

 

 

Sharing products from Product Maker

 

 

 

 

 

 

 

89

1

 

 

 

AWIPS shall have the capability to transfer products derived in the product maker between different forecast offices, national centers, and river forecast centers.

X

X

 

 

 

 

 

89

2

 

 

 

AWIPS shall have products that are created in the product maker on any workstation be available on any other workstation in the same forecast office.

X

 

X

 

 

 

 

105

0

 

 

 

Tools and Environment

 

 

 

 

 

 

 

105

1

 

 

 

AWIPS shall have a disc partition to keep data used for local software development separate from the operational data sets.

X

X

 

X

 

 

 

105

2

 

 

 

Guidelines for AWIPS local software development shall be available to AWIPS users in electronic format [there in 4.3].

X

X

 

X

 

 

 

105

3

 

 

 

APIs and libraries, and associated instructions, shall be provided to allow locally developed software that produces displays to interface with AWIPS data base and display capabilities.

X

X

 

X

 

 

 

107

0

 

 

 

Proximity Alarm

 

 

 

 

 

 

 

107

1

 

 

 

AWIPS shall provide an audible and visual alarm when a Satellite Precipitation Estimate (SPE) is issued which includes any portion of a site's area of responsibility. [first maintenance release] - replace AFOS capability

 

X

X

 

 

 

 

107

2

 

 

 

AWIPS shall provide an audible and visual alarm when a Satellite Precipitation Estimate (SPE) is issued which includes any portion of a neighboring site's area of responsibility for which the site is currently providing service backup. The user should no

 

X

X

 

 

 

 

107

3

 

 

 

AWIPS shall provide an audible and visual alarm when a site-specified forecast, watch, or warning product type which uses UGC codes or latitude/longitude coordinates is issued by other sites and includes any portion of a geographic area defined by the sit

 

X

X

 

 

 

 

108

0

 

 

 

Late And Missing Forecast Products Alarm

 

 

 

 

 

 

 

108

1

 

 

 

AWIPS shall allow the site to identify the expected arrival time of critical forecast or guidance products, the amount of time which should pass before the product is identified as late or missing, and the type and level of notification which should be pr

 

X

X

 

 

 

 

108

2

 

 

 

AWIPS shall allow the site to identify the time at which selected forecast products are to be issued, the amount of time prior to this time or after this time at which a notification should be sent, the type or level of notification, and the workstation

 

X

X

 

 

 

 

108

3

 

 

 

AWIPS shall allow the forecaster to identify the time at which a prepared product should be distributed. - similar to capability of XNOW to allow a forecaster to complete edit of a forecast product and schedule its transmittal at a given time in the futu

 

X

X

 

 

 

 

108

4

 

 

 

AWIPS shall allow the site to execute a site-defined procedure or an AWIPS functionality, such as the Hourly Weather Roundup, based on time of day. This capability is available to some extent through the use of "cron" jobs. The site should have the abil

 

X

X

 

 

 

 

108

5

 

 

 

AWIPS shall allow the site to execute a site-defined procedure or an AWIPS functionality, such as the TAF monitor, based on receipt of some data or product. This capability is available to some extent through the use of generic AWIPS triggers, but multip

 

X

X

 

 

 

 

167

0

 

 

 

Entering Spotter Reports ( REFER TO RWP 66)

 

 

 

 

 

 

 

167

1

 

 

 

AWIPS shall provide a template to support entry of spotter reports into the AWIPS database. Where appropriate, field entry should support user selections (e.g. the state field may allow the user to select on a pop up or pull down menu from the states inc

 

X

X

X

 

 

 

167

1

1

 

 

The template shall allow inclusion of the following input fields if the information is available :

 

X

X

X

 

 

 

167

1

1

1

 

Source of Report (e.g., county sheriff, John Smith, trained spotter, ham observer K3B76H, boater)

 

X

X

X

 

 

 

167

1

1

2

 

Type and magnitude of event or observation (e.g., rotating wall cloud, dime size hail, roof taken off barn)

 

X

X

X

 

 

 

167

1

1

3

 

Date of event (default today)

 

X

X

X

 

 

 

167

1

1

4

 

Time of event or observation (default now)

 

X

X

X

 

 

 

167

1

1

5

 

State name (default may be assigned by site or based on observer)

 

X

X

X

 

 

 

167

1

1

6

 

County, City name, or Marine Zone (may assign default based on id of observer)

 

X

X

X

 

 

 

167

1

1

7

 

Location of event or observation

 

X

X

X

 

 

 

167

1

1

8

 

Fatalities or injuries reported

 

X

X

X

 

 

 

167

1

1

9

 

Report Received by

 

X

X

X

 

 

 

167

1

1

10

 

Comments (such as location of nearest buoy or CMAN station for reports from boater)

 

X

X

X

 

 

 

167

2

 

 

 

AWIPS shall support creation of a spotter location database and a geographic depictable (map) of the customary spotter locations.

X

 

X

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

168

0

 

 

 

PUP Functionality

 

 

 

 

 

 

 

168

3

 

 

 

AWIPS shall provide complete information contained in the product legend of a displayed product, such as the Volume Coverage Pattern, the product type, the resolution(s) of the products contained in the display, the location of the maximum value, and othe

 

X

X

 

 

 

 

168

4

 

 

 

AWIPS shall display values of Vr shear in standard scientific nomenclature as sec -1, from the highest azimuthal range data available to ensure the optimal estimate has been made. Estimates still differ from the PUP. See OSF OTB report.

 

X

X

 

 

 

 

168

5

 

 

 

AWIPS shall display the mean distance from the RDA and the length of the selected line used in the Vr Shear computation.

 

X

X

 

 

 

 

168

6

 

 

 

AWIPS shall be capable of calculating and displaying the Vr shear on all four panels of a 4-panel display of velocity at four elevation angles by one single selection.

 

X

X

 

 

 

 

168

7

 

 

 

AWIPS shall be capable of displaying all parts (graphic, graphic attributes, and alphanumeric) of all WSR-88D products. (These include CFC, USP, SS, and CSC text information.) The CFC product needs the segment number and the type of suppression (surveilla

 

X

X

 

 

 

 

168

8

 

 

 

AWIPS shall provide product-specific information in addition to date-time data in the product inventory list so the user can easily identify and select unique radar products from the radar inventory. This is the display of parameters specified in the RPG

 

X

X

 

 

 

 

168

8

1

 

 

Data shall be displayed in a user-friendly manner (e.g., not binary or hexadecimal, but instead presented using common units such as floating point degrees, nmi, knots, or kilo-feet) and be consistent with the display of the same information in product re

 

X

X

 

 

 

 

168

9

 

 

 

AWIPS shall provide the capability for user selection of adaptable data for the display of Hail and SCIT products. These include Hail-Index symbol fill-in thresholds, numbers of storms shown on the STI graphic with indication of how many cells are not sho

 

X

X

 

 

 

 

168

10

 

 

 

AWIPS shall display azimuth-range readouts in nautical miles,

 

X

X

 

 

 

 

168

10

1

 

 

and if there are distance scales on the product, such as in cross section products, they shall also be displayed in nautical miles.

 

X

X

 

 

 

 

168

10

2

 

 

The operator shall be given the ability to toggle between nautical miles, statute miles, and kilometers.

 

X

X

 

 

 

 

168

11

 

 

 

AWIPS shall use the same product identifier mnemonics as in the WSR-88D. For example, reflectivity products are R in the 88D parlance, and Z in the AWIPS usage. The DHR product is now correctly labeled. The USP product is still identified as the USRA prod

 

X

X

 

 

 

 

168

12

 

 

 

(AWIPS shall follow the usage in the WSR-88D for display of hail symbols. AWIPS still displays the hail size immediately to the right of the hail symbol. The related storm is plotted at its centroid position.) This was corrected in Build 4.3.

 

X

X

 

 

 

 

168

13

 

 

 

AWIPS shall follow the usage in the WSR-88D for display of mesocyclone symbols. The relative size of the mesocyclone doesn't appear to be relative to the magnification. And the cell it is identified with is still kept at the same distance to the right of

 

X

X

 

 

 

 

168

14

 

 

 

AWIPS shall follow the usage in the WSR-88D for display of the ETVS symbol. There is a default that can be set for display of the ETVS.

 

X

X

 

 

 

 

168

15

 

 

 

NEW - AWIPS shall provide the status and location of alerts immediately after the conditions are met, as is presently available in the PUP ( SAL) command. The text browser would display the pertinent information concerning the alert thresholds exceeded in

 

X

X

 

 

 

 

169

0

 

 

 

National Radar Composite

 

 

 

 

 

 

 

169

1

 

 

 

AWIPS shall support central generation and distribution of a half-hourly National radar composite with a 10-km resolution based on information provided in the radar-coded message from every WSR-88D

X

 

X

 

 

 

 

169

2

 

 

 

AWIPS shall support central generation and distribution of a National radar reflectivity composite with a 2-km resolution based on the 0.5o elevation 1.1-nm (2-km) resolution reflectivity data provided from every WSR-88D; this product shall be generated

X

X (TDL)

X

X

 

 

 

169

6

 

 

 

AWIPS shall generate local and state radar composites of the data types identified in (2) and (3). All composite products except the three-hour precipitation and user selectable precipitation shall be generated and displayed at six minute intervals. Thr

 

X

X

X

 

 

 

169

6

1

 

 

All composite products except the three-hour precipitation and user selectable precipitation shall be generated and displayed at six minute intervals.

 

X

X

X

 

 

 

169

6

2

 

 

Three hour precipitation and user selectable precipitation shall be generated and displayed at the intervals defined in (3).

 

X

X

X

 

 

 

169

6

3

 

 

These composite products shall be based on the best resolution provided by available products used in the composite. AWIPS should be able to identify which radar was used to provide the data at any given point, as well as the data value, elevation of the

 

X

X

X

 

 

 

171

0

 

 

 

Audible Alarm For WSR-88D Problems

 

 

 

 

 

 

 

171

1

 

 

 

AWIPS shall provide an audible and visual alarm within 5 minutes for any of the conditions that cause loss of data for which general status messages are available. The list of messages which indicate loss of data may be obtained from the description below

 

X

X

 

 

 

 

171

2

 

 

 

AWIPS shall generate an audible and visual alarm within 5 minutes when system or process monitors indicate that AWIPS is no longer receiving or storing data from any associated radar.

 

X

X

 

 

 

 

171

3

 

 

 

This capability is required for support to warning operations and shall function regardless of failure of any application server, data server, communications processor, or other system component.

 

X

X

 

 

 

 

175

0

 

 

 

Open RPG Interface (LAN interface, 8-bit Z and V)

 

 

 

 

 

 

 

175

1

 

 

 

AWIPS shall support connectivity to the Open Radar Product Generator (ORPG) through a 100 Mbps Local Area Network (LAN) connection using TCP/IP as well as through the existing modems - ORPG Build 1

 

X

 

 

 

X

 

175

2

 

 

 

The AWIPS/ORPG LAN connection shall allow acquisition of radar data and products from the ORPG using Routine Product Set (RPS) lists, One-Time Requests (OTR), alerts, status messages, and automatic distribution of products from the ORPG based on a Product

 

X

 

 

 

X

 

175

4

 

 

 

AWIPS shall use the ORPG LAN connection to request and receive new radar products, such as

 

X

 

 

 

X

 

175

4

1

 

 

Data Array Products, including Base Reflectivity, Base Velocity, VWP, and others ORPG Build 1

 

X

 

 

 

X

 

175

4

2

 

 

SCAN-related Products and Data ORPG Build 1

 

X

 

 

 

X

 

175

4

3

 

 

Snow Accumulation Product ORPG Build 2

 

X

 

 

 

X

 

175

4

4

 

 

User selectable Layer Composite Reflectivity ORPG Build 1

 

X

 

 

 

X

 

175

4

5

 

 

More Fixed Layers of Layer Composite Reflectivity ORPG Build 2

 

X

 

 

 

X

 

175

4

6

 

 

Freezing Level Layer Composite Reflectivity ORPG Build 2

 

X

 

 

 

X

 

175

4

7

 

 

Composite Reflectivity with Anomalous Propagation edited ORPG Build 1

 

X

 

 

 

X

 

175

4

8

 

 

Radar Echo Classifier ORPG Build 2

 

X

 

 

 

X

 

175

4

9

 

 

FAA ITWS Digital Base Velocity ORPG Build 1

 

X

 

 

 

X

 

175

4

10

 

 

Updates by elevation scan of Volume-Based Derived products ORPG Build 2 These will include products based on new Volume Coverage Patterns

 

X

 

 

 

X

 

175

6

 

 

 

AWIPS shall support the ORPG Precipitation Processing Subsystem by distributing precipitation bias information from AWIPS to the ORPG via the AWIPS LAN . ORPG Build 1

 

X

 

 

 

X

 

192

0

 

 

 

Retain Site Customized Localization/Configuration Files with AWIPS Upgrades

 

 

 

 

 

 

 

192

1

 

 

 

AWIPS shall provide techniques (may be combination of software and operational procedures) that allow site personnel to recover local modifications to the system within two hours after a software upgrade.

 

X

X

 

 

 

 

192

1

1

 

 

This shall include, but not necessarily be limited to, WARNGEN localizations and modifications done to the various depictables in D2D such as satellite/radar color curves, etc.

 

X

X

 

 

 

 

192

2

 

 

 

AWIPS shall have the capability to merge nationally-maintained files with locally modified files in a way so when there is a national upgrade, the site has the ability to control whether to permit overwriting of any local changes which have been made.

 

X

X

 

 

 

 

192

3

 

 

 

The functionalities in requirements 1 and 2 shall exist at WFOs, RFCs, and the National Centers.

 

X

X

 

 

 

 

193

0

 

 

 

Archive of Individual Cases

 

 

 

 

 

 

 

193

2

 

 

 

AWIPS shall allow the user to select which type or which combinations of types of data to store.

 

X

X

 

 

 

 

193

3

 

 

 

AWIPS shall allow the user to select time window of data to be stored (typically 1 - 3 days is maximum).

 

X

X

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

206

0

 

 

 

Flash Flood Monitoring and Prediction (Basin)

 

 

 

 

 

 

 

206

9

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour FFG data on an areal display of counties and river basins.

X

 

X

X

X

 

 

206

10

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour DPA radar precipitation accumulations on an areal display of counties and river basins.

 

X

 

X

X

 

 

206

11

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Digital Hybrid Reflectivity (DHR) radar precipitation accumulations on an areal display of counties and river basins.

 

X

 

X

X

 

 

206

12

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Flash Flood Threat data (based on DHR radar data) on an areal display of counties and river basins both as ratio (i.e., precipitation/FFG) and as difference (i.e., precipitation - FFG).

 

X

 

X

X

 

 

206

13

 

 

 

The user shall be able to display a tabular listing of Flash Flood Threats based on DHR radar data.

 

X

 

X

X

 

 

206

14

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Multisensor Precipitation Estimator (MPE) gage-only, radar-only, and multisensor precipitation accumulations on an HRAP grid areal display.

 

X

 

 

X

 

 

206

15

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Multisensor Precipitation Estimator (MPE) gage-only, radar-only, and multisensor precipitation accumulations on an areal display of counties and river basins.

 

X

 

 

X

 

 

206

16

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Flash Flood Threat data (based on MPE data) on an HRAP grid areal display both as ratio (i.e., precipitation/FFG) and as difference (i.e., precipitation - FFG).

 

X

 

 

X

 

 

206

17

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Flash Flood Threat data (based on MPE data) on an areal display of counties and river basins both as ratio (i.e., precipitation/FFG) and as difference (i.e., precipitation - FFG).

 

X

 

 

X

 

 

206

18

 

 

 

The user shall be able to display a tabular listing of Flash Flood Threats based on MPE data.

 

X

 

 

X

 

 

206

19

 

 

 

The user shall be able to display 1-hour or 6-hour Quantitative Precipitation Forecast (QPF) precipitation accumulations on an HRAP grid areal display.

 

X

X

 

X

 

 

206

20

 

 

 

The user shall be able to display 1-hour or 6-hour QPF precipitation accumulations on an areal display of counties and river basins.

 

X

X

 

X

 

 

206

21

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Flash Flood Threat data (based on QPF data) on an HRAP grid areal display both as ratio (i.e., precipitation/FFG) and as difference (i.e., precipitation - FFG).

 

X

 

 

X

 

 

206

22

 

 

 

The user shall be able to display 1-hour, 3-hour, and 6-hour Flash Flood Threat data (based on QPF data) on an areal display of counties and river basins both as ratio (i.e., precipitation/FFG) and as difference (i.e., precipitation - FFG).

 

X

 

 

X

 

 

206

23

 

 

 

The user shall be able to display a tabular listing of Flash Flood Threats based on QPF data.

 

X

 

 

X

 

 

206

24

 

 

 

The user shall be able to display differences between QPF and observed precipitation on an areal display of counties and river basins.

 

X

X

 

X

 

 

207

0

 

 

 

Tools To Support Service Backup

 

 

 

 

 

 

 

207

1

 

 

 

Users shall be able to acquire and use the requisite product templates and product control files used by RiverPro for the offices which they must provide service backup.

X

 

 

 

X

 

 

207

2

 

 

 

The IHFS Database shall provide data structures that define the ownership of station locations, counties, forecast zones, and river basins. The ownership of these data entities is required so that users may use filters in the Hydro applications to focus

X

 

 

 

X

 

 

207

3

 

 

 

The IHFS Database shall provide data structures that define the backup responsibility for station locations, counties, forecast zones, and river basins. The backup responsibility of these data entities is required so that users may use filters in the Hyd

X

 

 

 

X

 

 

207

4

 

 

 

Users shall be able to define "service groups" and assign various station locations, counties, forecast zones, and river basins to these user-defined service groups. Two special service groups would be the primary service backup group and the secondary s

 

X

 

 

X

 

 

207

5

 

 

 

The user shall be able to use filters based on service groupings of station locations, counties, forecast zones, and river basins to control which of these data entities are displayed and/or used by HydroBase, HydroView, RiverPro, and Hydro Time Series.

X

 

 

 

X

 

 

207

5

1

 

 

no filter, show all data

X

 

 

 

X

 

 

207

5

2

 

 

show/use entities owned by this office

X

 

 

 

X

 

 

207

5

3

 

 

show/use entities defined for primary service backup

X

 

 

 

X

 

 

207

5

4

 

 

show/use entities defined for primary service backup and owned by neighbor office

X

 

 

 

X

 

 

207

5

5

 

 

show/use entities defined for secondary service backup

X

 

 

 

X

 

 

207

5

6

 

 

show/use entities defined for secondary service backup and owned by neighbor office

X

 

 

 

X

 

 

207

5

7

 

 

show/use entities owned by neighbor office

X

 

 

 

X

 

 

207

5

8

 

 

show/use entities defined for other user-defined service groupings

X

 

 

 

X

 

 

208

0

 

 

 

WHFS User-Requested Enhancements

 

 

 

 

 

 

 

208

14

 

 

 

The name field for a station location shall be expanded to 50 characters.

X

 

 

 

X

 

 

208

15

 

 

 

The user shall be able to define a "forecast issuance stage" and a "forecast issuance flow" for a river forecast point. Typically, the forecast issuance stage (flow) will be the stage (flow) at which the RFC issues a forecast if the location is not a dai

 

X

 

 

X

 

 

208

16

 

 

 

The existing staff gage page which can be printed shall be modified such that:

 

X

 

 

X

 

 

208

16

1

 

 

The increments shall be either 2- or 5-foot increments, instead of the current 6-foot increments.

 

X

 

 

X

 

 

208

16

2

 

 

The bottom label of the staff gage shall be either flood stage or the lowest damage description, whichever is lower

 

X

 

 

X

 

 

208

16

3

 

 

The top level of the staff gage shall be either the flood of record, or the high water mark, whichever is higher.

 

X

 

 

X

 

 

208

16

4

 

 

The display of historical crests along the right side of the staff gage shall be limited to those that fit on the same page as the staff gage.

 

X

 

 

X

 

 

208

16

5

 

 

The display of historical crests along the right side of the staff gage shall include the highest values known.

 

X

 

 

X

 

 

208

17

 

 

 

The existing rating curve display shall be enhanced to show: a. Most recent shift applied, b. The USGS rating number, and c. The date of the rating.

X

 

 

 

X

 

 

208

18

 

 

 

When applying a shift to the existing rating curve, the base rating curve shall be retained in the database.

X

 

 

 

X

 

 

208

19

 

 

 

A history of shifts applied to the base rating curve shall be retained.

X

 

 

 

X

 

 

208

20

 

 

 

The field for the Observer's name shall be expanded to ?? characters.

 

X

 

 

X

 

 

208

21

 

 

 

The user shall have the ability to print Impact Statements.

X

 

 

 

X

 

 

208

22

 

 

 

The user shall be able to sort historical crest information by:

X

 

 

 

X

 

 

208

22

1

 

 

Date,

X

 

 

 

X

 

 

208

22

2

 

 

Stage,

X

 

 

 

X

 

 

208

22

3

 

 

Flow (Discharge).

X

 

 

 

X

 

 

208

24

 

 

 

The user shall be alerted if the observed or forecast stage (flow) exceeds flood stage (flow) without the Hydroview display on the screen.

X

 

 

 

X

 

 

208

25

 

 

 

The user shall be able to set defaults for the Hydroview map displays of stage (flow), precipitation.

 

X

 

 

X

 

 

208

25

1

 

 

The user shall be able to define a default number of hours to look back for data, and the basis for the data (i.e. most recent observed data, maximum forecast data, or the higher of the two) for the Hydroview stage (flow) map display.

 

X

 

 

X

 

 

208

25

2

 

 

The user shall be able to define a default ending time and duration for the Hydroview precipitation map display.

 

X

 

 

X

 

 

208

26

 

 

 

The user shall be able to define which temperature (maximum, minimum, or instantaneous) elements and which snow (snow depth, snow water equivalent) elements to display on the Hydroview map display.

X

 

 

 

X

 

 

208

27

 

 

 

The flood stage shall be displayed in the Time Series Tabular display.

X

 

 

 

X

 

 

208

28

 

 

 

The staff gage display shall be enhanced to show the date of the record stage.

 

X

 

 

X

 

 

208

29

 

 

 

The Riverpro application shall update automatically with the most recent data, so the user doesn't have to manually "refresh" the application.

 

X

 

 

X

 

 

208

30

 

 

 

The Riverpro application shall support the inclusion of multiple time zones in the formatted products.

 

X

 

 

X

 

 

208

31

 

 

 

When formatting products, the Riverpro application shall be able to distinguish between rising and falling conditions so that point-specific information (e.g. impact statements) can be included based upon the state of the river (i.e. rising or falling).

 

X

 

 

X

 

 

208

32

 

 

 

The Riverpro application shall create products that comply with the Valid Time Event Coding (VTEC) specifications.

X

 

 

 

X

 

 

208

33

 

 

 

The Riverpro application shall be able to create segmented products.

X

 

 

 

X

 

 

208

34

 

 

 

The user shall be able to define flood categories in terms of flow or discharge (e.g. cubic feet per second).

X

 

 

 

X

 

 

208

35

 

 

 

The Hydroview map display shall be able to plot values of flow or discharge which have been derived from an observed stage value and a rating curve.

 

X

 

 

X

 

 

208

36

 

 

 

The Hydroview map display shall be able to plot values of stage which have been derived from an observed flow or discharge value and a rating curve.

 

X

 

 

X

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

209

0

 

 

 

Site-Specific Hydrologic Prediction

 

 

 

 

 

 

 

209

1

 

 

 

The IHFS Database shall be able to store enhanced information about river rating curves, that is, multiple rating curves per station that differ by revision date and offsets that can be applied to base rating curves.

X

 

 

 

X

 

 

209

2

 

 

 

The WHFS GUI (i.e., HydroBase) shall allow the user to add, delete, and modify the enhanced river rating curve reference data.

X

 

 

 

X

 

 

209

7

 

 

 

The IHFS Database shall store time zone information for station locations. The user shall be able to edit a station location's time zone information.

 

X

 

 

X

 

 

211

0

 

 

 

RFC Field Requested Enhancements

 

 

 

 

 

 

 

211

1

 

 

 

Improved RFC automated hydromet data handling system

X

 

 

 

X

 

 

211

2

 

 

 

RFC Data Display System

X

 

 

 

X

 

 

211

3

 

 

 

NWSRFS river forecast product generation system "text & image"

X

 

 

 

X

 

 

211

5

 

 

 

RFC river forecast verification software

 

X

 

 

X

 

 

211

6

 

 

 

Field User Requested Enhancements for NWSRFS

 

X

 

 

X

 

 

212

0

 

 

 

RFC Wide

 

 

 

 

 

 

 

212

1

 

 

 

Be able to display radar, rain gage, bias adjusted radar and multisensor fields seperately.

X

 

 

 

X

 

 

212

2

 

 

 

Be able to display which radar DPAs are available and which radar DPAs are not available.

X

 

 

 

X

 

 

212

3

 

 

 

Be able to display height of coverage array, radar coverage map (also called index array) and bias table.

X

 

 

 

X

 

 

212

4

 

 

 

Be able to remove precipitation (i.e., AP) from as well as add precipitation to the RFC grid and then display the new gridded field data.

X

 

 

 

X

 

 

212

5

 

 

 

Be able to zoom in and out of the gridded data field and edit displayed gage data.

X

 

 

 

X

 

 

212

6

 

 

 

Utilize the time lapse feature.

X

 

 

 

X

 

 

212

7

 

 

 

Create pseudo gages.

X

 

 

 

X

 

 

213

0

 

 

 

Gridded Threshold Runoff

 

 

 

 

 

 

 

213

1

 

 

 

AWIPS shall provide a tool for the River Forecast Centers (RFC) to derive gridded threshold runoff values used in the Flash Flood Guidance System (FFGS) to compute gridded flash flood guidance.

X

 

 

 

X

 

 

214

0

 

 

 

NWSRFS Major Enhancements

 

 

 

 

 

 

 

214

1

 

 

 

Ability to dynamically model river systems that have a dendritic tree-type structure with nth order tributaries.

X

 

 

 

X

 

 

214

2

 

 

 

Levee overtopping/crevasse flow modeling

X

 

 

 

X

 

 

214

5

 

 

 

Ability to use RES-J operation to model a single reservoir within NWSRFS

 

X

 

 

X

 

 

214

6

 

 

 

Ability to use RES-J operation to model a 2 reservoir system within NWSRFS

 

X

 

 

X

 

 

215

0

 

 

 

Generate sounding-based initializations as model fields arrive

 

 

 

 

 

 

 

215

1

 

 

 

AWIPS shall provide a method to generate sounding based initializations within IFPS for the model levels and parameters required for initialization of sensible weather elements from the following models :

 

X

X

 

 

 

 

215

1

1

 

 

-NGM

 

X

X

 

 

 

 

215

1

2

 

 

-AVN

 

X

X

 

 

 

 

215

1

3

 

 

-MRF

 

X

X

 

 

 

 

215

1

4

 

 

-ETA

 

X

X

 

 

 

 

215

1

5

 

 

-RUC II

 

X

X

 

 

 

 

215

1

6

 

 

-Global WaveWatch III [100 km resolution]

 

X

X

 

 

 

 

215

1

7

 

 

-Regional Alaskan Waters Wave Watch III [30 km resolution]

 

X

X

 

 

 

 

215

1

8

 

 

-Regional Western North Atlantic Wave Watch III [30 km resolution]

 

X

X

 

 

 

 

215

2

 

 

 

AWIPS shall provide a method of initialization from the models for the following sensible weather elements:

 

X

X

 

 

 

 

215

2

1

 

 

-temperature

 

X

X

 

 

 

 

215

2

2

 

 

-dewpoint temperature

 

X

X

 

 

 

 

215

2

3

 

 

-maximum and minimum temperature

 

X

X

 

 

 

 

215

2

4

 

 

-relative humidity

 

X

X

 

 

 

 

215

2

5

 

 

-maximum and minimum relative humidity

 

X

X

 

 

 

 

215

2

6

 

 

-wind at surface over land and water

 

X

X

 

 

 

 

215

2

7

 

 

-wind at 20 feet

 

X

X

 

 

 

 

215

2

8

 

 

-transport wind

 

X

X

 

 

 

 

215

2

9

 

 

-sky condition

 

X

X

 

 

 

 

215

2

10

 

 

-probability of precipitation

 

X

X

 

 

 

 

215

2

11

 

 

-quantitative precipitation

 

X

X

 

 

 

 

215

2

12

 

 

-snow amount

 

X

X

 

 

 

 

215

2

13

 

 

-weather

 

X

X

 

 

 

 

215

2

14

 

 

-wave

 

X

X

 

 

 

 

215

2

15

 

 

-swell vector

 

X

X

 

 

 

 

215

2

16

 

 

-lightning activity level

 

X

X

 

 

 

 

215

2

17

 

 

-chance of wetting rain

 

X

X

 

 

 

 

215

2

18

 

 

-Haines Index

 

X

X

 

 

 

 

215

2

19

 

 

-Mixing Height

 

X

X

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

220

0

 

 

 

Weather color tables display for the Graphical Forecast Editor

 

 

 

 

 

 

 

220

1

 

 

 

AWIPS shall provide a default set of colors and fill patterns in GFE for each of the following sensible weather elements available within IFPS:

X

 

X

 

 

 

 

220

1

1

 

 

-temperature

X

 

X

 

 

 

 

220

1

2

 

 

-dewpoint temperature

X

 

X

 

 

 

 

220

1

3

 

 

-maximum and minimum temperature

X

 

X

 

 

 

 

220

1

4

 

 

-relative humidity

X

 

X

 

 

 

 

220

1

5

 

 

-maximum and minimum relative humidity

X

 

X

 

 

 

 

220

1

6

 

 

-wind at surface

X

 

X

 

 

 

 

220

1

7

 

 

-wind at 20 feet

X

 

X

 

 

 

 

220

1

8

 

 

-transport wind

X

 

X

 

 

 

 

220

1

9

 

 

-sky condition

X

 

X

 

 

 

 

220

1

10

 

 

-probability of precipitation

X

 

X

 

 

 

 

220

1

11

 

 

-quantitative precipitation

X

 

X

 

 

 

 

220

1

12

 

 

-snow amount

X

 

X

 

 

 

 

220

1

13

 

 

-weather

X

 

X

 

 

 

 

220

1

14

 

 

-wave

X

 

X

 

 

 

 

220

1

15

 

 

-swell vector

X

 

X

 

 

 

 

220

1

16

 

 

-lightning activity level

X

 

X

 

 

 

 

220

1

17

 

 

-chance of wetting rain

X

 

X

 

 

 

 

220

1

18

 

 

-Haines Index

X

 

X

 

 

 

 

220

1

19

 

 

-Mixing Height

X

 

X

 

 

 

 

229

0

 

 

 

Detail levels by zone

 

 

 

 

 

 

 

229

1

 

 

 

AWIPS shall provide the capability for users to set the detail levels which are to be included in the text of the following products created at WFOs using IFPS:

X

 

 

X

 

 

 

229

1

1

 

 

Zone Forecast Product (ZFP)

X

 

 

X

 

 

 

229

1

2

 

 

Coastal Waters Forecast (CWF)

X

 

 

X

 

 

 

229

1

3

 

 

Offshore Forecast (OFF)

X

 

 

X

 

 

 

229

1

4

 

 

Nearshore Forecast (NSH)

X

 

 

X

 

 

 

229

1

5

 

 

Open Lake Forecast (GLF)

X

 

 

X

 

 

 

229

2

 

 

 

AWIPS shall provide the capability in IFPS to allow for user selection of the detail level desired for all the text generated in the following products created using IFPS at all forecast periods out to the day seven period:

X

 

 

X

 

 

 

229

2

1

 

 

Zone Forecast Product (ZFP)

X

 

 

X

 

 

 

229

2

2

 

 

Coastal Waters Forecast (CWF)

X

 

 

X

 

 

 

229

2

3

 

 

Offshore Forecast (OFF)

X

 

 

X

 

 

 

229

2

4

 

 

Nearshore Forecast (NSH)

X

 

 

X

 

 

 

229

2

5

 

 

Open Lake Forecast (GLF)

X

 

 

X

 

 

 

231

0

 

 

 

Snow Level Intervals

 

 

 

 

 

 

 

231

1

 

 

 

AWIPS shall provide the capability to add a new weather element in the Graphical Forecast Editor (GFE) of IFPS for both display of, and for generation of products which include details on snow elevation levels at 6 hour intervals out to the day seven fore

 

X

 

X

 

 

 

231

2

 

 

 

AWIPS shall provide the capability in IFPS for site configurable levels and intervals for snow accumulation forecasts in products generated in both gridded and graphical formats, in user configurable intervals.

 

X

 

X

 

 

 

231

3

 

 

 

AWIPS shall provide the capability in GFE to display gridded fields of forecast snow accumulation at elevation intervals, in forecast amounts at or above a user specified threshold amount.

 

X

 

X

 

 

 

231

3

1

 

 

These shall be available at six hour forecast periods, and in user configurable intervals such as 6, 12, and 24 hour total forecast accumulation.

 

X

 

X

 

 

 

233

0

 

 

 

Day 6-7 Zones

 

 

 

 

 

 

 

233

1

 

 

 

AWIPS shall provide the capability in IFPS to generate the following text and tabular products out to the day seven range, with the format as specified in the NWS Operations Manuals C-10, C-11, and C-20:

X

 

 

X

 

 

 

233

1

2

 

 

-Tabular State Forecast Product (SFT)

X

 

 

X

 

 

 

233

2

 

 

 

AWIPS shall provide the capability in IFPS to generate the following text products out to the day seven range, with the format as specified in the NWS Operations Manuals D-51 and D-52:

X

 

 

X

 

 

 

233

2

1

 

 

-Coastal Marine Forecast (CWF)

X

 

 

X

 

 

 

233

2

2

 

 

-Near Shore Forecast (NSH)

X

 

 

X

 

 

 

233

2

3

 

 

-Great Lakes Open Lake Forecast (GLF)

X

 

 

X

 

 

 

238

0

 

 

 

Gridded Products

 

 

 

 

 

 

 

238

1

 

 

 

AWIPS shall provide the capability in IFPS to produce gridded products derived from the gridded fields of sensible weather elements which have been initialized in the Graphical Forecast Editor (GFE) and are contained within the official forecast database

X

X

 

 

 

 

 

 

RWP # L1 Req # L2 Req # L3 Req # L4 Req # CAPABILITY R5.1a R5.1b FSL TDL OH APO PRC

241

0

 

 

 

Snow Level Phrases

 

 

 

 

 

 

 

241

1

 

 

 

AWIPS shall provide the capability to generate products in IFPS with a new gridded sensible weather element, snow level.

 

X

 

X

 

 

 

241

2

 

 

 

AWIPS shall provide the capability to generate products in IFPS with details on snow elevation levels at 6 hour intervals out to the day seven forecast period.

 

X

 

X

 

 

 

241

3

 

 

 

AWIPS shall provide the capability in IFPS for site configurable levels and intervals for snow accumulation forecasts in products generated in text and tabular formats.

 

X

 

X

 

 

 

241

4

 

 

 

AWIPS shall provide the capability in IFPS to generate text with snow level phrases, and tabular products which describe the elevation intervals for which snowfall accumulations at or above a user specified threshold amount are forecast.

 

X

 

X

 

 

 

242

0

 

 

 

Distribute and Use National Operational Hydrologic Remote Sensing Center (NOHRSC) Products on AWIPS

 

 

 

 

 

 

 

242

2

 

 

 

AWIPS shall acquire, decode, and store operational products received from the NOHRSC. Product format information for these products is found in Section B.

 

X

X

 

 

 

 

242

3

 

 

 

AWIPS shall display information from text NOHRSC products as it displays other point data information.

 

X

X

 

 

 

 

242

4

 

 

 

AWIPS shall display information from gridded NOHRSC products as it displays other gridded data of the same display scale (CONUS).

 

X

X

 

 

 

 

252

0

 

 

 

AWIPS and WMO ID Based Text Database Storage, Retrieval, and Editing Functionality

 

 

 

 

 

 

 

252

1

 

 

 

AWIPS shall support multiple methods for users to retrieve text products; by AFOS PIL and AWIPS ID (an AWIPS ID consists of a WMO ID (TTAAii CCCC bbb), a 4-6 character abbreviated AFOS PIL, and by version number *** 1. Design Goal Note: To have a "clea

 

X

X

 

 

 

 

252

1 C

 

 

 

text version radio boxes which include "latest", "previous", "select version" (via a pop-up menu containing all available version) and "all versions". This functionality already exists for PIL based products and is requested to be extended to the AWIPS I

 

X

X

 

 

 

 

252

2

 

 

 

AFOS PIL text storage and retrieval shall continue to be supported through build 5

 

X

X

 

 

 

 

252

3

 

 

 

The bbb field shall only be populated in the database if the incoming report has this field.

 

X

X

 

 

 

 

252

4

 

 

 

User initiated text database queries shall be accomplished by supplying the TTAAii CCCC fields for a particular text product; if users supply a partial field (anything less than TTAAii CCCC);

 

X

X

 

 

 

 

252

4

1

 

 

the query shall be considered incomplete and the user prompted for more query fields to execute a successful query

 

X

X

 

 

 

 

252

5

 

 

 

AWIPS shall allow users to request products by version of a product with a particular TTAAii CCCC ***1. Design Goal Note: To have a "clean" user interface that resembles the current text browser int

 

X

X

 

 

 

 

252

6

 

 

 

AWIPS shall allow users to request "N" number of versions of a product with a particular TTAAii CCCC

 

X

X

 

 

 

 

252

7

 

 

 

If a validate query is made (all query examples above) and no successful retrievals are returned, AWIPS shall indicate to the user that no products were found in the database

 

X

X

 

 

 

 

258

0

 

 

 

Software Architectural re-structuring, built efficiency and standardization

 

 

 

 

 

 

 

258

1

 

 

 

AWIPS software shall be compliant with the ISO C++ standard with regard to the correct scoping of FOR loop indices.

X

 

X

 

 

 

 

258

2

 

 

 

AWIPS software shall be compatible with the C++ Standard Template Library (STL)

 

X

X

 

 

 

 

260

0

 

 

 

Log Stream Enhancements

 

 

 

 

 

 

 

260

1

 

 

 

AWIPS shall provide an application logging service which is thread-safe

X

 

X

 

 

 

 

260

2

 

 

 

AWIPS shall provide an application logging service which enables multiple processes to generate a single log file

X

 

X

 

 

 

 

260

3

 

 

 

AWIPS shall provide the capability for multiple invocations of a single process to write to the same persistent log file.

X

 

X

 

 

 

 

262

0

 

 

 

Integration of MHS APIs

 

 

 

 

 

 

 

262

1

 

 

 

AWIPS shall provide a Message Handling Server process which integrates and centralizes the message handling for all AWIPS WAN product distribution.

 

X

 

 

 

X

 

271

0

 

 

 

Compress Radar Data

 

 

 

 

 

 

 

271

1

 

 

 

AWIPS radar data and products transmitted on the AWIPS Satellite Broadcast Network shall be in compressed form.

 

X

 

X

 

 

 

271

2

 

 

 

Where compression is used, there shall be no distortion of the data or loss of information when performing the compression/decompression. This includes potential loss of information if encrypted U.S. or Canadian radar data are compressed.

 

X

 

X

 

 

 

277

0

 

 

 

LDAD Web Dissemination for Decision-Makers

 

 

 

 

 

 

 

277

1

 

 

 

AWIPS shall provide a simple graphical user interface (GUI) for the LDAD Web Dissemination System (LWS) that is easy to learn in a non-daily/constant use environment.

 

X

X

 

 

 

 

277

1

1

 

 

AWIPS shall provide on-line help files that allow users to quickly find out system information.

 

X

X

 

 

 

 

277

2

 

 

 

AWIPS LWS shall use only one window, but may incorporate the use of multiple panes within that one window.

 

X

X

 

 

 

 

277

3

 

 

 

AWIPS LWS shall allow the user to configure the system to focus only on the weather information in which they are interested.

 

X

X

 

 

 

 

277

4

 

 

 

AWIPS LWS shall allow users to bundle various datasets allowing for a single mouseclick to generate a set of data displays.

 

X

X

 

 

 

 

277

5

 

 

 

AWIPS LWS shall allow users to customize color schemes, the display area, and to add new datasets.

 

X

X

 

 

 

 

277

6

 

 

 

AWIPS LWS shall allow users to view, animate, and zoom high resolution analyses, model weather grids, and radar data.

 

X

X

 

 

 

 

277

7

 

 

 

AWIPS LWS shall allow users to view textual data such as warnings, watches, advisories, statements, forecast discussions, public forecasts, fire weather forecasts, marine forecasts, and observations (including quality control information).

 

X

X

 

 

 

 

277

8

 

 

 

AWIPS LWS shall allow users to view NWS watch and warning areas in mapped graphical format.

 

X

X

 

 

 

 

277

9

 

 

 

AWIPS LWS shall have the ability to integrate and view data from a variety of sources.

 

X

X

 

 

 

 

277

9

1

 

 

This shall include external data (non-NWS and local), and both dynamic and static data.

 

X

X

 

 

 

 

277

10

 

 

 

AWIPS LWS shall have the ability to retrieve image datasets in commonly used formats (e.g., GIF, JPG, etc.) from external websites and integrate them for viewing.

 

X

X

 

 

 

 

277

11

 

 

 

AWIPS LWS shall give users the ability to view summary information for various weather parameters such as max, min, and mean weather parameters for any arbitrary region.

 

X

X

 

 

 

 

277

11

1

 

 

This shall include geographic regions such as cities, counties, river basins, interstate sections, etc.

 

X

X

 

 

 

 

277

11

2

 

 

This summary information shall be displayed in a tabular format for easy readability.

 

X

X

 

 

 

 

277

12

 

 

 

AWIPS LWS shall allow the user to define thresholds for notification of possible impending weather phenomena.

 

X

X

 

 

 

 

277

13

 

 

 

AWIPS LWS shall have an Application Programming Interface for various agencies to create additional capabilities with LWS such as visualization of new data, etc.

 

X

X

 

 

 

 

277

14

 

 

 

AWIPS LWS shall be compatible with geographic information system (GIS) software.

 

X

X

 

 

 

 

277

14

1

 

 

AWIPS LWS shall produce data in formats that are usable by GIS software packages.

 

X

X

 

 

 

 

277

15

 

 

 

AWIPS LWS shall give the users the capability to easily send data (e.g., spotter and storm reports, precipitation reports, spot fire weather forecast requests, etc.) back to the servicing WFO site.

 

X

X

 

 

 

 

278

0

 

 

 

NWR/CRS Concatenated voice formatter support for Watches, Warnings and Advisories

 

 

 

 

 

 

 

278

1

 

 

 

AWIPS shall provide the capability to include the "C " in the header of the text products generated by the W/W/A and WarnGen applications and all text products formatted for CRS, prior to dissemination of these products to the CRS.

X

 

 

X

 

 

 

278

1

1

 

 

This header formatting shall be done for those products for which voice concatenation shall be done in CRS. .

X

 

 

X

 

 

 

278

2

 

 

 

AWIPS shall provide templates which can be locally configured for vocabulary options to support the generation of text products from the W/W/A and WarnGen applications, and for additional text products to be formatted for dissemination by CRS, in formats

X

 

 

X

 

 

 

278

3

 

 

 

AWIPS shall utilize a delimiter to mark the free form portions of the text products generated with the W/W/A and WarnGen applications which should not be included in the products disseminated to CRS.

X

 

 

X

 

 

 

278

4

 

 

 

AWIPS shall provide a notification to users when portions of the wording included in the text products to be disseminated to CRS contain words or phrases which are not acceptable for voicing by CRS, prior to the product dissemination.

 

X

 

X

 

 

 

278

5

 

 

 

AWIPS shall support delivery of products to the local office automated phone systems.

 

X

 

X

 

 

 

290

0

 

 

 

New Track Option in WarnGen

 

 

 

 

 

 

 

290

1

 

 

 

AWIPS shall provide an additional option for multiple storms in the WarnGen menu under track type. The following three options for storms shall be supported in WarnGen:

 

X

X

 

 

 

 

290

1

1

 

 

one storm;

 

X

X

 

 

 

 

290

1

2

 

 

multiple storms;

 

X

X

 

 

 

 

290

1

3

 

 

line of storms

 

X

X

 

 

 

 

292

0

 

 

 

IFPS Gridded Data Resolution

 

 

 

 

 

 

 

292

1

 

 

 

AWIPS shall provide the capability to initialize and display grids of default (as specified in RWP 238) and derived sensible weather elements in the Graphical Forecast Editor (GFE) of IFPS at the following spatial resolution:

 

X

 

X

 

 

 

292

1

1

 

 

10 km ;

 

X

 

X

 

 

 

292

1

2

 

 

1 km

 

X

 

X

 

 

 

292

2

 

 

 

AWIPS shall provide the capability to generate images from grids of default (as specified in RWP 238) and derived sensible weather elements within the GFE at the following spatial resolution:

 

X

 

X

 

 

 

292

2

1

 

 

10 km ;

 

X

 

X

 

 

 

292

2

2

 

 

1 km

 

X

 

X

 

 

 

292

3

 

 

 

AWIPS shall provide the capability in IFPS to locally configure the spatial resolution of the sensible weather element initialization, display and product generation available in GFE in the following ranges:

 

X

 

X

 

 

 

292

3

1

 

 

from 19 km to 10 km ;

 

X

 

X

 

 

 

292

3

2

 

 

from 19 to 1 km

 

X

 

X

 

 

 

292

4

 

 

 

AWIPS shall provide the capability to generate gridded products of sensible weather from grids of default and derived sensible weather grids within the GFE at the following spatial resolution:

 

X

 

X

 

 

 

292

4

 

 

 

10 km;

 

X

 

X

 

 

 

292

4

 

 

 

1 km

 

X

 

X