At the time of this document, you can find related developer-level details at the following blog URL on Niagara-Central: https://www.niagara-central.com/ord?portal:/blog/BlogEntry/267
Starting in AX-3.7U1 (build 3.7.104 or later), the Wunderground Weather Provider is an available type when adding a WeatherReport in the Weather Manager, providing that the weatherUnderground module is installed (along with the weather module). See it in the drop-down “Type to Add” field in the New dialog when adding a new WeatherReport (Figure 28).
Usage is intended for “international weather”, meaning locales outside of the U.S. (and/or areas served by U.S. NWS reports). Otherwise, it is recommend to use the default type: NwsWeatherProvider.
The following requirements and limitations apply when using the Wunderground Weather Provider:
You require a Weather API “key ID” from wunderground.com, received after opening a developer account. Costs range from free to some tiered monthly fee, based on usage (calls/day and calls/minute). At the time of this document, find more details at: www.wunderground.com/weather/api
When adding a new Wunderground Weather Provider, you enter your key ID string.
Although forecasting components and current conditions are available, currently there is no Niagara support for advisories issued through a Wunderground Weather Provider. Thus, the AdvisoryContainer component under the CurrentConditions of such a WeatherReport will remain empty.
Air quality properties (Ozone, Particulate Matter) and Heat Index of CurrentConditions also remain at null values. Thus, the Current Air Quality View remains at “unknown”.
When adding, in a secondary New dialog, you enter a weather report name, the known latitude and longitude for the location (in decimal degrees), your unique key ID string. Figure 29 shows an example.
Figure 29. Secondary New dialog, with latitude, longitude, and API “key ID” issued by wunderground.com

Once added, a connection is made to the weather API at wunderground.com, the location is resolved, and the report is updated, including current conditions and some number of forecast days (Figure 30).
Note values display in Workbench converted to metric units (as shown above) only if the Workbench user’s options are set for metric, otherwise values appear in English units (degrees F, mph). Web browser access displays values in units according to the user’s Facets, Unit Conversion setting.
At the time of this document update, a few CurrentConditions properties may be fixed in English values or units—for example “Pressure” (in Hg) vs. millibars (mb) or “Visibility” (mile) vs. kilometers (km).
Property sheet access of a WundergroundWeatherProvider shows values that represent the three selections made when adding (or editing) the WeatherReport, as well as the resolved location (Figure 32.).
These properties are:
Latitude
Latitude of target location in decimal degrees (both minutes and seconds in decimal format).
An online converter for going from degrees, minutes, seconds, to decimal degrees can be found at: http://www.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html (at this document time).
Longitude
Longitude of target location in decimal degrees (both minutes and seconds in decimal format).
Location
(Read-only) Location text string received from the wunderround.com weather API, resolved for the latitude and longitude values entered.
Key
Your unique Key ID string value received from wunderground.com, for your project account (can be used for multiple different WeatherReports).
If you regenerate this API key using wunderground.com’s Weather API site, you also need to update this property string to
match in your WundergroundWeatherProviders.
Copyright © 2000-2014 Tridium Inc. All rights reserved.