Hi, creator of Open-Meteo here. The limits are 600 calls / min, 5.000 calls / hour and 10.000 calls / day. Limits are applied on an IP basis.
This is not ideal for shared hosting services like cloudflare workers, but is the easiest and privacy-friendly way to limit access to fair-use.
Additionally, weather data is uploaded to a AWS S3 open-data sponsorship and you can run your own API instances (even commercially). The only draw back is, that a lot of data needs to transferred. I am working on a S3 cloud-native approach, but it is still in testing.
The free tier is cross-financed by commercial customers that use the service for energy forecasting, agriculture planing or wild fire prevention. There is no external funding, VCs, or whatsoever, the code is build in public on GitHub and I intent to continue running the free API service as is.
You rang ;-) I’m in the middle of adding more ECMWF data that will be released as open data starting October 1st. At the moment, only a limited set of lower-resolution (0.25°) ECMWF forecasts can be shared open-data. That’s going to change in a big way, though I can’t share more details just yet.
I’ve been building an open-source weather API over the past few years. It pulls in data from a wide range of global and local high-resolution weather models. The API is free to use without an API key, though there are commercial options available. I'm the sole owner behind it. No VC funding or outside backing.
The core tech is tuned for performance, using local gridded files instead of a traditional database or response caching. This efficiency is what allows it to stay free.
Just wanted to say thank you for this service. I have a little homebrew clock I build from a Raspberry Pi and a small display in my bathroom. Below the time, it displays the weather forecast for the day so I know how to dress. That little clock has become an essential piece of my morning routine.
I switched to Open Meteo a few months ago when the previous API I was using quit working. It's been rock solid and such a nice user experience compared to everything else I tried.
Awesome, I will change https://weather.bingo to use this service; the previous paid API I used was too expensive to justify given I was the only real user :P.
Love open-meteo - no registration or API key required.
Great for tutorials.
I used it my upcoming O'Reilly book- use weather to predict air quality at the street level:
https://github.com/featurestorebook/mlfs-book/
Just wanted to say, seeing you in the wild, thank you very much for the hard work you do on OpenMeteo.
Picked up a commercial license about 3 months ago, service is amazing and have been using it for helping to provide runtime data analysis and anomaly detection for smart home thermostats.
So true, it is so awesome. I've just replaced my weather network bookmark with the open-meteo's "API Response" chart. I hope open-meteo doesn't mind :)
Hi, I am building an Open-Source Weather API aggregating open-data weather models from NOAA, ECMWF, DWD, MeteoFrance, JMA, CMA, CMCC and others. I agree that many weather companies basically redistribute NWS data at a premium. There is a free API service available on https://open-meteo.com and all databases are redistributed via an AWS Open-Data Sponsorship. Feel free to reach out if you need help building your weather data broker startup
A sincere personal "thank you" from me! I use Breezy Weather[1] on my smartphone, which gets most of its data from your aggregating service, Open-Meteo. It's the perfect combination of accurate, international and open.
Under the hood Open-Meteo is using a custom file format with time-series chunking and specialised compression for low-frequency weather data. General purpose time-series databases do not even get close to this setup.
Creator of the open-source weather API open-meteo.com here.
The future of weather forecasting is likely to rely heavily on AI models. The article discusses Pangu Weather and HN comments mention GraphCast as examples. Interestingly, on the first of March, the European weather forecast center ECMWF released their new AI weather model AIFS as open data. This model is not only more accurate than their existing numerical model, but also requires significantly less computing power to run. They've published comparisons showing AIFS outperforms other models in terms of forecast precision: https://www.ecmwf.int/en/about/media-centre/aifs-blog/2024/f...
Richard Turner gave an overview of AI weather forecasting to the Cambridge Philosophical Society at the end of last year. Recording available here:
https://www.youtube.com/watch?v=JGn18WH0d6s
Thank you for sharing! Creator of Open-Meteo here. It's been an incredible experience dedicating a more than a full year to this open-source project.
My goal is to make weather data easily accessible, providing information from the past 80 years or forecasts for up to one month. All the data is sourced from reputable national weather services and is based on open-data. While I offer commercial subscriptions to support Open-Meteo's servers, my primary focus is on open-data and open-access. For this commitment, I'm actively working on redistributing the entire Open-Meteo weather dataset as open-data through an AWS Open Data Sponsorship.
In the coming months, my plans include integrating seasonal weather forecasts spanning up to 8 months, incorporating more historical ocean wave data, and improving integrations in Python, Swift, Kotlin, Typescript, and other programming languages.
This is not ideal for shared hosting services like cloudflare workers, but is the easiest and privacy-friendly way to limit access to fair-use.
Additionally, weather data is uploaded to a AWS S3 open-data sponsorship and you can run your own API instances (even commercially). The only draw back is, that a lot of data needs to transferred. I am working on a S3 cloud-native approach, but it is still in testing.
The free tier is cross-financed by commercial customers that use the service for energy forecasting, agriculture planing or wild fire prevention. There is no external funding, VCs, or whatsoever, the code is build in public on GitHub and I intent to continue running the free API service as is.