GNOME Bugzilla – Bug 341782
Oakland zone should be changed (comment #4)
Last modified: 2021-06-09 21:02:01 UTC
Please describe the problem: I live near Berkeley, CA and there are no cities listed in the gweather applet near me that report weather forecasts. Steps to reproduce: 1. Open the applet's Preferences window and set a location. 2. Choose Oakland, Ca. 3. Visit 'Forecast' in the Details window. Actual results: "Forecast not currently available for this location." Current Conditions does have current weather info. Expected results: The forecast should be displayed. Does this happen every time? Yes. It used to work for this location, but stopped about 6 months ago. Other information:
I live in Chongqing of China, there is no any forecasting available too (current weather status works well though). However, Firefox's Forecastfox extension does this function very well.
Okland works for me as of this minute. Suggest closing this bug.
See Red Hat bug #187984 -- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187984 It seems that the problem is due to a change in the codes used to identify locations. (gnome-applets-2.8.0-5 in RHEL/CentOS 4.)
Oakland needs the following change in order to work properly. I used http://www.findlocalweather.com/forecast/ca/oakland.html to get the correct wx zone. The diff is from Ubuntu Gutsy gnome-applets 2.19.91-0ubuntu1 Locations.xml file. @@ -33678,7 +33688,7 @@ <name xml:lang="zh_HK">奧克蘭</name> <name xml:lang="zh_TW">奧克蘭</name> <code>KOAK</code> - <zone>CAZ007</zone> + <zone>CAZ508</zone> <radar>sfo</radar> <coordinates>37-43-10N 122-14-07W</coordinates> </location>
Moving libgweather-specific bugs out of gweather-applet
The general forecast bug is bug 147719. Keeping this bug for comment #4.
There are numerous incorrect US forecast zones in Locations.xml based on spot checks using the US NWS public forecast zone shapefile and data from Locations.xml. Here are just a few examples: KBNO|ORZ022|Burns Municipal Airport|boi|43.595000|-118.956389 Should be ORZ061 http://weather.noaa.gov/pub/data/forecasts/zone/or/orz061.txt KEWB|MAZ017|New Bedford Regional Airport|bos|41.675278|-70.956944 Should be MAZ020 http://weather.noaa.gov/pub/data/forecasts/zone/ma/maz020.txt PHLI|HIZ001|Lihue Airport|hawaii|21.983889|-159.341111 Should be HIZ002 http://weather.noaa.gov/pub/data/forecasts/zone/hi/hiz002.txt KHIO|ORZ004|Portland-Hillsboro Airport|pdx|45.548056|-122.954444 KTTD|ORZ004|Portland-Troutdale Airport|pdx|45.551111|-122.408889 Should be ORZ006 http://weather.noaa.gov/pub/data/forecasts/zone/or/orz006.txt Pipe-delimited columns are: code|zone|name|radar|lat|lon The NWS shapefile with all US forecast zones is here: http://www.nws.noaa.gov/geodata/catalog/wsom/html/pubzone.htm Quantum GIS can read this file and display it as a map without any problems. http://www.qgis.org/ qgis-0.11.0-4.fc10.i386 After parsing Locations.xml and converting the locations to a delimited text file, it is possible to import them into QGIS using a plugin. With these two layers it is very easy to visually correlate the zones from Locations.xml with the US NWS zones. Cross-reference: Weather Report gives wrong forecast for Portland-Hillsboro Airport https://bugzilla.redhat.com/show_bug.cgi?id=479526
In 2.25, we use a better interface to NWS forecast data, which lets us pass just the latitude and longitude rather than needing to know a zone id. So all these problems should be obsolete when 2.26 comes out.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/libgweather/-/issues/89.