As a heads-up I just noticed that NWS is making changes to the Atom alerts feed page. I hope they are not going to be permanently changing the URL’s. One thing that might be useful is that it shows the number of active alerts for each state.
The ATOM/CAP alerts will still be available, along with an entirely new set of NWS data via api.weather.gov … see the forecast-v3.weather.gov site, click on the link at the top to reveal the changes coming up on March 7,2017.
I’ll have a replacement advforecast2.php script to use their API released by then… no more page scraping 
One unfinished thing I’ve been discussing with the NWS developers is about ‘what’ will go into the API feed. Currently, only Watch, Warning, Advisory appear. Outlooks and Statements do not (unlike the current forecast.weather.gov point forecast page which does show it). It would be a shame to lose visibility to Outlook and Statement info.
Thanks for the info, Ken. Yes, it would be a shame to lose the outlooks and statements. Guess I better do some testing to see how the alerts are going to work with my parser. I see a couple of potential problems already.
Ken, as far as the outlooks and statements are concerned, had you considered using the IEMBot RSS feeds? Of course, the messages in those feeds don’t go away when they expire but, roll off the feed after 12-24 hours, as near as I can figure. If NWS continues sending the outlooks and statements to IEMBot, you could extract them from there.
https://weather.im/iembot-rss/wfo/kmtr.xml
IEMBot Project Main Page
http://mesonet.agron.iastate.edu/projects/iembot/
So far, neither the new forecast-v3.weather.gov or the api-v1.weather.gov sites contain either Outlook or Statement types, and my question to the NWS developers about that remains unanswered. 
I’m a bit wary of using non-NWS sources for NWS data with scripts… they tend (over time) to be less dependable than the actual source. I wish I knew just what the IEMBot software was reading from the NWS so maybe we could play too…
I can appreciate your concern. I have scripts that I created 7 years ago using the IEMbot feeds with my parser (Carp) and haven’t touched them since and they are still working fine. I have encountered only a few problems with the IEMBot feeds (i.e. temporary connection problem or the feed being updated when trying to access it(?)). The IEMBot software is reading the messages from NWSChat https://nwschat.weather.gov/live/ to update the IEMBot feeds which contain WWA’s, NWS local office products i.e. outlooks, statements, area forecast discussions, public information statements, record event reports, local storm reports, and short term forecasts. The list of more products can be found on the IEMbot Project page.
This is how the it works:
[size=83]iembot is a Jabber chat bot that relays National Weather Service issued text products to Jabber chat rooms hosted on the conference.weather.im multi-user chat service. iembot was written to aid the dissemination and use of NWS issued warnings by their chat partners.How does iembot work?
iembot consists of two programs that run on the Iowa Mesonet server. The first is a parser that ingests text products issued by the NWS. The parser picks out the important information regarding the product and sends it via a Jabber instant message to the bot logged in on the chat server. The bot then routes the incoming message to a WFO chatroom from which the product was issued. The entire process takes much less than a second[/size]
The service was developed by Iowa Environmental Mesonet of Iowa State University and they also have an IEMBot Monitor IEMBot Monitor and client Weather.IM Live that mirrors NWSChat.