Continuous Monitoring Data From Herring River Wetlands, Cape Cod, Massachusetts, 2015 to January 2020

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Continuous Monitoring Data From Herring River Wetlands, Cape Cod, Massachusetts, 2015 to January 2020
Abstract:
The Herring River estuary (Wellfleet, Cape Cod, Massachusetts) has been tidally restricted for over a century by a dike constructed near the mouth of the river. Behind the dike, the tidal restriction has caused the conversion of salt marsh wetlands to various other ecosystems including impounded freshwater marshes, flooded shrub land, drained forested upland, and wetlands dominated by Phragmites australis. This estuary is now managed by the National Park Service, which has plans to replace the dike and restore tidal flow to the estuary. To assist National Park Service land managers with restoration planning, study collaborators have been investigating differences in soil properties, carbon accumulation, and greenhouse gas fluxes across differing ecosystems within the Herring River Estuary. The U.S. Geological Survey collected continuous monitoring data (including water level, soil temperature, air temperature, and meteorological parameters). These datasets can help evaluate key ecosystem drivers to make predictions about potential changes as restoration commences.
Supplemental_Information:
For more information, see the following field activities: https://cmgds.marine.usgs.gov/fan_info.php?fan=2015-042-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2015-044-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2015-063-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2016-016-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-039-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-055-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-018-FA
  1. How might this data set be cited?
    Jennifer A. O'Keefe Suttles, Gonneea, Meagan E., Brosnahan, Sandra M., Mann, Adrian G., Brooks, Thomas W., Kroeger, Kevin D., Medeiros, Kelly, Smith, Timothy P., Wang, Faming, and Tang, Jim, 20200625, Continuous Monitoring Data From Herring River Wetlands, Cape Cod, Massachusetts, 2015 to January 2020: data release DOI:10.5066/P9R4SRTR, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: O’Keefe Suttles, J.A., Gonneea, M.E., Brosnahan, S.M., Mann, A.G., Brooks, T.W., Kroeger, K.D., Medeiros, K., Smith, T.P., Wang, F., and Tang, J., 2020, Continuous monitoring data from Herring River wetlands, Cape Cod, Massachusetts, 2015 to January 2020: U.S. Geological Survey data release, https://doi.org/10.5066/P9R4SRTR
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.0567088
    East_Bounding_Coordinate: -70.0509867
    North_Bounding_Coordinate: 41.9603891
    South_Bounding_Coordinate: 41.9374193
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5eab1f3582cefae35a225504?name=tidally_restricted_wetland_HerringRiverEstuary.jpg (JPEG)
    Photograph of a tidally restricted wetland in the Herring River Estuary, Cape Cod, MA (Photo Credit: Daniel Roberts).
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 2015
    Ending_Date: 2020
    Currentness_Reference:
    Ground Condition. Check individual sensor data for exact time period of data collection. All sensors were not collecting data at all locations for the entire study period.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Text files (*.TXT).
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      Indirect_Spatial_Reference: Geographic Names Information System (GNIS) placenames
      This is a Point data set.
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 1.0E-5. Longitudes are given to the nearest 1.0E-5. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: North American Vertical Datum of 1988
      Altitude_Resolution: 0.01
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method: Attribute values
  7. How does the data set describe geographic features?
    HR_Well_2015_Jan2020
    Continuous monitoring of well water level, temperature, and salinity in tidally restricted wetlands within the Herring River Estuary. Raw pressure data, used to calculate water level, is reported as either absolute pressure or atmospherically corrected pressure (as exported from manufacturers' software). The TEXT file also includes latitude and longitude of sensor placement. The dataset includes 397,577 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Herring RiverA data point collected from a tidally restricted wetland within the Herring River Estuary.
    treatment
    A text identifier indicating the vegetation type that now dominates the tidally restricted study site. (Source: Producer-defined)
    ValueDefinition
    Dry ForestData point collected from the Herring River Estuary that is now "dry" or drained and forested (dominated by upland tree species).
    Typha WetlandData point collected from the Herring River Estuary that is now dominated by Typha (cattail).
    Wet ShrubData point collected from the Herring River Estuary that is now dominated by shrubs tolerant of periodic standing water.
    Phragmites WetlandData point collected from the Herring River Estuary that is now dominated by Phragmites.
    latitude
    Latitude decimal degrees north, NAD83 (Source: Producer-defined)
    Range of values
    Minimum:41.9374193
    Maximum:41.9603891
    Units:decimal degrees
    longitude
    Longitude decimal degrees west, NAD83. The negative value indicates a location in the western hemisphere. (Source: Producer defined)
    Range of values
    Minimum:-70.0567088
    Maximum:-70.0509867
    Units:decimal degrees
    date_time
    A text string identifier for the date and time the data point was logged in the format yyyy-mm-dd hh:mm:ss (UTC). (Source: Producer-defined)
    Range of values
    Minimum:2015-09-29 18:00:00
    Maximum:2020-01-08 18:00:00
    Units:yyyy-mm-dd hh:mm:ss (UTC)
    temp_well
    A numeric data value of logged well water temperature. Manufacturer's specifications for temperature accuracy and resolution of Onset HOBO U20 water level loggers are +/- 0.44 degrees Celsius from 0 to 50 degrees Celsius and 0.10 degrees Celsius at 25 degrees Celsius, respectively. Manufacturer's specifications for temperature accuracy and resolution of In-Situ AquaTroll 200 water level loggers are +/- 0.1 degrees Celsius and 0.01 degrees Celsius or better, respectively. (Source: Producer-defined)
    Range of values
    Minimum:2.296
    Maximum:19.139
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor deployment dates. The attribute "temp_well" has 4,906 records with the "NaN" domain.
    sal_well
    A numeric data value of logged well water salinity. Salinity is converted in the manufacturer's software from measured conductivity which has a manufacturer's specification for accuracy of +/- 0.5 percent of the reading + 1 microsiemens per centimeter when reading less than 80,000 microsiemens per centimeter and a resolution of 0.1 microsiemens per centimeter. (Source: Producer-defined)
    Range of values
    Minimum:0.221
    Maximum:6.420
    Units:practical salinity units (PSU)
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset or a placeholder for a water level logger that did not report salinity. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor deployment dates. The attribute "sal_well" has 191,147 records with the "NaN" domain.
    press_abs
    A numeric data value of absolute pressure logged by non-vented pressure loggers. Data reported for non-vented pressure loggers manufactured by In-Situ do not include absolute pressure because the data generated by the manufacturer's barometric pressure compensation software only reports the corrected pressure and atmospheric pressure. However, end-users may calculate absolute pressure by adding the corrected pressure and atmospheric pressure. Accuracy and resolution of absolute pressure loggers are stated in domain definitions for the attribute "sensor_WL". (Source: Producer-defined)
    Range of values
    Minimum:14.6024
    Maximum:16.7056
    Units:pounds per square inch (PSI)
    The value "NaN" is defined as a textual representation of either an erroneous measurement that was excluded from the dataset or a placeholder for water level sensors that did not report absolute pressure. Data reported for non-vented pressure loggers manufactured by In-Situ do not include absolute pressure because the data generated by the manufacturer's barometric pressure compensation software only reports the corrected pressure and atmospheric pressure. However, end-users may calculate absolute pressure by adding the corrected pressure and atmospheric pressure. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor deployment dates. The attribute "press_abs" has 211,336 records with the "NaN" domain.
    press_atm
    A numeric data value of atmospheric pressure logged by the barometer. Accuracy and resolution for atmospheric pressure loggers are stated in domain definitions for the attribute "sensor_baro". (Source: Producer-defined)
    Range of values
    Minimum:14.0700
    Maximum:15.4774
    Units:pounds per square inch (PSI)
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor start dates. The attribute "press_atm" has 1,032 records with the "NaN" domain.
    press_corr
    A numeric data value of corrected pressure. For non-vented pressure loggers corrected pressure is calculated (in the manufacturers' software) as the difference between the absolute pressure (press_abs) logged by the water level sensor and the atmospheric pressure (press_atm) logged by the barometer. Accuracy and resolution for absolute pressure loggers are stated in domain definitions for the attribute "sensor_WL". (Source: Producer-defined)
    Range of values
    Minimum:0.407
    Maximum:1.671
    Units:pounds per square inch (PSI)
    The value "NaN" is defined as a textual representation of either an erroneous measurement that was excluded from the dataset or a placeholder for water level sensors that did not report corrected pressure. Data reported for non-vented pressure loggers manufactured by Onset do not include corrected pressure because the data generated by the manufacturer's barometric pressure compensation software only reports the absolute pressure and atmospheric pressure. However, end-users may calculate corrected pressure by subtracting the atmospheric pressure from the absolute pressure. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor deployment dates. The attribute "press_corr" has 191,147 records with the "NaN" domain.
    dbs
    A numeric data value of water depth below land surface ("dbs") calculated from field measured sensor deployment depth and pressure logged by the water level sensor. Data reported were collected from wells installed in wetlands or drained wetlands; the land surface upon which the well was installed may have been periodically inundated with surface water. "Positive" dbs were periods of land surface inundation by surface water (water over the land surface); "negative" dbs were periods when the land surface was not inundated with surface water and water level was below the land surface. (Source: Producer-defined)
    Range of values
    Minimum:-1.012
    Maximum:0.287
    Units:meters
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset; data may have been excluded if water levels dropped below the sensor deployment depth or when the sensor was removed from the well for maintenance. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor start dates. The attribute "dbs" has 4,906 records with the "NaN" domain.
    WL_NAVD88
    A numeric data value of water elevation calculated from field measured land surface elevation, sensor deployment depth, and pressure logged by the water level sensor. Calculations for this attribute are described in the process steps. (Source: Producer-defined)
    Range of values
    Minimum:-0.210
    Maximum:0.660
    Units:meters
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset; data may have been excluded if water levels dropped below the sensor deployment depth or when the sensor was removed from the well for maintenance. The entity, "HR_WellSensorDeploymentHeights_2015_Jan2020", may be referenced for specific sensor start dates. The attribute "WL_NAVD88" has 4,906 records with the "NaN" domain.
    sensor_WL
    A text identifier for the manufacturer make and model information of the water level sensor used to collect the given data point. (Source: Manufacturer-defined)
    ValueDefinition
    In-Situ Aqua TROLL 200-30 psiaA data point collected using a water level logger manufactured by In-Situ, model type Aqua TROLL 200 (30 psi maximum pressure; "a" indicates an absolute pressure sensor that is not vented to the atmosphere). The manufacturer's accuracy specification for this sensor is +/- 0.05 percent full-scale from -5 to 50 degrees Celsius, long-term stability is less than 0.1 percent full-scale; the manufacturer's specification for resolution is 0.005 percent full-scale or better.
    Onset HOBO U20-001-02A data point collected using a water level logger manufactured by Onset, model type HOBO U20 (300 psi maximum pressure; absolute, non-vented pressure sensor). The manufacturer's accuracy specification for this sensor is +/- 0.3 percent full-scale and the resolution specification is less than 0.006 psi.
    Onset HOBO U20-001-01A data point collected using a water level logger manufactured by Onset, model type HOBO U20 (30 psi maximum pressure; absolute, non-vented pressure sensor). The manufacturer's accuracy specification for this sensor is +/- 0.3 percent full-scale and the resolution specification is less than 0.003 psi.
    WL_sn
    WL_sn (Water Level_Serial Number) is a numeric identifier used to uniquely tag each water level sensor. (Source: Manufacturer-defined) The serial number of each water level logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    sensor_baro
    A text identifier for the manufacturer make and model information of the barometer used to atmospherically correct absolute pressure data collected by non-vented water level sensors. (Source: Manufacturer-defined)
    ValueDefinition
    Onset HOBO U20-001-01An atmospheric pressure (press_atm) data point collected using a water level logger manufactured by Onset, model type HOBO U20 (30 psi maximum pressure; absolute, non-vented pressure sensor). The manufacturer's accuracy specification for this sensor is +/- 0.3 percent full-scale and the resolution specification is less than 0.003 psi.
    In-Situ Rugged BaroTROLLAn atmospheric pressure (press_atm) data point collected using a barometer manufactured by In-Situ, model type Rugged BaroTROLL. The manufacturer's accuracy specification for this sensor is +/- 0.05 percent full-scale from -5 to 50 degrees Celsius; and the manufacturer's specification for resolution is 0.01 percent full-scale or better.
    In-Situ BaroTROLL 500An atmospheric pressure (press_atm) data point collected using a barometer manufactured by In-Situ, model type BaroTROLL 500. The manufacturer's accuracy specification for this sensor is +/- 0.05 percent full-scale from -5 to 50 degrees Celsius, long-term stability is specified as less than 0.1 percent full-scale; the manufacturer's specification for resolution is 0.005 percent full-scale or better.
    baro_sn
    A numeric identifier, the barometer serial number is used to uniquely tag each barometer. (Source: Manufacturer-defined) The serial number of each barometer is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    HR_TEMP_2016_Jan2020
    Continuous monitoring of soil and air temperature in tidally restricted wetlands within the Herring River Estuary. The TEXT file also includes latitude and longitude of sensor placement. The dataset contains 224,850 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Herring RiverData point collected from a tidally restricted wetland within the Herring River Estuary.
    treatment
    A text identifier indicating the vegetation type that now dominates the tidally restricted study site. (Source: Producer-defined)
    ValueDefinition
    Dry ForestData point collected from the Herring River Estuary that is now "dry" or drained and forested (dominated by upland tree species).
    Typha WetlandData point collected from a site in the Herring River Estuary that is now dominated by Typha (cattail).
    Phragmites WetlandData point collected from a site in the Herring River Estuary that is now dominated by Phragmites.
    Wet ForestData point collected from a site in the Herring River Estuary that is now forested with periods of standing water.
    latitude
    Latitude decimal degrees north, NAD83. Note that the position of the Wet Forest temperature logger was determined using a hand-held Garmin GPS; all other sensor positions were determined using RTK GPS. (Source: Producer-defined)
    Range of values
    Minimum:41.9374278
    Maximum:41.960450
    Units:decimal degrees
    longitude
    Longitude decimal degrees west, NAD83. The negative value indicates a location in the western hemisphere. Note that the position of the Wet Forest temperature logger was determined using a hand-held Garmin GPS; all other sensor positions were determined using RTK GPS. (Source: Producer-defined)
    Range of values
    Minimum:-70.0567088
    Maximum:-70.0554317
    Units:decimal degrees
    date_time
    A text string identifier for the date and time the data point was logged in the format yyyy-mm-dd hh:mm:ss (UTC). (Source: Producer-defined)
    Range of values
    Minimum:2016-05-16 15:00
    Maximum:2020-01-08 18:00
    Units:yyyy-mm-dd hh:mm:ss (UTC)
    temp_air
    A numeric data value of logged air temperature. (Source: Producer-defined)
    Range of values
    Minimum:-14.746
    Maximum:43.284
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the data set. The attribute "temp_air" has 10,661 records with the "NaN" domain.
    temp_soil
    A numeric data value of logged soil temperature; sensor installed 10 cm below land surface. (Source: Producer-defined)
    Range of values
    Minimum:-3.035
    Maximum:22.681
    Units:degrees Celsius
    sensor
    A text identifier for the manufacturer make and model information of the temperature sensor logger used to collect the given data point. (Source: Manufacturer-defined)
    ValueDefinition
    Onset HOBO U23 ProV2A data point collected using a dual channel temperature sensor logger manufactured by Onset, model type HOBO U23 Pro v2. The manufacturer's specification of accuracy is +/- 0.21 degrees Celsius from 0 degrees Celsius to 50 degrees Celsius; the manufacturer's specification for resolution is 0.02 degrees Celsius at 25 degrees Celsius.
    sensor_sn
    Temperature Sensor Serial Number (sensor_sn) is a numeric identifier used to uniquely tag each temperature sensor logger. (Source: Manufacturer-defined) The serial number of each temperature sensor logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    HR_MET_2016_Jan2020
    Continuous monitoring of photosynthetically active radiation (PAR) and other meteorological parameters in tidally restricted wetlands within the Herring River Estuary. The dataset also includes latitude and longitude of sensor placement. The dataset contains 126,361 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Herring RiverData point collected from a tidally restricted wetland within the Herring River Estuary.
    treatment
    A text identifier indicating the vegetation type that now dominates the tidally restricted study site. (Source: Producer-defined)
    ValueDefinition
    Typha WetlandData point collected from the Herring River Estuary that is now dominated by Typha (cattail).
    Phragmites WetlandData point collected from the Herring River Estuary that is now dominated by Phragmites.
    latitude
    Latitude decimal degrees north, NAD83 (Source: Producer-defined)
    Range of values
    Minimum:41.9380529
    Maximum:41.9602485
    Units:decimal degrees
    longitude
    Longitude decimal degrees west, NAD83. The negative value indicates a location in the western hemisphere. (Source: Producer-defined)
    Range of values
    Minimum:-70.0561075
    Maximum:-70.0553112
    Units:decimal degrees
    date_time
    A text string identifier for the date and time the data point was logged in the format yyyy-mm-dd hh:mm:ss (UTC). (Source: Producer-defined)
    Range of values
    Minimum:2016-05-16 14:30:01
    Maximum:2020-01-08 18:45:02
    Units:yyyy-mm-dd hh:mm:ss (UTC)
    par
    A numeric data value of logged photosynthetically active radiation; PAR logger was deployed above the height of vegetative growth near to the sensor (at least 3 meters above the land surface). This sensor measures light intensity over wavelengths from 400 to 700 nanometers. Although data is logged over the entire day, it must be noted that values in darkness are logged as 1.2 micromoles per meter squared per second; accuracy of the PAR sensor +/- 5 micromoles per meter squared per second and resolution of the PAR sensor is 2.5 micromoles per meter squared per second. (Source: Producer-defined)
    Range of values
    Minimum:1.2
    Maximum:2553.7
    Units:micromol per meter squared per second
    The value "NaN" is defined as a textual representation of a time point that does not have an associated PAR measurement. The time point may have had an erroneous PAR measurement that was excluded from the dataset or the PAR sensor may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "par" has 6,455 records with the "NaN" domain.
    rain
    A numeric data value of rain accumulation over the logger interval (15 minutes). Tthe rain gauge was deployed on a mast with other meteorological sensors; it was positioned about 2 meters above the land surface. Accuracy of the rain gauge +/- 1 percent and resolution is 0.2 millimeters. (Source: Producer-defined)
    Range of values
    Minimum:0
    Maximum:15.6
    Units:millimeters
    The value "NaN" is defined as a textual representation of a time point that does not have an associated rain measurement. The time point may have had an erroneous rain measurement that was excluded from the dataset or the rain gauge sensor may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "rain" has 37,342 records with the "NaN" domain.
    temp_air
    A numeric data value of logged air temperature; the air temperature sensor was enclosed within a solar radiation shield and deployed on a mast with other meteorological sensors. Accuracy of the temperature sensor is 0.21 degrees Celsius and resolution is 0.02 degrees Celsius. (Source: Manufacturer-defined)
    Range of values
    Minimum:-15.064
    Maximum:35.609
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of a time point that does not have an associated air temperature measurement. The time point may have had an erroneous temperature measurement that was excluded from the dataset or the air temperature sensor may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "temp_air" has 37,344 records with the "NaN" domain.
    RH
    A numeric data value of logged relative humidity; the RH sensor was enclosed within a solar radiation shield and deployed on a mast with other meteorological sensors. Typical accuracy of the RH sensor is +/-2.5 percent and resolution is 0.1 percent RH. (Source: Manufacturer-defined)
    Range of values
    Minimum:21.8
    Maximum:100
    Units:percent
    The value "NaN" is defined as a textual representation of a time point that does not have an associated relative humidity measurement. The time point may have had an erroneous RH that was excluded from the dataset or the RH sensor may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "RH" has 37,344 records with the "NaN" domain.
    wind_speed
    A numeric data value of wind speed logged by the anemometer (15 minute logging interval). Cup revolutions are accumulated every three seconds for the duration of the logging interval; the logged wind speed is the average speed for the entire logging interval. The anemometer was deployed on a mast with other meteorological sensors. Typical accuracy of the wind speed sensor is +/- 1.1 meters per second or +/- 5 percent of the reading (whichever is greater) and resolution is 0.5 meters per second. (Source: Manufacturer-defined)
    Range of values
    Minimum:0
    Maximum:8.02
    Units:meters per second
    The value "NaN" is defined as a textual representation of a time point that does not have an associated wind speed measurement. The time point may have had an erroneous wind speed that was excluded from the dataset or the anemometer may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "wind_speed has 40,732 records with the "NaN" domain.
    gust_speed
    A numeric data value of wind gust speed logged by the anemometer (15 minute logging interval). Cup revolutions are accumulated every three seconds for the duration of the logging interval; gust speed is the highest three second wind recorded during the logging interval. The anemometer was deployed on a mast with other meteorological sensors. Typical accuracy of the wind speed sensor is +/- 1.1 meters per second or +/- 5 percent of the reading (whichever is greater) and resolution is 0.5 meters per second. (Source: Manufacturer-defined)
    Range of values
    Minimum:0
    Maximum:18.03
    Units:meters per second
    The value "NaN" is defined as a textual representation of a time point that does not have an associated wind gust speed measurement. The time point may have had an erroneous wind gust speed that was excluded from the dataset or the anemometer may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "gust_speed" has 40,732 records with the "NaN" domain.
    wind_dir
    A numeric data value of wind direction logged by the anemometer. The anemometer was deployed on a mast with other meteorological sensors; the sensor was oriented zero degrees to true north as described in the manual. Typical accuracy of the wind direction sensor is +/- 7 degrees and resolution is 1 degree. (Source: Manufacturer-defined)
    Range of values
    Minimum:0
    Maximum:355.2
    Units:degrees
    The value "NaN" is defined as a textual representation of a time point that does not have an associated wind direction measurement. The time point may have had an erroneous wind direction that was excluded from the dataset or the anemometer may not have been deployed during the time period of record. The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific sensor deployment dates. The attribute "wind_dir" has 40,732 records with the "NaN" domain.
    HR_WellSensorDeploymentHeights_2015_Jan2020
    Summary of land surface elevation, deployment length, and well height measurements for water level loggers deployed at Herring River sites between 2015 and 2019; measurements used in final calculation of water elevation and water depth below land surface. There are 20 records in the table. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Herring RiverData point collected from a tidally restricted wetland within the Herring River Estuary.
    treatment
    A text identifier indicating the vegetation type that now dominates the tidally restricted study site. (Source: Producer-defined)
    ValueDefinition
    Dry ForestData point collected from the Herring River Estuary that is now "dry" or drained and forested (dominated by upland tree species).
    Typha WetlandData point collected from the Herring River Estuary that is now dominated by Typha (cattail).
    Wet ShrubData point collected from the Herring River Estuary that is now dominated by shrubs tolerant of periodic standing water.
    Phragmites WetlandData point collected from the Herring River Estuary that is now dominated by Phragmites.
    well_type
    A text identifier indicating the type of well installation used to deploy a water level logger. (Source: Producer-defined)
    ValueDefinition
    deepA well qualified as "deep" was installed with the bottom of the screened section greater than 50 cm below the land surface.
    shallowA well qualified as "shallow" was installed with the bottom of the screened section less than 50 cm below the land surface.
    start_date
    A text string identifier for the date the deployment started (in the format yyyy-mm-dd). (Source: Producer-defined)
    Range of values
    Minimum:2015-09-29
    Maximum:2019-04-29
    Units:date format yyyy-mm-dd
    end_date
    A text string identifier for the date the deployment ended (in the format yyyy-mm-dd). (Source: Producer-defined)
    Range of values
    Minimum:2016-01-04
    Maximum:2020-01-08
    Units:date format yyyy-mm-dd
    latitude
    Latitude decimal degrees north, NAD83. (Source: Producer-defined)
    Range of values
    Minimum:41.9374193
    Maximum:41.9603891
    Units:decimal degrees
    longitude
    Longitude decimal degrees west, NAD83. The negative value indicates a location in the western hemisphere. (Source: Producer-defined)
    Range of values
    Minimum:-70.0567088
    Maximum:-70.0509867
    Units:decimal degrees
    land_surface_elevation
    A manual measurement of the land surface elevation (NAVD88) at a particular location (coordinates also measured and reported, measurement made using the RTK GPS). (Source: Producer-defined)
    Range of values
    Minimum:0.0763
    Maximum:0.8025
    Units:meters
    height_above_land_surface
    A manual measurement (using a measuring stick) of the height above land surface of the well used for water level logger deployment. (Source: Producer-defined)
    Range of values
    Minimum:0.285
    Maximum:1.48
    Units:meters
    deployment_length
    A manual measurement in meters (using a measuring stick) of the length of the well logger deployment cable (cable plus sensor). (Source: Manufacturer-defined)
    Range of values
    Minimum:1.326
    Maximum:2.200
    Units:meters
    sensor_depth_below_land_surface
    Calculated deployment depth of the water level logger below the land surface (equal to the deployment_length minus the height_above_land_surface). (Source: Producer-defined)
    Range of values
    Minimum:0.350
    Maximum:1.275
    Units:meters
    sensor_WL
    A text identifier for the manufacturer make and model information of the water level sensor used to collect the given data point. (Source: Manufacturer-defined)
    ValueDefinition
    In-Situ Aqua TROLL 200-30 psiaData point collected using a water level logger manufactured by In-Situ, model type Aqua TROLL 200 (30 psi maximum pressure; "a" indicates an absolute pressure sensor that is not vented to the atmosphere).
    Onset HOBO U20-001-02Data point collected using a water level logger manufactured by Onset, model type HOBO U20 (300 psi maximum pressure; absolute, non-vented pressure sensor).
    Onset HOBO U20-001-01Data point collected using a water level logger manufactured by Onset, model type HOBO U20 (30 psi maximum pressure; absolute, non-vented pressure sensor).
    WL_sn
    A numeric identifier of the serial number of the water level logger; it is created by the manufacturer to uniquely tag each water level sensor. (Source: Manufacturer-defined) The serial number of each water level logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    HR_MET_deployments_2016_Jan2020
    Summary of deployment dates and serial numbers of meteorological sensors deployed at Herring River sites between 2016 and January 2020. There are 12 records in the table. (Source: Producer defined)
    start_date
    A text string identifier for the date the deployment started (in the format yyyy-mm-dd). Meteorological sensors were continuously deployed until sensor failure as indicated by the start date of the replacement sensor. (Source: Producer defined)
    Range of values
    Minimum:2016-05-13
    Maximum:2019-10-30
    Units:date format yyyy-mm-dd
    lgr_sn
    A numeric identifier of the serial number of the Onset HOBO microstation H21-002 used to log data from all of the deployed meteorological sensors; it is created by the manufacturer to uniquely tag each sensor. Note that the same microstation data logger was used for all reported data. (Source: Manufacturer defined) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    par_sn
    A numeric identifier of the serial number for the deployed PAR sensor (Onset HOBO Photosynthetically Active Radiation Smart Sensor S-LIA-M003); it is created by the manufacturer to uniquely tag each sensor. (Source: Manufacturer designed) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment.
    rain_sn
    A numeric identifier of the serial number for the deployed rain gauge sensor (Onset HOBO Rain Gauge Smart Sensor S-Rgx-M002); it is created by the manufacturer to uniquely tag each sensor. Note that for the same rain gauge/sensor was used for all reported data. (Source: Manufacturer defined) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment. The value "NaN" is defined as a textual representation of a time period that does not have an associated rain measurement. The rain gauge sensor was not deployed at Herring River until 2017-06-09.
    temp_sn
    A numeric identifier of the serial number for the deployed temperature sensor (Onset HOBO Temperature/RH Smart Sensor S-THB-M00x); it is created by the manufacturer to uniquely tag each sensor. Note that for the same temperature sensor was used for all reported data. (Source: Manufacturer defined) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment. The value "NaN" is defined as a textual representation of a time period that does not have an associated temperature measurement. The air temperature sensor, on the meteorological station, was not deployed at Herring River until 2017-06-09.
    RH_sn
    A numeric identifier of the serial number for the deployed relative humidity sensor (Onset HOBO Temperature/RH Smart Sensor S-THB-M00x); it is created by the manufacturer to uniquely tag each sensor. Note that for the same sensor was used for all reported data. (Source: Manufacturer defined) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment. The value "NaN" is defined as a textual representation of a time period that does not have an associated relative humidity measurement. The RH/temperature sensor was not deployed at Herring River until 2017-06-09.
    wind_sn
    A numeric identifier of the serial number for the deployed anemometer (Onset HOBO Davis Wind Speed and Direction Smart Sensor S-WCF-M003); it is created by the manufacturer to uniquely tag each sensor. (Source: Manufacturer defined) The serial number of each sensor or logger is a numeric identifier, created by the manufacturer, to uniquely tag each piece of equipment. The value "NaN" is defined as a textual representation of a time period that does not have an associated measurement from an anemometer. The anemometer (wind speed/direction sensor) was not deployed at Herring River until 2017-06-09.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Jennifer A. O'Keefe Suttles
    • Meagan E. Gonneea
    • Sandra M. Brosnahan
    • Adrian G. Mann
    • Thomas W. Brooks
    • Kevin D. Kroeger
    • Kelly Medeiros
    • Timothy P. Smith
    • Faming Wang
    • Jim Tang
  2. Who also contributed to the data set?
    Barry Irwin (USGS Geophysicist) and Jonathan Borden (USGS Electronics Technician) helped with RTK GPS data collection at these study sites.
  3. To whom should users address questions about the data?
    Jennifer A. O'Keefe Suttles
    Northeast Region: WOODS HOLE COASTAL & MARINE SCIENCE CENTER
    Chemist
    384 Woods Hole Road
    Woods Hole, MA
    United States

    508-548-8700 x2385 (voice)
    jokeefesuttles@usgs.gov

Why was the data set created?

Environmental parameters affecting plant productivity, such as water level, salinity, soil temperature, and photosynthetically active radiation (and others) included in this dataset, are key components of salt marsh carbon cycling, carbon storage, and its ability to maintain elevation. Data were collected to (1) facilitate National Park Service restoration planning and (2) provide background data to evaluate potential differences in water level and land-surface elevation between sites.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 2019 (process 1 of 6)
    PVC wells were installed by USGS at four of the five sites; the Dry Forest well was previously installed by collaborators at the National Park Service (NPS). USGS wells consisted of two pre-manufactured sections of 1 inch (2.54 cm) diameter well casing that were threaded together: a length of slotted screened casing (2.5 feet, ~0.762 meters; slot size 0.010 inch; ~ 0.3 mm) and a solid well casing that stuck above the sediment surface. USGS wells were installed by pushing the well section into the sediment by hand or lightly tapping the top of the well with a mallet. The tip of the slotted screened well section was pushed about 1 meter below the land surface for deep wells and about 0.3 meters below land surface for shallow wells; the threaded portion (connecting the slotted length with the solid length) was below the sediment surface. Enough well casing remained above the sediment surface to ensure the groundwater well was not over-topped with surface water (0.3 meter - 1 meter). A vent hole was drilled near the top of the solid well casing. An eye-bolt was drilled into the inward facing edge of the threaded well cap; water level loggers were hung by aircraft cable threaded through the eye-bolt and through the logger cap and secured on both ends using crimped stainless-steel oval sleeves. Exact well heights and sensor deployment lengths are summarized in a separate entity and attribute section (HR_WellSensorDeploymentHeights_2015_2019.txt).
    The NPS Dry Forest well was a 1.5 inch diameter PVC well (0.010 inch slotted screen) loosely capped with a PVC cap socket. The water level logger hung using the same aircraft cable used in the other wells; however it was not attached to the cap, it hung from a bolt between holes drilled approximately 4 cm from the top of the well casing.
    We categorize the Typha site well installed in 2015 as "deep". In 2016, we attempted to collect water level data from a shallower well (0.3 meters below land surface) at the Typha site in order to log salinity closer to the root zone. However, this well suffered from low water level during a drought year in addition to a series of data logger problems. Therefore, water level data is unavailable from the Typha site for much of 2016 until we moved the logger back to the deeper well.
    In 2017, we installed the Wet Shrub site well, the Phragmites “deep” well and the Phragmites “shallow” well. To prevent possible disturbance from other on site research activities, the Phargmites wells were moved, in 2019, slightly further away from the walking path. The process date represents the latest process date.
    Date: 2020 (process 2 of 6)
    Additional sensors were co-deployed at the same sites as the groundwater level sensors including: dual channel (soil and air) temperature loggers, a barometer, and a photosynthetically active radiation (PAR) sensor. In 2017, the PAR sensor was moved from the Typha site to the Phragmites site and additional meteorological sensors were deployed on the same mast with the PAR. The PAR sensor and anemometer were deployed on a mast above the height of the nearest vegetation in a location that would not be shaded or impacted by vegetation or other structures (at least 3 meters above the land surface). The other meteorological sensors (rain gauge, air temperature/relative humidity) were deployed on the same mast about 2 meters above the land surface. The barometer was deployed in air (approximately 1.5 meters above the land surface) near to the PAR sensor. Note that, within the Phragmites site, the meteorological station was deployed on an exposed knoll with less vegetation density and less standing water than is otherwise characteristic of the site. This was done to to capture weather data above the height of the dense Phragmites canopy. The dual channel soil/air temperature logger were deployed with the water level wells within the Phgramites vegetation.
    Soil temperature sensors were attached to a wooden stick and pushed by hand so that the bottom of the temperature sensor was 10 cm below the land surface. The air temperature sensor was attached near to the top of the groundwater well (approximately 1 meter above the land surface; for exact well heights, see included text file, HR_WellSensorDeploymentHeights_2015_2019.txt). Note that draft shields were not consistently used for air temperature sensors until 2017. The Wet Forest air temperature logger was attached to a well; however water level data was not collected at this site. Soil/air temperature data is not available for the Wet Shrub site.
    Data was logged in 15 minute intervals for all parameters. Specific deployments may have been started immediately (not on a timed interval). Additionally, the Onset HOBO Micro Station, used to log data from the meteorological sensors, has a one-time 2 second delay upon starting up a new sequence that cannot be avoided. Deployments took place between 2016 and January 2020, with the process date representing the latest process date.
    Date: 2020 (process 3 of 6)
    Well data loggers were initially deployed at two sites in September 2015. In subsequent years, additional sites, wells, and sensors were added to the study. In some years, sensors were removed from the field over winter and redeployed in spring. Data loggers were periodically downloaded in the field using instrument manufacturers' software (HOBOPro, WinSitu); data were inspected for general accuracy. Further data processing and calculation steps are described in the next process steps. Note that temperature loggers were not deployed at all sites for the entire study period. Dates of site visits are listed as follows, Typha: 9/29/2015, 10/7/2015, 11/13/2015, 1/4/2016, 5/16/2016, 6/17/2016, 7/6/2016, 7/14/2016, 7/22/2016, 8/17/2016, 8/30/2016, 9/16/2016, 10/6/2016, 10/28/2016, 11/10/2016, 4/27/2017, 5/19/2017, 6/16/2017, 6/22/2017, 6/28/2017, 7/11/2017, 7/19/2017, 8/28/2017, 10/3/2017, 1/3/2018, 4/24/2018, 5/24/2018, 7/11/2018, 9/21/2018, 12/19/2018, 4/29/2019, 5/14/2019, 7/17/2019, 9/26/2019, 1/8/2020. Dry Forest: 9/29/2015, 10/7/2015, 11/13/2015, 1/4/2016, 6/17/2016, 7/14/2016, 8/30/2016, 10/28/2016, 11/10/2016, 4/27/2017, 6/16/2017, 7/11/2017, 10/3/2017, 1/3/2018, 4/24/2018, 5/24/2018, 7/11/2018, 9/21/2018, 12/19/2018, 4/29/2019, 5/14/2019, 7/17/2019, 9/26/2019, 1/8/2020. Wet Forest: 7/11/2017, 10/3/17, 1/3/18, 4/24/18. Wet Shrub: 6/9/2017, 6/22/2017, 7/11/2017, 7/19/2017, 8/22/17, 9/27/17, 10/3/17, 1/3/2018, 5/24/2018, 7/11/2018, 9/21/2018, 12/19/2018, 4/29/2019, 5/14/2019, 7/17/2019, 9/26/2019, 1/8/2020. Phragmites: 6/9/2017, 6/16/2017, 6/28/2017, 7/11/2017, 7/19/2017, 8/22/17, 9/27/2017, 10/3/2017, 10/27/17, 1/3/2018, 5/24/2018, 7/11/2018, 9/21/2018, 12/19/2018, 4/29/2019, 5/14/2019, 7/17/2019, 9/26/2019, 1/8/2020.
    The process date represents the latest process date.
    Date: 2020 (process 4 of 6)
    Pressure data from non-vented water level sensors were barometrically corrected in manufacturers’ software (HOBOPro or WinSitu BaroMerge); corrected pressure was converted to sensor depth assuming a brackish water density (HOBOPro: 1.010 grams per cubic centimeter; WinSitu: 1.012 grams per cubic centimeter). Barometric pressure and density corrections were processed throughout the deployment period and checked while finalizing the data report. Raw pressure and barometric pressure are reported in this data release.
    Data from all continuous monitoring sensors were exported from manufacturers' software as a .csv file and compiled using MATLAB. Water elevation calculations were performed in MATLAB as described in the following process steps. Data resulting from erroneous measurements (malfunctioning sensors or insufficient water within a well) were excluded from the final dataset. Data were processed throughout the deployment period and checked while finalizing the data report; the process date represents the latest date of data processing.
    Date: 2020 (process 5 of 6)
    Field measured deployment heights for specific time periods are summarized in a txt file (tab-delimited, filename: HR_WellSensorDeploymentHeight_2015_2019.txt) included with this data release. These deployment heights were used to convert sensor depth (calculated from pressure in the manufacturer's software; described in previous process step) to water depth below land surface (dbs) and water elevation (WL_NAVD88). Calculations were processed throughout the deployment period in MATLAB. Positive dbs indicates water above the land surface; negative dbs indicates water below the land surface. The following parameters are used for these two calculations (units for all measurements are in meters): a: depth of sensor as calculated in manufacturer's software (see previous process step for description of measured pressure data and assumptions of density constants) b: land surface elevation (in the NAVD88 datum) at deployment location measured by RTK (land_surface_elevation; positive above (elevation) and negative below the datum) c: deployment well height above land surface measured periodically in the field using a meter stick (height_above_land_surface; always positive) d: total length of the deployment cable and water level sensor measured in the field using a meter stick (deployment_length; always positive)
    Well water elevation is calculated as: WL_NAVD88 = a +b+c-d
    Well water depth below land surface is calculated as: dbs = a+c-d
    Calculations were processed throughout the deployment period; the process date represents the latest date of data processing.
    Date: 07-Aug-2020 (process 6 of 6)
    Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
  3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    No formal attribute accuracy tests were conducted for the photosynthetically active radiation (PAR) sensors or other sensors included with the meteorological station (anemometer, rain gauge, air temperature, relative humidity). All other continuous monitoring sensors were bench tested for accuracy in the laboratory at the beginning and end of the field season as described below.
    Data from temperature sensors logging in air were compared to a National Institute of Standards and Technology (NIST) Traceable Digital Thermometer (Fisher brand) co-deployed on the bench. Logged temperature readings that were within manufacturer’s accuracy specification of temperature measured by the NIST Traceable Thermometer were deemed acceptable.
    Salinity sensors were checked with a purchased calibration standard (Ricca 50.000 millisiemens per centimeter, catalog number 2248-1) and re-calibrated as needed. Salinity sensors were also field checked periodically and re-calibrated as needed; field service dates are listed in the process steps.
    Water level sensors were tested in the laboratory for accuracy by comparing logged pressure readings in air to the barometers used for barometric compensation; logged pressure readings that were within manufacturer’s accuracy specification of the barometer’s logged pressure in air were deemed acceptable. The make and model of the water level logger and barometer used for each water level measurement are included as attributes in the data file.
    Data was exported as logged by each sensor; the manufacturer's accuracy and resolution specifications for each continuous monitoring sensor are stated in the attribute or domain definitions of each entity. Calculated attributes of water level ("dbs" and "WL_NAVD88) from all sensor types are reported to a resolution of 0.001 meters to allow for relative point-to-point comparisons. However, accuracy of these calculated parameters is dependent upon sensor accuracy, manual measurements of deployment depths, and RTK GPS elevation measurements. For example, an observed 2-3 centimeter change in the well heights at the Phragmites site, between 2017 and 2018, may be attributed to the unconsolidated nature of the sediment surface at this location. It is very wet and fluid with thick thatch. Overall, the approximate accuracy of this measurement technique is 1-5 centimeters.
    Note that draft shields were not consistently used for air temperature sensors until 2017; use of draft shields protect air temperature sensors from unknown influences such as direct exposure to sunlight and wind gusts.
  2. How accurate are the geographic locations?
    Horizontal positions were determined with a Trimble Real-Time Kinematic (RTK) GPS with Positional Dilution of Precision (PDOP) and Horizontal Dilution of Precision (HDOP) values less than or equal to 1.300 and 0.700 respectively. The latitude and longitude reported are the averages of several RTK measurements taken on at least two different days. Based on the range in these measurements, the horizontal accuracy is estimated to be +/- 30 centimeters. No formal positional accuracy tests were conducted.
  3. How accurate are the heights or depths?
    Water level loggers were deployed in wells at 4 different locations; sensor depth data from these instruments were converted to water elevation relative to NAVD88 using land surface elevations measured by Trimble Real-Time Kinematic (RTK) GPS. An average of land surface elevation measurements made around the well at each site was used for the water level calculation. Details on this calculation are described in the process steps. Vertical Dilution of Precision (VDOP) for RTK GPS measurements were less than 1.000; average vertical accuracy of this method is +/- 5 centimeters. No formal positional accuracy tests were conducted.
  4. Where are the gaps in the data? What is missing?
    Gaps in the continuous data record for a given parameter may have been the result of one of several sources: sensor not deployed during that time period, vandalism of an instrument by humans or destruction by chewing animals, removal of an instrument for maintenance, corrupt data file due to malfunctioning instrument, or wells with insufficient water level to produce reliable data. Exclusions of data from the continuous record are coded as the unrepresentable domain "NaN" (used in MATLAB, meaning "not a number"). The NaN count for each attribute are included in the domain definition for NaN. In some cases the sensor error may have affected only one logged parameter. Short periods of NaN usually coincide with field maintenance and download; these dates are listed in the process steps below.
    Gaps in the continuous record that are not represented by NaN indicate the sensor was not deployed or a large part of a deployment was excluded from the dataset. To note a specific large data gap, in 2016 we attempted to collect data from a shallower well at the Typha site in order to log salinity closer to the root zone. However, throughout the summer we had problems with malfunctioning loggers and low water levels due to drought conditions. By November 2016 this well was abandoned and data were only collected from the deeper well originally installed in 2015.
    Between 2016 and 2017-06-09, the PAR sensor was deployed at the Typha site; it was then moved to the Phragmites Wetland site. Other meteorological sensors (anemometer, rain gauge, relative humidity, air temperature) were also co-deployed when the PAR sensor moved sites.The entity, "HR_MET_deployments_2016_Jan2020", may be referenced for specific deployment and replacement dates for meteorological sensors.
  5. How consistent are the relationships among the observations, including topology?
    Each logged parameter set was queried for maximum and minimum values to be sure logged data fell within expected ranges for the environmental conditions. Data were plotted to look for any obvious instrument errors (data jumps or gaps or noisy data). Erroneous data in the logged data files may be the result of one of several sources: vandalism of an instrument, removal of an instrument for maintenance, corrupt data file due to malfunctioning instrument, or wells with insufficient water level to produce reliable data. These data were excluded from the final data report.
    Note that observed differences in air temperature between the Phragmites meteorological station's air temperature logger and the air temperature logger attached to the water level well (from the dual channel soil/air temperature logger) are due to differences in relative exposure of these two sensors. The meteorological station was deployed on an exposed knoll with less vegetation density and less standing water than is otherwise characteristic of the site. This was done to to capture weather data above the height of the dense Phragmites canopy and to protect other instruments deployed by study collaborators. The dual channel soil/air temperature loggers were deployed on the water level wells (approximately 1 meter above the land surface) within the Phgramites vegetation.
    Additionally, observed differences in well water temperature between the deep and shallow wells at the Phragmites site are due to different deployment depths of the water level loggers within these wells. The water level sensor in the deep well is further from the land surface than the shallow well logger.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: none
Use_Constraints: none
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - ScienceBase
    Denver Federal Center, Building 810, Mail Stop 302
    Denver, CO
    United States of America

    1-888-275-8747 (voice)
    sciencebase@usgs.gov
  2. What's the catalog number I need to order this data set? This dataset contains 5 individual TEXT files. The following files are comma-separate values: HR_MET_2016_Jan2020.txt, HR_TEMP_2016_Jan2020.txt, and HR_Well_2015_Jan2020.txt. The following files are tab-delimited files: HR_MET_deployments_2016_Jan2020.txt, HR_WellSensorDeploymentHeights_2015_2019.txt. The dataset also contains a browse graphic (tidally_restricted_wetland_HerringRiverEstuary.jpg) and the FGDC CSDGM metadata in XML format (HR_meta_2015_January_2020.xml).
  3. What legal disclaimers am I supposed to read?
    Neither the U.S. Government, the Department of the Interior, nor the USGS, nor any of their employees, contractors, or subcontractors, make any warranty, express or implied, nor assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, nor represent that its use would not infringe on privately owned rights. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in the use of these data or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?
  5. What hardware or software do I need in order to use the data set?
    The zip file resulting from the first network resource link contains data in TEXT format (3 files are comma-delimited, 2 is tab-delimited). The user must have software capable of uncompressing the zip file and reading the data formats.

Who wrote the metadata?

Dates:
Last modified: 07-Aug-2020
Metadata author:
Jennifer A. O'Keefe Suttles
Northeast Region: WOODS HOLE COASTAL & MARINE SCIENCE CENTER
Chemist
384 Woods Hole Road
Woods Hole, MA
United States

508-548-8700 x2385 (voice)
jokeefesuttles@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/whcmsc/SB_data_release/DR_P9R4SRTR/HR_meta_2015_to_January_2020.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:19:18 2021