After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 337305 - Seattle, WA area forecasts not being updated
Seattle, WA area forecasts not being updated
Status: RESOLVED DUPLICATE of bug 166014
Product: gnome-applets
Classification: Other
Component: gweather
2.14.x
Other All
: Normal normal
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks: locations-love
 
 
Reported: 2006-04-05 04:53 UTC by brad.kittredge
Modified: 2010-01-24 01:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description brad.kittredge 2006-04-05 04:53:33 UTC 
Please describe the problem:
The forecast tab in gweather is not recieving updated forecasts for the Seattle,
Washington, USA area since February 28th, 2006.  NOAA indicated in an email that
they are no longer using the zone numbers that gweather uses.  The new zone
numbers are here:


http://www.weather.gov/mirs/public/prods/maps/state_zone_washington.htm


Steps to reproduce:
1. Open gweather applet
2. Select the "Forecast" tab
3. The forecast never changes


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
The National Weather service informed me in an email about the zone number
changes  that took place on February 28th, 2006
Comment 1 Chris Hollenbeck 2006-06-26 23:21:40 UTC 
While the zone should probably be updated, I'm wondering if the problem you've been experiencing is due to a station no longer reporting data.  The Current Conditions work with Seattle -> Boeing and Seattle -> Seattle.  However, only the Forecast shows up for Seattle -> Seattle NEXRAD.  The code for this is KATX, and it comes up as an error when you search for it at http://weather.noaa.gov/weather/metar.shtml.
Comment 2 Danielle Madeley 2006-08-20 15:01:04 UTC 

*** This bug has been marked as a duplicate of 166014 ***