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 688481 - libgweather displays wrong sunset/sunrise times
libgweather displays wrong sunset/sunrise times
Status: RESOLVED DUPLICATE of bug 685433
Product: libgweather
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: future
Assigned To: libgweather-maint
libgweather-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-16 17:24 UTC by alex diavatis
Modified: 2012-12-02 03:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description alex diavatis 2012-11-16 17:24:19 UTC 
Opening gnome-clocks (git and stable - 0.1.4) I checked the Sunrise/Sunset times in Athens/Greece for today (Nov 16).
Clocks says <Sunrise 7.05>, <Sunset 17.11>, when the actual times are  <Sunrise 7.07>, <Sunset 17.12>

I don't know if this is a bug or if there is a global standardization in these values, but these are the values that are given from Greek national services.

If I knew the online services that libgweather uses to get the data, I could dig further.
Comment 1 Giovanni Campagna 2012-11-16 18:45:25 UTC 
libgweather does the math internally based on the geographical coordinates. The problem is that clocks uses the weather station (nearest airport, usually) as the location, while still displaying the city name, and the coordinates are slightly different, which causes the wrong data.

Note: this is not a bug in clocks. The problem is that you can't retrieve a GWeatherLocation at an arbitrary level from the DB, only a weather station. It is a known bug, I just haven't found time to fix it yet.
Comment 2 Giovanni Campagna 2012-12-02 03:20:31 UTC 
Marking duplicate of another bug that is caused by the same underlying issue in libgweather, and has a patch solving this one too.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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