A type of Calculation that specifies that cooling degree days should be calculated and that holds the base temperature that they should be calculated to.
A type of DatedBreakdown used to specify that degree days should be broken down into the custom date ranges specified e.g. to match the dates of your energy-usage records.
A type of Period that is defined explicitly in terms of the range of days that it covers.
A type of AverageBreakdown used to specify that average-degree-day figures should be derived from data covering a specified number of full calendar years.
A type of Calculation that specifies that heating degree days should be calculated and that holds the base temperature that they should be calculated to.
A type of Period that automatically resolves to a date range including the latest available data and the specified number of degree-day values.
Specifies a location in terms of longitude and latitude coordinates.
Specifies a location using a postal code (or zip code, post code, or postcode - the terminology depends on the country).
A type of TimeSeriesCalculation that specifies that temperature data should be calculated with the specified interval (e.g. hourly) and unit (e.g. Celsius).
These classes provide a range of options for specifying the degree-day data you want as part of a LocationDataRequest.
Instead of accessing these classes directly, it's generally easier to use the static factory methods on the abstract types in DegreeDays.Api.Data. For example, when you need to create a Location object, type Location. and your IDE should pop up static factory methods for the various location types that you can choose from, like Location.StationId and Location.PostalCode.
Whether you're using the static-factory methods or not, this package is the place to look for detailed documentation on the types it contains.