2002091912470500FALSE{0F58961D-A8B6-4313-BEB1-BE0DBB6DF90D}20020920144211002002092413592700GeoPlan, during the QA/QC process included the following aspects: (1) Reprojected data to FGDL Albers HPGN (See "Map Projection Parameters" below) (2) Upcased all character records (3) Changed original file name from "nhd" to "nhdwb" (4) Joined NHD.drain to NHD.reach (5) Joined shapefile with FCODE table (6) Renamed DESCRIPT field to DESC (7) DESCRIPT item was added based on the item FTYPE (8) Dropped old internal coverage items: RCH#, RCH_ID, WB_ID, WB# (9) Converted coverage to shapefile (10) Clipped shapefile to State of Florida20020918173728002002MAPPublication dateSpatial and Attribute InformationUnited States Geological Survey, The United States Environmental Protection Agency200206261:100,00020020626publication dateUSGSThe NHD is produced by a joint effort between the Environmental Protection Agency (EPA) and U.S. Geological Survey (USGS). Data was downloaded by GeoPlan in coverage format from the USGS/NHD website (http://nhd.usgs.gov/) in June 2002. When received, data was in the following projection: Geographic, Datum: NAD 83, Spheroid: GRS80, units: Decimal Degrees. The shapefile was then clipped to the State of Florida, and projected to FGDL Albers HPGN. 2002Relied 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.Please note that the NHD is designed to have many users nation wide that use as well as update the dataset. By using the data set in shapefile format it will no longer be possible to update the NHD. For information on how you can take part in the updating of NHD data, or how to get the latest version, see their website: http://nhd.usgs.gov The NHDWB dataset is a combination of the Waterbody and Waterbody Reach datasets taken from the NHD. The two datasets were nearly identical so the attributes of the Waterbody Reach dataset were joined to the Waterbody dataset to form NHDWB. The field "SQ_KM" was dropped from Waterbody Reach the "NAME" and "GNIS_ID" were combined into the same named field in Waterbody. Note that this is a region coverage so some some features may completly cover other features. For example, a lake/pond may be underneath a swamp/marsh feature making it appear that the lake/pond is not there. For more information on why the NHD is processed this way see http://nhd.usgs.gov/techref.html. The National Hydrography Dataset (NHD) is a feature-based database that interconnects and uniquely identifies the stream segments or reaches that comprise the nations surface water drainage system. It is based initially on the content of the U.S. Geological Survey 1:100,000-scale Digital Line Graph (DLG) hydrography data, integrated with reach-related information from the U.S. Environmental Protection Agency Reach File Version 3.0 (RF3). More specifically, it contains reach codes for networked features and isolated lakes, flow direction, names, stream level, and centerline representations for areal water bodies. Reaches are also defined to represent waterbodies and the approximate shorelines of the Great Lakes, the Atlantic and Pacific Oceans, and the Gulf of Mexico. The NHD also incorporates the National Spatial Data Infrastructure framework criteria set out by the Federal Geographic Data Committee. The National Hydrography Dataset combines elements of the DLG and RF3: spatial accuracy and comprehensiveness from the DLG and network relationships, names, stream level, and a unique identifier (reach code) for surface water features from RF3. The NHD supersedes DLG and RF3 by incorporating them, not by replacing them. Users of DLG and RF3 will find the National Hydrography Dataset both familiar and greatly expanded and refined. The NHD provides a national framework for assigning reach addresses to water-related entities, such as industrial dischargers, drinking water supplies, fish habitat areas, wild and scenic rivers. Reach addresses establish the locations of these entities relative to one another within the NHD surface water drainage network in a manner similar to street addresses. Once linked to the NHD by their reach addresses, the upstream/downstream relationships of these water-related entities and any associated information about them can be analyzed using software tools ranging from spreadsheets to geographic information systems (GIS). GIS can also be used to combine NHD-based network analysis with other data layers, such as soils, land use and population, to help better understand and display their respective effects upon one another. Furthermore, because the NHD provides a nationally consistent framework for addressing and analysis, water-related information linked to reach addresses by one organization (national, state, local) can be shared with other organizations and easily integrated into many different types of applications to the benefit of all. The National Hydrography Dataset is designed to provide comprehensive coverage of hydrologic data for the U.S. While initially based on 1:100,000-scale data, the NHD is designed to incorporate - and encourage the development of -higher-resolution data required by many users. It will facilitate the improved integration of water-related data in support of the application requirements of a growing national user community and will enable shared maintenance and enhancement.For further research of NHD item definitions go to the "National Hydrology Dataset, Contents and Concepts" at: http://nhd.usgs.gov/chapter1/index.html#_toc474479742Relied on the integrity of the attribute information within the original data layer.Relied on the integrity of the attribute information within the original data layer.NHD - http://nhd.usgs.gov/index.htnl United States Geological Survey, The United States Environmental Protection Agency20020626nhdwbShapefileState of FloridaMapping Division - http://mapping.usgs.gov/index.html Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.2.0.700enThis dataset contains the spatial extent of water bodies for the National Hydrography Dataset (NHD) in the State of Florida. These features represent areas that contain water such as lake/pond, swamp/marsh, stream/river, canal/ditch, area of complex channels, estuary, ice mass, playa, reservoir, sea/ocean, and wash. For research of the National Hydrography Dataset in the State of Florida.POLYGONpublication date20020626CompleteAs needed-82.663385-82.04026629.93931329.422649NONENational Hydrography Dataset WaterbodiesUSGSNONENONEWeb 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.orgShapefilefile://\\cosmos\christine\finaldata\edit_state\nhdwb.shpLocal Area Network00246.728ShapefileMicrosoft Windows 2000 Version 5.0 (Build 2195) Service Pack 2; ESRI ArcCatalog 8.2.0.700nhdwb-81629.656459805164.214655902430.75583355853.8848751-89.097286-79.71126632.13266924.4203821enFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timehttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata ProfileNational Mapping Division, U.S. Department of Interior, U.S. Geological Survey mailing addressRestonVA20192

