Shark River Slough Total Phosphorus Concentration Compliance Tracking Sample Clauses

Shark River Slough Total Phosphorus Concentration Compliance Tracking. The daily flows through the individual Shark River Slough structures and S334 from July 2001 through June 2003 are presented in Figure 4a. Since mid- November 2002 inflows to Shark River Slough have been through S333 and S12D. Beginning in mid-January 2003 a large proportion of the flow in the L29 Canal was released from the system through S334 due to above-average rainfall. This condition lasted until mid-June. The relationship between the sum of the daily flows at Shark River Slough structures and corresponding flow-weighted mean total phosphorus concentrations for individual sampling events is presented in Figure 4b. Values for Water Years 2001 and 2002 follow the strong inverse relationship between flow and total phosphorus concentration expected for waters entering the Park through Shark River Slough. However, during the un-seasonal rainfall conditions that occurred from February through June 2003, total phosphorus concentrations were greater and more variable, 9 to 18 ppb, than observed previously when flows were less than 500 cfs. S333 S12C S12A S12D S12B S334 8000 7000 A 6000 5000 4000 3000 2000 1000 0 4500 50 4000 B 45 3500 40 3000 35 30 2500 25 2000 20 1500 15 1000 10 500 5 0 0 Flow (cfs) FWMC Phosphorus Jun-03 May-03 Apr-03 Mar-03 Feb-03 Jan-03 Dec-02 Nov-02 Oct-02 Sep-02 Aug-02 Jul-02 Jun-02 May-02 Apr-02 Mar-02 Feb-02 Jan-02 Dec-01 Nov-01 Oct-01 Sep-01 Aug-01 Jul-01 Jun-03 May-03 Apr-03 Mar-03 Feb-03 Jan-03 Dec-02 Nov-02 Oct-02 Sep-02 Aug-02 Jul-02 Jun-02 May-02 Apr-02 Mar-02 Feb-02 Jan-02 Dec-01 Nov-01 Oct-01 Sep-01 Aug-01 Jul-01 Total Phosphorus (ppb) Daily Flow (cfs) Daily Flow (cfs) Figure 4. A. Daily flows into Shark River Slough by structure. B. The relationship between daily flow at Shark River Slough structures and the corresponding flow-weighted mean total phosphorus concentrations for individual sampling events. Taylor Slough and the Coastal Basins Under the Consent Decree, a single total phosphorus long-term limit of 11 ppb, to be met by December 31, 2006, was set for the two points of inflow to Taylor Slough (S332 and S175) and the inflow point to the Coastal Basins (S18C). The 11 ppb limit applies to the water year ending September 30. C-111 Project Structures and Detention Areas Beginning in August 1999, structure S332D, a new pump station constructed by the U.S. Army Corps of Engineers (USACE), began operation. The structure is adjacent to spillway S174 and pumps water from the L31N canal into the L31W canal. The S332D and S174 ...
Sample 1See All (4)
AutoNDA by SimpleDocs
Shark River Slough Total Phosphorus Concentration Compliance Tracking. 12-Month Period Ending On Total Period Flow Flow Weighted Mean Total Phosphorus (ppb) Interim Limit (ppb) Long Term Limit (ppb) Percent of Sampling Events Greater than 10 ppb (Kac-ft) Effective 10/1/2003 Effective 12/31/2006 (%) Guideline Observed 31-Oct-03 921.8 9.7 9.9 8.3 43.3 50.0 30-Nov-03 1001.5 9.5 9.6 7.9 41.4 46.2 31-Dec-03 1076.8 9.1 9.4 7.6 40.1 46.2 31-Jan-04 1049.0 9.2 9.4 7.7 40.4 46.2 29-Feb-04 1033.9 9.1 9.5 7.8 40.7 44.4 31-Mar-04 1036.7 8.9 9.4 7.7 40.7 37.0 30-Apr-04 1012.9 9.0 9.5 7.9 41.2 40.7 31-May-04 980.2 9.0 9.7 8.0 41.9 40.7 30-Jun-04 942.5 8.7 9.8 8.2 42.8 36.0 31-Jul-04 832.0 8.4 10.2 8.8 45.5 27.3 30-Sep-04* 704.4 8.4 10.8 9.4 49.0 35.0 31-Oct-04 727.8 8.9 10.7 9.3 48.3 35.0 30-Nov-04 760.3 8.7 10.6 9.1 47.4 33.3 31-Dec-04 738.5 9.0 10.7 9.2 48.0 35.0 31-Jan-05 717.3 9.0 10.7 9.3 48.6 38.9 28-Feb-05 709.8 9.1 10.8 9.4 48.8 37.5 31-Mar-05** 698.3 9.2 10.8 9.4 49.2 46.7 30-Apr-05 732.6 9.1 10.7 9.3 48.2 46.7 31-May-05 767.1 10.0 10.5 9.1 47.3 50.0 30-Jun-05 836.0 10.5 10.2 8.7 45.4 55.6 31-Jul-05 1054.7 10.5 9.4 7.7 40.3 55.0 30-Sep-05* 1345.9 9.4 9.4 7.6 40.1 42.9 Notes: 1) Highlighted rows indicate the end of the water year (Oct 1st to Sept 30th)
Sample 1
Shark River Slough Total Phosphorus Concentration Compliance Tracking. Notes: Bold italicized values exceeded the guideline percentages. The daily flows through the individual Shark River Slough structures from October 2002 through September 2004 are presented in Figure 5. During dry periods inflows to Shark River Slough have been through S333 and S12D. The relationship between the sum of the daily flows at Shark River Slough structures and corresponding flow-weighted mean total phosphorus concentrations for individual sampling events is presented in Figure 6. Values follow the strong inverse relationship between flow and total phosphorus concentration expected for waters entering the Park through Shark River Slough.
Sample 1
Shark River Slough Total Phosphorus Concentration Compliance Tracking. Notes: Bold italicized values exceeded the guideline percentages. The daily flows through the individual Shark River Slough structures from July 2002 through June 2004 are presented in Figure 5. The total inflow to Shark River Slough during the reporting quarter, April 2004 through June 2004 was 28,500 acre-feet. Almost all of that flow was through S333 and S12D only. The total flow was relatively small compared to the previous 10 year average, 101,700 acre-feet for the same quarter, April through June. The relationship between the sum of the daily flows at Shark River Slough structures and corresponding flow-weighted mean total phosphorus concentrations for individual sampling events is presented in Figure 6. Values follow the strong inverse relationship between flow and total phosphorus concentration expected for waters entering the Park through Shark River Slough. The current quarter sampling event flow-weighted mean concentrations ranged from 11.0 to 17.6 ppb.
Sample 1
Shark River Slough Total Phosphorus Concentration Compliance Tracking. Notes: Bold italicized values exceeded the guideline percentages. The daily flows through the individual Shark River Slough structures from July 2003 through June 2005 are presented in Figure 5. Since mid-December 2004 inflows to Shark River Slough have been through mostly S333 and S12D. A large proportion of this water in the L29 Canal entered through S333 and was released from the system through S334. This condition lasted until mid-June. Structures S12A, S12B and S12C were closed, except S12A on March 21 through 23, 2005, until June 22, 2005 in accordance with Interim Operational Plan (IOP) for protection of the Cape Sable Seaside Sparrow. The relationship between the sum of the daily flows at Shark River Slough structures and corresponding flow-weighted mean total phosphorus concentrations for individual sampling events is presented in Figure 6. Values follow the strong inverse relationship between flow and total phosphorus concentration expected for waters entering the ENP through Shark River Slough.
Sample 1
Shark River Slough Total Phosphorus Concentration Compliance Tracking. The daily flows through the individual Shark River Slough structures and S334 from October 2001 through December 2003 are presented in Figure 4A. Since mid-November 2002 inflows to Shark River Slough have been through S333 and S12D. Beginning in mid-January 2003 a large proportion of the flow in the L29 Canal was released from the system through S334 due to above-average rainfall. This condition lasted until mid-June. The relationship between the sum of the daily flows at Shark River Slough structures and corresponding flow-weighted mean total phosphorus concentrations for individual sampling events is presented in Figure 4B. Values for Water Years 2002 and 2003 follow the strong inverse relationship between flow and total phosphorus concentration expected for waters entering the Park through Shark River Slough. However, during the unseasonable rainfall conditions that occurred from February through May 2003, total phosphorus concentrations were greater and more variable, 9 to 18 ppb, than observed previously when flows were less than 500 cfs. From June through September 2003, increasing flows resulted in gradually decreasing total phosphorus concentrations from 18 ppb to 9 ppb. The concentration continued to decrease to 5.5 ppb by the end of December 2003.
Sample 1
Shark River Slough Total Phosphorus Concentration Compliance Tracking. Table 2 also presents the moving flow-weighted mean concentrations for each 12-month period beginning in July 2000 as well as the corresponding interim and long-term total phosphorus concentration limits, calculated using the 12-month period flow. For the 12-month periods ending in April, May and June 2002, the flow- weighted mean total phosphorus concentrations were 10.5, 10.6 and
Sample 1
AutoNDA by SimpleDocs

