-
Notifications
You must be signed in to change notification settings - Fork 3
Add TIME_bounds variable to describe binning intervals #113
Copy link
Copy link
Open
Labels
aggregated_timeseriesIssues relating to the aggregated time series productIssues relating to the aggregated time series productenhancementNew feature or requestNew feature or requesthourly_timeseriesIssues relating to the hourly time series productIssues relating to the hourly time series productvelocity_aggregatedIssues relating to the velocity aggregated time series productIssues relating to the velocity aggregated time series productvelocity_hourlyIssues relating to the velocity hourly time series productIssues relating to the velocity hourly time series product
Milestone
Metadata
Metadata
Assignees
Labels
aggregated_timeseriesIssues relating to the aggregated time series productIssues relating to the aggregated time series productenhancementNew feature or requestNew feature or requesthourly_timeseriesIssues relating to the hourly time series productIssues relating to the hourly time series productvelocity_aggregatedIssues relating to the velocity aggregated time series productIssues relating to the velocity aggregated time series productvelocity_hourlyIssues relating to the velocity hourly time series productIssues relating to the velocity hourly time series product
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
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_measurementattribute in ADCP files, or theinstrument_burst_durationglobal attribute).