Hudson River (HUD) NERR Water Quality Metadata March - December 2004 Latest Update: May 2, 2005
Entry ID:
CDMO_hudwq03-12.04m
|
[
Get Data
]
[
Update this Record
]
|
Updating this record requires registration.
|
Summary
Abstract:
Water quality monitoring is conducted at 26 National Estuarine Research Reserves (NERR) at four locations within or adjacent to the reserve. The following parameters are collected at least every 30 minutes: water temperature, specific conductivity, salinity, percent saturation, dissolved oxygen concentration, water depth, pH and turbidity. All water quality data loggers will be deployed from a known depth from the bottom at each site.
Purpose:
Research objectives The objective of this study is to monitor surface water quality at the Tivoli Bays component of the Hudson River National Estuarine Research Reserve (NERR). Two tidal freshwater wetlands, Tivoli North Bay and Tivoli South Bay, and their primary upland tributaries, Stony Creek and Saw Kill Creek respectively, are monitored using four dataloggers (YSI 6600 sondes). In Tivoli ... North Bay and Tivoli South Bay the dataloggers monitor the ebbing and flooding Hudson River water. In Stony Creek and Saw Kill Creek, the dataloggers are deployed above the area of tidal influence and monitor the quality of water entering the Tivoli Bays via stream flow. Thus, the relative importance of stream flow and tidal exchange and the potential impacts of intertidal areas on the water quality of the Tivoli Bays can be determined. Monitoring the water quality of the tributaries is important because it has previously been determined that urban and residential land use practices are markedly influencing the water chemistry of the tributaries, especially Saw Kill Creek. Since residential coverage continues to increase, we hope that the intensive monitoring of the surface waters in these watersheds will identify trends associated with this rapid development. Examining the influence of tidal exchange allows identification of long-term trends in the water quality of the Hudson River Estuary at this location and the potential inputs to the Estuary from the Tivoli Bays. Finally, the influence of intertidal areas on water quality within the Tivoli Bays is interesting because of the potential impacts of both floating and emergent invasive plant species present in this system.
SUPPLEMENTAL INFORMATION:
Associated researchers and projects As part of the Hudson River NERR water quality monitoring project, physical and chemical constituents of the tributary waters discharging into HUDNERR marshes and marsh waters are measured monthly during ebb tides. Measurements include dissolved oxygen, seston, alkalinity, pH, temperature, salinity, conductivity and concentrations of ammonium, nitrate, phosphate, sulfate and chloride. Associated researchers working at the Tivoli Bays component site include scientists from the Institute of Ecosystem Studies in Millbrook, NY, Yale School of Forestry and Environmental Studies in New Haven, CT, and Rensselaer Polytechnic Institute in Troy, NY. Other remarks/notes A reference to negative and/or zero depth or depth readings flagged as outliers indicates that depth was recorded as a negative value in the raw data file and as zero in the edited data file due to the formatting of Excel. The technician edited none of these data points by hand nor did the technician delete any of them. The range for the turbidity probe is 0-1000 NTU, with an accuracy of + 0.5% or 2 NTU, whichever is greater. Therefore, a reading of –2 is acceptable. Saw Kill Creek is a low-turbidity site due to the presence of a dam allowing settling of a large amount of suspended matter. Turbidity readings of 0 to –2 are frequently recorded, but are not outliers. Therefore, QA/QC of the turbidity data (all sites) involves flagging all data below –2 NTU as outliers, data between 0 and –2 are not considered outliers and are not documented in the metadata.. If the post-deployment dissolved oxygen readings were out of the specification range (98%-102%), the data were carefully examined for obvious shifts in dissolved oxygen readings during deployment and readings at the end of deployment were checked against readings from the newly calibrated replacement sonde. If there were no obvious discontinuities and the probe was functioning adequately, data are not considered suspect and the post-deployment readings were not mentioned in the Data Anomalies section (Section 11) of the metadata. The location of the sonde in Stony Creek (SC) was changed on 7/21/2004, due to variable stream flow resulting in frequent exposure of the instrument to air. The new location is approximately 50 m upstream, in a pool area. Daily precipitation totals for 2004: Date TotPrcp (mm) 1/2/2004 1.5 1/3/2004 3.3 1/4/2004 10.7 1/5/2004 11.2 1/12/2004 0.8 1/15/2004 0.3 1/18/2004 0.3 1/27/2004 0.5 1/29/2004 0.3 1/31/2004 0.3 2/1/2004 1 2/2/2004 0.5 2/3/2004 1.5 2/4/2004 6.9 2/5/2004 0.8 2/6/2004 8.4 2/7/2004 14 2/9/2004 1 2/10/2004 4.6 2/13/2004 0.3 2/21/2004 0.5 3/2/2004 1 3/4/2004 2.3 3/5/2004 3 3/6/2004 5.8 3/7/2004 0.3 3/8/2004 11.4 3/9/2004 1.3 3/17/2004 2.8 3/18/2004 7.1 3/19/2004 0.8 3/20/2004 1.5 3/26/2004 0.3 3/27/2004 3.3 3/31/2004 19.6 4/1/2004 18.8 4/2/2004 0.8 4/12/2004 8.6 4/13/2004 21.3 4/14/2004 0.5 4/22/2004 3 4/23/2004 18.3 4/24/2004 0.3 4/25/2004 0.3 4/26/2004 18 4/27/2004 1 5/2/2004 1.8 5/3/2004 11.2 5/4/2004 0.3 5/9/2004 0.8 5/10/2004 2.8 5/12/2004 0.5 5/13/2004 1.5 5/18/2004 4.8 5/21/2004 0.8 5/22/2004 0.3 5/23/2004 5.8 5/24/2004 17 5/25/2004 1 5/26/2004 35.1 5/27/2004 3.6 5/28/2004 4.8 5/31/2004 6.1 6/1/2004 10.9 6/2/2004 1.5 6/3/2004 0.8 6/5/2004 0.3 6/6/2004 0.8 6/9/2004 1.8 6/17/2004 5.1 6/22/2004 1.8 6/25/2004 1.5 6/26/2004 6.6 6/28/2004 1.5 6/29/2004 0.3 7/1/2004 3.6 7/2/2004 2.3 7/5/2004 11.7 7/8/2004 3.8 7/12/2004 1.8 7/13/2004 3 7/14/2004 1.8 7/15/2004 5.3 7/16/2004 0.3 7/18/2004 11.2 7/23/2004 27.7 7/27/2004 27.9 7/28/2004 2.8 7/30/2004 4.1 7/31/2004 0.3 8/1/2004 14 8/4/2004 5.1 8/5/2004 4.6 8/7/2004 1 8/8/2004 1 8/11/2004 8.4 8/12/2004 6.6 8/13/2004 15.5 8/16/2004 16.5 8/17/2004 0.3 8/20/2004 11.7 8/21/2004 23.9 8/30/2004 43.2 8/31/2004 0.3 9/8/2004 32.3 9/9/2004 16 9/17/2004 29.7 9/18/2004 52.1 9/28/2004 65.3 9/29/2004 4.6 9/30/2004 3 10/2/2004 5.8 10/14/2004 0.8 10/15/2004 9.7 10/16/2004 0.8 10/18/2004 2 10/19/2004 20.3 10/21/2004 2 11/3/2004 0.3 11/4/2004 15 11/12/2004 2 11/13/2004 3 11/14/2004 0.5 11/20/2004 2.3 11/21/2004 1 11/24/2004 12.7 11/25/2004 15 11/28/2004 27.2 12/1/2004 29.2 12/7/2004 19.1 12/9/2004 5.8 12/10/2004 14.7 12/11/2004 2.5 12/13/2004 0.3 12/19/2004 0.5 12/22/2004 2 12/23/2004 30.7 12/27/2004 0.8 12/30/2004 0.3
CURRENTNESS REFERENCE:
Observed
SPATIAL DATA ORGANIZATION INFORMATION:
Indirect Spatial Reference: Site location and character The Hudson River National Estuarine Research Reserve (HUDNERR) is a multi-component site totaling approximately 5,000 acres. Each component of the reserve is referenced by River Mile (RM) of the Hudson River in New York State proceeding north from the southern tip of Manhattan (RM 0). The reserve includes the following four component sites: Piermont Marsh, Rockland County (RM 24)(41o02'30"N 73o54'15"W), Iona Island, Rockland County (RM 45)(41o18'15"N 73o58'45"W), Tivoli Bays, Dutchess County (RM 98)(42o02'15"N 73o55'10"W), and Stockport Flats, Columbia County (RM 124)(42o02'30"N 73o46'00"W). The four component sites include open water, tidal wetland, and adjacent upland buffer habitats and are representative of the diverse plant and animal communities that occupy the salinity gradient within the Hudson River Estuary. Development within the watersheds of the four component sites ranges from predominantly urban/suburban to forested/agricultural. The highlighted component for this study is the Tivoli Bays in Annandale, NY. This component includes four monitored sites: Tivoli South Bay (TS), Tivoli North Bay (TN), Saw Kill Creek (SK) and Stony Creek (SC). All four monitored sites are freshwater (0.0 ppt salinity). Tivoli South Bay (latitude 42° 01' 37.336" N, longitude 73° 55' 33.445" W) is a tidal freshwater wetland with intertidal mudflats exposed at low tide. During the growing season (June – September), the subtidal area of Tivoli South Bay is dominated by the invasive floating macrophyte Trapa natans. Tivoli South Bay has a tidal range of 1.19 meters and a soft, silt/clay bottom type. The depth at the sampling location ranges from 0.5 to 2.5 meters. The non-tidal freshwater input to Tivoli South Bay includes that of a large upland tributary and a few small perennial streams. Tivoli North Bay (latitude 42° 02' 11.56464" N, longitude 73° 55' 31.16645" W) is a freshwater tidal marsh with emergent marsh vegetation dominated by the cattail Typha angustifolia. Tivoli North Bay has a tidal range of 1.19 meters, a soft, silt/clay bottom type, and a depth range from 0.5 to 3.0 meters at the sampling location. The non-tidal freshwater input to Tivoli North Bay includes that of a large upland tributary and a few small perennial streams. Saw Kill Creek (latitude 42° 01' 01.543" N, longitude 73° 54' 53.589" W) is the main tributary flowing into Tivoli South Bay. The Saw Kill Creek watershed is 26.6 square miles and land use within the watershed includes forested (51.1%), agricultural (25.8%), and urban (16.5%) areas. Saw Kill Creek is non-tidal and freshwater input to this tributary consists of smaller creeks in the watershed. At the sampling location Saw Kill Creek has a depth range of 0.5 to 2.0 meters, a discharge range of 2x10-5 to 1.2 m3/sec, and a rocky bottom type. Stony Creek (latitude 42° 02' 46.881" N, longitude 73° 54' 38.984" W) is the main tributary flowing into Tivoli North Bay. The Stony Creek watershed is approximately 23 square miles and is dominated by agricultural land use. Characteristics of Stony Creek at the sampling location include a solid rock bottom and a depth range of 0.5 to 1.5 meters. Stony Creek discharge is currently being determined. Since both Stony Creek and Saw Kill Creek are non-tidal, freshwater input to these tributaries consists of smaller creeks in their watersheds. This site was moved permanently to latitude 42° 02' 46.8816" N, longitude 73° 54' 38.984" W on 07/21/04. The entire Hudson River system south of the Troy Dam is affected by polychlorinated biphenyls (PCBs), and Tivoli North and South Bays have low sedimentary concentrations of PCBs. Nutrient inputs to the Tivoli Bays via the non-tidal tributaries are the main concern in terms of pollutants. High concentrations of nitrate and phosphate have previously been documented in both Saw Kill Creek and Stony Creek. Saw Kill Creek appears to be strongly influenced by residential land use practices. Stony Creek appears to be strongly influenced by a municipal wastewater treatment plant upstream of the sampling site. This highlights the importance of continued monitoring and identification of both non-point and point sources of pollution at these sites. 
Geographic Coverage
(Click for Interactive Map)
Spatial coordinates
| |
N: 42.36
|
|
S: 41.01
|
|
E: -73.76
|
|
W: -73.99
|
Data Set Citation
Dataset Originator/Creator:
William C. Nieder, Geofrey E. Eckerlin, Serena Ciparis
Dataset Title:
Hudson River (HUD) NERR Water Quality Metadata March - December 2004 Latest Update: May 2, 2005
Dataset Release Date:
2006-02-10
Data Presentation Form:
Unknown
Other Citation Details:
NA
Online Resource:
http://cdmo.baruch.sc.edu/
Parent DIF
This data set description is a member of a collection. The
collection is described in
noaanosnerr_d_nerrparent
Temporal Coverage
Start Date:
2004-03-01
Stop Date:
2004-12-31
Quality
ATTRIBUTE ACCURACY REPORT: Anomalous/Suspect Data March 2004 TN No data anomalies. TS No data anomalies SC No data anomalies SK A non-vented sonde was deployed at this site from 13:30 on 3/25/2004 to 11:30 on 4/19/2004 due to unavailability of a vented instrument. Differences in depth readings were observed upon deployment of a vented instrument on 04/19/2004. Depth data are not suspect, but the ... influence of barometric pressure on the depth readings between 3/25/2004 and 4/19/2004 should be considered. April 2004 TN Isolated high readings for both specific conductivity and salinity occurred on 04/15/2004. The readings do not appear to have been related to a problem with the probe and were likely due to a change in water column conditions at the time of sampling. The following data were left in: Station Code Date Time SpCond Sal hudtnwq 4/15/2004 21:30 000.38 00.2 TS Depth (level) readings included negative numbers and were flagged as outliers, but the other parameters were unaffected. The depth readings were considered near zero during low tide and the probes appear to have remained in the water. The following depth data were left in: STNCODE Date Time Date Time Depth hudtswq 04/05/2004 19:30 - 04/05/2004 21:00 -0.01 hudtswq 04/06/2004 08:30 - 04/06/2004 09:30 -0.02 hudtswq 04/06/2004 20:30 - 04/06/2004 21:00 -0.02 hudtswq 04/15/2004 04:30 - 04/15/2004 06:00 -0.01 hudtswq 04/15/2004 17:00 - 04/15/2004 17:30 -0.01 SC No data anomalies SK A non-vented sonde was deployed at this site from 13:30 on 3/25/2004 to 11:30 on 4/19/2004 due to unavailability of a vented instrument. Differences in depth readings were observed upon deployment of a vented instrument on 04/19/2004. Depth data are not suspect, but the influence of barometric pressure on the depth readings between 3/25/2004 and 4/19/2004 should be considered. A low temperature reading with corresponding high specific conductivity, salinity, and dissolved oxygen readings occurred on 04/17/2004. Subsequent readings were not affected and the anomalous readings were likely due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Temp SpCond Sal DOpct DOmgl hudskwq 4/17/2004 14:00 08.9 000.37 00.2 104.2 12.1 A subtle shift in the baseline of the turbidity readings began on 04/04/2004 and elevation of the baseline was evident on 4/13/2004. The cause of the shift is unknown, but does not appear to have been caused by a malfunction of the probe or blockage of the optic sensor. The probes were heavily fouled upon retrieval, and fouling may have contributed to the elevated turbidity readings. The following turbidity data are suspect, but were left in: Station Code Date Time Date cTime hudskwq 04/13/2004 19:00 - 04/19/2004 11:30 The sonde was heavily fouled with biogenic material upon retrieval at 11:30 on 04/19/2004 and differences in pH and dissolved oxygen readings between 11:30 and 12:00 (newly calibrated instrument) were observed. A distinct shift in the data was not evident, but fouling may have influenced the readings toward the end of the deployment. All data were left in. May 2004 TN An isolated high turbidity reading occurred on 05/26/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtnwq 5/26/2004 01:00 0437 TS No data anomalies SC An isolated high turbidity reading occurred on 05/11/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudscwq 5/11/2004 06:00 0348 Depth readings included negative numbers and were flagged as outliers, but the other parameters were unaffected. The probes appear to have remained in the water and the depth readings were considered near zero during low stream flow. The following depth data were left in: Station Code Date Time Date cTime hudscwq 05/18/2004 14:30 - 05/18/2004 19:30 hudscwq 05/22/2004 03:00 - 05/22/2004 04:30 hudscwq 05/22/2004 08:30 - 05/24/2004 20:30 hudscwq 05/31/2004 11:30 - 05/31/2004 23:30 SK A spike in depth (level) readings occurred at 14:30 on 05/08/2004, and readings were elevated thereafter. The sensor may have become blocked during the deployment. The following depth data were left in, but are suspect: Station Code Date Time Date Time hudskwq 05/08/2004 14:30 - 05/12/2004 10:00 June 2004 TN An isolated high turbidity reading occurred on 6/16/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtnwq 6/16/2004 21:00 0788 TS No data anomalies SC Depth readings included negative numbers and were flagged as outliers, but the other parameters were unaffected. The probes appear to have remained in the water and the depth readings were considered near zero during low stream flow. The following depth data were left in: Station Code Date Time Date Time hudscwq 06/01/2004 00:00 - 06/01/2004 06:00 hudscwq 06/01/2004 13:00 - 06/01/2004 14:00 Noisy specific conductivity and salinity readings occurred between 06/13/2004 and 06/16/2004. Subsequent readings were not affected and the anomalous readings were likely due to localized water column conditions. The following specific conductivity and salinity data are suspect, but were left in: Station Code Date Time Date Time hudscwq 06/13/2004 16:30 - 06/16/2004 11:30 Due to drought conditions and extremely low stream flow, the top half of the sonde was exposed for most of the sampling period. All probes appeared to have remained in the water, but it is possible that the depth sensor was not in the water for the entire deployment. The following depth data were marked as outliers and were left in, but are considered suspect: Station Code Date Time Date Time hudscwq 06/22/2004 15:30 - 06/22/2004 18:30 SK No data anomalies July 2004 TN An isolated high turbidity reading occurred on 7/26/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtnwq 7/26/2004 21:00 0255 TS An isolated high turbidity reading occurred on 7/24/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtswq 7/24/2004 05:30 0934 SC Due to drought conditions and extremely low stream flow, the top half of the sonde was exposed for most of the sampling period. All probes appeared to have remained in the water, but it is possible that the depth sensor was not in the water for the entire deployment. The following depth data were marked as outliers and were left in, but are considered suspect: Station Code Date Time Date Time hudscwq 07/04/2004 17:00 - 07/04/2004 18:00 hudscwq 07/04/2004 19:30 hudscwq 07/05/2004 01:30 - 07/05/2004 20:30 hudscwq 07/06/2004 03:00 - 07/06/2004 06:00 hudscwq 07/06/2004 12:30 - 07/06/2004 20:30 hudscwq 07/07/2004 08:30 - 07/08/2004 19:30 hudscwq 07/13/2004 16:30 - 07/16/2004 16:30 An isolated low dissolved oxygen reading occurred on 07/26/2004. Subsequent readings were unaffected and the anomalous reading was likely due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time DO_pct DO_mgl hudscwq 7/26/2004 14:30 039.9 03.6 SK No data anomalies August 2004 TN Upon retrieval of the datalogger on 08/02/2004, fouling was observed and the post-deployment specific conductivity reading was out of range (0.948). A shift in the data was observed (0.01 mS/cm) when the new datalogger recorded the first reading at 10:00 on 08/02/2004. However, the specific conductivity data collected from 17:00 on 07/13/2004 to 09:00 on 08/02/2004 did not appear to drift and are therefore not considered suspect. TS A single high reading for both specific conductivity and salinity occurred on 08/28/2004. The readings do not appear to have been related to a problem with the probe and were likely due to a change in water column conditions at the time of sampling. The following data were left in: Station Code Date Time SpCond Sal hudtswq 8/28/2004 11:00 000.46 00.2 Extremely low dissolved oxygen readings were occasionally recorded between 08/31/2004 and 09/11/2004, likely caused by invasive water chestnut (Trapa natans) at the site. Hypoxic conditions and possible exposure to hydrogen sulfide caused negative readings. At the advice of the datalogger’s manufacturer (YSI), the following negative readings (DO_pct and DO_mg/L) were changed to 0.0 in the database: Station Code Date Time DO_pct DO_mg/L hudtswq 08/31/2004 21:30 -004.3 -00.4 Since the aforementioned hypoxic events were short-lived, the manufacturer suggested that damage to the probe probably did not occur during the deployment. The data appear to be consistent, but the post-deployment dissolved oxygen reading was out of range (122.8). The following dissolved oxygen data were left in, but are suspect: Station Code Date Time Date Time hudtswq 08/31/2004 22:00 - 08/31/2004 23:30 SC No data anomalies SK Noisy turbidity readings occurred between 08/03/2004 and 08/05/2004. The readings were within the acceptable range of the probe and may have been due to localized water conditions driven by rain events on 8/01, 8/04, and 8/05. The following turbidity data are suspect, but were left in: Station Code Date Time Date Time hudskwq 08/03/2004 15:30 - 08/05/2004 12:00 Dissolved oxygen readings began to climb at 03:30 on 8/21/2004. This corresponds to rain events on 8/20 and 8/21, which is normal at this site. However, the dissolved oxygen readings did not return to baseline, the reading during the post-deployment calibration check was very high (116.2 %), and a difference was observed between the last reading of the deployment at 17:00 on 08/23/2004 (110 %) and the first reading of the newly calibrated instrument at 17:30 on 08/23/2004 (101.4 %). The membrane may have become compromised between 08/20/2004 and 08/23/2004, although a spike in dissolved oxygen readings due to a puncture is not evident. The following were left in, but are suspect: Station Code Date Time Date Time hudskwq 08/21/2004 03:30 - 08/23/2004 17:00 September 2004 TN An isolated high dissolved oxygen reading occurred on 9/9/2004. Subsequent readings were unaffected and the anomalous reading was likely due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time DO_pct DO_mgl hudtnwq 9/9/2004 12:00 143.9 12.3 High turbidity readings occurred on 09/18/2004 and the baseline turbidity remained elevated until 09/20/2004. An extremely heavy rain event occurred between 09/17/2004 and 09/18/2004 and the elevated turbidity readings are most likely a result of this event. The following turbidity data were left in: Station Code Date Time Date Time hudtnwq 09/18/2004 09:00 - 09/20/2004 21:00 A sudden drop in battery voltage occurred at 09:30 on 09/17/2004. The cause of the drop in voltage is unknown but data were not affected. All data were left in. TS Extremely low dissolved oxygen readings were occasionally recorded between 08/31/2004 and 09/11/2004, likely caused by invasive water chestnut (Trapa natans) at the site. Hypoxic conditions and possible exposure to hydrogen sulfide caused negative readings. At the advice of the datalogger’s manufacturer (YSI), the following negative readings (DO_pct and DO_mg/L) were changed to 0.0 in the database: Station Code Date Time DO_pct DO_mg/L hudtswq 09/08/2004 04:00 -000.8 -00.1 hudtswq 09/08/2004 15:00 -003.1 -00.3 hudtswq 09/09/2004 04:00 -001.1 -00.1 hudtswq 09/09/2004 04:30 -001.9 -00.2 hudtswq 09/10/2004 05:30 -009.3 -00.8 hudtswq 09/10/2004 06:00 -006.5 -00.6 hudtswq 09/10/2004 06:30 -004.5 -00.4 hudtswq 09/10/2004 07:00 -004.6 -00.4 hudtswq 09/10/2004 07:30 -003.7 -00.3 hudtswq 09/11/2004 06:00 -005.3 -00.5 hudtswq 09/11/2004 06:30 -005.8 -00.5 hudtswq 09/11/2004 07:00 -005.7 -00.5 Since the aforementioned hypoxic events were short-lived, the manufacturer suggested that damage to the probe probably did not occur during the deployment. The data appear to be consistent, but the post-deployment dissolved oxygen reading was out of range (122.8). The following dissolved oxygen data were left in, but are suspect: StationCode Date Time Date Time hudtswq 09/01/2004 00:00 09/14/2004 09:00 SC Isolated high dissolved oxygen readings occurred on 9/11/2004 and 09/12/2004. Subsequent readings were unaffected and the anomalous readings were likely due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time DO_pct DO_mgl hudscwq 9/11/2004 09:00 112.8 10.5 hudscwq 9/12/2004 17:00 117.2 10.7 SK Isolated high dissolved oxygen readings occurred at 06:30 on 9/21/2004 (115.7 %) and at 04:30 on 09/25/2004 (111.4 %). There was a difference between the last reading taken by this sonde at 13:30 on 10/04/2004 (109.9 %) and the first reading taken by the newly calibrated sonde at 14:00 on 10/04/2004 (103.4 %). The membrane may have become compromised on 09/21/2004. The following data were left in, but are suspect: Station Code Date Time Date Time hudskwq 9/21/2004 06:30 - 10/04/2004 13:30 October 2004 SK A shift in depth (level) readings (0.3 m) occurred when a new sonde was deployed at 14:00 on 10/04/2004. This lasted for three deployments, until 14:00 on 12/07/2004. The reason for the shift is unknown, as three different calibrated, vented sondes were used during this time period, and readings from these sondes were consistent. The data were left in, and changes in depth during the three deployments due to events are considered to be correct. However, the shift in depth readings should be taken into consideration. Dissolved oxygen readings began to climb at 18:00 on 10/18/2004. This corresponds to rain events on 10/18 and 10/19, which is normal at this site. However, the dissolved oxygen readings did not return to baseline, the reading during the post-deployment calibration check was high (104.7 %) and a difference was observed between the last reading of the deployment at 15:30 on 11/02/2004 (110.9 %)and the first reading of the newly calibrated instrument at 16:30 on 11/02/2004 (103.1 %). A spike in dissolved oxygen readings due to a puncture was not evident and the reason for the climb is unknown. The following were left in, but are suspect: Station Code Date Time Date Time hudskwq 10/18/2004 18:00 - 11/02/2004 15:30 November 2004 TN A single high turbidity reading occurred on 11/1/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtnwq 11/1/2004 07:00 0349 TS No data anomalies SC No data anomalies SK A shift in depth (level) readings (0.3 m) occurred when a new sonde was deployed at 14:00 on 10/04/2004. This lasted for three deployments, until 14:00 on 12/07/2004. The reason for the shift is unknown, as three different calibrated, vented sondes were used during this time period. The data were left in, and changes in depth during the three deployments due to events are considered to be correct. However, the shift in depth readings should be taken into consideration. A shift in pH readings (0.4 pH units) was observed upon deployment of a newly calibrated sonde at 15:30 on 11/17/2004. The pH probe on the sonde retrieved at 14:30 on 11/17/2004 was out of range during the post-deployment calibration check and subsequently died. A distinct shift in pH readings was not observed during deployment. The following pH data were left in, but are suspect: Station Code Date Time Date Time hudskwq 11/2/2004 16:30 - 11/17/2004 14:30 December 2004 TN A single high turbidity reading occurred on 12/16/2004. The reading was within the acceptable range of the probe and may have been due to localized water column conditions. The following data are suspect, but were left in: Station Code Date Time Turb hudtnwq 12/16/2004 06:00 0433 TS Depth (level) readings included negative numbers and were flagged as outliers, but the other parameters were unaffected. The depth readings were considered near zero during low tide and the probes appear to have remained in the water. The following depth data were left in: Station Code Date Time Date Time hudtswq 12/18/2004 00:30 - 12/18/2004 01:00 SC Depth readings included negative numbers and were flagged as outliers, but the other parameters were unaffected. The probes appear to have remained in the water and the depth readings were considered near zero during low stream flow. The following depth data were left in: Station Code Date Time Date Time hudscwq 12/13/2004 12:00 - 12/13/2004 15:30 SK A shift in depth (level) readings (0.3 m) occurred when a new sonde was deployed at 14:00 on 10/04/2004. This lasted for three deployments, until 14:00 on 12/07/2004. The reason for the shift is unknown, as three different calibrated, vented sondes were used during this time period. The data were left in, and changes in depth during the three deployments due to rain events are considered to be correct. However, the shift in depth readings should be taken into consideration. A non-vented sonde was deployed at this site from 14:30 on 12/07/2004 through 00:00 on 12/31/2004 due to unavailability of a vented instrument. Differences in depth readings were observed upon deployment of the non-vented instrument. Depth data are not suspect, but the influence of barometric pressure on the depth readings between 12/07/2004 and 12/31/2004 should be considered. There was a difference between the final dissolved oxygen reading of the sonde retrieved at 14:00 on 12/07/2004 (105.5 %) and the first reading of the newly calibrated sonde deployed at 14:30 on 12/07/2004 (96.3 %). The reason for the difference is unclear, as the readings did not drift during deployment and the probe was in range during the post-deployment calibration check. The switch from a vented to a non-vented sonde may account for the difference. The data are not suspect. Post deployment information Post-deployment readings for un-cleaned probes in standard solutions (Dissolved oxygen (DO) = 100%, pH = 7.00, Depth = 0.0, Turbidity = 0.0, Specific Conductivity = 1.0). Deployed Retrieved DO_% pH Depth (m) Turb SpCond TN 3/25/2004 4/19/2004 99.4 7.03 -0.213 1.3 0.947 TN 4/19/2004 5/13/2004 105.2 7.05 0.023 1.5 1 TN 5/13/2004 5/27/2004 106 6.75 -0.181 2 0.982 TN 5/27/2004 6/8/2004 104.1 7.06 0.125 0.4 0.982 TN 6/8/2004 6/23/2004 100.5 7.04 -0.077 1.4 0.987 TN 6/23/3004 7/13/2004 94.4 7.03 -0.061 0.9 0.991 TN 7/13/2004 8/2/2004 92.3 7.09 -0.02 0.5 0.948 TN 8/2/2004 8/25/2004 95 7.02 0.077 0.7 0.996 TN 8/25/2004 9/14/2004 101.9 7.12 0.014 0.5 0.946 TN 9/14/2004 10/1/2004 103.1 7.12 -0.07 0.4 0.979 TN 10/1/2004 10/15/2004 112.3 7.05 -0.234 2.2 0.993 TN 10/15/2004 11/3/2004 102.5 7.01 0.169 0.5 0.99 TN 11/3/2004 11/18/2004 94.3 6.94 0.002 1.2 0.988 TN 11/18/2004 12/15/2004 110.5 7.01 0.075 0.1 0.986 TN 12/15/2004 12/30/2004 103.2 7.13 0.019 0.8 0.993 TS 3/25/2004 4/19/2004 101 6.99 -0.452 -0.8 0.945 TS 4/19/2004 5/12/2004 TS 5/12/2004 5/27/2004 98.7 7.09 0.123 0.9 0.993 TS 5/27/2004 6/23/2004 101.5 7.05 0.252 -3 0.999 TS 6/23/2004 7/13/2004 109.7 7.15 -0.004 0.8 0.996 TS 7/13/2004 8/3/2004 104.4 7.03 0.005 -0.3 0.973 TS 8/3/2004 8/25/2004 104.8 7.09 -0.001 1 0.985 TS 8/25/2004 9/14/2004 122.8 7.12 0.002 -0.5 0.998 TS 9/14/2004 10/1/2004 103.4 7.02 -0.036 0.2 0.988 TS 10/1/2004 10/15/2004 102.8 7.1 0 1 0.994 TS 10/15/2004 11/4/2004 98.8 7.04 0.005 0 0.975 TS 11/4/2004 11/18/2004 100 7.13 4 -1.3 0.993 TS 11/18/2004 12/8/2004 122 0.271 0.5 1.005 TS 12/8/2004 12/23/2004 99.2 7.03 0.003 -1.1 0.973 SC 3/25/2004 4/19/2004 102.3 7.05 -0.225 0.7 0.983 SC 4/19/2004 5/12/2004 106.9 7.27 0.03 0.003 0.975 SC 5/12/2004 6/3/2004 109.8 7.1 -0.117 -0.7 0.989 SC 6/3/2004 6/23/2004 96.2 7.12 -0.032 -1.1 1 SC 6/23/2004 7/12/2004 77.1 7.13 0.046 2.8 0.995 SC 7/12/2004 7/21/2004 96.6 7.12 -0.055 0.6 0.994 SC 7/21/2004 8/3/2004 105.5 7.19 -0.062 0.5 0.993 SC 8/3/2004 8/25/2004 98.2 7.11 0.149 0.7 0.99 SC 8/25/2004 9/13/2004 103.2 7.15 -0.058 0.1 0.982 SC 9/13/2004 10/4/2004 102.5 7.1 -0.1 0.3 1 SC 10/4/2004 10/27/2004 106.5 7.03 0.097 0.8 0.994 SC 10/27/2004 11/18/2004 100.1 7.12 -0.047 0.5 0.983 SC 11/18/2004 12/8/2004 100.5 7.03 0.014 -0.2 1.028 SC 12/8/2004 12/30/2004 103.7 7.1 0.204 -0.4 0.978 SK 3/25/2004 4/19/2004 92.2 6.92 -0.237 0.9 0.943 SK 4/19/2004 5/12/2004 105.9 7.07 0.148 1 0.972 SK 5/12/2004 5/27/2004 99.8 7.01 0.007 0.7 0.983 SK 5/27/2004 6/22/2004 103.8 7.06 -0.003 1 0.991 SK 6/22/2004 7/12/2004 98.6 7.09 6.62 0.4 0.994 SK 7/12/2004 8/2/2004 103.1 7.12 -0.153 -0.3 0.999 SK 8/2/2004 8/23/2004 116.2 7.1 0.002 0.6 0.993 SK 8/23/2004 9/13/2004 103.8 7.09 -0.001 0.1 0.964 SK 9/13/2004 10/4/2004 107.5 7.03 -0.4 -0.1 0.993 SK 10/4/2004 11/2/2004 104.7 7.1 0.047 -2 0.985 SK 11/2/2004 11/17/2004 99.8 7.25 -0.284 -2 1.007 SK 11/17/2004 12/7/2004 102.4 7.03 -0.24 -1.5 0.994 SK 12/7/2004 1/6/2005 93.6 7.09 -0.154 0 0.995 LOGICAL CONSISTENCY REPORT: NACOMPLETENESS REPORT: Data collection period YSI 6-series datalogger sampling at Saw Kill Creek (SK) and Tivoli South Bay (TS) began in May 1995. Sampling at Tivoli North Bay (TN) began in July 1996 but ceased in 1997-1998 due to instrument exposure at low tide. In 1999, an alternate site was established for TN and sampling began again in July of 1999. Sampling began at Stony Creek (SC) in April 2002. Sampling is continuous from April through December but is not conducted from approximately mid-December through the end of March due to winter storms and ice on the Hudson River and the tributaries. A YSI 6600 Extended Deplyment System (EDS) sonde was deployed at Tivoli South Bay starting on 04/08/2003. The EDS differs from the other 6600 instruments in that a large wiper is positioned centrally to the probes and wipes them prior to every sample. This wiper requires that the pH probe not have a guard over the glass bulb, and a new flat pH probe was deployed on the EDS starting 09/25/2003. Otherwise, the EDS sonde is identical to the other 6600 dataloggers. Beginning 03/25/2004 an EDS unit was also deployed in Saw Kill Creek. Dates and times for site deployments and retrievals: Site Deployment Deployment Retrieval Retrieval Date Time Date Time mm/dd/yy hh:mm mm/dd/yy hh:mm TN 3/25/2004 12:30 4/19/2004 9:00 TN 04/19/2004 10:00 05/13/2004 14:00 TN 05/13/2004 14:30 05/27/2004 14:00 TN 05/27/2004 15:00 06/08/2004 12:30 TN 06/08/2004 13:00 06/23/2004 13:00 TN 06/23/3004 13:30 07/13/2004 16:00 TN 07/13/2004 17:00 08/02/2004 09:00 TN 08/02/2004 10:00 08/25/2004 14:00 TN 08/25/2004 15:00 09/14/2004 09:00 TN 09/14/2004 09:30 10/01/2004 10:30 TN 10/01/2004 11:00 10/15/2004 08:30 TN 10/15/2004 11:00 11/03/2004 11:30 TN 11/03/2004 12:00 11/18/2004 11:30 TN 11/18/2004 15:00 12/15/2004 11:00 TN 12/15/2004 11:30 12/30/2004 10:30 TS 03/25/2004 12:00 04/19/2004 09:30 TS 04/19/2004 10:00 05/12/2004 12:30 TS 05/12/2004 13:00 05/27/2004 10:30 TS 05/27/2004 13:30 06/23/2004 11:00 TS 06/23/2004 11:30 07/13/2004 07:30 TS 07/13/2004 09:30 08/03/2004 10:30 TS 08/03/2004 11:00 08/25/2004 14:00 TS 08/25/2004 14:30 09/14/2004 09:00 TS 09/14/2004 09:30 10/01/2004 10:30 TS 10/01/2004 11:30 10/15/2004 10:30 TS 10/15/2004 11:00 11/04/2004 14:30 TS 11/04/2004 15:00 11/18/2004 11:00 TS 11/18/2004 15:00 12/08/2004 14:30 TS 12/08/2004 15:30 12/23/2004 13:30 SC 03/25/2004 13:00 04/19/2004 10:00 SC 04/19/2004 10:30 05/12/2004 09:30 SC 05/12/2004 10:00 06/03/2004 08:30 SC 06/03/2004 09:00 06/23/2004 10:00 SC 06/23/2004 11:00 07/12/2004 11:00 SC 07/12/2004 11:30 07/21/2004 11:00 SC 07/21/2004 11:30 08/03/2004 10:00 SC 08/03/2004 11:00 08/25/2004 09:30 SC 08/25/2004 10:00 09/13/2004 14:00 SC 09/13/2004 14:30 10/04/2004 14:00 SC 10/04/2004 14:30 10/27/2004 07:30 SC 10/27/2004 08:00 11/18/2004 15:00 SC 11/18/2004 16:30 12/08/2004 14:30 SC 12/08/2004 15:00 12/30/2004 11:00 SK 03/25/2004 13:30 04/19/2004 11:30 SK 04/19/2004 12:00 05/12/2004 10:00 SK 05/12/2004 10:30 05/27/2004 07:30 SK 05/27/2004 10:30 06/22/2004 12:30 SK 06/22/2004 13:00 07/12/2004 11:30 SK 07/12/2004 12:00 08/02/2004 13:00 SK 08/02/2004 13:30 08/23/2004 17:00 SK 08/23/2004 17:30 09/13/2004 08:30 SK 09/13/2004 09:30 10/04/2004 13:30 SK 10/04/2004 14:00 11/02/2004 15:30 SK 11/02/2004 16:30 11/17/2004 14:30 SK 11/17/2004 15:30 12/07/2004 14:00 SK 12/07/2004 14:30 01/06/2005 14:30 Deleted Data March 2004 No deleted data April 2004 SC Significant rain events and subsequently high stream flow caused the location of the sonde cage on the streambed to change during deployment and depth readings were not consistent. The following depth data were removed: Station Code Date Time Date Time hudscwq 04/01/2004 21:30 - 4/06/2004 09:30 Turbidity readings became erratic, including readings outside of the acceptable range for the probe (>1000 NTU), starting on 04/05/2004. This may have been due to blockage of the optical sensor or the probe may have been out of the water. The following turbidity data were deleted: Station Code Date Time Date Time hudscwq 04/05/2004 01:30 - 04/06/2004 09:30 The probes were out of the water and exposed to the air after high stream flow subsided. The following data (all parameters) were deleted: Station Code Date Time Date Time hudscwq 04/06/2004 10:00 - 04/19/2004 10:00 May 2004 SK An anomalous turbidity reading occurred on 5/26/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudskwq 5/26/2004 22:30 1825 June 2004 TN An anomalous turbidity reading occurred on 6/16/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudtnwq 6/16/2004 11:30 1589 SK The deployed sonde had been sent to the manufacturer for circuit board repairs and for investigation of apparent problems with the depth sensor. The problems were supposedly corrected and prior to deployment the depth calibrated properly. However, depth data were incorrect from the start of deployment and fluctuations between –7.0 and 7.0 m were recorded, which are impossible at this site. The following depth data were deleted: Station Code Date Time Date Time hudskwq 06/22/2004 13:00 - 06/30/2004 23:30 July 2004 SC An anomalous turbidity reading occurred on 7/2/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudscwq 07/02/2004 07:00 1491 Turbidity readings were very noisy, with frequent spikes outside of the acceptable range of the probe (>1000 NTU), and the sonde was heavily fouled with algae, sediment and biogenic material upon retrieval. The anomalous turbidity readings were probably due to fouling/blocked probe. The following turbidity data were deleted: Station Code Date Time Date Time hudscwq 07/07/2004 19:00 - 07/12/2004 11:00 Due to very low stream flow the sonde was out of the water and the probes were exposed to air. The following data (all parameters) were deleted: Station Code Date Time Date Time hudscwq 07/16/2004 17:00 - 7/21/2004 11:00 Noisy turbidity readings occurred, including readings outside of the acceptable range of the probe (>1000 NTU). The noisy readings started on 07/23/2004, which corresponds to a significant rain event. The optical sensor likely became blocked by debris in the stream. The following turbidity data were removed: Station Code Date cTime Date cTime hudscwq 07/23/2004 18:00 - 07/26/2004 04:00 Noisy turbidity readings occurred, including readings outside of the acceptable range of the probe (>1000 NTU). The noisy readings did not appear to be related to an event. Upon the post-deployment sensor check and recalibration, the turbidity probe appeared to be functioning properly. The optical sensor likely became blocked by debris in the stream. The following turbidity data were removed: Station Code Date Time Date Time hudscwq 07/31/2004 17:30 - 07/31/2004 23:30 SK The deployed sonde had been sent to the manufacturer for circuit board repairs and for investigation of apparent problems with the depth sensor. The problems were supposedly corrected and prior to deployment the depth calibrated properly. However, depth data were incorrect from the start of deployment and fluctuations between –7.0 and 7.0 m were recorded, which are impossible at this site. The following depth data were deleted: Station Code Date Time Date Time hudskwq 07/01/2004 00:00 - 07/12/2004 11:30 August 2004 SC Noisy turbidity readings occurred, including readings outside of the acceptable range of the probe (>1000 NTU). The noisy readings did not appear to be related to an event. Upon the post-deployment sensor check and recalibration, the turbidity probe appeared to be functioning properly. The optical sensor likely became blocked by debris in the stream. The following turbidity data were removed: Station Code Date Time Date Time hudscwq 08/01/2004 00:00 - 08/02/2004 13:00 Noisy turbidity readings occurred, including readings outside of the acceptable range of the probe (>1000 NTU). The noisy readings did not appear to be related to an event. Upon the post-deployment sensor check and recalibration, the turbidity probe appeared to be functioning properly. The optical sensor likely became blocked by debris in the stream. The following turbidity data were removed: Station Code Date Time Date Time hudscwq 08/07/2004 05:00 - 08/08/2004 05:00 Anomalous turbidity readings occurred on 08/10/2004. The readings were outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudscwq 8/10/2004 16:30 1506 hudscwq 8/10/2004 17:00 1507 hudscwq 8/10/2004 18:00 1506 hudscwq 8/10/2004 18:30 1506 hudscwq 8/10/2004 21:00 1507 Anomalous turbidity readings occurred on 08/21/2004. The readings were outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudscwq 8/21/2004 15:00 1525 hudscwq 8/21/2004 23:00 1515 September 2004 TS An anomalous turbidity reading occurred on 9/03/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudtswq 9/3/2004 23:00 1628 SC Noisy turbidity readings occurred, including readings outside of the acceptable range of the probe (>1000 NTU). The noisy readings did not appear to be related to an event, but a fallen tree was on top of the sonde cage upon retrieval. The optical sensor likely became blocked by debris from the tree. The following turbidity data were removed: Station Code Date Time Date Time hudscwq 09/05/2004 09:00 - 09/08/2004 18:30 Significant rain events and subsequently high stream flow caused the location of the sonde cage on the streambed to change during deployment and when the water receded, the probes were exposed to air. The following data (all parameters) were deleted: Station Code Date Time Date Time hudscwq 09/20/2004 02:30 - 09/30/2004 23:30 October 2004 TN An anomalous turbidity reading occurred on 10/3/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudtnwq 10/3/2004 12:30 1359 The sonde was found on the riverbank, out of the water, on 10/15/2004. The data indicated that the sonde was out of the water (removed by a vandal) starting at 13:30 on 10/09/2004. The following data (all parameters) were deleted: Station Code Date Time Date Time hudtnwq 10/09/2004 13:30 - 10/15/2004 08:30 An anomalous turbidity reading occurred on 10/15/2004. The reading was outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudtnwq 10/15/2004 20:30 1788 TS Anomalous turbidity readings occurred on 10/12/2004 and 10/13/2004. The readings were outside the acceptable range of the probe (>1000 NTU) and most likely resulted from blockage of the optical sensor. The following data were deleted: Station Code Date Time Turb hudtswq 10/12/2004 23:00 1574 hudtswq 10/13/2004 04:00 1551 SC Significant rain events and subsequently high stream flow caused the location of the sonde cage on the streambed to change during deployment and when the water receded, the probes were exposed to air. The following data (all parameters) were deleted: Station Code Date Time Date Time hudscwq 10/01/2004 00:00 - 10/04/2004 14:00 A shift in the baseline of the turbidity readings occurred on 10/22/2004. The cause of the shift is unknown, but does not appear to have been caused by a malfunction of the probe or blockage of the optic sensor. However, the last turbidity reading of the deployment, recorded at 07:30 on 10/27/2004 was 0150 while the first turbidity reading of the next deployment, recorded at 08:00 on 10/27/2004, was 0002. The shift in the baseline may have been caused by debris in the sonde cage, which were removed upon deployment of the newly calibrated instrument. The following turbidity data appear to be inaccurate and were deleted: Station Code Date Time Date cTime hudscwq 10/22/2004 00:00 - 10/27/2004 07:30 November 2004 TN Dissolved oxygen readings climbed steadily from the onset of deployment at 15:00 on 11/18/2004 until retrieval at 11:00 on 12/15/2004. The exact reason for this is unknown, but it was likely due to a problem with the membrane, the KCL solution, or the sonde. The following dissolved oxygen data were deleted: Station Code Date Time Date Time hudtnwq 11/18/2004 15:00 - 11/30/2004 23:30 TS The depth sensor on the sonde malfunctioned starting at 04:00 on 11/9/2004, resulting in fluctuations between very shallow (0.08 m) and very deep (11.74 m) readings, followed by depth readings >10 m for an extended period of time. As the maximum water depth at the site is 2 m, these data are clearly a result of a problem with the sensor. Depth sensor malfunction may have been caused by vandalism of the PVC tube, which was evident upon retrieval. All other parameters appear to be consistent. Therefore, the following depth data were deleted: Station Code Date Time Date Time hudtswq 11/09/2004 04:00 - 11/18/2004 11:00 The sonde was out of the water during an extreme low tide on 11/26/2004. The following data (all parameters) were deleted: Station Code Date Time Date Time hudtswq 11/26/2004 06:00 - 11/26/2004 08:00 Dissolved oxygen readings climbed steadily from the onset of deployment at 15:00 on 11/18/2004 until retrieval at 14:30 on 12/08/2004. The exact reason for this is unknown, but it was likely due to a problem with the membrane, the KCL solution, or the sonde. The following dissolved oxygen data were deleted: Station Code Date Time Date Time hudtswq 11/18/2004 15:00 - 11/30/2004 23:30 SC On 11/25/2004 at 02:00 temperature readings suddenly dropped and subsequent readings were –10oC, indicating a malfunction of the temperature probe. Shifts in temperature dependent measurements were observed. The following data (all parameters) were deleted: Station Code Date Time Date Time hudscwq 11/25/2004 02:00 - 12/1/2004 09:30 SK Dissolved oxygen readings climbed steadily from the onset of deployment at 16:30 on 11/02/2004 until retrieval at 14:30 on 11/17/2004. The exact reason for this is unknown, but it was likely due to a problem with the membrane, the KCL solution, or the sonde. The following dissolved oxygen data were deleted: Station Code Date Time Date Time hudskwq 11/02/2004 16:30 - 11/17/2004 14:30 December 2004 TN Dissolved oxygen readings climbed steadily from the onset of deployment at 15:00 on 11/18/2004 until retrieval at 11:00 on 12/15/2004. The exact reason for this is unknown, but it was likely due to a problem with the membrane, the KCL solution, or the sonde. The following dissolved oxygen data were deleted: Station Code Date Time Date Time hudtnwq 12/01/2004 00:00 - 12/15/2004 11:00 TS Dissolved oxygen readings climbed steadily from the onset of deployment at 15:00 on 11/18/2004 until retrieval at 14:30 on 12/08/2004. The exact reason for this is unknown, but it was likely due to a problem with the membrane, the KCL solution, or the sonde. The following dissolved oxygen data were deleted: Station Code Date Time Date Time hudtswq 12/01/2004 00:00 - 12/08/2004 14:30 SC Significant rain events occurred on 11/28/2004 and 12/1/2004. The resulting high streamflow and debris pushed the sonde cage out of the water. The sonde was out of the water upon retrieval on 12/8/2004. The following data (all parameters) were deleted: StationCode Date Time Date Time hudscwq 12/1/2004 10:00 - 12/8/2004 14:30 Missing Data Data are missing due to equipment failure, maintenance/calibration of equipment, elimination of obvious outliers, or elimination of data due to calibration problems (both pre- and post-deployment). For more details on deleted data, see the Deleted Data (Section 10). Missing data are documented in this section. If more details about missing data are required, contact the Research Coordinator at the site submitting the data. April - May 2004 TS The circuit board of the datalogger malfunctioned during deployment causing the sonde to lose power and stop collecting data at 16:00 on 05/03/2004. All data collected prior to this loss of power were not included in the data set due to obvious inconsistencies caused by the malfunction (ie depth readings of –9.0 m). The following data are missing: Station Code Date Time Date Time hudtswq 04/19/2004 10:00 - 5/12/2004 12:30 June – October 2004 TS Data is missing for the following date and time. Datalogger failed to take reading, reason unknown. Station Code Date Time hudtswq 07/01/2004 22:00 November – December 2004 TS The sonde was deployed without an active pH sensor. A problem with the sensor was evident prior to deployment, but the other sonde used at the site had a malfunctioning depth sensor, and at a tidal site depth data were considered to be more important. The following pH data are missing: Station Code Date Time Date Time hudtswq 11/18/2004 15:00 - 12/08/2004 14:30 LINEAGE/PROCESS STEP: PROCESS DESCRIPTION: Additional Description: Entry verification The Centralized Data Management Office re-processed all SWMP water data collected from 1995-2002 to include an identifying station code (three letter reserve code, two letter sampling site code and data type code), a four digit year date stamp (mm/dd/yyyy) and a corrected time column (hh:mm). With the new format, the use of periods to denote deleted or missing data has been abandoned. Hence, all periods contained in the SWMP water data collected prior 2003 were removed and left blank. Deployment data (.DAT files) are uploaded from the YSI 6600 data logger to a Personal Computer (IBM compatible). Data plots are produced and examined and erroneous data are detected using the PC6000 or EcoWatch software from YSI. Notes are made of any unusual data during that deployment. Files are exported from EcoWatch in a comma-delimited format (.CSV) and opened in Microsoft Excel for pre-processing with the EQWin format macro that was developed by the CDMO. The macro ensures parameters are in the correct order, converts depth in feet to depth in meters, formats the data to the correct number of decimal points, inserts an identifying station code, inserts a corrected time column, allows the user to remove any pre- and post-deployment data from the file. Where deployment overlap occurs between files, the data produced by the newly calibrated sonde is accepted as being the most accurate. The pre-processed data are then copied into EQWin water.eqi file. The station and parameters are verified against the database, the file configurations are checked, the date and time formats are verified, and data are checked for duplication. The data are then updated to the EQWin database and are checked for outliers (data outside the acceptable range for the sensors) and large changes in the data using database queries and graphs of each parameter. The query results and graphs are printed and the data are reviewed. Anomalous data are either flagged and documented in Section 11 or deleted and documented in Section 12. EQWin is also used to generate statistics, view graphs, create customized queries and reports of the data, cross query the water, weather and nutrient data and finally export the data to the CDMO. Persons responsible for data verification are the Research Assistant and the Research Coordinator. PROCESS DATE: 20060210
Access Constraints
Data collected in conjunction with the National Estuarine Research Reserve System's (NERRS) System-wide Monitoring Program (SWMP) is considered public information. Please see site for further information: http://cdmo.baruch.sc.edu/aboutdata.htm
DISTRIBUTION LIABILITY:
Distribution NOAA Ocean and Coastal Resource Management Data Ownership and Dissemination ... Policy for the NERRS National Monitoring Program: Data collected in conjunction with the National Estuarine Research Reserve System's (NERRS) National Monitoring Program is considered public information. The principal investigators (PIs) responsible for collecting data at each NERRS site must process the data using Estuarine Reserve Division (ERD) approved quality assurance and quality control (QA/QC) protocols. The PI transmits the QA/QC processed data to ERD or an ERD approved Centralized Data Management Office (CDMO) in accordance with the standard rules for application to oceanographic data sets (NOAA Administrative Order 216-101). The submission schedule determined by the CDMO assumes an adequate and uninterrupted funding for the monitoring effort at each site, therefore the data processing and the transmission timetable may be adjusted accordingly. An awardee may own a copyright on the publication of the processed data developed or bought under a Federal assistance award. The Federal awarding agency reserves a royalty-free, nonexclusive, and irrevocable license to reproduce, publish, or otherwise use, and to authorize others to use, for Federal government purposes, the copyright in any work developed under an award, or any rights of copyright purchased by an awardee with Federal assistance support (15 C.F.R. 24.34). Any such publication will include a notice identifying the award and recognizing the license rights of the government under this clause. This paragraph will have no force and effect for the processed data not published by the recipient. The data set enclosed within this package/transmission is only as good as the quality assurance and quality control procedures outlined by the enclosed metadata reporting statement. The user bears all responsibility for its subsequent use/misuse in any further analyses or comparisons. The Federal government does not assume liability to the Recipient or third persons, nor will the Federal government reimburse or indemnify the Recipient for its liability due to any losses resulting in any way from the use of this data. NERR water quality data and metadata can be obtained from the Research Coordinator at the individual NERR site (please see Section 2.2-1 Principal investigators and contact persons), from the Data Manager at the Centralized Data Management Office (please see personnel directory under the general information link on the CDMO home page) and online at the CDMO home page http://cdmo.baruch.sc.edu/. Data are available in text tab-delimited format, Microsoft Excel spreadsheet format and comma-delimited format.
Use Constraints
The principal investigator (PI) listed in the enclosed metadata retains the right to be fully credited for having collected and processed the data. Please see the site for further information: http://cdmo.baruch.sc.edu/aboutdata.htm
Data Set Progress
COMPLETE
Distribution
Distribution Format:
Ascii File, Formatted For Text Attributes, Declared Format (ASCII)NA
Fees:
Data is available at no charge.
Personnel
Role:
DIF AUTHOR
Role:
TECHNICAL CONTACT
Contact Address:
New York State Department of Environmental Conservation
City:
Annandale
Province or State:
NY
Postal Code:
12504
Country:
USA
Creation and Review Dates
DIF Creation Date:
2008-08-01
Last DIF Revision Date:
2008-10-10
|
[
Update this Record
]
|
Updating this record requires registration.
|
|
