US Environmental Protection Agency (EPA) 19960101 20010000 vector digital data US Environmental Protection Agency (EPA) This dataset contains US EPA permitted Dam locations for the state of Florida. This dataset contains US EPA permitted Dam locations for the state of Florida. 19960101 publication date Complete As needed -87.485712 -79.891773 31.023963 25.277720 None structure inlandWaters ISO 19115 Topic Categories structure inlandWaters None Southeast United States Florida Southeast U.S None 1990s None THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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 A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling 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 Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html Web site: http://www.fgdl.org Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 US Environmental Protection Agency 19960101 Map GeoPlan relied on the integrity of the attribute information within the original data. 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." This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan US Environmental Protection Agency 19960101 Map 0 None 19960101 ground condition USEPA Spatial and Attribute Information 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 the DESCRIPT item based on PRM_PURPOS unknown Vector Entity point 590 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 DATABASE FILE Database File None NID_ID National Inventory of Dams ID Number Unknown Unknown ETAT_EPADAM_AREA STATE two letter state abbreviation Unknown Unknown DAM_NAME official dam name Unknown Unknown OTHER_NAME other common name Unknown Unknown EAP emergency action plan for dam Unknown Unknown STATE_NAME name of state in which dam is located Unknown Unknown CONG_DIST congressional district in which dam is located Unknown Unknown COUNTY county in which dam is located Unknown Unknown NEAR_CITY name of nearest downstream city Unknown Unknown SOURCE_ID official agency ID number for dam Unknown Unknown DIST_CITY distance from dam to nearest downstrem city Unknown Unknown RIVER official name of river on which dam is built Unknown Unknown PRM_PURPOS primary purpose for which dam is used Unknown Unknown YEAR_COMPL year original main dam structure was completed Unknown Unknown NID_HEIGHT calculated single height value in feet Unknown Unknown NID_STOR calculated maximum value from normal storage and maximium storage value used to obtain single storage value in acreft Unknown Unknown PERIMETER DAM_LENGTH dam length Unknown Unknown MAX_DISCH maximum discharge in cubic feet per second Unknown Unknown OWNER owner of dam Unknown Unknown STATE_AGCY state agency with regulatory or approval authority Unknown Unknown FED_AGCY federal agency involvement in the dam Unknown Unknown NONFED_DAM federal or nonfederal dam location Unknown Unknown SECT_TOWN dam location in terms of section, township, range Unknown Unknown PURPOSE purpose for which reservoir is used Unknown Unknown DAM_TYPE type of dam Unknown Unknown DAM_HEIGHT height of dam in feet Unknown Unknown HYDR_HGT hydraulic height in feet Unknown Unknown STRUCT_HGT structural height in feet Unknown Unknown NORM_STOR normal storage in acrefeet Unknown Unknown MAX_STOR maximum storage in acrefeet Unknown Unknown FIPS_STATE FIPS code used by US Census bureau for state Unknown Unknown SURF_AREA surface area of impoundmentnormal retention level (acres) Unknown Unknown DRAIN_AREA drainage area of dam in square miles Unknown Unknown EPADAM_ SPILL_TYPE type of spillway Unknown Unknown NUM_LOCKS number of existing navigation locks Unknown Unknown LOCK_LEN length of primary navigation lock in feet Unknown Unknown VOLUME cubic yards of materials used in dam structure Unknown Unknown INSP_DATE date of most recent inspection Unknown Unknown PHASEI_INS Phase I Inspection Program Unknown Unknown FD_CONSTRC federal agency involved in construction of dam Unknown Unknown FD_DESIGN federal agency involved in design of dam Unknown Unknown FD_FUNDING federal agency involved in funding of dam Unknown Unknown FD_INSPECT federal agency involved in inspection of dam Unknown Unknown FD_OPERATE federal agency involved in operation of dam Unknown Unknown FD_OTHER federal agency involved in other aspects of dam Unknown Unknown FD_OWNER federal agency that owns/partly owns dam Unknown Unknown BCU BASINS assigned cataloging unit Unknown Unknown EPADAM_ID FD_REGULAT federal agency involved in regulation of dam Unknown Unknown OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. SUPP_DATE date of transmittal Unknown Unknown LATITUDE_Y dam latitude in decimal degrees Unknown Unknown FIPS_CNTY FIPS code used by US Census bureau for county Unknown Unknown DESCRIPT FGDL assigned item containing info from PRM_PURPOS Unknown Unknown SUPP_FED federal agency providing field data Unknown Unknown HAZARD NID_DAMTYP OWN_TYPE SPILL_WDTH LOCK_WIDTH SOURC_AGCY SOURC_DATE LONGITUD_X AUTOID SHAPE Feature geometry. ESRI Coordinates defining the features. Operator mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US (352) 3920997, Operator Technical Support: http://www.fgdl.org/fgdlfeed.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html Web site: http://www.fgdl.org FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html 24 Hours / Day Please visit the web site, http://www.fgdl.org, for all questions or concerns. DOWNLOADABLE DATA 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. 20200302 Operator physical

401 M Street, SW

Washington DC 20460 (202) 2608614 FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time