meteo-jeff

10 ms·

1. 31.▲
   by meteo-jeff 5y ago

   Nice app. Even open source :) Regular "shortwave_radiation" should fit your needs. This is basically "direct_radiation + diffuse_radiation". I am not entirely sure, if this effects your users that much, because many will
2. 32.▲
   by meteo-jeff 5y ago

   For the VMs, the absolut minimum memory requirement is 16GB. The more, the better. Otherwise it takes around 40 GB of disk space for every day of data. For an history of 100 days, 4000 GB are required. With compression I could save 50%, but
3. 33.▲
   by meteo-jeff 5y ago

   I was thinking to use the geonames location database and build a simple fuzzy search engine around it. What wikidata objects are you referring to?
4. 34.▲
   by meteo-jeff 5y ago

   Sure, what kind of fire weather metrics could be added? Can they be derived from soil moisture, temperature, wind, humidity? Or are you referring to gridded fire indices from a different source? For now I would refrain to include data that
5. 35.▲
   by meteo-jeff 5y ago

   Glad you like it! Bootstrap v5 helped a lot :) I hope to improve the UX a bit further with a city-search for example. Unfortunately I am lacking a good geocoding API for that.
6. 36.▲
   by meteo-jeff 5y ago

   Correct. This cannot be prevented. Also for API keys you can just search for keys from basically any weather API and you will find credentials on GitHub. People also sign up 10x for free API services to circumvent typical request limits per
7. 37.▲
   by meteo-jeff 5y ago

   I chose the "Attribution-NonCommercial 4.0 International (CC BY-NC 4.0)" license to start the project without worrying about legal issues. Because the API is offered without API key restrictions, it could also be abused. The legal
8. 38.▲
   by meteo-jeff 5y ago

   DWD is quite unrestricted. Data is also processed, mixed with different models and many weather variables are calculated afterwards using other models. It is not showing raw data directly. As far as I interpret terms correctly, I have to in
9. 39.▲
   by meteo-jeff 5y ago

   That's cool :) I like this idea. Yes, please use the WMO weather code for that. I will also add precipitation probability in the next weeks. At >50% precipitation probability the umbrella hook light could also switch on.
10. 40.▲
    by meteo-jeff 5y ago

    Now I got it! Sorry, I did not get your point in the beginning. Compressed textures could be really interesting. So far I have no experience in this regard, but I will look into it
11. 41.▲
    by meteo-jeff 5y ago

    This is indeed a concern to me. As others pointed out, blocking IP addresses is an option. Blocking access based on the HTTP Origin header is also possible. I hope I can go on for some time without being to restrictive. With a fairly quick
12. 42.▲
    by meteo-jeff 5y ago

    Thanks for the hint. I did not know them yet
13. 43.▲
    by meteo-jeff 5y ago

    Including ensemble forecasts into Open-Meteo is already on my backlog. And yes, this will return those 90% confidence intervals. Forecast variability is difficult to express. For example precipitation probability describes how likely rain i
14. 44.▲
    by meteo-jeff 5y ago

    Thanks for pointing me towards ASTC HDR. I did not know this one. Compression will be an important part to build a longer historic database. I tested zstd, but it only had a ratio of 30%. Currently I am using fixed size files, because I upd
15. 45.▲
    by meteo-jeff 5y ago

    Currently only the past 2 days are available. To add more historical data is in the backlog [0]. Do you have an application in mind? Which weather variables over which timeframe? [0] https://github.com/open-meteo/open-m
16. 46.▲
    by meteo-jeff 5y ago

    Thanks for your offer. Unfortunately I cannot improve the weather forecast quality with a single station. National weather services collect all kinds of measurements and observations from weather stations, air planes, balloons, satellites a
17. 47.▲
    by meteo-jeff 5y ago

    You are right! The coordinates in the graph have the wrong label. I will quickly change it. Thanks!
18. 48.▲
    by meteo-jeff 5y ago

    API / processing: Swift + Vapor with modules in C, a lot of libraries to work with scientific data formats. Hosted on cheap rented VMs with Nginx in the front. Frontent: Bootstrap, jQuery Gilab CI/CD pipelines with deploys
19. 49.▲
    by meteo-jeff 5y ago

    I do not actively prevent commercial use. I stated a non-commercial license as precaution to prevent all kinds of legal complications. Mainly I also intent to reach open-source developers to make access to weather dat easier without the nee
20. 50.▲
    by meteo-jeff 5y ago

    The high-resolution NOAA GFS models will soon be integrated as well. Data are integrated seamlessly. The API will automatically select the best weather model for given coordinates. In the US the 2 km NOAA GFS model will then be used as defa
21. 51.▲
    by meteo-jeff 5y ago

    • Soil moisture data is based on DWD ICON models with up to 2 km resolution in central Europe. • ET is based on latent heat flux. This is not the potential evapotranspiration or ET0 reference evapotranspiration. I did not dive deep into the
22. 52.▲
    by meteo-jeff 5y ago

    Celsius is already the default temperature unit. You can optionally switch to Fahrenheit. For wind speeds, all typical units are available as well. Let me know if I missed one.
23. 53.▲
    by meteo-jeff 5y ago

    Do you know an open-data source for ocean visibility data? I want to integrate regular wave forecasts in the next month, but I am unaware of something that can improve dive visibility.
24. 54.▲
    by meteo-jeff 5y ago

    Yes, the API part is using Vapor. But there is not much code that actually relies on Vapor. It is mostly doing request parameter parsing and routing. I use simple 2D lat lon grids for different regions and resolutions. E.g. the global grid
25. 55.▲
    by meteo-jeff 5y ago

    Kachelmann seems to be more media oriented. I am not aware that there is a free API offer. It looks like Kachelmann is also integrating weather forecasts from different national weather services and the paid version from ECMWF. I am sure th
26. 56.▲
    by meteo-jeff 5y ago

    The host is netcup in Germany. I use regular KVMs. Yes, the amount of storage can be an issue, but I want to stay below 500GB of hot-data. One bottleneck is network traffic to copy updated files after each weather model update. My binary fi
27. 57.▲
    by meteo-jeff 5y ago

    For now I only offer 2 days of past weather data. Most likely I can store some basic weather variables like temperature, humidity, wind, precipitation and weather code for a couple of weeks. I will keep you request in my backlog: https:&#x
28. 58.▲
    by meteo-jeff 5y ago

    My personal preference for Swift was for sure a major aspect. I also like to profile my code and see how much I can out of it. It is more an academical challenge to compare performance mmap vs file reads calls, but I enjoy it :) With Python
29. 59.▲
    by meteo-jeff 5y ago

    There is no funding. Costs are negligible. Currently it is running on a cheap rented VM. Per single VM, it should scale to 3+ million API calls per days easily. To keep it simple, I also do not want to have any income with it. In case large
30. 60.▲
    by meteo-jeff 5y ago

    The API backend is written in Swift with some code in C (conversion Float16, interpolations, some solar radiation libraries). Data are read directly via mmap from local NVMe SSD disks. To scale, I can add new VMs and copy my binary files. T