National Weather Service Text Product
AFOS product STQJAX
Dates interpreted at 00:00 UTCDisplaying AFOS PIL: STQJAX
Product Timestamp: 2021-04-03 07:33 UTC
Bulk Download
Bulk Download Help
This bulk download tool provides the NWS text
in a raw form, hopefully directly usable by your processing system.
You can either provide a complete 6-character PIL/AFOS ID or provide
the 3-character base ID (e.g., AFD
). The start and end
dates represent 00 UTC for those dates. The Zip format is useful as
the filenames will have the product timestamp, which is useful for
when the product format has ambiguous timestamps.
391 BMBB91 KJAX 030733 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 nco.ops@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/NCO. 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 ------------ ------------------------- -------------------- ---------------------------------------- 2107449.0 2021-04-03 4:00 AM EDT 28 min left Clay County Fair Day 3 Comments and suggestions on this new product can be sent to virgil.middendorf@noaa.gov