Continuous Water Level, Salinity, and Temperature Data from Creeks and Monitoring Wells in Natural and Restored Wetlands on Cape Cod, Massachusetts, 2019

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

Frequently anticipated questions:

What does this data set describe?

Title:
Continuous Water Level, Salinity, and Temperature Data from Creeks and Monitoring Wells in Natural and Restored Wetlands on Cape Cod, Massachusetts, 2019
Abstract:
Environmental parameters affecting plant productivity and microbial respiration, such as water level, salinity, and groundwater temperature included in these datasets, are key components of wetland carbon cycling, carbon storage, and capacity to maintain elevation. Data were collected to (1) provide background data to evaluate potential differences in water level and carbon flux between wetland sites with differing elevation and tidal inundation and (2) facilitate applications of Blue Carbon projects in coastal wetlands. Associated child pages include continuous water level, salinity, and temperature from shallow wells installed in coastal wetland sites on Cape Cod, Massachusetts. These datasets are grouped by the project they support or by study site. Project study sites include salt marshes with natural tidal flow, salt marshes that were previously tidally restricted and have been restored, impounded coastal wetlands with restricted tidal flow inclusive of various vegetation types, and Phragmites dominated areas fringing natural salt marshes.
Supplemental_Information:
For more information, see the following field activities: https://cmgds.marine.usgs.gov/fan_info.php?fan=2016-036-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-018-FA . These data are linked to the project that started in 2016, hence the reason for indicating that field activity for related information.
  1. How might this data set be cited?
    Jennifer A. O'Keefe Suttles, Eagle, Meagan J., Sanders-DeMott, Rebecca, Nick, Sydney K., Brooks, Thomas W., Mann, Adrian G., and Kroeger, Kevin D., 20220818, Continuous Water Level, Salinity, and Temperature Data from Creeks and Monitoring Wells in Natural and Restored Wetlands on Cape Cod, Massachusetts, 2019: data release DOI:10.5066/P9T1KOTW, U.S. Geological Survey, Coastal and Marine Hazards and Resources Program, Woods Hole Coastal and Marine Science Center, Woods Hole, MA.

    Online Links:

    This is part of the following larger work.

    Jennifer A. O'Keefe Suttles, Eagle, Meagan J., Sanders-DeMott, Rebecca, Nick, Sydney K., Brooks, Thomas W., Mann, Adrian G., and Kroeger, Kevin D., 2022, Continuous Water Level, Salinity, and Temperature Data from Coastal Wetland Monitoring Wells, Cape Cod, Massachusetts: data release DOI:10.5066/P9T1KOTW, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: O'Keefe Suttles, J.A., Eagle, M.J., Sanders-DeMott, R., Nick, S.K., Brooks, T.W., Mann, A.G., and Kroeger, K.D., 2022, Continuous water level, salinity, and temperature data from coastal wetland monitoring wells, Cape Cod, Massachusetts (ver 2.0, August 2022): U.S. Geological Survey data release, https://doi.org/10.5066/P9T1KOTW
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.5199195
    East_Bounding_Coordinate: -69.9864529
    North_Bounding_Coordinate: 41.8022277
    South_Bounding_Coordinate: 41.7597901
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/62d18f37d34e87fffb2d4d1a?name=Scusset_RestoredSaltMarsh.jpg (JPEG)
    Photograph of the Scusset restored salt marsh site, Cape Cod, MA (Photo Credit: Jennifer O'Keefe Suttles).
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 29-Apr-2019
    Ending_Date: 24-Oct-2019
    Currentness_Reference:
    Ground Condition. Refer to the entity SensorDeploymentHeights_2019.csv for sensor deployment periods. Also check within the datafile for exact time period of data collection for each sensor. All sensors were not collecting data at all locations for the entire study period; refer to the completeness section of this metadata record for explanations of gaps in the continuous record.
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: Comma Separated Text files (*.csv).
  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?
    Wells_2019.csv
    Continuous monitoring of well water level, temperature, and salinity in wetland locations on Cape Cod. Raw pressure data, used to calculate water level, is reported as atmospherically corrected pressure (as exported from manufacturers' software). The CSV file also includes latitude and longitude of sensor placement. The dataset includes 25,602 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Boat MeadowA data point collected from a wetland along the Boat Meadow River in Eastham, MA on Cape Cod.
    ScussetData point collected from a wetland along Bass Creek in the Scusset Beach State Reservation, Sandwich, MA.
    Mill CreekData point collected from a wetland along Mill Creek in Sandwich, MA on Cape Cod.
    treatment
    A text identifier indicating the restoration status of the location within the wetland site from which the data point was collected. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the portion of the wetland that was not affected by a tidal restriction.
    Restored Salt MarshData point collected from the portion of the wetland upstream from a tidal restriction expansion.
    latitude
    Latitude decimal degrees north, NAD83 (Source: Producer-defined)
    Range of values
    Minimum:41.7597901
    Maximum:41.8022277
    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.5197397
    Maximum:-69.9864529
    Units:decimal degrees
    date_time
    A text string identifier for the date and time the data point was logged. (Source: Producer-defined)
    Range of values
    Minimum:5/14/2019 21:15:00
    Maximum:10/24/2019 18:15:00
    Units:mm-dd-yyyy hh:mm:ss (UTC)
    temp_well
    A numeric data value of logged well water temperature. 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:10.001
    Maximum:19.465
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset. After removing the logger from the well for downloading and maintenance, some parameters took time to re-equilibrate to ambient conditions when redeployed. The entity, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor deployment dates; the process description lists specific dates the logger was removed from the well for downloading. The attribute "temp_well" has 16 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:16.588
    Maximum:31.274
    Units:practical salinity units (PSU)
    The value "NaN" is defined as a textual representation of a measurement that was excluded from the dataset. After removing the logger from the well for downloading and maintenance, some parameters took time to re-equilibrate to ambient conditions when redeployed. The entity, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor deployment dates; the process description lists specific dates the logger was removed from the well for downloading. The attribute "sal_well" has 638 records with the "NaN" domain.
    press_atm
    A numeric data value of atmospheric pressure logged by the barometer using an In-Situ Barometer. Refer to the SensorDeploymentHeights_2019.csv entity and attribute section for manufacturer specifications of each barometer used. (Source: Producer-defined)
    Range of values
    Minimum:14.185
    Maximum:14.976
    Units:pounds per square inch (PSI)
    The value "NaN" is defined as a textual representation of a measurement that was excluded from the dataset. Atmospheric pressure measurements are excluded for data points not used to correct well water pressure measurements. After removing the logger from the well for downloading and maintenance, some parameters took time to re-equilibrate to ambient conditions when redeployed. The entity, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor deployment dates; the process description lists specific dates the logger was removed from the well for downloading. The attribute "press_atm" has 16 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 logged absolute pressure (press_abs) from the water level sensor and the logged atmospheric pressure (press_atm) from the barometer. Water level was measured using an In-Situ Aqua TROLL 200-30psia (30 psia 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. (Source: Producer-defined)
    Range of values
    Minimum:0.474
    Maximum:2.39
    Units:pounds per square inch (PSI)
    The value "NaN" is defined as a textual representation of a measurement that was excluded from the dataset. Logged datapoints when the logger was removed from the well for maintenance and downloading were excluded from the dataset. The entity, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor deployment dates. The attribute "press_corr" has 16 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; 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:-0.296
    Maximum:1.03
    Units:meters
    The value "NaN" is defined as a textual representation of a measurement that was excluded from the dataset; data may have been excluded if water level dropped below the sensor deployment depth or when the sensor was removed from the well for maintenance. The entity, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor start dates. The attribute "dbs" has 16 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. Positive values are above the datum and negative values below. (Source: Producer-defined)
    Range of values
    Minimum:0.389
    Maximum:1.83
    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, "SensorDeploymentHeights_2019.csv", may be referenced for specific sensor start dates. The attribute "WL_NAVD88" has 16 records with the "NaN" domain.
    Creek_2019.csv
    Continuous monitoring of creek water level, temperature, and salinity in wetland locations on Cape Cod. Raw pressure data, used to calculate water level, is reported as atmospherically corrected pressure (as exported from manufacturers' software). The CSV file also includes latitude and longitude of sensor placement. The dataset includes 16,528 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Boat MeadowA data point collected from a wetland along the Boat Meadow River in Eastham, MA on Cape Cod.
    ScussetData point collected from a wetland along Bass Creek in the Scusset Beach State Reservation, Sandwich, MA.
    treatment
    A text identifier indicating the restoration status of the location within the wetland site from which the data point was collected. (Source: Producer-defined)
    ValueDefinition
    Salt Marsh CreekData point collected from within a salt marsh tidal creek.
    latitude
    Latitude decimal degrees north, NAD83 (Source: Producer-defined)
    Range of values
    Minimum:41.7778897
    Maximum:41.8021428
    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.5199195
    Maximum:-69.9871923
    Units:decimal degrees
    date_time
    A text string identifier for the date and time the data point was logged. (Source: Producer-defined)
    Range of values
    Minimum:04/29/2019 18:30:00
    Maximum:10/24/2019 17:00:00
    Units:mm-dd-yyyy hh:mm:ss (UTC)
    temp_creek
    A numeric data value of logged well water temperature. 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:8.015
    Maximum:30.614
    Units:degrees Celsius
    sal_creek
    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:1.56
    Maximum:32.528
    Units:practical salinity units (PSU)
    The value "NaN" is defined as a textual representation of a measurement that was excluded from the dataset. Salinity data from fouled sensors were removed from the final dataset. The attribute "sal_creek" has 3,769 records with the "NaN" domain.
    press_atm
    A numeric data value of atmospheric pressure logged by the barometer using an In-Situ Barometer. Refer to the SensorDeploymentHeights_2019.csv entity and attribute section for manufacturer specifications of each barometer used. (Source: Producer-defined)
    Range of values
    Minimum:14.185
    Maximum:14.991
    Units:pounds per square inch (PSI)
    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. Water level was measured using an In-Situ Aqua TROLL 200-30psia (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. (Source: Producer-defined)
    Range of values
    Minimum:0.025
    Maximum:2.413
    Units:pounds per square inch (PSI)
    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. Positive values are above the datum and negative values below. (Source: Producer-defined)
    Range of values
    Minimum:-0.428
    Maximum:1.78
    Units:meters
    SensorDeploymentHeights_2019.csv
    Summary of deployment length and height measurements of water level loggers placed in wells and creeks as well as land surface elevation measurements used in final calculation of water elevation and water depth below land surface. There are 7 records in the table. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Boat MeadowData point collected from a wetland along the Boat Meadow River in Eastham, MA on Cape Cod.
    ScussetData point collected from a wetland along Bass Creek in the Scusset Beach State Reservation, Sandwich, MA.
    Mill CreekData point collected from a wetland along Mill Creek in Sandwich, MA on Cape Cod.
    treatment
    A text identifier indicating the restoration status of the location within the wetland site from which the data point was collected. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the portion of the wetland that was not affected by a tidal restriction.
    Restored Salt MarshData point collected from the portion of the wetland upstream from a tidal restriction restoration.
    Salt Marsh CreekData point collected from within a salt marsh tidal creek.
    deployment_type
    A text identifier indicating the type of installation used to deploy a water level logger. (Source: Producer-defined)
    ValueDefinition
    wellThe deployment of a water level logger in a well that was installed vertically in the surface of the salt marsh.
    postThe deployment of a water level logger that was on a post pushed or hammered vertically into the bottom of the creek bed.
    start_date
    A text string identifier for the date the deployment started (in the format mm/dd/yyyy). (Source: Producer-defined)
    Range of values
    Minimum:04/29/2019
    Maximum:09/19/2019
    Units:date format mm/dd/yyyy
    end_date
    A text string identifier for the date the deployment ended (in the format mm/dd/yyyy). (Source: Producer-defined)
    Range of values
    Minimum:06/27/2019
    Maximum:10/24/2019
    Units:date format mm-dd-yyyy
    latitude
    Latitude decimal degrees north, NAD83. (Source: Producer-defined)
    Range of values
    Minimum:41.75979007
    Maximum:41.80222774
    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.51991946
    Maximum:-69.98645292
    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). Positive values are above the datum and negative values below. (Source: Producer-defined)
    Range of values
    Minimum:-0.56775
    Maximum:1.2342
    Units:meters
    height_above_land_surface
    A manual measurement (using a measuring stick) of the height above land surface of either the well or the creek post that was used for the water level logger deployment. For this dataset, an average of measurements taken on different days is reported. (Source: Producer-defined)
    Range of values
    Minimum:0.403
    Maximum:1.43
    Units:meters
    deployment_length
    For well loggers, this is a manual measurement in meters (using a measuring stick) of the length of the well logger deployment cable (cable plus sensor). For creek loggers, this is a calculated value from two measurements which sum to equal the distance between the top of the creek deployment post and the bottom of the water level logger: measurement 1) from the top of the attached water level logger to the top of the deployment post; measurement 2) the measured length of the logger from it's top to the pressure sensor. (Source: Manufacturer-defined)
    Range of values
    Minimum:0.352
    Maximum:2.180
    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 psia maximum pressure; "a" indicates an absolute pressure sensor that is not vented to the atmosphere).
    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.
    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
    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.
    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; the manufacturer's specification for resolution is 0.01 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.

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 J. Eagle
    • Rebecca Sanders-DeMott
    • Sydney K. Nick
    • Thomas W. Brooks
    • Adrian G. Mann
    • Kevin D. Kroeger
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Jennifer A. O'Keefe Suttles
    Northeast Region: WOODS HOLE COASTAL and 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?

For several decades, local towns, conservation groups, and government organizations have worked to identify, replace, repair, and enlarge culverts to restore tidal flow upstream from historical tidal restrictions in an effort to restore salt marsh ecosystems on Cape Cod, Massachusetts. Undersized or failed culverts restrict tidal exchange between the marsh and the bays and estuaries, which leads to alterations in plant community composition and in fundamental processes controlling soil carbon accumulation, soil carbon transformations, and greenhouse gas emissions. In this study, sites were selected to compare salt marshes restored over a range of years and to compare marshes upstream and downstream from a restored tidal restriction. Salt marshes downstream from tidal restrictions represent "natural" conditions because hydrology was not substantially altered, whereas marshes upstream from repaired culverts represent "restored" conditions.

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)
    Well Installation: Four PVC wells were installed by USGS at three salt marsh sites at the beginning of the study period. 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 and a solid well casing that stuck above the sediment surface. The length of slotted section was 2.5 feet (~0.762 meters); the slot size was 0.010 inch (~ 0.3 mm). Well sections were pushed by hand or lightly tapped with a mallet to install the well into the sediment. The tip of the slotted screened well section was pushed about 80-100 cm below the land surface; the threaded portion (connecting the slotted length with the solid length) was below the sediment surface. At least 1.3 meters of well casing remained above the sediment surface to ensure that the groundwater well was not over-topped with surface water during the high tide. 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 (SensorDeploymentHeights_2019.csv). The process date represents the latest process date.
    Date: 2019 (process 2 of 6)
    Creek Logger Installation: Water level loggers were deployed in creeks near to the tidal restriction restoration by attaching the logger to a post driven into the creek bottom. Manual measurements of logger deployment heights were used in conjunction with RTK elevation measurements of the creek bottom to convert logged sensor depth to water elevation (calculation details given in process steps following). Deployments took place during 2019, with the process date representing the latest process date.
    Date: 2019 (process 3 of 6)
    Logger Deployments: All data loggers for this data release were In-Situ, model type Aqua TROLL 200 (30 psia 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. For specific logger serial numbers used at each site, refer to the file SensorDeploymentHeights_2019.csv included with this data release.
    Data loggers were deployed beginning in April 2019 for a period of at least six weeks and rotated to different sites throughout the field season. Data from loggers were periodically downloaded in the field using instrument manufacturer's software (Win-Situ 5 version 5.7.8.0); data were inspected for general accuracy. Creek sensor deployment heights were measured before removing the sensor for maintenance and after re-deploying the sensor to account for sensor movement and/or in-filling or scouring around the creek post. Dates of site visits are listed below. Boat Meadow: 04/29/19; 05/14/19; 06/27/19. Scusset: 07/02/19; 07/03/19; 08/20/19; 09/19/19; 10/24/19. Mill Creek: 08/20/19; 09/19/19; 10/24/19.
    The process date represents the most recent end date of this process step.
    Date: 2022 (process 4 of 6)
    A barometer was deployed in air (~1.5 meters from soil surface) and used to atmospherically correct data. Refer to the SensorDeploymentHeights_2019.csv entity and attribute section for manufacturer specifications of each barometer used.
    Manufacturer software (Win-Situ BaroMerge version 1.4.5.1) was used to atmospherically correct logged absolute pressure data from the non-vented water level sensors (corrected pressure = absolute pressure minus atmospheric pressure) and convert to an "uncorrected sensor depth" (depth not yet corrected for deployment height) using the equation: uncorrected sensor depth = (0.70307) multiplied by (corrected pressure) divided by (specific gravity). We assumed a brackish water density for all sites (Win-Situ specific gravity constant = 1.012 grams per cubic centimeter); the value 0.70307 is a property constant. Refer to the manufacturer's technical note for further details regarding these calculations McKee, Duane, 2007, Aqua Troll 200 Measurement Methodology: In-Situ Inc. Technical Note, 5 p.https://in-situ.com/uk/pub/media/support/documents/Aqua-TROLL-200-Measurement-Methodology-Tech-Note.pdf
    Data from all continuous monitoring sensors were exported from manufacturers' software as a .csv file and compiled using MATLAB (R2020b). Water elevation calculations were performed in MATLAB as described in the following process steps from the "uncorrected sensor depth" data previously calculated in Win-Situ BaroMerge software. Data resulting from erroneous measurements (malfunctioning sensors or insufficient water within a well) were excluded from the final dataset. Barometric pressure and density corrections were processed throughout the deployment period and checked while finalizing the data report. Corrected pressure and barometric pressure are the raw data reported in this data release; all calculated data can be reproduced with these raw data and the constants previously described. 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: 2022 (process 5 of 6)
    Creek water level (WL_NAVD88) was calculated in MATLAB using the following measured parameters (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; positive value when sensor pressure is greater than barometric pressure) 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 post height above land surface; measured periodically in the field using a meter stick (height_above_land_surface; always positive). d: deployment_length; equal to the measured distance from the top of the deployment post to the top of the deployed sensor plus the length of the deployed sensor; measured periodically in the field using a meter stick (always positive).
    Creek water elevation is calculated as: WL_NAVD88 = a+b+c-d
    Field measured deployment heights for specific time periods are summarized in a comma separated text file (SensorDeploymentHeights_2019.csv) included with this data release. Calculations were processed throughout the deployment period; the process date represents the latest date of data handling.
    Date: 2022 (process 6 of 6)
    Well water level calculations: Field measured deployment heights for specific time periods are summarized in a comma separated text file (SensorDeploymentHeights_2019.csv) 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) with respect to NAVD88. Calculations were processed throughout the deployment period in MATLAB (R2020b). 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; positive value when sensor pressure is greater than barometric pressure) 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 was 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.
  3. What similar or related data should the user be aware of?
    Eagle, Meagan J., Kroeger, Kevin D., Spivak, Amanda C., Wang, Faming, Tang, Jianwu, Abdul-Aziz, Omar I., Ishtiaq, Khandker S., O'Keefe Suttles, Jennifer, and Mann, Adrian G., 2022, Soil carbon consequences of historic hydrologic impairment and recent restoration in coastal wetlands: Science of The Total Environment Volume 848, Elsevier, Amsterdam.

    Online Links:

    Other_Citation_Details:
    Data reported in this data release support scientific findings in this journal article.
    O'Keefe Suttles, Jennifer A., Brosnahan, Sandra M., Gonneea, Meagan E., and Kroeger, Kevin D., 20191203, Continuous monitoring data from natural and restored salt marshes on Cape Cod, Massachusetts, 2016-17: data release DOI:10.5066/P9YLXOY8, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Associated data release with similar data types for additional sites referenced in the associated journal article.

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

  1. How well have the observations been checked?
    Sensors measuring conductivity, temperature, and depth (CTD) 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. Some noisy data from well deployments may be attributed to low water levels or air bubbles and thus only partial submergence of the conductivity sensor. Although obvious errors and large jumps in the data were removed, some of this "noisy" salinity data was included to allow for as much data as possible in the continuous record. At some sites, stratification within the well would yield a change in logged salinity on maintenance dates as removal of the logger for download and subsequent re-deployment resulted in mixing of water within the well. This artifact was deemed acceptable if the change in salinity was within the overall range of salinity observed at the site over the study period. Noisy salinity data was only included if data from all other logged parameters were deemed acceptable.
    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 file SensorDeploymentHeights_2019.csv; the manufacturer's accuracy and resolution specifications for each continuous monitoring sensor are stated in the process steps regarding well logger deployment and atmospheric corrections or in the attribute definitions.
    Data were exported as logged by each sensor. 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, the unconsolidated nature of the sediment surface at many sites (thick thatch, water above the land surface resulting in wet, fluid, dynamic sediment surface) may affect the accuracy of land surface measurements. Approximate accuracy of this measurement technique is 1-5 centimeters.
  2. How accurate are the geographic locations?
    Horizontal positions were determined with a SpectraPrecision (SP80) Real-Time Kinematic (RTK) GPS with Horizontal Dilution of Precision (HDOP) values less than or equal to 1.200. Horizontal accuracy is estimated to be less than +/- 5 centimeters for this method. No formal positional accuracy tests were conducted.
  3. How accurate are the heights or depths?
    Water level loggers were deployed in two tidal salt marsh creeks and in four wells on the surface of three salt marshes; sensor depth data from these instruments were converted to water elevation relative to NAVD88 using land surface elevations measured by SpectraPrecision (SP80) Real-Time Kinematic (RTK) GPS. Details on this calculation are described in the process steps. Vertical Dilution of Precision (VDOP) for RTK GPS measurements were less than 1.000; standard deviation of repeated measurements on different days less than 0.03 meters. 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, 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 un-representable domain "NaN" (used in MATLAB, meaning "not a number"). The NaN count for each attribute is 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. Refer to the file SensorDeploymentHeights_2019.csv included in this data release for logger deployment periods.
  5. How consistent are the relationships among the observations, including topology?
    Each dataset was queried for maximum and minimum values for each parameter 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, gaps, or noisy data). Erroneous data in the logged data files may be the result of one of several sources: 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.

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 3 individual comma separated text files: Wells_2019.csv; Creeks_2019.csv; SensorDeploymentHeights_2019.csv. The dataset also contains a browse graphic (Scusset_RestoredSaltMarsh.jpg) and the FGDC CSDGM metadata in XML format (RestoredMarshes_2019_meta.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 CSV format. The user must have software capable of uncompressing the zip file and reading the data formats.

Who wrote the metadata?

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

508-548-8700 x2385 (voice)
whsc_data_contact@usgs.gov
Contact_Instructions:
The metadata contact email address is a generic address in the event the person is no longer with USGS.
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_P9T1KOTW/RestoredMarshes_2019_meta.faq.html>
Generated by mp version 2.9.51 on Mon Aug 22 14:37:38 2022