gweather has some rounding issue
For the World panel in gnome-clocks, we use gweather's locations that are later serialized and stored in a gsetting. See https://gitlab.gnome.org/GNOME/gnome-clocks/-/blob/master/src/world-item.vala#L377-412
If you use gnome-clocks to add a location like Noida, India
Clocks will display it just fine, but if you restart the application, gweather is unable to find the same position. I'm wondering if it's just a rounding issue.
(org.gnome.clocks:2): org.gnome.Clocks-WARNING **: 13:22:04.370: world.vala:285: Failed to get a timezone for Noida, India
(org.gnome.clocks:2): GWeather-CRITICAL **: 13:22:04.370: gweather_timezone_get_offset: assertion 'zone != NULL' failed
(org.gnome.clocks:2): GLib-CRITICAL **: 13:22:04.370: g_date_time_get_utc_offset: assertion 'datetime != NULL' failed
(org.gnome.clocks:2): GLib-CRITICAL **: 13:22:04.370: g_date_time_get_day_of_year: assertion 'datetime != NULL' failed
(org.gnome.clocks:2): GLib-CRITICAL **: 13:22:04.370: g_date_time_get_day_of_year: assertion 'datetime != NULL' failed
(org.gnome.clocks:2): GLib-CRITICAL **: 13:22:04.370: g_date_time_get_day_of_year: assertion 'datetime != NULL' failed
(org.gnome.clocks:2): org.gnome.Clocks-CRITICAL **: 13:22:04.370: clocks_utils_wall_clock_format_time: assertion 'date_time != NULL' failed
I can't dig more into this right now. The same issue happens when a location is updated to a slightly different position and the user had the old position which causes issues as the location is shown as not added yet. I know that both issues are kind of unrelated but they are both caused by a rounding thing.
Using gnome-clocks 3.36.2 from Flathub with libgweather 3.36.1