Struct GetInterpolatedAssetPropertyValuesInput 

#[non_exhaustive]
pub struct GetInterpolatedAssetPropertyValuesInput {

    pub asset_id: Option<String>,
    pub property_id: Option<String>,
    pub property_alias: Option<String>,
    pub start_time_in_seconds: Option<i64>,
    pub start_time_offset_in_nanos: Option<i32>,
    pub end_time_in_seconds: Option<i64>,
    pub end_time_offset_in_nanos: Option<i32>,
    pub quality: Option<Quality>,
    pub interval_in_seconds: Option<i64>,
    pub next_token: Option<String>,
    pub max_results: Option<i32>,
    pub type: Option<String>,
    pub interval_window_in_seconds: Option<i64>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

asset_id: Option<String>

The ID of the asset, in UUID format.

property_id: Option<String>

The ID of the asset property, in UUID format.

property_alias: Option<String>

The alias that identifies the property, such as an OPC-UA server data stream path (for example, /company/windfarm/3/turbine/7/temperature). For more information, see Mapping industrial data streams to asset properties in the IoT SiteWise User Guide.

start_time_in_seconds: Option<i64>

The exclusive start of the range from which to interpolate data, expressed in seconds in Unix epoch time.

start_time_offset_in_nanos: Option<i32>

The nanosecond offset converted from startTimeInSeconds.

end_time_in_seconds: Option<i64>

The inclusive end of the range from which to interpolate data, expressed in seconds in Unix epoch time.

end_time_offset_in_nanos: Option<i32>

The nanosecond offset converted from endTimeInSeconds.

quality: Option<Quality>

The quality of the asset property value. You can use this parameter as a filter to choose only the asset property values that have a specific quality.

interval_in_seconds: Option<i64>

The time interval in seconds over which to interpolate data. Each interval starts when the previous one ends.

next_token: Option<String>

The token to be used for the next set of paginated results.

max_results: Option<i32>

The maximum number of results to return for each paginated request. If not specified, the default value is 10.

type: Option<String>

The interpolation type.

Valid values: LINEAR_INTERPOLATION | LOCF_INTERPOLATION

• LINEAR_INTERPOLATION – Estimates missing data using linear interpolation.

  For example, you can use this operation to return the interpolated temperature values for a wind turbine every 24 hours over a duration of 7 days. If the interpolation starts July 1, 2021, at 9 AM, IoT SiteWise returns the first interpolated value on July 2, 2021, at 9 AM, the second interpolated value on July 3, 2021, at 9 AM, and so on.

• LOCF_INTERPOLATION – Estimates missing data using last observation carried forward interpolation

  If no data point is found for an interval, IoT SiteWise returns the last observed data point for the previous interval and carries forward this interpolated value until a new data point is found.

