Florida Department of Environmental Protection 19991209 Shapefile http://www.dep.state.fl.us/ wtrmdl01 This dataset contains the 303(d) listed impaired waters for Florida counties. Total Maximum Daily Loads (TMDLs) are to be created for each pollutant of concern for each water segment on the 303(d) list. A TMDL is the amount of pollutant a waterbody can receive and still meet applicable water quality standards for its designated use. The 303(d) list is derived from the 305(b) report. Section 303(d) of the Clean Water Act requires states to submit a list of impaired waterbodies for their State. The impaired waters are those that do not meet their designated use according to the 305(b) report. The 303(d) list must contain the "parameters of concern" which resulted in the impairment of the waterbody. The 1998 303(d) coverage represents the basins containing the 1998 303(d) list of impaired waterways. The 1998 303(d) list is based on information from the State's 1996 305(b) report. The Clean Water Act then requires State's to develop a Total Maximum Daily Load (TMDL) for each parameter of concern for a 303(d) listed water. en 19991209 publication date Complete As needed -82.663385 -82.040266 29.939313 29.422649 529493.596923588939.710273602511.118596660306.534866 NONE Total Maximum Daily Loads (TMDLs) Pollutant Water quality standards Planning NONE Florida Southeast United States Southeast U.S. NONE December 9, 1999 1990s NONE NONE Data was downloaded from the website: ftp://ftp.dep.state.fl.us/pub/gis/data/ Florida Department of Environmental Protection 19991209 Map Web site: http://www.fgdl.orgTechnical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlMailing list for FGDL: http://www.fgdl.org/fgdl-l.htmlmailing address

431 Architecture PO Box 115706

