FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION
VERSION 2007

TITLE: DRAINAGE BASINS 

Geodataset Name:       basins
Geodataset Type:       Shapefile
Geodataset Feature:    Polygon
Feature Count:         98
GENERAL DESCRIPTION:
This dataset contains drainage basins as determined by the Florida. Department of Environmental Protection (FDEP). 
DATA SOURCE(S):                    FLORIDA DEPARTMENT OF ENVIRONMENTAL PROTECTION
SCALE OF ORIGINAL SOURCE MAPS:     24000
DATE OF AUTOMATION OF SOURCE:      1998
GEODATASET EXTENT:                 State of Florida

FEATURE ATTRIBUTE TABLES: 

Datafile Name: BASINS.DBF
ITEM NAME WIDTH TYPE N. DECIMAL DEGREES
FID
4 OID ---
Shape
0 Geometry ---
AREA
18 Number 5
PERIMETER
18 Number 5
BASINS_
11 Number ---
BASINS_ID
11 Number ---
HUC
8 String ---
EXTHUC
8 String ---
BASIN
22 String ---
FEATURE
6 String ---
PK_BASIN
6 Number ---
UFLAG
1 String ---
HUCINT
8 Number ---
HUC1
10 Number ---
HUC12
12 Number ---
HUC123
14 Number ---
HUC1234
16 Number ---

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item

Item Description





FID

Internal feature number.
















Shape

Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon.
















AREA

Area of the polygon in meters
















PERIMETER

Perimeter of the polygon in meters
















BASINS_

ArcInfo internal coverage item
















BASINS_ID

ArcInfo internal coverage item
















HUC

USGS hydrologic unit code; there are eight in the district
















EXTHUC

Extended HUC code with 8 digits signifying a hydrologic hierarchy: -First two digits denote the primary basin (redefined as item FIRST) -Second two digits denote the secondary basin (SECOND) -Third two digits denote the tertiary basin (THIRD) -Fourth two digits denote the quaternary basin (FOURTH) -Example:  In HUC 03080101, any polygon with EXTHUC cn 10----- or FIRST = 10 is part of the Jane Green Creek watershed -EXTHUC = 99000000 is used for the main water bodies that each HUC is based on, i.e., the main stem of the St. Johns River, Ocklawaha River, Indian River Lagoon, etc. These are more clearly described  by the Planning Unit codes.
















BASIN

Name (e.g. Sixmile Creek, unnamed canal, Crescent Lake)
















FEATURE

Water body type - see below for descriptions
















PK_BASIN

Unique statewide ID
















UFLAG

Update flag which indicates if the polygon was revised from the original USGS polygon:




A = attribute change only

M = existing arcs were revised (minor modification)

N = arcs were radically revised or basin was subdivided further

U = Attribute change and revised arcs or totally new basin













HUCINT

Item for internal use
















HUC1

Item for internal use
















HUC12

Item for internal use
















HUC123

Item for internal use
















HUC1234

Item for internal use




























USER NOTES:








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."













Relied on the integrity of the attribute information within the original data layer.

























To determine the various drainage basins for the state of Florida.







































THE DATA INCLUDED IN THIS APPLICATION ARE BASED ON INTERPRETATION OF AVAILABLE INFORMATION AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING.

Scale is an important factor in data usage. Certain scale data sets are not suitable for some projects, analysis, or modeling purposes. Please be sure you are using the best available data.

1:24000 scale data sets 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 data sets are recommended for projects that are at the multi-county or regional level.  1:250000 scale data sets 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 analyses. 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 web pages at:
http://www.geoplan.ufl.edu/education.html








REFERENCES: 














DATA LINEAGE SUMMARY: 








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 FEATURE item
Process Date: 2000









MAP PROJECTION PARAMETERS: 



Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000




DATA SOURCE CONTACT (S):








Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:




FDEP
Florida Department of Environmental Protection

3900 Commonwealth
Tallahassee, FL
32399
(850) 488-3701


http://www.dep.state.fl.us











FGDL CONTACT:

Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html