Skip to main content

Forecast Data V2 FAQ

During the last months, we have re-programmed our Forecast API and History API (formerly Package API) and updated the technology stack behind it. We have carefully tested the new API and verified its forecast data quality. With this substantial update, the API’s performance has been greatly enhanced, resulting in a significant multiplication of our server capacities. This empowers real-time processing of the highest resolution data, thereby further enhancing the quality of our meteblue weather forecast. Multiple new data sources were already added to our forecasting chain, so you can expect accuracy improvements, which will be constantly improved further. We aim to provide a seamless migration process to the new API version, so customers do not have to apply any changes on their side. We already executed silent pilot tests of that switch.

The current API will be replaced with the new API on 2024-03-04 at 10:00 CET.

This Frequently Asked Questions (FAQ) page is designed to address common queries and concerns you might have about our new API. If you don't see your question answered, don't hesitate to contact our support ([email protected]).

What are the key features of the new version of your Weather API?

Besides the technology improvements, additional data sources have been added to the forecast data calculation, mostly aiming at improving our nowcasting. Nowcasting calculations are made for the next 1-6 hours using data from observed (satellite, radar) or measured (weather stations) datasets processed on the fly. These data are especially useful for improving the forecasting of current weather conditions and the upcoming hours.

Below are some illustrative examples highlighting the enhancements brought about by the upgrade in the forecast data:

  • Satellite radiation data for North and South America were added to the calculation, resulting in a better radiation forecast.
  • IFS ensembles precipitation data have been added to our MultiModel precipitation calculation. This data is then further updated with additional radar datasets, which we have also extended (e.g. the Czech radar is now included). These additional datasets also allowed us to improve the calculation of precipitation probability.
  • The temperature data calculation for high altitudes and for mountain peaks was improved.
  • We introduced nowcasting for dew point temperature, which is then further used to calculate other weather variables (e.g. relative humidity).

Do I have to migrate the new Weather API?

We aim to provide a seamless migration process to the new API version. There are some breaking changes, but the customers concerned have already been informed. If you did not receive an email, your current API requests should not be affected. However, we recommend checking whether all API requests are correctly processed after the migration date (2024-03-04), especially when you query csv format.

Is it possible to test the new API?

For now, you can test the new version of the API by adding “V2” to your API request. Sample API-URL for the basic-1h data package for Basel:

If you encounter any issues or have specific questions during the transition, our support team is ready to help.

Which breaking changes should be considered?

We have carefully analysed the log files and pre-informed affected customers about breaking changes. If you have not been informed so far, no problems are to be expected with your API setup after the migration.

  • CSV format: If you are collecting our data in csv format, please ensure to parse the header and check the column location of the queried variable.

  • Time zone for ocean data: There are breaking changes concerning the sea data package if the time zone is not defined in your API request. While the current API delivers sea data in UTC time zone, the new API now defines the time zone based on the coordinates and returns the data in local time. You can either use the data in local time zone, or define the time zone in your API-URL, by applying the respective keyword.

  • Wrongly encoded asl parameters: If the altitude parameter(asl) is not correctly set (empty), it will return an error after the migration. Currently, the API assumes for this setting (“&asl=”) that the altitude of your location is 0m, resulting in wrong forecast data (since the temperature data strongly depend on the location’s altitude). You can add the correct altitude as a number to the API-URL (e.g. “&asl=314”) or remove the asl parameter in the API-URL. The API will then automatically detect the altitude based on a high-resolution digital elevation model for the specified coordinates.

  • Double encoded URL parameters: Most HTTP Clients handle the URL encoding part automatically, so please make sure that the framework you use does not URL encode an already URL encoded parameter once more.

  • Empty URL parameters: To prevent misuse, the API now implements a more rigorous validation for query parameters. As a result, specified but empty query parameters will trigger an error response. Therefore, please ensure that you remove any unnecessary empty query parameters from your API request.

    Faulty sample URL: