Spot Forecast Request
Issued by NWS Jacksonville, FL

Home | Current Version | Previous Version | Text Only | Print | Product List | Glossary On
Versions: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
000
BMBB91 KJAX 200030
STQJAX

*** weather.gov/spot open request status ***

*** Emergency Note ***
Incidents denoted with a * indicates that the AWIPS in Billings, MT did
receive an STQ for this incident. It could be AWIPS issues at Billings OR
it could be a more serious issue at the Gateway where no offices are getting
STQ products. If you are not getting the STQ products either, then open up a
ticket with toc.nwstg@noaa.gov and procede with alternative ways of getting
the spot forecast to customers.


Hello, this is a Pending Request notification product that will remind you
to deal with pending requests within your service area on the
http://weather.gov/spot/monitor/?wfo=jax page.

Below is a list of incidents that are in request pending status and
may need a forecast.

You are getting this notification for one or more reasons detailed
as follows...

1) You may not have received the STQ product for this/these incident(s),
   because of STQ transmission issues on the web farm/TOC. First run
   Change Request on the website to attempt another send of the STQ
   product. If that does not work, then run the Manual options in
   Spot formatter. Open TOC ticket for transmission issue.

2) Certain messages state that you are minutes, hours, days late in
   filling a forecast request. If a valid request, then I would post
   a forecast. However, the customer might have entered the wrong
   forecast deliver date/time. If that is the case, then run the
   Change Request link on website and fix it. Otherwise delete request.

3) Certain messages state that you have up to x minutes to complete
   the forecast. If this is a valid request, then work on the forecast
   and try to meet the deadline specified by the customer.

4) Customers occasionally submit multiple requests for the same
   incident, instead of using the Change Request functionality.
   If you only need to post a forecast to only one of the requests,
   then delete the request(s) that will not get a forecast posted to
   it.

5) Customers may have unintentually run "Copy Info into New Request
   for This Incident" or the "Request Forecast Update" link.
   You do not want to delete such requests,
   because forecasts have been posted against the incident. If the
   incident is finished, then Archive the incident. Otherwise,
   edit the incident and sent the deliver date/time to when the next
   forecast is needed.

6) Customers occasionally submit illegal requests on the website,
   like for a private prescribed burn. In this case, just delete the
   request.

7) If it is a test incident generated by someone in your office,
   then delete the incident. No need to generate a forecast for this
   incident.

 Incident ID   Forecast Deadline (LT)              Deadline Incident Name
------------ ------------------------- -------------------- ----------------------------------------
   1917268.0   2019-10-19 12:00 PM EDT      8 hour(s) past* Saint Simons Sound Incident Forecast #105
   1917478.2    2019-10-19 8:01 AM EDT     12 hour(s) past* Town of OP Fall Festival
   1916910.4    2019-10-19 8:00 AM EDT     12 hour(s) past* Ham Jam
   1917267.0    2019-10-19 4:00 AM EDT     16 hour(s) past* Saint Simons Sound Incident Forecast #104

Comments and suggestions on this new product can be sent to
virgil.middendorf@noaa.gov


USA.gov is the U.S. government's official web portal to all federal, state and local government web resources and services.
  • National Weather Service
  • El Paso, TX Weather Forecast Office
  • 7955 Airport Rd
  • Santa Teresa, NM 88008
  • (575) 589-4088
  • Page Author: EPZ Webmaster
  • Web Master's E-mail: sr-epz.webmaster@noaa.gov
  • Page last modified: Apr 16th, 2019 21:10 UTC