  For example, you can get the state of an on-off valve every 24 hours over a duration of 7 days. If the interpolation starts July 1, 2021, at 9 AM, IoT SiteWise returns the last observed data point between July 1, 2021, at 9 AM and July 2, 2021, at 9 AM as the first interpolated value. If a data point isn't found after 9 AM on July 2, 2021, IoT SiteWise uses the same interpolated value for the rest of the days.

interval_window_in_seconds: Option<i64>

The query interval for the window, in seconds. IoT SiteWise computes each interpolated value by using data points from the timestamp of each interval, minus the window to the timestamp of each interval plus the window. If not specified, the window ranges between the start time minus the interval and the end time plus the interval.

• If you specify a value for the intervalWindowInSeconds parameter, the value for the type parameter must be LINEAR_INTERPOLATION.

• If a data point isn't found during the specified query window, IoT SiteWise won't return an interpolated value for the interval. This indicates that there's a gap in the ingested data points.

For example, you can get the interpolated temperature values for a wind turbine every 24 hours over a duration of 7 days. If the interpolation starts on July 1, 2021, at 9 AM with a window of 2 hours, IoT SiteWise uses the data points from 7 AM (9 AM minus 2 hours) to 11 AM (9 AM plus 2 hours) on July 2, 2021 to compute the first interpolated value. Next, IoT SiteWise uses the data points from 7 AM (9 AM minus 2 hours) to 11 AM (9 AM plus 2 hours) on July 3, 2021 to compute the second interpolated value, and so on.

Implementations

impl GetInterpolatedAssetPropertyValuesInput

pub fn asset_id(&self) -> Option<&str>

The ID of the asset, in UUID format.

pub fn property_id(&self) -> Option<&str>

The ID of the asset property, in UUID format.

pub fn property_alias(&self) -> Option<&str>

The alias that identifies the property, such as an OPC-UA server data stream path (for example, /company/windfarm/3/turbine/7/temperature). For more information, see Mapping industrial data streams to asset properties in the IoT SiteWise User Guide.

pub fn start_time_in_seconds(&self) -> Option<i64>

The exclusive start of the range from which to interpolate data, expressed in seconds in Unix epoch time.

pub fn start_time_offset_in_nanos(&self) -> Option<i32>

The nanosecond offset converted from startTimeInSeconds.

pub fn end_time_in_seconds(&self) -> Option<i64>

The inclusive end of the range from which to interpolate data, expressed in seconds in Unix epoch time.

pub fn end_time_offset_in_nanos(&self) -> Option<i32>

The nanosecond offset converted from endTimeInSeconds.

pub fn quality(&self) -> Option<&Quality>

The quality of the asset property value. You can use this parameter as a filter to choose only the asset property values that have a specific quality.

pub fn interval_in_seconds(&self) -> Option<i64>

The time interval in seconds over which to interpolate data. Each interval starts when the previous one ends.

pub fn next_token(&self) -> Option<&str>

The token to be used for the next set of paginated results.

pub fn max_results(&self) -> Option<i32>

The maximum number of results to return for each paginated request. If not specified, the default value is 10.

pub fn type(&self) -> Option<&str>

The interpolation type.

Valid values: LINEAR_INTERPOLATION | LOCF_INTERPOLATION

• LINEAR_INTERPOLATION – Estimates missing data using linear interpolation.

  For example, you can use this operation to return the interpolated temperature values for a wind turbine every 24 hours over a duration of 7 days. If the interpolation starts July 1, 2021, at 9 AM, IoT SiteWise returns the first interpolated value on July 2, 2021, at 9 AM, the second interpolated value on July 3, 2021, at 9 AM, and so on.

• LOCF_INTERPOLATION – Estimates missing data using last observation carried forward interpolation

  If no data point is found for an interval, IoT SiteWise returns the last observed data point for the previous interval and carries forward this interpolated value until a new data point is found.

  For example, you can get the state of an on-off valve every 24 hours over a duration of 7 days. If the interpolation starts July 1, 2021, at 9 AM, IoT SiteWise returns the last observed data point between July 1, 2021, at 9 AM and July 2, 2021, at 9 AM as the first interpolated value. If a data point isn't found after 9 AM on July 2, 2021, IoT SiteWise uses the same interpolated value for the rest of the days.

pub fn interval_window_in_seconds(&self) -> Option<i64>

The query interval for the window, in seconds. IoT SiteWise computes each interpolated value by using data points from the timestamp of each interval, minus the window to the timestamp of each interval plus the window. If not specified, the window ranges between the start time minus the interval and the end time plus the interval.

• If you specify a value for the intervalWindowInSeconds parameter, the value for the type parameter must be LINEAR_INTERPOLATION.

• If a data point isn't found during the specified query window, IoT SiteWise won't return an interpolated value for the interval. This indicates that there's a gap in the ingested data points.

For example, you can get the interpolated temperature values for a wind turbine every 24 hours over a duration of 7 days. If the interpolation starts on July 1, 2021, at 9 AM with a window of 2 hours, IoT SiteWise uses the data points from 7 AM (9 AM minus 2 hours) to 11 AM (9 AM plus 2 hours) on July 2, 2021 to compute the first interpolated value. Next, IoT SiteWise uses the data points from 7 AM (9 AM minus 2 hours) to 11 AM (9 AM plus 2 hours) on July 3, 2021 to compute the second interpolated value, and so on.

impl GetInterpolatedAssetPropertyValuesInput

pub fn builder() -> GetInterpolatedAssetPropertyValuesInputBuilder

Creates a new builder-style object to manufacture GetInterpolatedAssetPropertyValuesInput.

Trait Implementations

impl Clone for GetInterpolatedAssetPropertyValuesInput

fn clone(&self) -> GetInterpolatedAssetPropertyValuesInput

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for GetInterpolatedAssetPropertyValuesInput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for GetInterpolatedAssetPropertyValuesInput

fn eq(&self, other: &GetInterpolatedAssetPropertyValuesInput) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for GetInterpolatedAssetPropertyValuesInput