See: Description
| Class | Description | 
|---|---|
| AverageBreakdown | 
 
 Defines how a set of average degree days should
 be broken down, including the period in time they should cover. 
 | 
| AverageDataSet | 
 Contains a set of average degree-day data generated to fulfil an
  
AverageDataSpec for a specific Location. | 
| AverageDataSpec | 
 Defines a specification for a set of average data such as 5-year-average
 degree days. 
 | 
| Breakdown | 
 Defines how a set of degree days should be broken down (e.g. daily,
 weekly, or monthly), and the period in time they should cover. 
 | 
| Calculation | 
 Defines how degree days should be calculated e.g. HDD or CDD to a
 specific base temperature. 
 | 
| DataApi | 
 Provides easy, type-safe access to the API's data-related operations. 
 | 
| DataSet | |
| DataSets | |
| DataSpec | 
 Defines a specification of a single set of degree-day data (or temperature
 data) in all aspects other than the location that the data should be
 generated for. 
 | 
| DataSpecs | 
 Defines up to 120 sets of data that should be generated to fulfil a
  
LocationDataRequest. | 
| DataValue | 
 Contains a value (e.g. an HDD or CDD value) and an approximate
 indication of its accuracy. 
 | 
| DatedBreakdown | 
 
 Defines how a set of dated degree days should be
 broken down, including the period in time they should cover. 
 | 
| DatedDataSet | 
 
 Contains a set of dated data (e.g. daily/weekly/monthly degree days)
 generated to fulfil a  
DatedDataSpec for a specific Location. | 
| DatedDataSpec | 
 Defines a specification for a set of dated data such as daily, weekly, or
 monthly degree days covering a specific period in time. 
 | 
| DatedDataValue | 
 
 Contains a degree-day value for a specific dated period (a single day or a
 range of days like a specific week, month, or year). 
 | 
| GeographicLocation | 
 
 Defines a location in terms of a longitude/latitude or postal/zip code,
 leaving it to the API to find the nearest good weather station. 
 | 
| Location | 
 Defines a location for which degree days should be calculated. 
 | 
| LocationDataRequest | 
 Defines a request for one or more sets of data from a particular location. 
 | 
| LocationDataResponse | 
 Contains the data generated to fulfil a  
LocationDataRequest. | 
| LocationInfoRequest | 
 Defines a request for info about the station(s) that would be used to fulfil
 an equivalent  
LocationDataRequest. | 
| LocationInfoResponse | 
 Contains the location/station-related info returned in response to a
  
LocationInfoRequest. | 
| Period | 
 Defines the period in time that a set of degree days should cover. 
 | 
| Source | 
 Contains basic information about a source of data that was used to satisfy a
 request. 
 | 
| Station | 
 Contains basic information about a weather station. 
 | 
| Temperature | 
 Defines a temperature value, typically the base temperature of a degree-day
 calculation. 
 | 
| TimeSeriesCalculation | 
 Defines how time-series data should be calculated e.g. temperature data,
 with hourly figures, in Celsius. 
 | 
| TimeSeriesDataSet | 
 
 Contains a set of time-series data (e.g. hourly temperature data)
 generated to fulfil a  
TimeSeriesDataSpec for a specific
 Location. | 
| TimeSeriesDataSpec | 
 Defines a specification for a set of time-series data such as hourly
 temperature data covering a specific period in time. 
 | 
| TimeSeriesDataValue | 
 
 Contains a value (e.g. a temperature value) for a specific point in
 time, and an approximate indication of its accuracy. 
 | 
| Enum | Description | 
|---|---|
| TemperatureUnit | 
 Defines the units of temperature measurement with enum constants to represent 
 Celsius and Fahrenheit. 
 | 
| TimeSeriesInterval | 
 Defines the interval (e.g. hourly) that time-series data should be
 calculated with. 
 | 
| Exception | Description | 
|---|---|
| DataTransformException | 
 Indicates that this client library could not transform a set of data into one
 with a different breakdown. 
 | 
| LocationException | |
| SourceDataException | 
For specifying and receiving degree-day data and temperature data from the API.
If you are new to this package, we suggest you start by looking at DataApi.
See www.degreedays.net/api/ for more about the Degree Days.net API.
You can sign up for a Degree Days.net API account and read the integration guide that is useful and applicable whether you are using Java or not.