Layer: EAA Regulatory Model Boundary: South Current (Water Year 2019 thru present) (ID: 6)

Name: EAA Regulatory Model Boundary: South Current (Water Year 2019 thru present)

Display Field: NAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>Chapter 40E-63, F.A.C., outlines the performance measure and compliance methodology for determining whether the EAA Basin is meeting the annual phosphorus load requirements described in the EFA. The EAA Basin is required to collectively maintain TP loads in runoff that are, at a minimum 25% below the historical pre-BMP baseline period of WY1980–WY1988. The EAA_South_Current describes the extent and location of boundaries of the lands represented by the pre-BMP baseline TP load dataset that currently contribute to runoff. The lands that historically discharged to Lake Okeechobee, are not included. This permit layer is updated as lands are taken out of production and no longer contributing to EAA runoff.<A href="https://www.flrules.org/gateway/ChapterHome.asp?Chapter=40E-63">See website</A>Table 1 summarizes the historical changes to the EAA Basin measured TP runoff load calculations since the first year of compliance assessment. For the purposes of this methodology, measured TP load in runoff refers to the permittees’ collective offsite discharges impacted by BMPs for each water year based on data collected by SFWMD at the basin boundary structures. Table 1. Historical timeline of changes to the EAA Basincompliance calculations.<TABLE><TBODY><TR><TD>Period</TD><TD>Area (acres)a</TD><TD>Changes of the EAA Basin Compliance Calculations</TD></TR><TR><TD>1980-1988</TD><TD>523,721</TD><TD>WY1980-WY1988 defined the base period for the EAA Basin runoff TP load calculation. The structures used for the base period were S-352, S-5A, S-2, S-6, S-7, S-150, S-3, S-8, G-88, and G-136. G-136 data is only available for a portion of the base period. </TD></TR><TR><TD ROWSPAN="2">WY1996</TD><TD ROWSPAN="2">523,721</TD><TD>This was the first year of compliance measurement for the EAA Basin. To account for water supply deliveries to the Holeyland Wildlife Management Area via the Miami Canal, structure G-200 was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structure G-250 became a new EAA Basin discharge structure with the construction of the Everglades Nutrient Removal Project and was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>WY1997</TD><TD>523,551</TD><TD>Structure G-600 became a new EAA Basin discharge structure with the construction of STA-6 and was added to the EAA Basin outflow for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD>WY1998</TD><TD>522,703</TD><TD>During the construction of STA-6, the discharge bypass canals G-605 and G-606 discharged into the EAA Basin and were added as EAA Basin inflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD ROWSPAN="4">WY2000</TD><TD ROWSPAN="4">512,013</TD><TD>Structures G-344A-D became EAA Basin inflow structures with the construction of STA-5 and were added as EAA Basin inflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structures G-349B and G-350B became new EAA Basin discharge structures with the construction of STA-5 and were added as EAA Basin outflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structure G-328 became a new EAA Basin discharge structure with the construction of STA-2 and was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD>Structure G-250 was located outside of the EAA Basin boundary with the construction of STA-1 West (STA-1W) and was removed from the EAA Basin runoff TP load calculation.</TD></TR><TR><TD ROWSPAN="2">WY2001</TD><TD ROWSPAN="2">507,719</TD><TD>Structures G-404 and G-357 were constructed between the Miami Canal and L-4 Canal near S-8, to supply water to the Big Cypress Indian Reservation and WCA-3A. Structures G-404 and G-357 became EAA Basin boundary structures and were added as EAA Basin outflows for the EAA Basin runoff TP load calculation. Structure G-88 no longer discharged to the EAA and was removed from the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>With the completion of Section 1 of STA-6, the discharge bypass canals G-605 and G-606 were removed in 2001 from the EAA Basin runoff TP load calculation.</TD></TR><TR><TD ROWSPAN="3">WY2002</TD><TD ROWSPAN="3">500,401</TD><TD>Within the Lake Okeechobee Diversion Basins, East Beach Water Control District (EBPS) and East Shore Water Control District (ESPS) structures discharged into the EAA basin, therefore structures EBPS and ESPS were added as EAA Basin inflows for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD>Structure G-410 was added with the construction of STA-5 and became an EAA basin discharge structure, therefore it was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structures G-402A-D were newly constructed and discharged into the Miami Canal from Rotenberger Wildlife Management Area, therefore these structures were added as EAA Basin inflows for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD ROWSPAN="4">WY2004</TD><TD ROWSPAN="4">500,401</TD><TD>The new structures G-204, G-205, and G-206 discharged from the Holeyland Wildlife Management Area into the L-5 Canal prior to discharging into the EAA Basin and were added as EAA Basin inflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structure G-507 became an EAA discharge structure with the construction of STA-5 and was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structures G-370 and G-372, associated with the construction of STA-3/4, were added as EAA Basin outflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structures G-376A-F discharged into the L-5 Canal, prior to discharging into the EAA Basin through the North New River Canal during the construction of STA-3/4 and were added as EAA Basin inflows for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD ROWSPAN="4">WY2005</TD><TD ROWSPAN="4">487,769</TD><TD>Structures G-379A-E discharged into the L-5 Canal, prior to discharging into the EAA Basin through the North New River Canal during the construction of STA-3/4 and were added as EAA Basin inflows for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>Structures G381A-F discharged into the L-5 Canal during the construction of STA-3/4, prior to discharging to the EAA Basin through the Miami Canal, therefore structures G381A-F were added as EAA Basin inflows for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD></TD></TR><TR><TD>The EAA Basin boundary moved north of STA-3/4 once construction of the STA was completed, therefore structures S-7, S-150, S-8, G-200, G600, G-404, G-357, G402A-D, G‑204, G-205, G-206, G-376A-F, G-379A-E, and G381A-F were removed from the EAA Basin runoff TP load calculation.</TD></TR><TR><TD>WY2013</TD><TD>468,059</TD><TD>Structure G-434 became a new EAA Basin discharge structure with the construction of STA-2 expansion project and was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>WY2014</TD><TD>463,030</TD><TD>Structure G-435 became a new EAA Basin discharge structure with the construction of the STA-2 expansion project, therefore structure G-435 was added as an EAA Basin outflow for the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>WY2016</TD><TD>450,805</TD><TD>Structure G-722 began discharging into the North New River Canal with the construction of the A-1 FEB, therefore it became an EAA Basin inflow structure and was added as an EAA Basin inflow for the EAA Basin runoff TP load calculation.</TD></TR><TR><TD>WY2018</TD><TD>445,566</TD><TD>With the completion of the L-8 FEB the area was removed from the total EAA Basin area considered in the EAA Basin runoff TP load calculation. </TD></TR><TR><TD>WY2019</TD><TD>473,776</TD><TD>WY2019 is the first year to include the Lake Okeechobee diversion basins in the EAA Basin runoff TP load reduction assessment. As a result of these changes, the Lake Okeechobee diversion basin lake structures (C-10, C-12, C-12A, C-4A, S236, and EPD07) became the north boundary structures for the EAA Basin runoff TP load compliance assessment.</TD></TR></TBODY></TABLE></DIV></DIV></DIV>

