These are GLEON-centric instructions to enter buoy data into the CUAHSI system based on one test case. They will likely need to be altered as experience is gained and CUAHSI software modified. Examples csv files are attached at the bottom of this page.
1. Create a Google account.
CUAHSI ties this to your database to a Google account. For example, the Lake Sunapee buoy data uses GLEON.Sunapee@gmail.com . CUAHSI will want you to log into their system with it. Currently, a separate Google account is required for each database.
2. Have CUAHSI set up a database
3. Register your data service. (Unclear what this is exactly)
a. Once CUAHSI has contacted you in Step 3, go to http://hiscentral.cuahsi.org where you must enter a few fields. Here are some living examples: http://hiscentral.cuahsi.org/pub_services.aspx Below are what we used for Lake Sunapee.
Data Service Title: Lake Sunapee, New Hampshire, USA Instrumented Buoy
Observation Network Name: GLEON_Sunapee
URL to WDSL: (CUAHSI should provide this to you in their email.)
4. Fill out the data and metadata templates. There are six that are required: five of metadata (Sites, Variables, Sources, Methods, QualityControlLevels) and one or more for data (DataValues). There may be more than one for DataValues because CUAHSI currently accepts at most 50,000 records per upload. Datasets with more than 50k data points will require multiple uploads of the data portion. Unused fields should be left blank but the field header must be left intact with an empty column below it.
The spreadsheet at the link will be helpful in describing fields: ODMGuide-Excel.
SITES
Bold are required fields. CV=Controlled Vocabulary
Field |
Entry Type |
Example Entry |
SiteCode |
Text (255) |
SUNAPEE |
SiteName |
Text (255) |
Lake Sunapee |
Latitude |
Numeric |
43.39133 |
Longitude |
Numeric |
-72.0577 |
LatLongDatumSRSName |
CV-SpatialReferences |
WGS84 |
Elevation_m |
Numeric |
333 |
VerticalDatum |
CV-VerticalDatum |
MSL |
LocalX |
Numeric |
|
LocalY |
Numeric |
|
LocalProjectionSRSName |
CV-SpatialReferences |
|
PosAccuracy_m |
Numeric |
|
State/Administrative Subdivision 1 |
Text (255) |
New Hampshire |
County/Administrative Subdivision 2 |
Text (255) |
Sullivan and Merrimack |
Comments |
Text (Unlimited) |
|
SiteType |
CV-SiteType |
Lake, Reservoir, Impoundment |
SOURCES
Bold are required fields. CV=Controlled Vocabulary
Field |
Entry Type |
Example Entry |
SourceCode |
Text (50) |
LSPA |
Organization |
Text (255) |
Lake Sunapee Protective Assoc. |
SourceDescription |
Text (Unlimited) |
Sunapee Buoy |
SourceLink |
Text (500) |
|
ContactName |
Text (255) |
June Fichter |
Phone |
Text (255) |
603 763 2210 |
|
Text (255) |
|
Address |
Text (255) |
63 Main Street |
City |
Text (255) |
Sunapee |
State |
Text (255) |
NH |
ZipCode |
Text (255) |
03782 |
Citation |
Text (unlimited) |
Weathers, K.C. et al (2014). Lake Sunapee GLEON buoy data. |
TopicCategory |
CV-? |
Unknown |
Title |
Text (255) |
Unknown |
Abstract |
Text (unlimited) |
Unknown |
ProfileVersion |
Text (255) |
Unknown |
MetadataLink |
Text (500) |
|
VARIABLES
All fields are required. CV=Controlled Vocabulary
Field |
Entry Type |
Example Entry |
VariableCode |
Text (50) |
watertemperature |
VariableName |
CV-VariableName |
Temperature |
Speciation |
CV-Speciation |
Not Applicable |
VariableUnitsName |
CV-Units |
degree celsius |
SampleMedium |
CV-SampleMedium |
Surface water |
ValueType |
CV-ValueType |
Field Observation |
IsRegular |
Boolean |
TRUE |
TimeSupport |
Numeric |
10 |
TimeUnitsName |
CV-Units |
minute |
DataType |
CV-DataType |
Average |
GeneralCategory |
CV-GeneralCategory |
Climate |
NoDataValue |
Numeric |
-9999 |
METHODS
Bold are required fields.
Field |
Entry Type |
Example Entry |
MethodCode |
Text (50) |
watertemp_2m |
MethodDescription |
Text (unlimited) |
Water temp at 2m depth measured with Nexsens T500 |
MethodLink |
Text (500) |
|
Methods is how similar but distinct measurements are currently handled. For example, a thermistor chain on a buoy will generate a separate method for each sensor/depth combination but require only one variable, water temperature:
MethodCode |
MethodDescription |
watertemp_1m |
Water temp at 1m depth measured with Nexsens T500 |
watertemp_2m |
Water temp at 2m depth measured with Nexsens T500 |
Another example: reporting battery voltages from both a data logger and data radio will require two different methods, but can/should use the same variable if all of the fields in the Variables table are identical.
VariableCode |
VariableName (CV) |
MethodCode |
MethodDescription |
batteryvoltage |
Battery voltage |
loggervolts |
Voltage on logger battery |
radiovolts |
Voltage on radio battery |
As a counter-example, wind speed might be reported as instantaneous, average, and maximum (i.e. gust). In this case, their distinction would be expressed in the Variables table because the TimeSupport, TimeUnitsName, and/or DataType fields in the Variables table will differ.
If possible, however, try to minimize the number of variables by expressing measurement differences in the Methods table if the fields in the Variables table are consistent.
QUALITYCONTROLLEVELS
This metadata table is required and needs to be uploaded along with the other metadata tables, but it is already created and can be downloaded
QualityControlLevelCode |
Definition |
Explanation |
-9999 |
Unknown |
The quality control level is unknown |
0 |
Raw Data |
Raw and unprocessed data and data products that have not undergone quality control. Depending on the variable, data type, and data transmission system, raw data may be available within seconds or minutes after the measurements have been made. Examples include real time precipitation, streamflow and water quality measurements. |
1 |
Quality Controlled |
Quality controlled data that have passed quality assurance procedures such as routine estimation of timing and sensor calibration or visual inspection and removal of obvious errors. An example is USGS published streamflow records following parsing through USGS quality control procedures. |
2 |
Derived products |
Derived products that require scientific and technical interpretation and may include multiple-sensor data. An example is basin average precipitation derived from rain gages using an interpolation procedure. |
3 |
Interpreted products
|
Interpreted products that require researcher driven analysis and interpretation, model-based interpretation using other data and/or strong prior assumptions. An example is basin average precipitation derived from the combination of rain gages and radar return data. |
4 |
Knowledge products |
Knowledge products that require researcher driven scientific interpretation and multidisciplinary data integration and include model-based interpretation using other data and/or strong prior assumptions. An example is percentages of old or new water in a hydrograph inferred from an isotope analysis. |
DATAVALUES
This table will likely be the result of a provider-generated effort (software script) to convert from their own data format to the one required by CUAHSI. Each record of data is a single time-sensor data point.
Bold are required fields. CV=Controlled Vocabulary
Field |
Entry Type |
Example Entry |
DataValues |
Numeric |
24.46 |
ValueAccuracy |
Numeric |
|
LocalDateTime |
Date/Time |
7/23/2013 17:00 |
UTCOffset |
Numeric |
-4 |
DateTimeUTC |
Date/Time |
7/23/2013 21:00 |
SiteCode |
Text |
SUNAPEE |
VariableCode |
Text |
watertemperature |
OffsetValue |
Numeric |
|
OffsetTypeCode |
Numeric |
|
CensorCode |
CV-CensorCode |
nc |
QualifierCode |
Numeric |
|
MethodCode |
Text |
watertemp_2m |
SourceCode |
Text |
LSPA |
SampleCode |
Numeric |
|
DerivedFromID |
Numeric |
|
QualityControlLevelCode |
Numeric |
0 |
In the Lake Sunapee data, the buoy manager generated data files that include 30 distinct measurements at each time increment. Each of these 30 measurements became a separate row to fit the format of the DataValues table.
5. Complete the data registration pages
Contact Mark Gahler (gahler@wisc.edu) with issues pertaining to these instructions
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer