GNOME Bugzilla – Bug 492268
Unable to get weather forecast for Australia, Northern Territory, Alice Springs.
Last modified: 2008-06-18 19:12:14 UTC
Please describe the problem: Can't get weather forecast for Australia, Northern Territory, Alice Springs. gweather goes looking for http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDD10110.txt instead of http://www.bom.gov.au/products/IDD10111.shtml. Steps to reproduce: 1. Switch to gweather location to Australia, Northern Territory, Alice Springs 2. Do an update 3. Go to the forecast tab of the details Actual results: I'm disappointed by the "Forecast not currently available for this location." message. Expected results: It would read http://www.bom.gov.au/products/IDD10111.shtml and give me a forecast. Does this happen every time? Yes Other information: Please please please, before every release of gnome-applets, run a script that checks each URL and outputs a list of the ones that error out. At least this way the data you have will be correct at the time of release. Also, it might be a good idea to have some sort of update mechanism, so that the applet can get a new list of URLs between GNOME releases. Alternatively to the HTML, you could use this plain text file: ftp://ftp.bom.gov.au/anon/gen/fwo/IDD10111.txt Probably can use the other text files in that directory for all Australian forecasts.
Just noticed that http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDD10111.txt works, so I guess it is just a typo (last 0 should be a 1).
In addition, a better forecast for Alice Springs would be IDD10161: http://www.bom.gov.au/products/IDD10161.shtml http://www.bom.gov.au/cgi-bin/wrap_fwo.pl?IDD10161.txt
Created attachment 100237 [details] [review] Patch to fix Alice Springs and add Darwin forecasts Patch attached to fix the missing forecast for Alice Springs. Also added forecast code for Darwin, which was also not present. Note no other NT towns appear to have dedicated forecast codes, so am omitting them.
Moving libgweather-specific bugs out of gweather-applet
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.