Service Item Id: 949e5a7d0b2249f194e4dabbea86ca4c

Copyright Text: SFWMD shares regulatory responsibilities for managing and protecting regional water resources with the Florida Department of Environmental Protection and other state and local governments. Geospatial Services manages and maintains geospatial products and data related to the Regulation business function. Regulation provides oversight over these products.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 6000000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Style:

Color:

Outline:

Style:

Color:

Width:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
Shape ( type: esriFieldTypeGeometry, alias: Shape )
Shape.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
Shape.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )
TYPE ( type: esriFieldTypeString, alias: TYPE, length: 20 )
RULE_ ( type: esriFieldTypeString, alias: RULE, length: 20 )
CHAPTER ( type: esriFieldTypeString, alias: CHAPTER, length: 100 )
BND_NAME ( type: esriFieldTypeString, alias: BND_NAME, length: 100 )
FIGURE ( type: esriFieldTypeString, alias: FIGURE, length: 50 )
NAME ( type: esriFieldTypeString, alias: NAME, length: 50 )
BND_TYPE ( type: esriFieldTypeString, alias: BND_TYPE, length: 100 )
WATERSHED_NAME ( type: esriFieldTypeString, alias: WATERSHED_NAME, length: 30 )
SUB_REGION ( type: esriFieldTypeString, alias: SUB_REGION, length: 20 )
SUB_REGION_NAME ( type: esriFieldTypeString, alias: SUB_REGION_NAME, length: 10 )
RESOURCE_TYPE ( type: esriFieldTypeString, alias: RESOURCE_TYPE, length: 20 )
TRANSPARENCY ( type: esriFieldTypeSmallInteger, alias: TRANSPARENCY )
SOURCE_FC ( type: esriFieldTypeString, alias: SOURCE_FC, length: 50 )
FIGURE_TEXT ( type: esriFieldTypeString, alias: FIGURE_TEXT, length: 100 )
RULE_LINK ( type: esriFieldTypeString, alias: RULE_LINK, length: 250 )
REF_DOC_LINK ( type: esriFieldTypeString, alias: REF_DOC_LINK, length: 250 )
COMMENT ( type: esriFieldTypeString, alias: COMMENT, length: 500 )
YEAR ( type: esriFieldTypeString, alias: YEAR, length: 4 )
DESCRIPTION ( type: esriFieldTypeString, alias: DESCRIPTION, length: 100 )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata