Blog

Do you want to receive weather data in your language? We have extended the list of supported languages for weather conditions.

Now the following languages are available in our API:

Arabic (ar); Czech (cz); Greek (el); Persian (Farsi) (fa); Galician (gl); Hungarian (hu); Japanese (ja); Korean (kr); Latvian (la); Lithuanian (lt); Macedonian (mk); Slovak (sk); Slovenian (sl); Vietnamese (vi).

We invite our users to test translations for weather conditions in different languages. We will be happy to extend our language support according to your wishes. If you have any questions or suggestions, please send them to https://openweathermap.desk.com/. The specification for all weather conditions is available here: http://openweathermap.org/weather-conditions.

We have added new versions of the rendering styles for the Weather Maps API.

To get the weather map layers in the new predefined styles, you need to add _new to the appropriate layer name, as follows:

http://tile.openweathermap.org/map/{layer}_new/{z}/{x}/{y}.png?appid={api_key}

For your convenience while working with our historical data, we have created the History Bulk section at OpenWeatherMap.com. There you can find a manual on extracting data for different time periods and cities/towns; there are also examples of data extraction in JSON and CSV file formats, and descriptions of weather parameters.

We are happy to introduce to you our new service that provides historical weather data for more than 30,000 cities/towns for the last 5 years.

Now you can simply choose a city/town (or several cities/towns) and download an archive, which contains a bulk file with the weather history for up to 5 years – any day or week, or even several years. Pricing is simple and easy – just $10 for one city/town, no matter how much data you receive – see http://openweathermap.org/price.

Just sign in and place an order on your personal page at https://home.openweathermap.org/history_bulks/new. Please note that our traditional History API stays the same.

One of the benefits of the VANE platform is that there is no need to search by scenes and footprints. It is based on a simple assumption: each location in the world has metadata – click on any location and you can get information about all pixels containing this location.

Such projects as cloudless atlases and Google base satellite maps are created according to this basic principle, stitching the best imagery pixels in one seamless mosaic. Based on the scene’s metadata, VANE can choose the best satellite cover – you need to set up a parameter “order=best” for this operation.

As well as this, the VANE language allows you to set up further requirements for your mosaic, providing appropriate parameters in your query:

no older than (“day>{yyyy-mm-dd}”)

or put all the latest imagery on the top (“order=last”)

or within a specific time interval (“between({yyyy-mm-dd}:{yyyy-mm-dd})”).

Then you can go further, applying your custom colours to the result mosaic, according to the VANE language specification.

Just to demonstrate this principle at work, we’ve launched a very basic application called Finder.

We invite you to try our new product, Weather Alerts – it provides weather alerts based on our meteorological data.

Now you can use simple syntax to create triggers, which will work upon the occurrence of specified weather conditions (temperature, humidity, pressure, etc.) in a certain period of time. For example, if you are interested in forecasts of the approach of frosts or the probability of strengthening of wind in a certain place, you can get this information by using our new tool.

The alerts will be generated in our service when the conditions for the trigger are satisfied. You will need to poll the service within a certain time interval in order to receive them. For the future, we are planning to improve and develop this service, with the addition of push notifications and new data sources.

You can find out more at http://openweathermap.org/triggers.

Weather Alerts structure: http://openweathermap.org/triggers-struct.

In the current version of the VANE Language, we use images from the Landsat 8 satellite, which captures the Earth’s entire surface every 16 days. The satellite makes hundreds of images, with a unique name for each one (such as “LC81410552016219LGN00”) and a pixel size of 30 metres. Each image consists of 11 bands; the size of an uncompressed image is 2 GB.

Landsat 8 Operational Land Imager (OLI) and Thermal Infrared Sensor (TIRS) images consist of nine spectral bands with a spatial resolution of 30 metres for Bands 1 to 7 and 9. New Band 1 (ultra-blue) is useful for coastal and aerosol studies, and also new Band 9 is applicable for cirrus cloud detection. The resolution of Band 8 (panchromatic) is 15 metres. Thermal Bands 10 and 11 provide more accurate surface temperatures and are collected at 100 metres. The approximate scene size is 170 km north–south by 183 km east–west (106 by 114 miles).

By default, we get Bands 2, 3, 4, 5 and 7, but it is possible to download any other bands.

OpenWeatherMap is happy to announce good news for owners of private weather stations! We are launching a new version of Weather Stations API 3.0. Now there are more easy ways to manage your stations and transmit their data.

Thank you to Francesco Azzola for the article:
– http://www.survivingwithandroid.com
– @survivingwithan
– https://it.linkedin.com/in/francescoazzola

This post describes how to use OpenWeatherMap UV Index. This is an interesting API because we can use it to explore some important aspects of Android and of location-aware APIs. OpenWeatherMap provides this API for free! As you may already know, OpenWeatherMap also provides a full set of APIs about weather information: you can get current weather conditions, forecast, historical information and so on. This information is free, and we can use OpenWeatherMap APIs free of charge.

At the end of this article, we will build an Android app that gets the UV index and shows it using Material Design guidelines.

Before diving into the details of the app, it is useful to have some idea about the UV index.

OpenWeatherMap presents the release of a new service – VANE Language (formerly Imagery API) – with examples here: http://owm.io/vaneLanguage.

We initially called this service the “Imagery API”, but later realised that it consists of much more than just API calls. “VANE Language” is a more appropriate name for it, as it is like an SQL for satellite images. It is a unique offering in the satellite market. VANE Language is an entirely online service – there are no manual procedures, or presets such as maps prepared in advance.

Each “image” that we receive from Landsat 8 is not an image as commonly understood, but several layers that have to be processed and merged in some way before you can do anything with them. Each unarchived number of bands occupies around 2 GB of storage, and it obviously takes a lot of resources and time to process it. For example, to create a global map you need around 10,000 images that need to be processed and merged.

With VANE Language, the developer does not worry about time-costly pre-processing, because we do it all online immediately. We provide a powerful tool that will be familiar to any developer and hides all the complexity. In short, VANE Language gives full flexibility for a developer to do whatever they want with images and deploy the results into applications.

It also has a unique feature: configuring the formula for image processing. This allows the developer to set up their image-processing logic to create specific vegetation indexes, false colours and any other images that they want to use for analysis of objects, changes, yield health, etc.