12201 Sunrise Valley Drive

USA1-888-ASK-USGS (275-8747)20020924ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset 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.Downloadable Data or CD ROM.Florida Geographic Data Library (FGDL)mailing address

431 Architecture PO Box 115706

GainesvilleFlorida32611-5706United StatesWeb 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.html46.72846.728coordinate pair0.0020480.002048metersAlbers Conical Equal Area24.00000031.500000-84.00000024.000000400000.0000000.000000Albers Conical Equal AreaGCS_North_American_1983_HARND_North_American_1983_HARNGeodetic Reference System 806378137.000000298.257222VectorSimplePolygonFALSE36129TRUEFALSEG-polygon36129Custom36129nhdwb01Feature Class36129.DBF fileFGDLFIDFIDOID400Internal feature number.ESRISequential unique whole numbers that are automatically generated.ShapeShapeGeometry000Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon.FGDLCoordinates defining the features.AREAAREANumber195Area of polygons in square metersUSGSPERIMETERPERIMETERNumber195Perimeter of polygons in metersUSGSCOM_IDCOM_IDNumber11Unique common identifier of the NHD feature or reach. In this dataset the COM_ID identifies the waterbody feature only.USGSRCH_COM_IDRCH_COM_IDNumber11Unique common identifier of the NHD feature or reach. In this dataset the RCH_COM_ID identifies the waterbody reach feature only. USGSFTYPEFTYPEString24Features are classified by type. These feature types provide the basic description of the features. Each type has a name and a definition. STREAM/RIVER - A body of flowing water. LAKE/POND - A standing body of water with a predominantly natural shoreline surrounded by land. SEA/OCEAN - The great body of salt water that covers much of the earth. SWAMP/MARSH - A noncultivated, vegetated area that is inundated or saturated for a significant part of the year. The vegetation is adapted for life in saturated soil conditions.USGSFCODEFCODENumber5A five-digit feature code encodes the feature type and combinations of characteristics and values that can be assigned to a type. The first three digits encode the feature type, and the last two digits encode a set of characteristics and values. The general format of the feature code is FFFCC, in which FFF is the three-digit code for a feature type. CC is the two-digit code for a combination of values for characteristics associated with a feature type. If only the feature type is identified, these last two digits are assigned the value "0".USGSELEVELEVNumber131The elevation of water surfaces where water pools is encoded for a few features. Water surface elevations may be encoded for features of the type area to be submerged, canal/ditch, inundation area, lake/pond, reservoir, and stream/river. Note that these elevations have not been entered for most features. The vertical datum for the conterminous United States and Alaska is the National Geodetic Vertical Datum of 1929. For Puerto Rico and the Virgin Islands, the datum is Local Mean Sea Level. Elevations are recorded in meters and stored in data elements named "ELEV". Two encoded values have special meanings. A value of -9999 means that an elevation value will not be applied to the feature. A value of -9998 means that a value can be applied to the feature but has not been specified. In addition to the elevation, the prevailing condition (for example, "average water elevation") to which the elevation applies is provided. The condition is stored as a text string in data elements named "STAGE". Where the "ELEV" field has a value of -9999 or -9998, the "STAGE" field is blank.USGSSTAGESTAGEString24The prevailing condition to which elevation applies.Where the "ELEV" field has a value of -9999 or -9998, the "STAGE" field is blank.USGSSQ_KMSQ_KMNumber193Area of polygon in square kilometers.USGSGNIS_IDGNIS_IDString8GNIS identifier of the waterbody reach name. A "blank" means that the name is not populated. GNIS is an 8-digit code from the Geographic Names Information System developed by the USGS and the USBGN. The Federally recognized name of each feature described in the data base is identified, and references are made to a feature's location by State, county, and geographic coordinates.USGSNAMENAMEString99Text of the reach name. A "blank" means that the name is not populated.USGSRCH_CODERCH_CODEString14Unique identifier, 14 digit code with two parts First 8 digits - Hydrologic Unit, code for the cataloging unit in which the reach exists. Hydrologic units provide a systematic means of identifying and subdividing river-basin units. Cataloging unit is the fourth-level subdivision of hydrologic units.Last 6 digits - Assigned in sequential order, and arbitrarily among the reaches. USGSRCH_DATERCH_DATEString8Date the RCH_CODE was assignedUSGSDESCRIPTDESCRIPTString24FGDL added item based on the item FTYPEFGDL20020924