Weather Data Layers

Layer Subscriptions

With more than 80 different data fields available, including weather, air quality, pollen, and fire index, you can build almost anything weather-related using the Tomorrow.io REST Weather API. You can also use the data points to create custom Insights that will trigger events whenever the conditions are met.

Here are best practices for calling the API for different timesteps and layers.

Timestep Availability

Timesteps are restricted as following, in the intersection with the field-specific availability:

Data availability beyond -6H in the past and beyond 4.5 days in the future is available for paid plans as an add-on only.

Field Availability

When detailing the different fields available for each Data Layer, we also specify its availability using the criteria annotation mentioned below:

Frame: the time frame in which numerical data is supported -

• [ and ] Square Brackets: means the time frame includes the edge intervals
• ( and ) Parenthesis: means the time frame excludes the edge intervals
• In any case of two different timesteps - like "m" (minutes), "h" (hours) or "d" (days) - the data is available for any timesteps options between them

Interfaces: where the data is supported -

• Timeline ( T ): queried data point for the conditions for any interval in a given time frame, in one or multiple timesteps
• Insights ( I ): PARAMETER representation in a conditions rule structure, to be used in Alerts or Dashboards - currently supports only Point locations
• Map ( M ): raster representation of a single field for a given time
• Route ( R ): queried data point for the conditions throughout all intervals of the legs of the route, in a single timestep

Area: the regional coverage in which the data is supported -

• WW: worldwide
• LAND: land-only
• MARINE: marine-only
• ISO 3166-1 codes: such as US or GB

Suffix (S): the postfix for which data is supported -

• Max (x): maximum - supported for any location type, non-"1d" timestep for point locations will resolve the raw value. Example: temperatureMax
• Min (n): minimum - supported for any location type, non-"1d" timestep for point locations will resolve the raw value. Example: temperatureMin
• Avg (-): average - supported for any location type, non-"1d" timestep for point locations will resolve the raw value. Example: temperatureAvg
• MinTime/MaxTime (%): time where Min/Max values occurred - currently only supported in "1d" timestep. Examples: temperatureMinTime, temperatureMaxTime

Probabilistic Forecasting (P): Does this field supports Probabilistic Forecasting.

• P -: Means it doesn't support Probabilistic Forecasting.
• P +: Means it does support Probabilistic Forecasting.

In any cases where a field is not available in a requested timestep, the request will result in a Timestep_Bounded_Field warning. For example, rainAccumulation is supported only for 1h and above; requesting 1m will result in a warning.

In any cases where a field is not available in a requested area, the request will result in a Location_Bounded_Field warning and will not be included in the response. For example, hailBinary is supported only for the US and over Europe will result in a warning.

If a field is available, but the weather phenomena don't occur over the request location, the request will result in null values. For example, moonriseTime is supported only for days the moon rises above the horizon; requesting moonriseTime for a day with no moon rise will result in null.