<?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>20110413</pubdate>
        <title>BASIN MANAGEMENT ACTION PLANS (BMAP) AREAS IN FLORIDA - OCTOBER 2011</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Tallahassee, FL</pubplace>
          <publish>Florida Department of Environmental Protection</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
        <onlink>http://www.dep.state.fl.us/gis/datadir.htm</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>A BMAP (Basin Management Action Plan) is the "blueprint" for restoring impaired waters by reducing pollutant loadings to meet the allowable loadings established in a Total Maximum Daily Load (TMDL). It represents a comprehensive set of strategies--permit limits on wastewater facilities, urban and agricultural best management practices, conservation programs, financial assistance and revenue generating activities, etc.--designed to implement the pollutant reductions established by the TMDL. These broad-based plans are developed with local stakeholders--they rely on local input and local commitment--and they are adopted by Secretarial Order to be enforceable.</abstract>
      <purpose>To spatially represent the areas undergoing BMAP implementation.</purpose>
      <supplinf>BMAP Standing/Status Values: BMAP Adopted / Adoption Pending: BMAP Adopted - The BMAP has been adopted by the Secretary and stakeholders have started implementing projects. Adoption Pending - We have stakeholder agreement on the BMAP and the BMAP is moving through the internal adoption process. Priority Areas with Basin Management Action Plan Activities in Progress: Areas where BMAPs are currently under development. Areas Undergoing Restoration Supporting TMDL Implementation (RA Plans and other non-BMAP TMDL implementation): These are local restoration strategies similar to BMAP strategies but were done without going through the BMAP process. BMAP Initiation in late 2011/early 2012: BMAP development will be initiated w/ local stakeholders during this time period.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20110413</begdate>
          <enddate>20111005</enddate>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.348493</westbc>
        <eastbc>-79.872667</eastbc>
        <northbc>30.632396</northbc>
        <southbc>24.503456</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>BMAP</themekey>
        <themekey>Basin Management Action Plan</themekey>
        <themekey>Best Management</themekey>
        <themekey>Stakeholders and TMDL</themekey>
        <themekey>Water Resources (Inland)</themekey>
      </theme>
    </keywords>
    <accconst>None</accconst>
    <useconst>Use is limited to showing approximate feature delineations. This layer is not intended for legal decision making.</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Department of Environmental Protection (FDEP) WRM, Water Data Services Section (WDSS)</cntorg>
          <cntper>Ronald Hughes</cntper>
        </cntorgp>
        <cntpos>Environmental Specialist III</cntpos>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2600 Blair Stone Road, MS 3526</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399-2400</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>850-245-8541</cntvoice>
        <cntemail>ronald.hughes@dep.state.fl.us</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>Florida Department of Environmental Protection (FDEP) WRM, Water Data Services Section (WDSS)</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>BMAP Homepage: http://www.dep.state.fl.us/central/Home/Watershed/BMAP.htm Basin Management Action Plans - News &amp; Announcements: http://www.dep.state.fl.us/water/watersheds/bmap.htm</othercit>
      </citeinfo>
    </crossref>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology</logic>
    <complete>This data is provided 'as is' by GeoPlan and is complete to our knowledge.</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>
        <srcscale>0</srcscale>
        <typesrc>onLine</typesrc>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Submitted as a new SDE Layer</procdesc>
      </procstep>
      <procstep>
        <procdesc>April 2011: Existing BMAP Project shapefiles from the November 2010 update were edited, updated and merged into one streamlined shapefile. BMAP Project Boundaries consisting of multiple shapefile records were dissolved into shapefiles with single records. Updated boundaries were verified for accuracy by way of direct communication with Basin Coordinators. Corrections and adjustments were made as needed.</procdesc>
      </procstep>
      <procstep>
        <procdesc>Updates for July 2011 BMAP have been incorporated and final BMAP Project updates have been verified.</procdesc>
      </procstep>
      <procstep>
        <procdesc>Added new layer in ArcSDE. Metadata updated, data published in DataMiner</procdesc>
        <procdate>20110729</procdate>
      </procstep>
      <procstep>
        <procdesc>Updates and revisions for October 2011 BMAP have been incorporated and verified.</procdesc>
        <procdate>20111005</procdate>
      </procstep>
      <procstep>
        <procdesc>Submitted for SDE update</procdesc>
        <procdate>20111006</procdate>
      </procstep>
      <procstep>
        <procdesc>Updated layer from shapefile sent by Ron Hughes. Metadata updated</procdesc>
        <procdate>20111011</procdate>
      </procstep>
      <procstep>
        <procdesc>GeoPlan downloaded this dataset from the Florida Department of Environmental Protection's GeoData Directory website (http://www.dep.state.fl.us/gis/datadir.htm) in November 2011. The data was downloaded in shapefile format and was in the following projection: Albers NAD 83 HARN. During the AQ/QC process the following tasks were undertaken: - Redefined the dataset's projection from FDEP Albers to FGDL Albers. - Deleted the OBJECTID field. - Uppercased all records in the table. - A DESCRIPT field was added based on PROJECT. - A FGDLAQDATE field was added based on date downloaded from source. - Renamed file from STATEWIDE_BMAP_AREAS to bmap_area_oct11.</procdesc>
        <procdate>20111201</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>33</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>BMAP_AREA_OCT11</enttypl>
        <enttypd>BMAP_AREA_OCT11.DBF</enttypd>
        <enttypds>FDEP</enttypds>
      </enttyp>
      <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>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>DISTRICT</attrlabl>
        <attrdef>The FDEP Regulatory District that the BMAP boundary is associated with</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>GROUP_NUM</attrlabl>
        <attrdef>Basin Rotation Group number 1-5</attrdef>
        <attrdefs>TMDL Basin Groups</attrdefs>
      </attr>
      <attr>
        <attrlabl>GROUP_NAME</attrlabl>
        <attrdef>The name of the TMDL Basin Rotation Group that the BMAP boundary lies within</attrdef>
        <attrdefs>TMDL Basin Groups</attrdefs>
      </attr>
      <attr>
        <attrlabl>PROJECT</attrlabl>
        <attrdef>BMAP Project Name</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>NOTES</attrlabl>
        <attrdef>Notes pertaining to the BMAP project</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>STATUS</attrlabl>
        <attrdef>Current stage within the BMAP developmental process.</attrdef>
        <attrdefs>FDEP</attrdefs>
        <attrdomv>
          <edom>
            <edomv>BMAP Adopted / Adoption Pending</edomv>
            <edomvd>The BMAP has been adopted by the Secretary and stakeholders have started implementing projects or we have stakeholder agreement on the BMAP and the BMAP is moving through the internal adoption process.</edomvd>
          </edom>
          <edom>
            <edomv>Adoption Pending</edomv>
            <edomvd>We have stakeholder agreement on the BMAP and the BMAP is moving through the internal adoption process.</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Priority Areas with Basin Management Action Plan Activities in Progress</edomv>
            <edomvd>Areas where BMAPs are currently under development.</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>Areas Undergoing Restoration Supporting TMDL Implementation (RA Plans &amp; other non-BMAP TMDL implementation)</edomv>
            <edomvd>These are local restoration strategies similar to BMAP strategies but were done without going through the BMAP process.</edomvd>
          </edom>
        </attrdomv>
        <attrdomv>
          <edom>
            <edomv>BMAP Initiation in late 2010/early 2011</edomv>
            <edomvd>BMAP development will be initiated w/ local stakeholders during this time period.</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SUB_DATE</attrlabl>
        <attrdef>Date that BMAP spatial boundary was submitted or updated.  A NULL value indicates that initial date of submittal is unknown.</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>CONTACT_NA</attrlabl>
        <attrdef>Contact name</attrdef>
      </attr>
      <attr>
        <attrlabl>CONTACT_PH</attrlabl>
        <attrdef>Contact phone</attrdef>
      </attr>
      <attr>
        <attrlabl>CONTACT_EM</attrlabl>
        <attrdef>Contact email</attrdef>
      </attr>
      <attr>
        <attrlabl>ACRES</attrlabl>
        <attrdef>Area measured in acres.  Calculated in Custom FL Albers Projection.</attrdef>
        <attrdefs>FDEP</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Based on PROJECT</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>The date FGDL acquired the data from the source</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>Unique ID added by GeoPlan</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE.AREA</attrlabl>
        <attrdef>Area in meters</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE.LEN</attrlabl>
        <attrdef>Perimeter in meters</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
    </detailed>
    <overview>
      <eaover>.</eaover>
    </overview>
  </eainfo>
  <distinfo>
    <distrib>
      <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>
          <country>US</country>
        </cntaddr>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>DOWNLOADABLE DATA</resdesc>
    <distliab>The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. 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 data sources. 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 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</distliab>
  </distinfo>
  <metainfo>
    <metd>20200302</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Department of Environmental Protection (FDEP) OTIS/GIS Section</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>2600 Blair Stone Rd, MS 6520</address>
          <city>Tallahassee</city>
          <state>Florida</state>
          <postal>32399-2400</postal>
          <country>US</country>
        </cntaddr>
        <cntemail>GIS.Librarian@dep.state.fl.us</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>