Hudson River (HUD) NERR Water Quality Metadata (April - Dec. 2003) Latest Update: April 12, 2004
Entry ID:
CDMO_hudwq04-12.03m
|
[
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. 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.
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, Tivoli North Bay, Saw Kill Creek and Stony Creek. 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' 45.556" N, longitude 73° 54' 40.237" 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. Like Saw Kill Creek, Stony Creek is non-tidal and freshwater input is via smaller creeks in the watershed. 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. 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. This highlights the importance of continued monitoring and identification of non-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,Serena Ciparis,
Dataset Title:
Hudson River (HUD) NERR Water Quality Metadata (April - Dec. 2003) Latest Update: April 12, 2004
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:
2003-04-01
Stop Date:
2003-12-31
Quality
ATTRIBUTE ACCURACY REPORT: Anomalous/Suspect Data April SC Stony Creek sampling for 2003 began at 14:30:00 on April 8. Turbidity readings were very low including zero and negative numbers, but the values were within the detection limits of the probe. The following turbidity data were left in: Date Time 04/21/2003 14:30:00 04/21/2003 15:00:00 04/21/2003 15:30:00 04/21/2003 16:00:00 04/21/2003 ... 16:30:00 04/21/2003 17:00:00 04/21/2003 17:30:00 04/25/2003 16:00:00 A new procedure for calibrating turbidity, with the calibration cup 2" below the bulkhead, was implemented 04/29/2003 TN Tivoli North Bay sampling for 2003 began at 13:00:00 on April 8. No data anomalies A new procedure for calibrating turbidity, with the calibration cup 2" below the bulkhead, was implemented 04/29/2003 SK Saw Kill Creek sampling for 2003 began at 09:30:00 on April 9. An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 04/17/2003 08:00:00 1616 Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limits of the probe. The following turbidity data were left in: Date Time Date Time 04/09/2003 09:30:00 - 04/09/2003 21:30:00 04/09/2003 22:30:00 04/10/2003 00:00:00 - 04/10/2003 02:00:00 04/10/2003 00:30:00 04/10/2003 01:30:00 - 04/10/2003 20:00:00 04/10/2003 21:30:00 04/10/2003 22:30:00 04/10/2003 23:30:00 04/11/2003 00:00:00 04/11/2003 07:30:00 - 04/11/2003 11:00:00 04/11/2003 15:30:00 - 04/11/2003 17:00:00 04/12/2003 11:00:00 04/12/2003 12:00:00 04/13/2003 08:00:00 04/13/2003 10:30:00 - 04/13/2003 12:00:00 04/13/2003 14:00:00 04/13/2003 16:00:00 04/13/2003 16:30:00 04/13/2003 18:00:00 04/14/2003 11:00:00 04/14/2003 12:00:00 04/14/2003 13:30:00 04/14/2003 14:30:00 04/14/2003 16:00:00 04/14/2003 18:30:00 04/15/2003 11:00:00 04/15/2003 13:30:00 04/15/2003 15:00:00 04/19/2003 22:30:00 04/19/2003 23:30:00 04/20/2003 08:00:00 A new procedure for calibrating turbidity, with the calibration cup 2" below the bulkhead, was implemented 04/29/2003 TS Tivoli South Bay sampling for 2003 began at 11:30:00 on April 8. 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 tide. The following depth data were left in: Date Time Date Time 04/16/2003 19:30:00 - 04/16/2003 20:30:00 Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limit of the probe. The following turbidity data were left in: Date Time Date Time 04/13/2003 10:00:00 04/13/2003 11:00:00 04/22/2003 16:30:00 04/22/2003 17:30:00 04/23/2003 07:30:00 04/24/2003 16:00:00 04/24/2003 19:30:00 - 04/24/2003 21:30:00 04/25/2003 06:00:00 04/25/2003 06:30:00 04/25/2003 07:30:00 - 04/25/2003 13:00:00 04/25/2003 20:30:00 - 04/25/2003 22:30:00 04/26/2003 07:00:00 - 04/26/2003 10:00:00 04/26/2003 19:30:00 - 04/26/2003 23:30:00 04/27/2003 08:00:00 - 04/27/2003 11:30:00 04/27/2003 20:30:00 - 04/27/2003 23:30:00 04/28/2003 00:00:00 04/28/2003 09:00:00 04/28/2003 09:30:00 04/28/2003 11:00:00 04/28/2003 11:30:00 04/28/2003 22:00:00 - 04/28/2003 23:30:00 04/29/2003 09:30:00 - 04/29/2003 13:00:00 04/29/2003 21:30:00 04/30/2003 00:00:00 04/30/2003 01:00:00 A new procedure for calibrating turbidity, with the calibration cup 2" below the bulkhead, was implemented 04/29/2003 May SC An anomalous dissolved oxygen reading occurred and it appears to have been related to a rain event. The following data were left in, but are suspect: Date Time DO (%) DO (mg/L) 05/12/2003 00:30:00 67.4 6.8 TN An anomalous dissolved oxygen reading occurred, in conjunction with a sudden drop in battery voltage. Subsequent readings appeared to be unaffected. The following dissolved oxygen data were deleted: Date Time DO (%) DO (mg/L) 05/09/2003 08:30:00 130.4 13.3 An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 05/17/2003 18:00:00 1258 SK An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 05/26/2003 11:00:00 1676 A spike in dissolved oxygen occurred at 16:00:00 on 05/26/2003 and subsequent readings were noisy. However, the spike corresponded with a rain event and multiple rain events occurred throughout the rest of the deployment. It is unclear whether the noisy data were caused by the rain events or a problem with the dissolved oxygen membrane. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 05/26/2003 16:00:00 - 05/31/2003 23:30:00 TS Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limit of the probe. The following turbidity data were left in: Date Time 05/02/2003 14:30:00 05/10/2003 21:30:00 05/19/2003 16:00:00 05/20/2003 17:00:00 An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 05/11/2003 02:00:00 2057 05/12/2003 15:30:00 2060 June 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: Date Time Date Time 06/01/2003 04:30:00 - 06/14/2003 10:30:00 06/22/2003 12:30:00 - 06/24/2003 13:00:00 The probes were out of the water and exposed to the air after a rain event and subsequently high stream flow caused the sonde cage to be pushed completely out of the water. The following data (all parameters) were deleted: Date Time Date Time 06/24/2003 13:30:00 - 06/30/2003 13:30:00 TN An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 06/20/2003 03:30:00 1107 SK A spike in dissolved oxygen occurred at 16:00:00 on 05/26/2003 and subsequent readings were noisy. However, the spike corresponded with a rain event and multiple rain events occurred throughout the rest of the deployment. It is unclear whether the noisy data were caused by the rain events or a problem with the dissolved oxygen membrane. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 06/01/2003 00:00:00 - 06/13/2003 15:00:00 An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 06/02/2003 18:00:00 1127 Anomalous turbidity readings (>1000 NTU) occurred over an extended period of time and were probably caused by a blocked probe. The following turbidity data were deleted: Date Time Date Time 06/05/2003 11:30:00 - 06/13/2003 15:00:00 TS An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 06/24/2003 17:00:00 1954 July SC An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 07/09/2003 15:00:00 1154 An anomalous dissolved oxygen reading occurred, but subsequent readings were unaffected. The following dissolved oxygen data were deleted: Date Time DO (%) DO (mg/L) 07/08/2003 17:30:00 049.3 04.1 During the post-deployment calibration check on 07/30/2003 a biofilm was observed on the membrane of the dissolved oxygen probe, the probe was out of range, and a shift in dissolved oxygen readings was apparent. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 07/22/2003 16:00:00 - 07/30/2003 14:30:00 TN No data anomalies SK On 07/30/2003 the dissolved oxygen reading for the post-deployment calibration check was very low (92.8) and the probe subsequently failed. Catastrophic failure during deployment was not obvious and the data were left in, but the following dissolved oxygen data are suspect: Date Time Date Time 07/17/2003 15:30:00 - 07/30/2003 14:00:00 TS Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limit of the probe. The following turbidity data were left in: Date Time 07/29/2003 14:00:00 07/30/2003 14:30:00 07/31/2003 15:30:00 An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 07/25/2003 05:00:00 2095 07/28/2003 00:30:00 2121 August SC No data anomalies TN During the post-deployment calibration check on 08/28/2003 a zebra mussel was attached to the membrane of the dissolved oxygen probe, the probe was out of range, and a shift in dissolved oxygen readings was apparent. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 08/13/2003 11:00:00 - 08/28/2003 08:30:00 SK An anomalous dissolved oxygen reading occurred. Subsequent readings were unaffected and the reading may have been related to rain events. The following data were left in, but are suspect: Date Time DO (%) DO (mg/L) 08/08/2003 03:30 69.8 6.2 TS Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limit of the probe. The following turbidity data were left in: Date Time 08/21/2003 20:30:00 08/23/2003 04:30:00 08/24/2003 23:00:00 September 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: Date Time Date Time 09/02/2003 07:00:00 - 09/04/2003 08:30:00 09/23/2003 09:30:00 - 09/30/2003 23:30:00 The post-deployment dissolved oxygen reading for the sonde retrieved on 10/06/2003 was outside the specification range and there was obvious drift in the data. The drift may have been associated with a concurrent large decrease in water temperature, but the ultimate cause is unknown. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 09/28/2003 06:30:00 - 09/30/2003 23:30:00 TN No data anomalies SK No data anomalies The post-deployment dissolved oxygen reading for the sonde retrieved on 09/12/2003 was outside the specification range and there was obvious drift in the data. The ultimate cause of this drift is unknown. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 09/04/2003 04:30:00 - 09/12/2003 08:30:00 TS No data anomalies October 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: Date Time Date Time 10/01/2003 00:00:00 - 10/06/2003 10:00:00 The post-deployment dissolved oxygen reading for the sonde retrieved on 10/06/2003 was outside the specification range and there was obvious drift in the data. The drift may have been associated with a concurrent large decrease in water temperature, but the ultimate cause is unknown. The following dissolved oxygen data were left in, but are suspect: Date Time Date Time 10/01/2003 06:30:00 - 10/06/2003 10:00:00 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. The following depth data were left in: Date Time Date Time 10/15/2003 00:30:00 - 10/15/2003 03:00:00 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: Date Time Date Time 10/27/2003 19:00:00 - 10/31/2003 23:30:00 TN An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 10/01/2003 02:00:00 1470 10/08/2003 10:00:00 1971 SK An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 10/22/2003 11:00:00 1086 10/29/2003 16:00:00 1172 TS Turbidity readings were very low including values of zero and negative numbers, but the values were within the detection limit of the probe. The following turbidity data were left in: Date Time 10/09/2003 12:30:00 10/09/2003 13:00:00 10/09/2003 20:30:00 10/10/2003 01:00:00 10/11/2003 01:30:00 10/14/2003 03:30:00 10/17/2003 17:00:00 - 10/17/2003 19:00:00 10/18/2003 19:00:00 10/19/2003 18:30:00 10/19/2003 19:00:00 10/20/2003 07:30:00 - 10/20/2003 08:30:00 10/20/2003 09:30:00 The probes were out of the water and exposed to the air during low tide. The following data (all parameters) were deleted: 10/16/2003 00:30:00 - 10/16/2003 01:00:00 November 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: Date Time Date Time 11/01/2003 00:00:00 - 11/02/2003 21:00:00 The probes were out of the water and exposed to the air after high stream flow subsided. The following data (all parameters) were deleted: Date Time Date Time 11/02/2003 21:30:00 - 11/05/2003 10:00:00 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. The following depth data were left in: Date Time Date Time 11/13/2003 02:00:00 - 11/13/2003 18:00:00 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: Date Time Date Time 11/20/2003 00:00:00 - 11/21/2003 11:00:00 TN An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 11/21/2003 07:00:00 1834 SK No data anomalies TS Depth 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: Date Time Date Time 11/08/2003 20:00:00 - 11/08/2003 20:30:00 An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 11/08/2003 07:00:00 1987 The probes were out of the water and exposed to the air during extremely low tides. The following data (all parameters) were deleted: Date Time Date Time 11/13/2003 22:00:00 - 11/15/2003 13:00:00 Due to exposure of the probe to air, there was a shift in dissolved oxygen readings. The following dissolved oxygen data were deleted: Date Time Date Time 11/15/2003 13:30:00 - 11/25/2003 09:30:00 Due to exposure of the probe to air, the pH probe was out of range during the post-deployment calibration check. There was not an obvious shift in pH readings and the data were left in, but the following pH data are suspect: Date Time Date Time 11/15/2003 13:30:00 - 11/25/2003 09:30:00 December SC No data anomalies. The sonde was pulled from the water for the rest of the year at 10:00:00 on 12/09/2003 due to winter conditions. TN An anomalous turbidity reading occurred and it was probably due to a blocked probe. The following turbidity data were deleted: Date Time Turb 12/02/2003 20:30:00 1866 Data began to shift, possibly due to the formation of ice crystals. The following data (all parameters) were left in, but are suspect: Date Time Date Time 12/03/2003 00:30:00 - 12/12/2003 11:00:00 The sonde was pulled from the water for the rest of the year at 11:00:00 on 12/12/2003 due to winter conditions. SK No data anomalies The sonde was pulled from the water for the rest of the year at 09:00:00 on 12/08/2003 due to winter conditions. TS 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 depth readings were considered near zero during low tide. The following depth data were left in: Date Time Date Time 12/02/2003 02:00:00 - 12/02/2003 04:00:00 The probes were out of the water and exposed to the air during low tide. The following data (all parameters) were deleted: Date Time Date Time 12/03/2003 02:00:00 - 12/03/2003 05:00:00 Depth readings were anomalous, most likely due to ice in the PVC tube and/or a frozen depth cable. The following depth data were deleted: Date Time Depth 12/03/2003 05:30:00 18.90 12/03/2003 06:00:00 18.94 12/03/2003 06:30:00 19.12 12/03/2003 07:00:00 19.20 12/03/2003 07:30:00 18.88 12/03/2003 08:00:00 9.86 Upon retrieval of the sonde, the depth cable was frozen and depth was out of range for the post-deployment calibration check. The following depth data were left in, but are suspect: Date Time Date Time 12/03/2003 08:30:00 - 12/05/2003 09:00:00 The sonde was pulled from the water for the rest of the year at 09:00:00 on 12/05/2003 due to winter conditions. Post deployment information Post-deployment readings for un-cleaned probes in standard solutions (Specific Conductivity = 1.0; Dissolved oxygen (DO) = 100% saturation; pH = 7.00; Turbidity = 0.0). SC Deploy Date; DO; pH; Sp Cond; Turb 04/08/2003; 98.6; 7.08; 1.015; -1.3 04/29/2003; 98.3; 7.09; 0.994; 0.1 05/15/2003; 98.1; 7.10; 1.005; -0.4 06/16/2002; 95.6; 7.09; 1.003; -0.2 06/30/2003; 98.8; 7.09; 1.002; -0.3 07/16/2003; 85.2; 7.00; 0.998; -1.1 07/30/2003; 100.8; 7.05; 0.996; 0.6 08/19/2003; 96.1; 7.05; 0.991; 0.5 09/04/2003; 99.9; 7.03; 0.998; 0.6 09/22/2003; 105.0; 7.10; 0.967; 0.4 10/06/2003; 98.5; 7.15; 0.985; 0.1 10/22/2003; 93.0; 7.08; 0.991; 1.8 11/05/2003; 96.5; 7.12; 0.982; 0.2 11/21/2003; 108.3; 7.07; 0.984; 0.3 TN Deploy Date; DO; pH; Sp Cond; Turb 04/08/2003; 99.5; 7.05; 0.973; -1.0 04/30/2003; 98.9; 6.90; 0.986; 1.8 05/15/2003; 98.4; 7.04; 1.008; 0.2 06/04/2003; 107.9; 7.08; 0.995; 0.3 06/17/2003; 99.4; 7.06; 0.999; 0.2 07/01/2003; 99.1; 7.09; 0.996; -0.1 07/16/2003; 98.6; 7.08; 1.016; 0.1 07/30/2003; 101.5; 7.10; 0.987; 0.028 08/13/2003; 105.0; 7.10; 0.985; 0.4 08/28/2003; 101.2; 7.08; 0.993; 0.5 09/09/2003; 104.2; 7.10; 0.981; 0.2 09/25/2003; 101.1; 7.11; 0.974; 0.4 10/09/2003; 102.0; 7.07; 0.986; 1.0 10/23/2003; 102.0; 7.09; 0.983; 1.6 11/10/2003; 104.4; 7.04; 0.997; 0.4 11/26/2003; 105.7; 7.10; 0.972; 1.7 SK Deploy Date; DO; pH; Sp Cond; Turb 04/09/2003; 99.8; 7.12; 1.000; -.06 04/29/2003; 99.9; 7.13; 1.078; 0.0 05/14/2003; 104.9; 7.12; 0.995; 0.3 06/16/2003; 103.8; 7.07; 0.988; 0.7 06/30/2003; 101.0; 7.12; 0.995; 0.0 07/17/2003; 92.8; 7.01; 0.997; 0.4 07/30/2003; 103.6; 7.07; 0.998; 0.2 08/15/2003; 100.5; 7.10; 0.973; 0.1 08/29/2003; 106.5; 7.04; 0.991; 0.2 09/12/2003; 98.5; 7.09; 0.998; 0.5 09/25/2003; 104.0; 7.07; 0.999; -0.8 10/10/2003; 99.0; 7.09; 0.980; 0.4 10/22/2003; 100.2; 7.09; 0.980; -0.2 11/05/2003; 102.0; 7.03; 0.996; 0.6 11/25/2003; 97.0; 7.06; 1.021; 0.7 TS Deploy Date; DO ; pH ; Sp Cond ; Turb 04/08/2003; 103.2; 7.03; 0.996; -6.7 04/30/2003; 102.7; 7.09; 1.000; 1.3 05/21/2003; 96.5; 7.14; 0.984; 0.0 06/17/2003; 105.3; 7.07; 0.993; 0.6 07/01/2003; 100.3; 7.03; 1.003; 0.3 07/08/2003; 105.1; 7.02; 0.998; 0.4 07/29/2003; 102.0; 7.08; 0.994; -0.3 08/13/2003; 102.9; 7.03; 0.996; -0.2 08/28/2003; 102.3; 6.96; 0.999; -0.5 09/09/2003; 106.0; 7.02; 0.999; 0.7 09/25/2003; 100.2; 7.02; 0.989; 0.5 10/09/2003; 99.9; 7.07; 0.998; -0.2 10/22/2003; 98.8; 7.03; 0.999; -0.6 11/07/2003; 109.2; 7.26; 1.001; 0.2 11/25/2003; 102.0; 7.16; 1.004; 0.6 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 nstruments 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. 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 SC 04/08/03 14:30:00 04/29/03 14:00:00 SC 04/29/03 14:30:00 05/15/03 10:00:00 SC 05/15/03 10:30:00 06/16/03 13:30:00 SC 06/16/03 14:00:00 06/30/03 13:30:00 SC 06/30/03 14:00:00 07/16/03 14:00:00 SC 07/16/03 15:00:00 07/30/03 14:30:00 SC 07/30/03 15:00:00 08/19/03 12:00:00 SC 08/19/03 12:30:00 09/04/03 08:30:00 SC 09/04/03 09:00:00 09/22/03 10:00:00 SC 09/22/03 10:30:00 10/06/03 10:00:00 SC 10/06/03 10:30:00 10/22/03 08:30:00 SC 10/22/03 09:00:00 11/05/03 10:00:00 SC 11/05/03 10:30:00 11/21/03 11:00:00 SC 11/21/03 11:30:00 12/09/03 10:00:00 TN 04/08/03 13:00:00 04/30/03 08:00:00 TN 04/30/03 08:30:00 05/15/03 08:30:00 TN 05/15/03 09:00:00 06/04/03 10:30:00 TN 06/04/03 11:00:00 06/17/03 09:00:00 TN 06/17/03 09:30:00 07/01/03 09:00:00 TN 07/01/03 10:00:00 07/16/03 10:30:00 TN 07/16/03 11:00:00 07/30/03 09:30:00 TN 07/30/03 10:00:00 08/13/03 10:30:00 TN 08/13/03 11:00:00 08/28/03 08:30:00 TN 08/28/03 09:00:00 09/09/03 08:00:00 TN 09/09/03 08:30:00 09/25/03 08:30:00 TN 09/25/03 09:00:00 10/09/03 07:30:00 TN 10/09/03 08:00:00 10/23/03 17:00:00 TN 10/23/03 17:30:00 11/10/03 09:00:00 TN 11/10/03 09:30:00 11/26/03 09:30:00 TN 11/26/03 10:00:00 12/12/03 11:00:00 SK 04/09/03 09:30:00 04/29/03 13:00:00 SK 04/29/03 13:30:00 05/14/03 14:30:00 SK 05/14/03 15:00:00 06/16/03 09:30:00 SK 06/16/03 10:00:00 06/30/03 10:00:00 SK 06/30/03 11:00:00 07/17/03 14:30:00 SK 07/17/03 15:30:00 07/30/03 14:00:00 SK 07/30/03 14:30:00 08/15/03 12:00:00 SK 08/15/03 12:30:00 08/29/03 08:00:00 SK 08/29/03 08:30:00 09/12/03 08:30:00 SK 09/12/03 09:00:00 09/25/03 14:00:00 SK 09/25/03 14:30:00 10/10/03 10:30:00 SK 10/10/03 11:00:00 10/22/03 13:30:00 SK 10/22/03 14:00:00 11/05/03 10:30:00 SK 11/05/03 16:30:00 11/25/03 12:00:00 SK 11/25/03 15:30:00 12/08/03 09:00:00 TS 04/08/03 11:30:00 04/30/03 08:00:00 TS 04/30/03 11:00:00 05/21/03 12:30:00 TS 05/21/03 15:30:00 06/17/03 09:30:00 TS 06/17/03 14:30:00 07/01/03 10:00:00 TS 07/01/03 14:30:00 07/08/03 10:00:00 TS 07/08/03 12:30:00 07/29/03 08:00:00 TS 07/29/03 13:30:00 08/13/03 10:30:00 TS 08/13/03 14:00:00 08/28/03 08:30:00 TS 08/28/03 12:30:00 09/09/03 08:30:00 TS 09/09/03 15:30:00 09/25/03 08:30:00 TS 09/25/03 11:30:00 10/09/03 07:30:00 TS 10/09/03 11:00:00 10/22/03 09:00:00 TS 10/22/03 14:30:00 11/07/03 10:00:00 TS 11/07/03 15:30:00 11/25/03 09:30:00 TS 11/25/03 12:30:00 12/05/03 09:00:00 Deleted Data Missing Data Missing data are denoted by a period in the data set. Periods were later removed for data dissemination purposes and left blank. 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 Anomalous 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 TS The sonde was not logging data at random times throughout deployments from 04/08/2003 until 06/17/2003 due to contamination in the battery compartment. The problem was corrected on 06/17/2003. Data missing for the following dates and times: 04/19/2003 00:00:00 04/20/2003 00:00:00 – 00:30:00, 08:00:00 – 08:30:00, 11:30:00 – 13:30:00, 18:30:00 04/21/2003 00:00:00, 01:00:00 – 01:30:00, 13:30:00 – 15:00:00 04/28/2003 17:30:00 04/29/2003 22:00:00 04/30/2003 20:30:00 – 21:30:00 May TS The sonde was not logging data at random times throughout deployments from 04/08/2003 until 06/17/2003 due to contamination in the battery compartment. The problem was corrected on 06/17/2003. Data missing for the following dates and times: 05/01/2003 10:00:00 – 10:30:00, 21:30:00 – 22:30:00 05/02/2003 11:00:00, 22:30:00 05/15/2003 22:00:00 05/16/2003 11:00:00 05/20/2003 15:00:00 05/21/2003 01:00:00 05/29/2003 10:00:00, 20:00:00 – 20:30:00 05/31/2003 21:30:00, 22:30:00 June SC The sonde was deployed but the program stopped before the instrument was exchanged with another. The following data are missing: Date Time Date Time 06/14/2003 11:00:00 06/16/2003 13:30:00 SK The sonde was deployed but the program stopped before the instrument was exchanged with another. The following data are missing: Date Time Date Time 06/13/2003 15:30:00 - 06/16/2003 09:30:00 TS The sonde was not logging data at random times throughout deployments from 04/08/2003 until 6/17/2003 due to contamination in the battery compartment. The problem was corrected on 6/17/2003. Data missing for the following dates and times: 06/01/2003 00:00:00 – 00:30:00, 11:30:00, 22:30:00 – 06/02/2003 00:30:00 06/02/2003 06:00:00, 07:00:00, 08:00:00 – 08:30:00, 12:00:00 06/03/2003 12:30:00, 13:30:00, 19:00:00, 20:00:00, 23:30:00 – 06/04/2003 00:30:00 06/04/2003 13:00:00 – 13:30:00 06/05/203 00:30:00 – 01:30:00, 11:00:00, 14:30:00 06/06/2003 01:00:00 – 01:30:00, 14:30:00 – 15:00:00, 16:00:00 – 16:30:00 06/07/2003 02:30:00, 03:30:00, 10:00:00, 11:30:00, 16:00:00 – 17:30:00 06/08/2003 03:00:00, 17:00:00 – 18:00:00 06/09/2003 03:30:00 – 04:00:00, 05:00:00 – 05:30:00, 17:30:00 – 18:30:00, 19:30:00 06/10/2003 06:30:00, 19:30:00 – 20:00:00 06/11/2003 08:30:00, 10:0:00, 19:30:00 06/12/2003 08:00:00 - -09:00:00, 20:00:00 – 21:30:00 06/13/2003 09:00:00 – 10:00:00, 20:30:00, 21:30:00 – 22:00:00 06/14/2003 06:00:00 – 1:30:00, 15:30:00, 23:00:00 06/15/2003 11:30:00 – 12:00:00, 22:00:00, 23:30:00 – 06/16/2003 23:30:00 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. The CDMO cdmomac3.xls macro is used to verify all water quality data. This macro allows the user to automatically format column widths to the correct number of decimal places based on YSI sensor specifications. The macro also allows the user to QA/QC each datalogger generated file for missing data points, fill all cells that do not contain data with periods, and find all data points that fall outside the range of what the datalogger is designed to measure (outliers). The CDMO import.xls macro allows PC users with 30-minute data to automatically create a monthly Excel file from a two-week deployment and insert periods for missing data. Periods were later removed for data dissemination purposes and left blank. In November 1999, graphing capabilities were added to this macro allowing users to produce single parameter and missing data point graphs on a monthly basis. Questionable data are either deleted or identified in section II.10. Persons responsible for data verification are the Research Coordinator and Research Assistant. 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 principle 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 has three (3) months from the date of data collection to process the data, and then three (3) months from the date of data processing to transmit 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 schedule reflected below 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. Unpublished intellectual property owned and developed by the recipient with federal assistance funds, i.e., processed data, will not be officially disseminated to the public for a period of one (1) year from the date of data processing. After one (1) year the QA/QC processed data will be made officially available to the general public on the Internet by the CDMO. However, if the data are requested pursuant to the Freedom of Information Act, the Government is required to release any data which are transferred to the Government by the recipient under the award. 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. NOAA/ERD retains the right to analyze, synthesize and publish summaries of the NERRS System-wide Monitoring Program data. The PI retains the right to be fully credited for having collected and processed the data. Following academic courtesy standards, the PI and NERR site where the data were collected will be contacted and fully acknowledged in any subsequent publications in which any part of the data is used. Manuscripts resulting from this NOAA/OCRM-supported research that are produced for publication in open literature, including refereed scientific journals, will acknowledge that the research was conducted under an award from the Estuarine Reserves Division, Office of Ocean and Coastal Resource Management, National Ocean Service, National Oceanic and Atmospheric Administration. 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:
TECHNICAL CONTACT
Role:
DIF AUTHOR
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.
|
|
