<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="./fgdc_classic_fgdl.xsl"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
  <idinfo>
    <citation>
      <citeinfo>
        <origin>FLORIDA DEPARTMENT OF ENVIRONMENTAL PROTECTION</origin>
        <pubdate>19980101</pubdate>
        <title>BASINS</title>
        <geoform>vector digital data</geoform>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains drainage basins as determined by the Florida Department of Environmental Protection (FDEP).</abstract>
      <purpose>To determine the various drainage basins for the state of Florida</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>19970101</begdate>
          <enddate>19980101</enddate>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.639107</westbc>
        <eastbc>-79.871591</eastbc>
        <northbc>31.042688</northbc>
        <southbc>25.090763</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Planning</themekey>
        <themekey>Basins</themekey>
        <themekey>Hydrology</themekey>
        <themekey>Drainage</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>planningCadastre</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Florida</placekey>
        <placekey>Southeast United States</placekey>
        <placekey>Southeast U.S.</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>1997</tempkey>
        <tempkey>1998</tempkey>
        <tempkey>1990s</tempkey>
      </temporal>
    </keywords>
    <accconst>None</accconst>
    <useconst>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</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Geographic Data Library (FGDL)</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>Florida</state>
          <postal>32611-5706</postal>
        </cntaddr>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
      </cntinfo>
    </ptcontac>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <origin>FLORIDA DEPARTMENT OF ENVIRONMENTAL PROTECTION</origin>
        <pubdate>unknown</pubdate>
        <title>drainage_basins_1997_areas.zip</title>
        <geoform>Map</geoform>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>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."</logic>
    <complete>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."</complete>
    <posacc>
      <horizpa>
        <horizpar>This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>FLORIDA DEPARTMENT OF ENVIRONMENTAL PROTECTION</origin>
            <pubdate>unknown</pubdate>
            <title>drainage_basins_1997_areas.zip</title>
            <geoform>Map</geoform>
          </citeinfo>
        </srccite>
        <srcscale>24000</srcscale>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>19970101</begdate>
              <enddate>19980101</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>FDEP</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>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</procdesc>
        <procdate>20000101</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>3801</ptvctcnt>
      </sdtsterm>
    </ptvctinf>
  </spdoinfo>
  <spref>
    <horizsys>
      <planar>
        <mapproj>
          <mapprojn>NAD 1983 HARN Florida GDL Albers</mapprojn>
          <albers>
            <stdparll>24.0</stdparll>
            <stdparll>31.5</stdparll>
            <longcm>-84.0</longcm>
            <latprjo>24.0</latprjo>
            <feast>400000.0</feast>
            <fnorth>0.0</fnorth>
          </albers>
        </mapproj>
        <planci>
          <plance>coordinate pair</plance>
          <coordrep>
            <absres>0.0001</absres>
            <ordres>0.0001</ordres>
          </coordrep>
          <plandu>meter</plandu>
        </planci>
      </planar>
      <geodetic>
        <horizdn>D North American 1983 HARN</horizdn>
        <ellips>GRS 1980</ellips>
        <semiaxis>6378137.0</semiaxis>
        <denflat>298.257222101</denflat>
      </geodetic>
    </horizsys>
  </spref>
  <eainfo>
    <detailed>
      <enttyp>
        <enttypl>DATABASE FILE</enttypl>
        <enttypd>Database file</enttypd>
        <enttypds>None</enttypds>
      </enttyp>
      <attr>
        <attrlabl>Shape</attrlabl>
        <attrdef>Data attribute inherent to the ESRI shapefile format, which defines the data as a point, polyline, or polygon.</attrdef>
        <attrdefs>FGDL</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>BASINS_ID</attrlabl>
        <attrdef>ArcInfo internal coverage item </attrdef>
        <attrdefs>FGDL</attrdefs>
        <attrdomv />
      </attr>
      <attr>
        <attrlabl>HUC</attrlabl>
        <attrdef>USGS hydrologic unit code; there are eight in the district</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>EXTHUC</attrlabl>
        <attrdef>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.</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>BASIN</attrlabl>
        <attrdef>Name (e.g. Sixmile Creek, unnamed canal, Crescent Lake)</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>FEATURE</attrlabl>
        <attrdef>Water body type - see below for descriptions</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>PK_BASIN</attrlabl>
        <attrdef>Unique statewide ID</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>UFLAG</attrlabl>
        <attrdef>Update flag which indicates if the polygon was revised from the original USGS polygon:</attrdef>
        <attrdefs>FDEP</attrdefs>
        <attrdomv>
          <edom>
            <edomv>A</edomv>
            <edomvd>attribute change only</edomvd>
          </edom>
          <edom>
            <edomv>M</edomv>
            <edomvd>existing arcs were revised (minor modification)</edomvd>
          </edom>
          <edom>
            <edomv>N</edomv>
            <edomvd>arcs were radically revised or basin was subdivided further</edomvd>
          </edom>
          <edom>
            <edomv>U</edomv>
            <edomvd>Attribute change and revised arcs or totally new basin</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HUC1</attrlabl>
        <attrdef>Item for internal use</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>HUC12</attrlabl>
        <attrdef>Item for internal use</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>HUC123</attrlabl>
        <attrdef>Item for internal use</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>HUC1234</attrlabl>
        <attrdef>Item for internal use</attrdef>
        <attrdefs>FDEP</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>OBJECTID</attrlabl>
        <attrdef>Internal feature number.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Sequential unique whole numbers that are automatically generated.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>HUCINT</attrlabl>
        <attrdef>Item for internal use</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SHAPE</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SHAPE.AREA</attrlabl>
      </attr>
      <attr>
        <attrlabl>SHAPE.LEN</attrlabl>
      </attr>
    </detailed>
  </eainfo>
  <distinfo>
    <distrib>
      <cntinfo>
        <cntperp>
          <cntper>Operator</cntper>
        </cntperp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>Florida</state>
          <postal>32611-5706</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>(352) 3920997, Operator</cntvoice>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <hours>24 Hours / Day</hours>
        <cntinst>Please visit the web site, http://www.fgdl.org, for all questions or concerns.</cntinst>
      </cntinfo>
    </distrib>
    <resdesc>DOWNLOADABLE DATA</resdesc>
    <distliab>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.</distliab>
  </distinfo>
  <metainfo>
    <metd>20200303</metd>
    <metc>
      <cntinfo>
        <cntperp>
          <cntper>Operator</cntper>
        </cntperp>
        <cntaddr>
          <addrtype>physical</addrtype>
          <address>Florida Department of Environmental Protection 3900 Commonwealth</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399</postal>
        </cntaddr>
        <cntvoice>(850) 488-3701</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>