Related to Shark River Slough Total Phosphorus Concentration Compliance Tracking

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx Communications has requested an Unbundled Loop and BellSouth uses Integrated Digital Loop Carrier (IDLC) systems to provide the local service to the end user and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx Communications. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will make alternative arrangements available to Xxxx Communications (e.g. hairpinning).

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Unbundled Loop Concentration 2.8.5.1 Upon the Effective Date of this Amendment, the Unbundled Loop Concentration (ULC) element will no longer be offered by BellSouth and no new orders for ULC will be accepted. Any existing ULCs that were provisioned prior to the Effective Date of this Amendment will be grandfathered at the rates set forth in the Parties’ interconnection agreement that was in effect immediately prior to this Amendment and may remain connected, maintained and repaired according to BellSouth’s TR73600 until such time as they are disconnected by Advantage Group, or BellSouth provides ninety (90) calendar days notice that such ULC must be terminated.

  • Signaling Link Transport 9.2.1 Signaling Link Transport is a set of two or four dedicated 56 kbps transmission paths between Global Connection-designated Signaling Points of Interconnection that provide appropriate physical diversity.

  • Direct Trunked Transport 7.3.2.1 Either Party may elect to purchase direct trunked transport from the other Party.

Time is Money Join Law Insider Premium to draft better contracts faster.