Weatherbit

Utilize Mapped's Weatherbit connector to create a virtual weather station on top of each of your buildings. With this connector, you can receive current weather data for your building's location such as air temperature, rainfall, humidity percentage, wind speed, pressure and solar radiation. Current weather is collected every 15 minutes and written to typed timeseries points, and historical hourly observations can be backfilled for a date range.

Use Cases

Some possible use cases for weather data include:

• Reactive air conditioning adjustments based on real outside temperature data
• Alerting based on rainy conditions at your location
• Adjusting indoor air quality strategies based on humidity
• Predicting occupancy based on weather at the office
• Correlating energy use with spikes in cold or heat
• Analyzing historical weather alongside building performance

Configuration

Authentication

The connector works with Mapped's Weatherbit subscription by default. Supplying your own Weatherbit API key is optional and uses your organization's Weatherbit subscription instead.

Field	Required	Description
Weatherbit API Key	No	A valid API key from your Weatherbit account. Add this when you want to use your own subscription or need points available only with a customer subscription.

Weather Stations

With the new connector entities framework, Weatherbit does not provide a list of stations to import. Instead, the connector offers existing buildings in your Mapped organization as candidates for virtual weather stations.

For each station, provide the following fields in the Weather Stations section:

Field	Required	Description
Name	Yes	The display name of the virtual weather station. New stations default to <building name> Weather Station.
Location	Yes	The Mapped Building, Site, or Space that the station represents. New stations default to the building from which they were created.

The connector uses the selected building's geographic coordinates. If those coordinates are unavailable, it attempts to use the building's postal address. A station without usable coordinates remains in the graph, but no weather observations are collected until coordinates become available.

Select the desired Weather Stations from the Grid and Save to create them.

Each weather station is a Mapped-side virtual entity rather than a Weatherbit source record. Moving a station to another location changes its relationship to the Building, Site, or Space without creating a new station identity.

Points and Measurement System

All listed points are enabled by default. You can turn individual point writes on or off without removing the point from the graph.

Choose one measurement system:

Option	Effect
Metric	Default. Temperature is Celsius, precipitation and snow are millimetres per hour, and wind speed is metres per second.
Imperial	Temperature is Fahrenheit, precipitation and snow are inches per hour, and wind speed is miles per hour.
Scientific	Temperature is Kelvin; precipitation, snow, and wind speed use the same units as Metric.

Units

Point type	Metric (M)	Imperial (I)	Scientific (S)
Air temperature	DEG_C	DEG_F	K
Dew point	DEG_C	DEG_F	K
Precipitation rate	MilliM-PER-HR	IN-PER-HR	MilliM-PER-HR
Snow accumulation	MilliM-PER-HR	IN-PER-HR	MilliM-PER-HR
Relative humidity	PERCENT_RH	PERCENT_RH	PERCENT_RH
Sea-level pressure	MilliBAR	MilliBAR	MilliBAR
Solar radiation	W-PER-M2	W-PER-M2	W-PER-M2
Wind direction	DEG	DEG	DEG
Wind speed	M-PER-SEC	MI-PER-HR	M-PER-SEC

Backfill

Use Backfill to collect hourly historical weather for every configured weather station in a selected date range. The range must start before it ends, cannot include future dates, and can span up to 1,095 days (about three years). Only one backfill can run at a time.

Mapped Concepts

The connector creates one virtual weather station per station you save, places it at the selected Building, Site, or Space, and writes weather observations to points on that station.

Graph Entities

API to Mapped Entities

Source	Mapped Entity	exactType	Relationship
Selected Mapped place	Thing (virtual weather station)	Weather_Station	hasLocation → the selected Building, Site, or Space (required)

Migrated and Pre-Migration Connectors

Stations have the same exactType (Weather_Station) whether or not your connector has been migrated to connector entities. What differs is the name:

Connector state	Station name	Example
Migrated to connector entities	<building name> Weather Station by default, or the name you entered in the Grid	40 Mount Street Weather Station
Not yet migrated	Virtual Weather Station for every station	Virtual Weather Station

Because pre-migration stations all share one name, identify them by ID rather than by name. Filter on exactType: "Weather_Station" to find stations in either case.

Time Series

API to Mapped Points

Current observations are written every 15 minutes, and backfill writes hourly observations. All points use the DOUBLE datatype.

Weatherbit Field	Mapped Point exactType	Unit in Metric / Scientific	Unit in Imperial
dewpt	Dewpoint_Sensor	°C / K	°F
precip	Precipitation_Sensor	mm/h	in/h
rh	Relative_Humidity_Sensor	% relative humidity	% relative humidity
slp	Sea_Level_Air_Pressure_Sensor	millibar	millibar
snow	Snow_Accumulation_Sensor	mm/h	in/h
solar_rad	Solar_Irradiance_Sensor	W/m²	W/m²
temp	Air_Temperature_Sensor	°C / K	°F
wind_dir	Wind_Direction_Sensor	degrees	degrees
wind_spd	Wind_Speed_Sensor	m/s	mph

When Weatherbit omits a measurement from an observation, the connector does not write a value for that point. Disabling a point stops new timeseries writes but preserves its existing graph metadata and history.

Heartbeats

This connector does not currently implement heartbeats.

Sample Code

To access data from the Weatherbit Connector, once it's enabled, you'll can make a call to things and filter it for "Weather_Station". If you have multiple buildings with Weatherbit set up, you'll likely want to retrieve data for each individual Weather Station, which is easiest by just filtering by the specific Weather Station's ID:

{
  things(filter: {id: {eq: "THGGfFWQ4BAQ3X5fAQou5ewuV"}}) {
    id
    name
    exactType
    points {
      id
      name
      series(latest: true) {
        timestamp
        value {
          float64Value
        }
      }
    }
  }
}

If you're unsure what the unit of measure is for each value, include the unit field under points:

{
  things(filter: {id: {eq: "THGGfFWQ4BAQ3X5fAQou5ewuV"}}) {
    id
    name
    exactType
    points {
      id
      name
      unit {
        name
      }
      series(latest: true) {
        timestamp
        value {
          float64Value
        }
      }
    }
  }
}

Read more about Things, Points, and Filtering in our Developer Docs.