-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-model data is not up-to-date #117
Comments
Hi @jragbeer, Yes - it's possible to update data more frequently. I think we need to check when exactly our data sources are updating their datasets and then import all data at once. I will put it as a to do. Can't give you an ETA though. |
Hello everyone, Meteostat just received an E-Mail from Environment Canada:
This is a setback for our data coverage in Canada and as fas as I know there is no public bulk data interface provided by Environment Canada. Anyone who can help finding a work-around? |
~47k requests per day is a lot. Especially given the above issue where data isn't up-to-date.... Is it possible to spread the data gathering across other instances/IPs (acquire cheap VMs from Linode/DO to request from Environment Canada)? |
I was hoping they might have an interface which allows data to be queried in bulk. Maybe this is better than what we're using atm? |
Hello!
This project is amazing and very convenient to use! Thanks for the great work!
I'm trying to integrate this into our project, but the timing seems to be off.
As an example, the data from Environment Canada doesn't seem to be the latest that it could be. Looking specifically at Toronto City Centre (https://meteostat.net/en/station/2XUGG?t=2022-12-11/2022-12-13). I see that non-model data is present up to the start of 12/12/2022 only, while data from the source is available up to the beginning of 12/13/2022.
When do sources get updated? Would it be possible for meteostat to be updated more frequently? I use the python client and would much prefer using this library than going back to using Environment Canada's API.
The text was updated successfully, but these errors were encountered: