Got this email forwarded to me from a friend at the the NWS.
*** This email has been addressed to WCMs, SCHs and NWS Regional Offices ***
There is a bug in the production of several time fields in NWS CAP
messages and ATOM feeds, including the , , ,
and fields. The times are being shown as one hour later than
the actual times. We want to let everyone know that it is being
handled as an emergency fix and will be pushed into the production of
CAP and ATOM feeds as quickly as possible…
Please feel free to pass on this message to anyone who may have
contacted you regarding this issue or anyone you think may be impacted.
Sorry for the inconvenience and thanks for your cooperation. We will
provide an update after the fix has been placed into production.
I don’t know if they were already aware of it, but I sent them email informing them of the problem last week. I’m glad they are finally going get it fixed. I also received email from them saying they were going to try to install the fix today but, so far I haven’t seen it yet. Since I use the timestamps from the titles in my displays, I had to add some code to my scripts to change the time back an hour so my visitors don’t get confused.
Looks like they finally got the fix installed. The timestamps in the titles now agree with the text however, the “Sent” field in the text is still showing incorrect times i.e. Sent: 17:00 on 12-31-2010, Sent: 19:00 on 12-31-2010.
Just got a follow up email on the Atom/CAP problems…
The most serious bug has been fixed in the production of NWS CAP and
ATOM feeds that was causing various time fields to be shown as one hour
later than the actual times. However, two issues remain:
- the time is populated with a 2010-12-31 date and,
- if you view the "State" pages on the NWS alerts webpage at
http://alerts.weather.gov/, the "Last updated:" date/time may not be
updating.
These remaining bugs is are being worked and will be fixed soon as well.