Meteomatics' Weather API delivers fast, direct, simple access to an extensive range of global weather and environmental data.
Meteomatics' Weather API was originally created to improve colleagues access to weather data access and allow them to build solutions for industry, However, we soon realized that we could empower users and industries around the world, by giving them access to the worlds richest and most performant weather and climate API.
1) Underpinned by solid foundations
Meteomatics' API is underpinned by our Meteocache that aligns data in time and space to ensure that the weather API can efficiently and very quickly, return the requested data query in spite of the size and format of the original data set.
2) Single source of weather data
Users are offered a single API endpoint to access weather and climate data, covering the planets land and oceans, across all timescales: nowcast, forecast, seasonal, climate and space! Historical data (back to 1979 dependent on location). Observational data sets such as satellite, station data, weather drones, and observations from the Internet of Things.
Plus, all our web feature services (WFS’s) and web mapping services (WMS’s) that can be accessed using Meteomatics single API endpoint. Simplifying access to weather data and reducing the complexity commonly associated with meteorological information.
3) On the fly calculation for most up-to-date forecasts
Meteomatics Meteocache holds a large amount of observations in memory, enabling Meteomatics' API to re-calculate the forecast with the latest available information on the state of the atmosphere, removing the common forecast practise of using old forecast data and delivering our customers the most up-to-date forecast possible! What we call calculating ‘on the fly’.
Numerical weather models typically take a long time to produce their results (the fastest NWP models are run every hour). Sometimes models may not capture a particular event and the model cannot correct or adjust its output until the next model run.
This ‘on the fly’ approach gives users confidence that they are receiving the most accurate and up to date weather data possible.
Meteomatics continuously ingests new observational data, with some datasets updating at 1-minute intervals.
Calculating on the fly can also minimize the need for manual intervention and allow customers to automate decision making, achieve greater consistency across their products and services.
4) Downscaling weather forecasts to 90 metres.
We improve the accuracy of weather data by taking into account the detail of the topography.
As numerical weather prediction models typically use a coarse model resolution to ensure it can create a weather forecast on a global scale within the compute capability available, which has a few disadvantages.
Firstly, the model grid points are for a fixed area, (for example ECMWF project their model onto 8-10km grid points - at the equator), which can result in atmospheric events not being included in the model if they occur over areas smaller than the grid points.
Also, coarser model resolutions do not sufficiently capture the detail of the underlying topography which makes it difficult to forecast in areas that are not flat and become even more problematic in mountainous terrain.
Plus, physical parameterizations are based on assumptions for horizontally homogeneous and flat terrain, by assuming that the surface is flat and not taking into account the friction created by a landmass as air passes over (impacting precipitation forecasts for example).
So we decided to incorporate NASA’s highest-resolution topographic data set, which is at a resolution of 90m and mapped it to the neighbouring cells in the model data we ingest. Allowing the API to accurately calculate a weather forecast by taking into account the topography that represents ground truth.
Plus, we created an interpolation scheme that allows for the forecast of the actual height of the query specified in the lat / long, giving us the ability to generate the forecast for the height a user is interested in.