Interactive documentation for your Premium plan

Tools (9)

Extracted live via the executor SDK.

• locationEndpoints.findPlacesFindPlacesGet

  Search for places

  You can use this endpoint to obtain place_id of the location you want, to be used in point endpoint. The response also contains detailed information about the location, such as coordinates, timezone and the country the place belongs to.

  Unlike the /find_place_prefix endpoint, complete words are required here. You can search for cities, mountains, lakes, countries, ZIP codes, etc. The response can contain multiple places, sorted by relevance. You can then identify the one you want by coordinates, country, or the administrative area.

• locationEndpoints.findPlacesPrefixFindPlacesPrefixGet

  Search for places by prefix

  You can use this endpoint to obtain place_id of the location you want, to be used in point endpoint. The response also contains detailed information about the location, such as coordinates, timezone and the country the place belongs to.

  Unlike the /find_places endpoint, you should only specify the prefix of the place you are looking for. This is particularly useful for autocomplete forms. You can search for cities, mountains, lakes, countries, ZIP codes, etc. The response can contain multiple places, sorted by relevance. You can then identify the one you want by coordinates, country, or the administrative area.

• locationEndpoints.nearestPlaceNearestPlaceGet

  Search for nearest place by coordinates

  You can use this endpoint to find the nearest place from given coordinates.

  Note: If you specify coordinates of a secluded place (e.g. middle of the ocean), the nearest point can be very far from the coordinates.

• pointWeather.airQualityAirQualityGet

  Air quality forecast for a single location

  Location specification

  The location of the weather data is the only parameter that is required and must be specified. There are two ways to do this:

  1. Specify the GPS coordinates of the location using the parameters lat and lon.
  2. OR specify the name of the place using the parameter place_id. To obtain the place_id for the location you want, please use endpoints /find_places_prefix (search by prefix) or /find_places (search by full name).

  Notes

  • For a detailed description of variables, please consult ⚠️ description of variables ⚠️ in Documentation or Schema of the response (link next to Example value in the Responses section below).
  • Do not make any assumptions about the number and ordering of the variables. New variables and sections may be introduced in the future. Always check the data are present before you try to use them.
  • The response contains an Expires header, which defines the point at which the API response will not change for the same request. We highly recommend using this to avoid unnecessary requests and increase the performance of your app.
  • Meteosource API supports HTTP compression. To enable it, simply add an Accept-Encoding: gzip header to your request.
  • When daylight saving time starts, one hourly record will be missing (typically 2:00:00 AM). When daylight saving time ends, the hourly forecast will contain two records with duplicate times (typically 2:00:00 AM).
• pointWeather.pointPointGet

  Current weather and forecast for single location

  Location specification

  The location of the weather data is the only parameter that is required and must be specified. There are two ways to do this:

  1. Specify the GPS coordinates of the location using the parameters lat and lon.
  2. OR specify the name of the place using the parameter place_id. To obtain the place_id for the location you want, please use endpoints /find_places_prefix (search by prefix) or /find_places (search by full name).

  Note: For mountains, it is usually better to specify the place_id rather than the lat and lon. When you use place_id, you are guaranteed to receive forecasts for the precise elevation of the peak. When you specify the coordinates, the elevation can be less precise.

  Sections

  The endpoint can return multiple sections of data. To obtain the best performance, we advise only requesting the sections you actually need. The available sections are as follows:

  • Current weather situation
  • Hourly forecast (for 24/48/96/168 hours, depending on the tier)
  • Daily forecast (for 7/10/30 days, depending on the tier)
  • Minutely precipitation forecast (for 60 minutes in the following hour, only for higher tiers)
  • Weather alerts (only for higher tiers)

  By default, only the current and hourly sections are returned. The division into daily parts (morning, afternoon and evening) is only available for the first 7 days of the forecast. For details regarding available parameters, see the parameter description below.

  Notes

  • For a detailed description of variables (e.g. icons), please consult ⚠️ description of variables ⚠️ in Documentation or Schema of the response (link next to Example value in the Responses section below).
  • Variables can be instantaneous, averaged, or accumulated over certain time. For example, precipitation forecast provides the precipitation accumulated until the next hour (data with timestamp as 12:00:00 is rain accumulated from 12:00:00 to 13:00:00).
  • Do not make any assumptions about the number and ordering of the variables. New variables and sections may be introduced in the future. Always check the data are present before you try to use them.
  • The response contains an Expires header, which defines the point at which the API response will not change for the same request. We highly recommend using this to avoid unnecessary requests and increase the performance of your app.
  • Meteosource API supports HTTP compression. To enable it, simply add an Accept-Encoding: gzip header to your request.
  • When daylight saving time starts, one hourly record will be missing (typically 2:00:00 AM). When daylight saving time ends, the hourly forecast will contain two records with duplicate times (typically 2:00:00 AM).
  • The detailed description of weather alerts is only available in English. The alert category is translated into selected language.
• timeMachineHistoricalWeather.timeMachineTimeMachineGet

  Actual weather data for a single location and day in the past

  The output contains actual weather data for each day up to 8 years in the past, and long-term statistics of selected weather variables aggregated over 40 years.

  Location specification

  The location of the weather data must be specified. There are two ways to do this:

  1. Specify the GPS coordinates of the location using the parameters lat and lon.
  2. OR specify the name of the place using the parameter place_id. To obtain the place_id for the location you want, please use endpoints /find_places_prefix (search by prefix) or /find_places (search by full name).

  Note: For mountains, it is usually better to specify the place_id rather than the lat and lon. When you use place_id, you are guaranteed to receive data for the precise elevation of the peak. When you specify the coordinates, the elevation can be less precise.

• weatherMaps.mapMapGet

  PNG weather forecast maps for given area and variable

  Area specification

  There are two ways to specify geographical area you need for your map:

  1. Specify X and Y coordinates and zoom level Z of desired tile in Google Maps Tile notation.
  2. Specify latitude and longitude bounds of the area you want to cover.

  Notes

  • The resulting PNG maps are always in Google Mercator projection (EPSG:3857).
  • As Meteosource only covers areas between latitudes 80° and -80°, you can only request maps within these bounds, when specifying the latitude and longitude boundaries. When specifying the area using Google Maps Tile notation, the regions outside our supported latitudes will be fully transparent.
  • The finest resolution is not available for maps covering very large regions. The resulting map will be automatically downscaled in this case, to guarantee high-speed responses.
  • Weather maps are only supported for forecasts, not for archive data.
• openapi.previewSpec

  Preview an OpenAPI document before adding it as a source

• openapi.addSource

  Add an OpenAPI source and register its operations as tools