Dataset Submission: HakaiPruthDockProvisional about hakai-datasets

[JessyBarrette]

@n-a-t-e Think it would be best to create a view for this dataset with the following variables available (see here):

• PruthDock.TideHeight_Avg
• PruthDock.TideHeightDelta_Avg
• PruthDock.TideHeightPLS_Avg
• PruthDock.AirTemp_Avg
• PruthDock.AirTemp2_Avg
• PruthDock.SeaLevelAirPressure_Avg
• PruthDock.SeaLevelAirPressure_Avg
• PruthDock.PAR_Avg
• PruthDock.SolarRad_Avg
• PruthDock.Rain
• PruthDock.UVRad_Avg
• PruthDock.WindDir_Avg
• PruthDock.WindSpd_Avg
• PruthDock.StationAirPressure_Avg
• PruthDock:RH

Potentially (that data has some issues and would need to corrected)

• PruthDock.PLS_Salinity_Avg
• PruthDock.PLS_Cond_Avg
• PruthDock.PLS_TDS_Avg
• PruthDock.PLS_Temp_Avg

[JessyBarrette]

@raytula Regarding the tide gauge data at Pruth dock. Do you have any thoughts regarding also including the meteorological station data coming from the exact same location?

[raytula]

@raytula Regarding the tide gauge data at Pruth dock. Do you have any thoughts regarding also including the meteorological station data coming from the exact same location?

@JessyBarrette that sounds good to me.

[JessyBarrette]

Alright, we'll get that setup like that. Should be a simple link to the database!

[JessyBarrette]

Preliminary dataset is now available here https://goose.hakai.org/erddap/tabledap/HakaiPruthDockProvisional.html

@raytula have a look, there's a lot of variables listed within this dataset with more than 60% being quality flag-related variables.
I wonder if we should just omit the Hakai flag columns and only consider keeping the QARTOD flag ones.

Let me know your thoughts!

[raytula]

I wonder if we should just omit the Hakai flag columns and only consider keeping the QARTOD flag ones.

Would it make sense to do the same as we are doing for the BoL datasets, where I believe we are passing through the UQL column and the flags (string) column? The Hakai QC column is mapped to UQL.

At some point we should likely review how the two Hakai QC columns are passed through to ERDDAP, as there are likely one or more improvements that should be made there.

[JessyBarrette]

Oh yeah I agree, keeping the UQL as level 1 flag and QC as level 2. I forgot about that makes sense! Ok I'll make some changes regarding that. Replace _QC to _flag like I did for the BoL datasets.

…

On Fri, Jun 18, 2021 at 6:53 AM Ray Brunsting ***@***.***> wrote: I wonder if we should just omit the Hakai flag columns and only consider keeping the QARTOD flag ones. Would it make sense to do the same as we are doing for the BoL datasets, where I believe we are passing through the UQL column and the flags (string) column? The Hakai QC column is mapped to UQL. At some point we should likely review how the two Hakai QC columns are passed through to ERDDAP, as there are likely one or more improvements that should be made there. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#30 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHICYONEKQVA77QUL5KLW53TTNFUBANCNFSM43VKUUKA> .

-- *Jessy Barrette M.Sc.* *Marine Instrumentation Specialist* Hakai Institute <https://www.hakai.org/> | ***@***.*** | (C) [phone]

[JessyBarrette]

I have one issue with the tide data water level. I need to specify to which datetum 0m refers too. Easy fix is to shift the data to center it on the mean value, but it would probably be better to keep the datum used by CHS. Both can probably live together at the same time on the same ERDDAP dataset.

From https://cfconventions.org/Data/cf-standard-names/77/build/cf-standard-name-table.html

• sea_surface_height_above_geopotential_datum
  "Height_above_X" means the vertical distance above the named surface X. "Sea surface height" is a time-varying quantity. The "geopotential datum" is any estimated surface of constant geopotential used as a datum i.e. a reference level; for the geoid as a datum, specific standard names are available. To specify which geoid or geopotential datum is being used as a reference level, a grid_mapping variable should be attached to the data variable as described in Chapter 5.6 of the CF Convention.

• sea_surface_height_above_mean_sea_level
  alias: sea_surface_height_above_sea_levelalias, sea_surface_height
  "Sea surface height" is a time-varying quantity. "Height_above_X" means the vertical distance above the named surface X. "Mean sea level" means the time mean of sea surface elevation at a given location over an arbitrary period sufficient to eliminate the tidal signals. The standard name for the height of the sea surface above the geoid is sea_surface_height_above_geoid. The standard name for the height of the sea surface above the reference ellipsoid is sea_surface_height_above_reference_ellipsoid.

There are other terms that I think refer only to the tide-related variability.

• tidal_sea_surface_height_above_lowest_astronomical_tide
  "Sea surface height" is a time-varying quantity. "Height_above_X" means the vertical distance above the named surface X. "Lowest astronomical tide" describes a local vertical reference based on the lowest water level that can be expected to occur under average meteorological conditions and under any combination of astronomical conditions. The tidal component of sea surface height describes the predicted variability of the sea surface due to astronomic forcing (chiefly lunar and solar cycles) and shallow water resonance of tidal components; for example as generated based on harmonic analysis, or resulting from the application of harmonic tidal series as boundary conditions to a numerical tidal model.
• tidal_sea_surface_height_above_mean_lower_low_water
  "Sea surface height" is a time-varying quantity. "Height_above_X" means the vertical distance above the named surface X. "Mean lower low water" is the arithmetic mean of the lower low water height of each tidal day observed at a station over a Tidal Datum Epoch, which is a period of time that is usually greater than 18.6 years to include a full lunar cycle. Tidal datums in certain regions with anomalous sea level changes may be calculated using a shorter, or modified, Tidal Datum Epoch (e.g. 5 years). To specify the tidal datum epoch to which the quantity applies, provide a scalar coordinate variable with standard name reference_epoch.

[JessyBarrette]

Regarding this, i will for the moment shift the tide data to center (mean value recorded) and use the standard_name: sea_surface_height_above_mean_sea_level

Conductivity and salinity data will be removed for now since they are giving some questionable data. A correction needs to be applied based on profile data collected at KC1.

[JessyBarrette]

Added Hakai Metadata Form

[JessyBarrette]

Pruth Dock data is now available on ERDDAP and CIOOS CKAN!