Here's the place to learn and talk about our data products – both current and future.
- Instrument search has been modified to include deployed sites in the instrument tree, allowing users to quickly select the instrument and site combination that interests them. (Affects instrument searches in plotting utility, but does not affect location, network or project searches.)
- Integration of QAQC flags in to data products is partially complete. Users will see some new columns in CSV data products and new fields MAT data products that contain the flags. Future revisions will enable users to select various options on the data products, including filtering data that fail QAQC checks.
- Min/Max resampling is temporarily disabled. It will not appear in the resample type options until it can be improved.
- Rebuilds of the RDI and Nortek ensemble-averaging data products - the major benefits include adding backscatter and amplitude to the current plots, speed, reliability and ensemble files that can contain up to one year of data.
- See the latest release notes here.
Metadata reports are now available with many different data products, including the scalar data products. These PDF reports are produced automatically when a data search is completed and are made available via a link adjacent to the data, see step 3 in data search help. The reports contain extensive information about the data, including instrument location, deployment, calibration, data quality and data gaps.
Time-stamps: Time-stamps are always in UTC. For file-names and string dates, the format conforms to the ISO8601 convention: yyyymmddTHHMMSS. In some cases, the millisecond portion may be added: yyyymmddTHHMMSS.FFFZ. Numerical time-stamps within data product files may follow a different format as noted on the data product pages. For instances, numeric time-stamps within MAT files are in the MATLAB serial date format. When resampling, the time-stamps are generally taken from the the centre of the resample interval.
File-names: Note that the underscore character, "_", is used to separate the components of the names. It is also used to replace any spaces in the name to maintain compatibility. File breaks occur for many reasons, including configuration or device changes (location search only), plus some data products have daily file breaks.
For an instrument search, files are named as DEVICECODE_SENSORNAME_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where:
For a location search, files are named as STATIONNAME_DEVICECATEGORY_SENSORNAME_yyyymmddTHHMMSSZ_yyyymmddTHHMMSSZ-MODE.EXT where
Additional resources for available file formats is available here.
If you have any data product related questions or would like to see additional data products, please let us know.