DatedBreakdownAllowPartialLatest Property

public bool AllowPartialLatest { get; }

Public ReadOnly Property AllowPartialLatest As Boolean
	Get

Property Value

When specifying time-series data (like hourly temperature data), you can specify a breakdown with this AllowPartialLatest property set to true, to tell the API to include values for the latest incomplete day so far (usually today for real-world weather stations with quick updates). For example:

TimeSeriesDataSpec hourlyTempsIncludingPartialLatestDay = DataSpec.TimeSeries(
    TimeSeriesCalculation.HourlyTemperature(TemperatureUnit.Celsius),
    DatedBreakdown.Daily(Period.LatestValues(31))
        .WithAllowPartialLatest(true));

Dim hourlyTempsIncludingPartialLatestDay As TimeSeriesDataSpec = DataSpec.TimeSeries(
    TimeSeriesCalculation.HourlyTemperature(TemperatureUnit.Celsius),
    DatedBreakdown.Daily(Period.LatestValues(31)) _
        .WithAllowPartialLatest(True))

If you requested the above-specified hourly temperature data at, say, 11:42 on any given day, for a real-world weather station that updates quickly, it would likely include values for 00:00, 01:00, 02:00, through to 11:00 on that day. Though bear in mind that some stations are slower to update than others so you won't always get the most recent values – our FAQ on update schedules explains more.

Please note that the most recent time-series data can be a little volatile, as weather stations sometimes send multiple reports for the same time, some delayed, and some marked as corrections for reports they sent earlier. Our system generates time-series data using all the relevant reports that each weather station has sent, but the generated figures may change if delayed or corrected reports come through later. If you are storing partial-latest time-series data we suggest you overwrite it later with figures generated after the day has completed and any delayed/corrected reports have had time to filter through.

This AllowPartialLatest property exists mainly for time-series data, but you can also set it to true on a breakdown for degree days, to specify that the data can include a value for the latest partial week/month/year. For example:

DatedDataSpec monthlyHddIncludingPartialLatest = DataSpec.Dated(
    Calculation.HeatingDegreeDays(Temperature.Fahrenheit(65)),
    DatedBreakdown.Monthly(Period.LatestValues(12))
        .WithAllowPartialLatest(true));

Dim monthlyHddIncludingPartialLatest As DatedDataSpec = DataSpec.Dated(
    Calculation.HeatingDegreeDays(Temperature.Fahrenheit(65)),
    DatedBreakdown.Monthly(Period.LatestValues(12)) _
        .WithAllowPartialLatest(True))

If you requested the above-specified monthly degree-day data on, say, June 22nd, for a real-world weather station with quick updates, you could typically expect the last of the 12 values returned to cover from the start of June 1st through to the end of June 21st. The day range of that last value would make clear what day it ended on. If you left AllowPartialLatest with its default value of false, the last of the 12 values returned would be for the full month of May (i.e. from the start of May 1st to the end of May 31st), as the monthly figure for June wouldn't become available until after June ended and the station reported its first temperature reading for July.

Unlike for time-series data, this property will never cause degree days to be calculated for partial days. So for degree days this property will only make a difference on weekly, monthly, yearly, and custom breakdowns with day ranges covering multiple days.

Any partial-latest day range will always start on the usual day (i.e. it will never be cut short at the start), it's only the end that can be cut short. This is true for both degree days and time-series data.

To create a DatedBreakdown with this AllowPartialLatest property set to true, use the WithAllowPartialLatest methods listed below under "See Also".

Reference