Skip to content

Add TIME_bounds variable to describe binning intervals #113

Open

Description

@mhidas

There are CF standard ways to describe values that are representative of an interval, and we should be using these to document our products. In particular, binning time intervals can be described using a TIME_bounds variable. We should add such variables in

  • The aggregated products, to describe any binning that has already been applied to values in the input files
  • The hourly products to describe the hourly binning intervals.

Ideally, the bounds relevant to the input files would just be copied from those files, but they are not currently in there. However, they can be computed from existing metadata in the files (such as the TIME:seconds_to_middle_of_measurement attribute in ADCP files, or the instrument_burst_duration global attribute).

Activity

  1. added
    aggregated_timeseriesIssues relating to the aggregated time series product
    hourly_timeseriesIssues relating to the hourly time series product
    velocity_aggregatedIssues relating to the velocity aggregated time series product
    on Mar 19, 2020
  2. changed the title [-]Add TIME_bounds variables to describe binning intervals[/-] [+]Add TIME_bounds variable to describe binning intervals[/+] on Mar 19, 2020
  3. added
    velocity_hourlyIssues relating to the velocity hourly time series product
    enhancementNew feature or request
    on Mar 19, 2020
  4. added this to the v2.1+ milestone on Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    aggregated_timeseriesIssues relating to the aggregated time series productenhancementNew feature or requesthourly_timeseriesIssues relating to the hourly time series productvelocity_aggregatedIssues relating to the velocity aggregated time series productvelocity_hourlyIssues relating to the velocity hourly time series product

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions