Continuous Monitoring Data From Great Barnstable Marsh on Cape Cod, Massachusetts, 2017-19

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

Frequently anticipated questions:

What does this data set describe?

Title:
Continuous Monitoring Data From Great Barnstable Marsh on Cape Cod, Massachusetts, 2017-19
Abstract:
Salt marshes are environmental ecosystems that contribute to coastal landscape resiliency to storms and rising sea level. Ninety percent of mid-Atlantic and New England salt marshes have been impacted by parallel grid ditching that began in the 1920s–40s to control mosquito populations and to provide employment opportunities during the Great Depression (James-Pirri and others, 2009; Kennish, 2001). Continued alteration of salt marsh hydrology has had unintended consequences for salt marsh sustainability and ecosystem services. Great Barnstable Marsh (Barnstable, Cape Cod, Massachusetts) has areas of salt marsh that were ditched as well as natural areas. The U.S. Geological Survey (USGS) measured parameters for groundwater wells (water elevation, water depth below land surface, salinity, and water temperature), soil and air temperature, and other meteorological parameters. All these parameters affect plant productivity and are key components of salt marsh carbon cycling, carbon storage, and its ability to maintain elevation in response to changing sea level. These USGS datasets can be used to evaluate changes in water levels across ditched and natural salt marsh regions and provide information for any future studies of salt marsh productivity and geomorphic models in Great Barnstable Marsh.
James-Pirri, M.-J.,Ginsberg, H.S., Erwin,R.m., and Taylor, J., 2009, Effects of open marsh water management on numbers of larval salt marsh mosquitoes: Journal of Medical Entomology, 46(6), 1392-1399, doi:10.1603/033.046.0620. Kennish, M. J., 2001, Coastal salt marsh systems in the U.S.-A Review of Anthropogenic Impacts: Journal of Coastal Research, 17(3), 731-748, https://www.jstor.org/stable/4300224.
Supplemental_Information:
For more information, see the following field activities: https://cmgds.marine.usgs.gov/fan_info.php?fan=2019-018-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2018-055-FA https://cmgds.marine.usgs.gov/fan_info.php?fan=2017-036-FA
  1. How might this data set be cited?
    Jennifer A. O'Keefe Suttles, Gonneea, Meagan E., Mann, Adrian G., Brooks, Thomas W., Kroeger, Kevin D., Spivak, Amanda C., Wang, Faming, and Tang, Jim, 20200601, Continuous Monitoring Data From Great Barnstable Marsh on Cape Cod, Massachusetts, 2017-19: data release DOI:10.5066/P9FYDG9Z, U.S. Geological Survey, Reston, VA.

    Online Links:

    Other_Citation_Details:
    Suggested citation: O’Keefe Suttles, J.A., Gonneea, M.E., Mann, A.G., Brooks, T.W., Kroeger, K.D., Spivak, A.C., Wang, F., and Tang, J., 2020, Continuous monitoring data from Great Barnstable Marsh on Cape Cod, Massachusetts, 2017-19: U.S. Geological Survey data release, https://doi.org/10.5066/P9FYDG9Z.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -70.38159502
    East_Bounding_Coordinate: -70.36442384
    North_Bounding_Coordinate: 41.73219942
    South_Bounding_Coordinate: 41.72976573
  3. What does it look like?
    https://www.sciencebase.gov/catalog/file/get/5e945de982ce172707f03429/?name=GBM_Ditches_Photo.jpg (JPEG)
    Aerial photograph of the ditched portion of Great Barnstable Marsh, Cape Cod, MA (photo credit: Aerial Imaging and Mapping group, USGS WHCMSC).
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 2017
    Ending_Date: 2019
    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?
    GBM_Well_2017_2019
    Continuous monitoring of well water level, temperature, and salinity in salt marsh sites within the Great Barnstable Marsh. Raw pressure data, used to calculate water level, is reported as either absolute pressure or atmospherically corrected pressure (as exported from manufacturers' software). The comma-delimited TEXT file also includes latitude and longitude of sensor placement. The dataset includes 145,587 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Great Barnstable MarshA data point collected from a salt marsh site within Great Barnstable Marsh (Cape Cod, MA).
    treatment
    A text identifier indicating any hyrdrologic alteration of the study site. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the Great Barnstable Marsh in an area that did not have hydrologic alteration (ditching).
    Ditched Salt MarshData point collected from the Great Barnstable Marsh in an area with altered hydrologic conditions (ditching).
    station
    A text identifier indicating proximity of the well to a ditch or natural tidal creek. (Source: Producer-defined)
    ValueDefinition
    Interior WellA text identifier indicating the well was at least 30 meters from a natural tidal creek.
    Creek WellA text identifier indicating the well was adjacent to (0-5 meters from) a natural tidal creek.
    Ditch Adjacent WellA text identifier indicating the well was adjacent to (0-5 meters from) a ditch.
    well_abbrev
    A text identifier indicating the abbreviation used to identify the well while processing data. (Source: Producer defined) The well abbreviation code contains a two-digit numeric identifier for the year of data collection and a text identifier indicating the general study site location (EC = eddy covariance flux tower site; Dit = ditched; Int = interior; Crk = Creek; Nat = natural). The eddy covariance flux tower site is an interior station, this station was not used for the investigation comparing ditched and unditched/natural salt marshes in Great Barnstable Marsh and as such the well abbreviation is coded a bit differently.
    latitude
    Latitude decimal degrees north, NAD83 (Source: Producer-defined)
    Range of values
    Minimum:41.7297657
    Maximum:41.7321994
    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.3815950
    Maximum:-70.3644238
    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:2017-04-12 19:30:00
    Maximum:2019-12-23 18:00:00
    Units:yyyy-mm-dd hh:mm:ss (UTC)
    temp_well
    A numeric data value of logged well water temperature. (Source: Producer-defined)
    Range of values
    Minimum:6.09
    Maximum:19.33
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset.
    sal_well
    A numeric data value of logged well water salinity. (Source: Producer-defined)
    Range of values
    Minimum:28.09
    Maximum:40.65
    Units:practical salinity units (PSU)
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the dataset.
    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. (Source: Producer-defined)
    Range of values
    Minimum:15.237
    Maximum:17.027
    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.
    press_atm
    A numeric data value of atmospheric pressure logged by the barometer. (Source: Producer-defined)
    Range of values
    Minimum:14.185
    Maximum:15.115
    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.
    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. (Source: Producer-defined)
    Range of values
    Minimum:0.619
    Maximum:2.306
    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.
    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 was 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: Manufacturer-defined)
    Range of values
    Minimum:-0.50
    Maximum:0.80
    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.
    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: Manufacturer-defined)
    Range of values
    Minimum:1.03
    Maximum:2.34
    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.
    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).
    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).
    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
    In-Situ Rugged BaroTROLLAn atmospheric pressure (press_atm) data point collected using a barometer manufactured by In-Situ, model type Rugged BaroTROLL.
    In-Situ BaroTROLL 500An atmospheric pressure (press_atm) data point collected using a barometer manufactured by In-Situ, model type BaroTROLL 500.
    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.
    GBM_TEMP_2017_2019
    Continuous monitoring of soil and air temperature in salt marsh sites within the Great Barnstable Marsh. The comma-delimited TEXT file also includes latitude and longitude of sensor placement. The dataset contains 56,569 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Great Barnstable MarshData point collected from a salt marsh study site within the Great Barnstable Marsh (Cape Cod, MA).
    treatment
    A text identifier indicating any hydrologic alteration of the study site. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the Great Barnstable Marsh in an area that did not have hydrologic alteration (ditching).
    latitude
    Latitude decimal degrees north, NAD83. (Source: Producer-defined)
    Range of values
    Minimum:41.7297671
    Maximum:41.7298125
    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.3645119
    Maximum:-70.3644238
    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:2017-04-12 17:15:00
    Maximum:2019-10-25 19:15: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:-9.13
    Maximum:36.23
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the data set.
    temp_soil
    A numeric data value of logged soil temperature; sensor installed 10 cm below land surface. (Source: Producer-defined)
    Range of values
    Minimum:2.40
    Maximum:28.00
    Units:degrees Celsius
    The value "NaN" is defined as a textual representation of an erroneous measurement that was excluded from the data set.
    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 Pro v2A data point collected using a dual channel temperature sensor logger manufactured by Onset, model type HOBO Pro v2.
    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.
    GBM_MET_2017_2019
    Continuous monitoring of photosynthetically active radiation (PAR) and other meteorological parameters in Great Barnstable Marsh (Cape Cod, MA). The comma-delimited TEXT file also includes latitude and longitude of sensor placement. The dataset contains 62,009 records. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Great Barnstable MarshA data point collected from a salt marsh site within Great Barnstable Marsh (Cape Cod, MA).
    treatment
    A text identifier indicating any hydrologic alteration of the study site. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the Great Barnstable Marsh in an area that did not have hydrologic alteration (ditching).
    latitude
    Latitude decimal degrees north, NAD83. Weather station position was determined from Google Earth aerial imagery of the study site. (Source: Producer-defined)
    Range of values
    Minimum:41.72980
    Maximum:41.72981
    Units:decimal degrees
    longitude
    Longitude decimal degrees west, NAD83. The negative value indicates a location in the western hemisphere. Weather station position was determined from Google Earth aerial imagery of the study site. (Source: Producer-defined)
    Range of values
    Minimum:-70.364575
    Maximum:-70.364476
    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:2017-04-24 15:00:02
    Maximum:2019-12-23 18:00: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. 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.
    rain
    A numeric data value of logged rain accumulation; the rain gauge was deployed on a mast with other meteorological sensors. Accuracy of the rain gauge +/- 1% and resolution is 0.2 millimeters. (Source: Producer-defined)
    Range of values
    Minimum:0
    Maximum:20.00
    Units:millimeters
    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:-16.53
    Maximum:34.26
    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.
    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% and resolution is 0.1% RH. (Source: Manufacturer-defined)
    Range of values
    Minimum:27.7
    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.
    wind_speed
    A numeric data value of wind speed logged by the anemometer; 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% of the reading (whichever is greater) and resolution is 0.5 m/sec. (Source: Manufacturer-defined)
    Range of values
    Minimum:0
    Maximum:19.04
    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.
    gust_speed
    A numeric data value of wind gust speed logged by the anemometer; 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% of the reading (whichever is greater) and resolution is 0.5 m/sec. (Source: Manufacturer-defined)
    Range of values
    Minimum:0
    Maximum:28.05
    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.
    wind_dir
    A numeric data value of wind gust speed logged by the anemometer; 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% of the reading (whichever is greater) and resolution is 0.5 m/sec. (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.
    GBM_WellSensorDeploymentHeights_2017_2019
    Summary of land surface elevation, deployment length, and well height measurements for water level loggers deployed at Great Barnstable Marsh sites between 2017 and 2019; measurements used in final calculation of water elevation and water depth below land surface. There are 11 records in the table. Tab-separated TEXT file. (Source: Producer-defined)
    site_name
    A text identifier for the general location of the study site. (Source: Producer-defined)
    ValueDefinition
    Great Barnstable MarshA data point collected from a salt marsh site within Great Barnstable Marsh (Cape Cod, MA).
    treatment
    A text identifier indicating any hydrologic alteration of the study site. (Source: Producer-defined)
    ValueDefinition
    Natural Salt MarshData point collected from the Great Barnstable Marsh in an area that did not have hydrologic alteration (ditching).
    Ditched Salt MarshData point collected from the Great Barnstable Marsh in an area with altered hydrologic conditions (ditching).
    station
    A text identifier indicating proximity of the well to a ditch or natural tidal creek. (Source: Producer-defined)
    ValueDefinition
    Interior WellA text identifier indicating the well was at least 30 meters from a natural tidal creek.
    Creek WellA text identifier indicating the well was adjacent to (0-5 meters from) a natural tidal creek.
    Ditch Adjacent WellA text identifier indicating the well was adjacent to (0-5 meters from) a ditch.
    well_abbrev
    A text identifier indicating the abbreviation used to identify the well while processing data. (Source: Producer-defined) The well abbreviation code contains a two-digit numeric identifier for the year of data collection and a text identifier indicating the general study site location (EC = eddy covariance flux tower site; Dit = ditched; Int = interior; Crk = Creek; Nat = natural); the year is listed after the "EC" abbreviations but it is listed first in all other abbreviations.
    deployment_type
    A text identifier indicating the type of well installation used to deploy a water level logger. (Source: Producer-defined)
    ValueDefinition
    vented wellA well with a hole drilled near the top of the well casing to allow for equilibration with atmospheric pressure.
    vented well with fill holeA well with a hole drilled near the top of the well casing to allow for equilibration with atmospheric pressure and a hole drilled about 5 cm above the sediment surface to allow for surface water to fill the well on a flood tide.
    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:2017-04-12
    Maximum:2019-06-12
    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:2017-12-31
    Maximum:2019-12-23
    Units:date format yyyy-mm-dd
    latitude
    Latitude decimal degrees north, NAD83. (Source: Producer-defined)
    Range of values
    Minimum:41.7297657
    Maximum:41.7321994
    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.3815950
    Maximum:-70.3644238
    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). Positive is elevation above 0 for the datum. (Source: Manufacturer-defined)
    Range of values
    Minimum:1.3595
    Maximum:1.6434
    Units:meters
    The value "NaN" is defined as a textual representation of a well that did not have a land surface elevation measurement or the measurement made was erroneous. The parameter "WL_NAVD88" will not be available for any well that did not have a measurement for land surface elevation.
    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:1.190
    Maximum:1.480
    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:2.070
    Maximum:2.235
    Units:meters
    sensor_depth_below_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.980
    Maximum:-0.590
    Units:meters
    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.
    GBM_MET_deployments_2017_2019
    Summary of deployment dates and serial numbers of meteorological sensors deployed at Great Barnstable Marsh between 2017 and 2019. There are 9 records in the table. Tab-delimited TEXT file. (Source: Producer-defined)
    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:2017-04-24
    Maximum:2019-09-05
    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. (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. Note that the PAR data between 2019-08-24 and 2019-10-30 had an error value (data from this time period was excluded); the sensor was replaced 2019-10-30. (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. The textual value "NaN" is used for periods of time when a sensor was not deployed.
    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.
    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. (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.
    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. (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.
    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. Note that for the anemometer had faulty wind direction data (due to corrosion) for most of the 2018 field season. (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.
    notes
    Notation on sensor deployment and retrieval. (Source: Producer-defined) A textual description of sensor deployments or retrievals for the data reporting period.

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
    • Adrian G. Mann
    • Thomas W. Brooks
    • Kevin D. Kroeger
    • Amanda C. Spivak
    • Faming Wang
    • Jim Tang
  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 & 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?

These datasets may be used to quantify and compare metrics of salt marsh sustainability and ecosystem services (including platform elevation, soil accretion rates, carbon sequestration, and plant productivity) in ditched and natural salt marshes.

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: 2020 (process 1 of 8)
    Great Barnstable Marsh (part of Sandy Neck Park, a municipal park in the town of Barnstable) was selected in 2017 as study location because of it's vast expanse of undeveloped salt marsh. It serves as natural control site to a number of investigations by study collaborators researching the effects of hydrologic alterations on salt marsh ecosystems and other tidally restricted wetlands. Upon initial site selection in 2017 a station was established with various continuous monitoring sensors (eddy co-variance carbon dioxide flux tower, meterological tower, water level sensor, soil and air temperature sensors). These sensors were removed in the winters and redeployed each spring. In 2018, an additional investigation began in a portion of Great Barnstable Marsh with specific goals of investigating differences between ditched and natural (unditched) salt marsh areas of Great Barnstable Marsh; well water level and temperature data were collected at different dtiched and natural transects in this portion of the marsh. This data release groups continuous monitoring data collected by USGS at all of our Great Barnstable Marsh study locations. The eddy co-variance carbon dioxide data is not reported here because that data was collected by non-USGS study collaborators.
    Date: 2019 (process 2 of 8)
    Between 2017 and 2019, water level and conductivity were measured in a PVC well that was installed near to the eddy co-variance flux tower in the spring of each year; the well and logger were removed in the winter. Wells consisted of two pre-manufactured sections of 1 inch (2.54 cm) diameter well casing that were threaded together: a 2.5 inch (~0.762 meter) length of slotted screened casing (slot size 0.01 inch; ~ 3 mm) and a solid well casing that stuck above the sediment surface. An eyebolt was drilled into the inward facing edge of the threaded well cap; water level loggers were hung by aircraft cable threaded through the eyebolt and through the logger cap and secured on both ends using crimped stainless-steel oval sleeves. PVC 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 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 meter 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. The well was destroyed by ice during the first winter deployment and was removed prior to ice formation in the following field seasons. Each spring, wells were reinstalled using the protocol previously described. Exact well heights and sensor deployment lengths are summarized in a separate entity and attribute section. The process date represents the latest process date.
    Date: 2019 (process 3 of 8)
    Additional sensors were co-deployed at the long-term monitoring site, including dual channel (soil and air) temperature loggers, a barometer, and a weather station (photosynthethically active radiation, anemometer, rain gauge, air temperature and relative humidity). 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 the groundwater well ~1 m above the land surface. Note that draft shields were not used on the dual channel air temperature logger in 2017; however draft shields were used in subsequent years and draft shields were used on the weather station temperature/relative humidity sensor all years. The barometer was deployed in air near to the well location on the weather station mast. The PAR sensor was deployed above the height of the nearby Eddy Co-Variance CO2 flux tower in a location that would not be shaded by vegetation or other structures; other meteorological sensors were deployed on the same mast with the PAR sensor. Deployments took place between 2017 and 2019, with removal of instruments over the winter season. The process date represents the latest process date.
    Date: 2019 (process 4 of 8)
    Well sensors were periodically downloaded in the field using instrument manufacturers' software (HOBOPro or WinSitu); data were inspected for general accuracy. Salinity sensors were periodically cleaned and checked in the field for fouling and calibration drift. Listed below are dates of visits to the eddy co-variance flux tower site. 04/12/2017; 05/24/2017; 05/26/2017; 06/07/2017; 08/09/2017; 08/17/2017; 08/24/2017; 09/12/2017; 11/14/2017; 01/10/2018 05/21/2018; 06/21/2018; 08/06/2018; 08/08/2018; 10/17/2018; 12/3/2018 04/17/2019; 05/01/2019; 05/22/2019; 06/12/2019; 08/22/2019; 09/05/2019; 10/25/2019; 12/23/2019 The process date represents the latest process date.
    Date: 2019 (process 5 of 8)
    In 2018 and 2019, in addition to the eddy co-variance flux tower site, water level was also monitored in wells in a portion of the salt marsh with altered hydrology (“ditched”) and in an adjacent portion of the salt marsh with unaltered hydrology (“natural” or “un-ditched”). PVC wells were installed at each plot as described in the previous process step for wells installed at the eddy co-variance flux site. However, wells for plots in the hydrology study had an additional “fill” hole drilled about 10 cm above the sediment surface to allow the well to fill with surface water on the flood tide. Wells were installed along one ditched transect in 2018 and removed in December 2018 for the winter season (to prevent destruction by ice). Wells were reinstalled in 2019 along a different transect which included both ditched and natural salt marsh areas. Exact well heights and sensor deployment lengths are summarized in a separate entity and attribute section. Well water level data loggers were deployed from October 2018 – December 2018 and April 2019 – October 2019. Loggers were periodically downloaded in the field using instrument manufacturers' software (HOBOPro, WinSitu); data were inspected for general accuracy. Dates of site visits are listed as follows, Ditched Transect 2018: 6/21/18, 7/9/18, 7/19/18, 9/19/18, 10/17/18,12/3/18. Ditched Transect 2019: 4/17/19, 5/1/19, 5/8/19, 6/12/19, 8/22/19, 10/25/19. Natural Transect 2019: 4/17/19, 5/8/19, 5/22/19, 6/12/19, 8/22/19, 10/25/19.
    During the 04/17/19 installation of the “Natural Creek Well”, it was noted that the well was slow to recharge. We had concerns that this well may be clogged, so an additional well was installed nearby on 5/22/19 with an In-Situ AquaTroll 200 deployed until 6/12/19. On 6/12/19 the In-Situ AquaTroll 200 was removed to be used in a different study and the HOBO U20-001-01 from the first “Natural Creek Well” was redeployed into the second “Natural Creek Well”. Deployment string lengths for these two different logger types were significantly different. Although this does not affect the reported water level (deployment string length is factored into water level calculations), it does affect the reported well water temperature. Groundwater temperature changes with depth from the land surface, thus an observed jump in groundwater temperature in the “Natural Creek Well” well on 6/12/19 is due to a difference in the depth at which the logger was measuring well water temperature. Note that data from the first “Natural Creek Well”, beginning 04/17/19, are not reported. The process date representing the latest process date.
    Date: 2020 (process 6 of 8)
    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; the sensor depth calculated in the manufacturer's software is not reported because the sensor deployment heights must be accounted for to have meaningful water level data. 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 7 of 8)
    Field measured deployment heights for specific time periods are summarized in a txt file (tab-delimited, filename: GBM_WellSensorDeploymentHeight_2017_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 (WL_NAVD88) is calculated as: WL_NAVD88 = a +b+c-d
    Well water depth below land surface (dbs) is calculated as: dbs = a+c-d
    The process date represents the latest date of data processing.
    Date: 07-Aug-2020 (process 8 of 8)
    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 weather station sensors. All other continuous monitoring sensors were bench tested for accuracy in the laboratory at the beginning and end of the field season; salinity sensors were also field checked periodically. At the beginning of the field season, 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. Draft shields were placed around air temperature sensors to protect the sensor from unknown influences such as direct exposure to sunlight and wind gusts. 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. Salinity sensors were checked with a purchased calibration standard (Ricca 50.000 millisiemens per centimeter, product number 2248-1) and re-calibrated as needed. These procedures were repeated at the end of the field season. If sensor accuracy was found to have drifted over the field season, data corrections would be applied as described in the Process Steps portion of this metadata record.
  2. How accurate are the geographic locations?
    Horizontal positions for well locations 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.000 and 0.600 respectively. The latitude and longitude reported for 2018 and 2019 are 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 +/- 10 centimeters. The 2017 well and weather station location were estimated from Google Earth imagery of the study site. No formal positional accuracy tests were conducted.
  3. How accurate are the heights or depths?
    Water level loggers were deployed in wells at different stations within the Great Barnstable Marsh; 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 elevation measurements made around the 2018 and 2019 well locations 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 0.800; average vertical accuracy of this method is +/- 5 centimeters. The 2017 well location did not have an RTK elevation measurement; water depth below land surface is the only water depth measurement reported for this year. 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, removal of an instrument for maintenance, corrupt data file due to malfunctioning instrument, wells with insufficient water level to produce reliable data, or logged data outside of the manufacturer's accuracy specifications. These data were removed from the final data report. As noted in the positional accuracy report, land surface elevation data was not available for the 2017 well at the eddy co-variance flux tower site. Water depth below land surface (dbs) is reported for this well, however the water elevation (WL_NAVD88) is not reported. Salinity data from the 2017 well deployment at the eddy co-variance flux tower site were excluded from the final dataset because the logged salinity values were greater than manufacturer's accuracy specifications for converting specific conductance to salinity units. The logger was within specification for specific conductance readings, calibration checks fell within acceptable ranges, and discrete checks of well water salinity using a refractometer were comparable to logged salinity (converted from specific conductance). However, because the salinity was outside of manufacturer's specification, it is not reported. Additionally, we have had concerns that wells at the eddy co-variance flux site may become stratified in the summer. Logged salinity in all three years is hypersaline and in 2019 the logged salinity data indicated that there may have been mixing within the well during routine well maintenance as loggers were removed and redeployed (characterized by lower salinity after a redeployment followed by a gradual return to hypersaline conditions). Salinity data from these periods of re-equilibration/re-stratification following routine maintenance in 2019 were excluded from the final dataset. Note that data from the first “Natural Creek Well”, beginning 04/17/19, are not reported; details are in a following process step. The anemometer on the weather station was replaced several times. This model anemometer has separate moving parts for measuring wind speed and wind direction. In some instances the wind speed sensor appeared to be collecting reliable data when the wind direction sensor was rusted in one position. In those cases only the wind speed data was reported.
  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 removed from the final data report. Draft shields were not used on the dual channel soil/air temperature logger in 2017, although it was used in following years (the draft shield was used on the meteorological station's air temperature sensor all years).

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: GBM_MET_2017_2019.txt, GBM_TEMP_2017_2019.txt, and GBM_Well_2017_2019.txt, The following files are tab-delimited files: GBM_MET_deployments_2017_2019.txt, GBM_WellSensorDeploymentHeights_2017_2019.txt. The dataset also contains a browse graphic (GBM_Ditches_Photo.jpg) and the FGDC CSDGM metadata in XML format (GBM_meta_2017_2019.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 are 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: 19-Mar-2024
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)
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. (updated on 20240319)
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_P9FYDG9Z/GBM_meta_2017_2019.faq.html>
Generated by mp version 2.9.51 on Wed Jun 26 15:25:06 2024