Show HN: Meteosource Weather API: current, forecast and historical data using ML (meteosource.com)
It is well known that most weather APIs just download data from NOAA and "repackage" them to JSON format. This means you will get data only for the nearest grid point which might be a few kilometers away and at a different altitude than your actual location.
Meteosource combines more models (GFS, ECMW, UKMO, GEM,...). It compares individual models' performance to historical data and uses machine learning to create a single output. This approach minimises inaccuracies of individual models and feeds a proprietary hyper-local model that computes weather exactly for the specified location.
The historical data API is based on actual measurements (not forecasts as usual) and there is a free developer plan available.
I greatly appreciate any feedback and thoughts!
19 comments
[ 5.3 ms ] story [ 54.4 ms ] threadI note that you state 8 years of historical data is available for one of the priced plans, and then on another page there is mention of larger bulk historical data services for custom plans. How much further back can your historical data go? Is it the sort of thing that we could pay once for, for a few thousand GPS points?
The use case is to get historical weather data at each power pole on an electrical transmission system. Obviously the observational and forecast data is of interest to us, but we can't make much value of the observations if we don't have the historical context with which to build real-time models on.
Is it all huge modeling still?
Have you published a backtest against NOAA's data? Have you looked into why they don't provide more hyperlocal data themselves? There's some interesting papers on the work they've done to get wildland firefighters appropriately local data.
meteosource.com also appears to be a rebrand of forecasts.cloud. Why?
The multiple rebrandings and false claims make me hesitant to trust you.
Your answer ignores why you didn't pursue forecasts.cloud as this new venture instead of meteosource though.
Regarding forecasts.cloud - this website will focus on our applied modelling (renewable generation etc.) and will serve as an offer of models for specialised industries, not weather API. It is not fully operational yet (the English version will be launched later this year) - I am impressed you have been able to find it :)
* vague testimonials
* scrolling list of companies (with no evidence)
* lack of specificity around payments (who's the processor?)
* the random face shown above the "contact us" button
* the lack of details around how the systems actually work (the "how we create our AI weather forecasts" link in your FAQ is just a 404)
* the lack of evidence that your system actually works better the alternatives
* the nearly-pointless blog spam
* the hand-wavy claims of "nearly 100% API uptime"
It's not that I think your API won't work and that you're just trying to steal my money. Instead it seems like this is a marketing effort to sell a low quality service using the magic buzzword "AI".
I miss Dark Sky.