GainesvilleFlorida32611-5706For FGDL Software: http://www.fgdl.org/software.htmlFlorida Geographic Data Library (FGDL)Web site: http://www.fgdl.orgShapefile Relied on the integrity of the attribute information within the original data layer. Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modelling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html. These data are based on interpretation of available information and should not be construed as legally binding. Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s.". Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s." Florida Department of Environmental Protection 19991209 Map 24000 MAP 19991209 ground condition FDEP Spatial and Attribute Information Publication date The process step describes, in general, the process used in the production of data sets. The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers (2) Set Precision to DOUBLE (3) Set Tolerances to FGDL Standards (4) Added DESCRIPT item based on BASIN item 2002 Metadata imported.C:\DOCUME~1\CHRIST~1\LOCALS~1\Temp\xml1BE6.tmp2002102910545500 coordinate pair 0.000128 0.000128 meters Albers Conical Equal Area24.00000031.500000-84.00000024.000000400000.0000000.000000 D_North_American_1983_HARN Geodetic Reference System 80 6378137.000000 298.257222 CustomGCS_North_American_1983_HARN wtrmdl01 Database File None Feature Class22 FID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. FIDOID400 Shape Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon. FGDL Coordinates defining the features. ShapeGeometry000 AREA Area of the polygon in meters FGDL Unknown AREANumber185 PERIMETER Perimeter of the polygon in meters FGDL Unknown PERIMETERNumber185 WTRMDL_ ArcInfo internal coverage item FGDL Unknown WTRMDL_Number11 WTRMDL_ID ArcInfo internal coverage item FGDL Unknown WTRMDL_IDNumber11 HUC USGS hydrologic unit code FDEP Unknown HUCString8 BASIN Name of WBID FDEP Unknown BASINString22 WBID Unique watershed identifier number FDEP Unknown WBIDString5 WQ96 Stream condition index (SCI) for biology samples FDEP Unknown WQ96String7 MAPID Basin ID number from 303(d) report FDEP Unknown MAPIDNumber11 CLASS Unknown Unknown Unknown CLASSString1 MINYR Unknown Unknown Unknown MINYRNumber11 MAXYR Unknown Unknown Unknown MAXYRNumber11 NOBS Unknown Unknown Unknown NOBSNumber11 STATUS Unknown Unknown Unknown STATUSString10 TURB Turbidity index value (1-100) FDEP Unknown TURBString5 SD Secchi disc trend (1=improve 2=stable 3=degrade) FDEP Unknown SDString5 COLOR Color in platinum color units FDEP Unknown COLORString5 COND Conductivity (micromho) FDEP Unknown CONDString5 DO Dissolved Oxygen index value (1-100) FDEP Unknown DOString5 BOD Biochemical Oxygen Demand index value (1-100) FDEP Unknown BODString5 PH pH FDEP Unknown PHString5 ALK Total Alkalinity (CaCO3mg/l) index value (1-100) FDEP Unknown ALKString5 TSS Total Suspended Solids index value (1-100) FDEP Unknown TSSString5 TN Total Nitrogen index value (1-100) FDEP Unknown TNString5 TP Total Phosphorous index value (1-100) FDEP Unknown TPString5 TCOLI Total Coliform index value (1-100) FDEP Unknown TCOLIString5 FCOLI Fecal Coliform index value (1-100) FDEP Unknown FCOLIString5 CHLA Chlorophyll A index value (1-100) FDEP Unknown CHLAString5 COD Chemical Oxygen Demand index value (1-100) FDEP Unknown CODString5 TOC Total Organic Carbon index value (1-100) FDEP Unknown TOCString5 DOSAT Percent saturation of dissolved oxygen FDEP Unknown DOSATString5 WQIXX Percent saturation of dissolved oxygen FDEP Unknown WQIXXString5 WQIYY Water Quality index value (1-100) FDEP Unknown WQIYYString5 HUC_NAME USGS hydrologic unit name FDEP Unknown HUC_NAMEString22 Z03D_LIST Name of the waterbody on the 1998 303(d) list submitted to USEPA, if that name was different from the names in the 1996 305(b) report. FDEP Unknown Z03D_LISTString24 WMD Water Management District FDEP Unknown WMDString16 DISTRICTDISTRICTString16DEP Regulatory DistrictFDEPPARAMETERSPARAMETERSString138Water quality parameters contributing to the impairment of the waterbody.FDEPTMDLYEARTMDLYEARNumber199Year in which TMDLs are to be completed for waterbodies according to a consent decree containing a TMDL development schedule.FDEPSPECTMDLYRSPECTMDLYRString14Special TMDL development year. The development of a TMDL ahead of schedule. It is usually for a specific parameter.FDEPSPECTMDLPASPECTMDLPAString25The parameter for which the special TMDL is to be created.FDEPDESCRIPTDESCRIPTString22Based on BASIN itemFGDL mailing address

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 United States Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.htmlFor FGDL Software: http://www.fgdl.org/software.htmlFGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.htmlMailing list for FGDL: http://www.fgdl.org/fgdl-l.htmlFLORIDA GEOGRAPHIC DATA LIBRARY THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED AS IS.THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE QUALITY OR SUITABILITY OF THE MATERIALS, EITHER EXPRESSLY OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THE UNIVERSITY OF FLORIDA GEOPLAN CENTER MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. THE UNIVERSITY OF FLORIDA GEOPLAN CENTER SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED AS A RESULT OF USING, MODIFYING, CONTRIBUTING OR DISTRIBUTING THE MATERIALS. 2001 Operator Florida Department of Environmental Protection physical address

3900 Commonwealth

Tallahassee FL 32399 (850) 921-9395 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 enlocal timehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile {B2EB47F6-D57B-4D5A-B00E-7B8CC7A9172F}2002102910545500FALSE20021029105455002002103016303800Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.2.0.700wtrmdl01529493.596923588939.710273660306.534866602511.1185961-82.663217-82.04015129.94342929.4157551ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\cosmos\christine\finaldata\v3\alachua\wtrmdl01.shpLocal Area Network0.159ShapefileSimplePolygonFALSE22FALSEFALSECustom2220021030