Weather applet - doesn't work with Holešov

Bug #508124 reported by delance
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
libgweather
New
Low
libgweather (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Hi.
The temperature and sky displayed in the weather and clock applets for the town Holešov, Czech Republic is wrong.
According to the weather applet, it has been 23°C / 296K in Holešov for more than 1 year.

Thanks everyone

---------------------------------------------------------------------------------------------------------------------------------------------

This town is the single of the country to have temperature above zero.

Changed in yelp (Ubuntu):
status: New → Confirmed
affects: yelp (Ubuntu) → libgweather (Ubuntu)
Revision history for this message
Mitch Towner (kermiac) wrote :

I think this may be related to the brainstorm idea below:
http://brainstorm.ubuntu.com/idea/17670/

I just changed my location in the weather applet to "Holešov" & I can confirm it says 23°C but the wind speed for me is North / 3.0 knots (5.6 km/h) whereas google is currently showing -3°C & Wind: E at 10 km/h. I believe that this is more than likely an issue with the weather source data rather than the actual applet code.

Revision history for this message
zub (zub-linux) wrote :

The entry for Holešov in libgweather sources (data/Locations.xml.in) is:

        <!-- A city in the Czech Republic -->
        <_name>Holešov</_name>
        <coordinates>49.333333 17.583333</coordinates>
        <location>
          <name>Holešov</name>
          <code>LKHO</code>
          <coordinates>49.316667 17.566667</coordinates>
        </location>

The source of the data seems to be METAR (http://en.wikipedia.org/wiki/METAR). A lookup on "LKHO" (http://weather.noaa.gov/cgi-bin/mgetmetar.pl?cccc=LKHO) yields:

The most recent METAR observation from LKHO in our system was generated at the source at:
2009/07/01 08:00 UTC

The observation is:
LKHO 010800Z VRB03KT CAVOK 23/17 Q1019

So this proves (not surprisingly) the data source to be the problem. The only solution would probably be to change to a different data source/add more data sources as per http://brainstorm.ubuntu.com/idea/17670/

zubozrout (zubozrout)
description: updated
Revision history for this message
ooze (zoe-gauthier) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Lucid Lynx.

Changed in libgweather (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
ooze (zoe-gauthier) wrote :

Sorry, I tought it was updating correctly, but after a few seconds it changed to the "default" weather.

The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in libgweather (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
zub (zub-linux) wrote :

There are several bug upstream that are related. The closest one seemed to be this:

https://bugzilla.gnome.org/show_bug.cgi?id=574296

Revision history for this message
Mitch Towner (kermiac) wrote :

Thanks for reporting this bug and any supporting documentation upstream. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in libgweather (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Changed in libgweather:
importance: Unknown → Low
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.