Meteostat currently publishes the coordinates of the stations only with an accuracy of two digits in their lat/lon.
This throws away very important information and creates unnecessary jitter. You can see this in the example below. On the left it shows the location of a station (here airport station in Lisbon) in Meteostat. On the right is shown its location shown by a provider with the full coordinates.

I think the culprit are lines
https://github.com/meteostat/jasper/blob/92521f40614aaa4ac6e822c2ee127748f11c0c8a/cron/export/bulk/gridded/daily.py#L74
and
https://github.com/meteostat/jasper/blob/92521f40614aaa4ac6e822c2ee127748f11c0c8a/cron/export/bulk/gridded/daily.py#L75
I would recommend removing these two lines and storing the coordinates in the full accuracy they are provided by the agencies.
Meteostat currently publishes the coordinates of the stations only with an accuracy of two digits in their lat/lon.

This throws away very important information and creates unnecessary jitter. You can see this in the example below. On the left it shows the location of a station (here airport station in Lisbon) in Meteostat. On the right is shown its location shown by a provider with the full coordinates.
I think the culprit are lines
https://github.com/meteostat/jasper/blob/92521f40614aaa4ac6e822c2ee127748f11c0c8a/cron/export/bulk/gridded/daily.py#L74
and
https://github.com/meteostat/jasper/blob/92521f40614aaa4ac6e822c2ee127748f11c0c8a/cron/export/bulk/gridded/daily.py#L75
I would recommend removing these two lines and storing the coordinates in the full accuracy they are provided by the agencies.