<?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>US Corp of Engineering</origin>
        <pubdate>20201001</pubdate>
        <title>U.S. Army Corp of Engineering 404 Jurisdiction Notification Layer - April 2021</title>
        <geoform>Vector Digital Data Set (Polygon)</geoform>
        <pubinfo>
          <pubplace>Washington, D.C.</pubplace>
          <publish>U.S. Army Corps of Engineers</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset is a combination of the usace404_assumption layer and the Florida boundary. This layer indicates whether 404 jurisdiction is USACE or FDEP for a given area.</abstract>
      <purpose>This dataset is based on the usace404_assumption layer and the Florida boundary. This layer is intended for use with the EST notification tool.</purpose>
      <supplinf>This a consolidation of multiple datasets that together represent the approximate extent of retained waters, with a 300-foot buffer applied to each dataset. It is divided into 2 components, Screening Layer 1 and Screening Layer 2, which overlap in many areas. Screening Layer 1 Datasets: Retained Waters List &#8211; This is a subset of lines and polygons from the USGS National Hydrography Dataset (1:24,000) representing the waters that are named on the MOA&#8217;s Retained Waters List. NOAA Composite Shoreline &#8211; This layer depicts shorelines of tidal water bodies as digitized from NOAA&#8217;s historic surveys (T-sheets) of shorelines at Mean HighWater (MHW) Screening Layer 2 Datasets: FWC Shoreline (1:12,000) &#8211; This layer depicts shorelines of tidal and other major waters as digitized from aerial imagery (2004 DOQQs) NOAA MHHW Inundation (Sea Level Rise 0 foot) &#8211; This layer is a GIS analysis of tidal and elevation data to show areas that would be inundated at Mean Higher High Water (MHHW) Note that mapped shorelines may be changed by erosion, accretion, construction, and sea level rise, maybe obscured by vegetation, and may not take into account the presence of water control structures, so the mapped shoreline may not be the same as the actual shoreline. The actual location of the 300 foot guideline must and shall be measured from the actual presence and location of the MHW (for tidal waters) or OHW (for non-tidal portions of the Retained Waters List) based on application drawings, site observations, or professional surveys. The purpose of the American Indian and Alaska Native Land Area Representation (AIAN-LAR) Geographic Information System (GIS) dataset is to depict the external extent of federal Indian reservations and the external extent of associated land held in &#8220;trust&#8221; by the United States, &#8220;restricted fee&#8221;or &#8220;mixed ownership&#8221; status for federally recognized tribes and individual Indians. This dataset includes other land area types such as Public Domain Allotments, Dependent Indian Communities and Homesteads. This GIS Dataset is prepared strictly for illustrative and reference purposes only and should not be used, and is not intended for legal, survey,engineering or navigation purposes. No warranty is made by the Bureau of Indian Affairs (BIA)for the use of the data for purposes not intended by the BIA. This GIS Dataset may contain errors. There is no impact on the legal status of the land areas depicted herein and no impact on land ownership. No legal inference can or should be made from the information in this GIS Dataset. The GIS Dataset is to be used solely for illustrative, reference and statistical purposes and may be used for government to government Tribal consultation. Reservation boundary data is limited in authority to those areas where there has been settled Congressional definition or final judicial interpretation of the boundary. Absent settled Congressional definition or final judicial interpretation of a reservation boundary, the BIA recommends consultation with the appropriate Tribe and then the BIA to obtain interpretations of the reservation boundary.The land areas and their representations are compilations defined by the official land title records of the Bureau of Indian Affairs (BIA) which include treaties, statutes, Acts of Congress,agreements, executive orders, proclamations, deeds and other land title documents. The trust,restricted, and mixed ownership land area shown here, are suitable only for general spatial reference and do not represent the federal government&#8217;s position on the jurisdictional status of Indian country. Ownership and jurisdictional status is subject to change and must be verified with plat books, patents, and deeds in the appropriate federal and state offices. Included in this dataset are the exterior extent of off reservation trust, restricted fee tracts and mixed tracts of land including Public Domain allotments, Dependent Indian Communities, Homesteads and government administered lands and those set aside for schools and dormitories. There are also land areas where there is more than one tribe having an interest in or authority over a tract ofland but this information is not specified in the AIAN-LAR dataset. The dataset includes both surface and subsurface tracts of land (tribal and individually held) &#8220;off reservation&#8221; tracts and not simply off reservation &#8220;allotments&#8221; as land has in many cases been subsequently acquired in trust.These data are public information and may be used by various organizations, agencies,units of government (i.e., Federal, state, county, and city), and other entities according to the restrictions on appropriate use. It is strongly recommended that these data be acquired directly from the BIA and not indirectly through some other source, which may have altered or integrated the data for another purpose for which they may not have been intended.Integrating land areas into another dataset and attempting to resolve boundary differences between other entities may produce inaccurate results. It is also strongly recommended that careful attention be paid to the content of the metadata file associated with these data. Users are cautioned that digital enlargement of these data to scales greater than those at which they were originally mapped can cause misinterpretation. The BIA AIAN-LAR dataset&#8217;s spatial accuracy and attribute information are continuously being updated, improved and is used as the as the single authoritative land area boundary data for the BIA mission. These data are available through the Bureau of Indian Affairs, Office of Trust Services, Division of Land Titles and Records, Branch of Geospatial Support.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20210401</caldate>
        </sngdate>
      </timeinfo>
      <current>Unknown</current>
    </timeperd>
    <status>
      <progress>In work</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.679145</westbc>
        <eastbc>-79.769058</eastbc>
        <northbc>31.702955</northbc>
        <southbc>24.339714</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>boundary</themekey>
      </theme>
    </keywords>
    <accconst>None</accconst>
    <useconst>The GIS datasets are not precise and therefore can only assist the initial and necessarily rapid screening of an application/request. The final determination can only be made by comparing actual observations of the site to the text of the MOA. Per the MOA (paragraph II.A): &#8220;The Corps will retain responsibility for permitting for the discharge of dredged or fill material in those waters identified in the Retained Waters List, as well as all waters subject to the ebb and flow of the tide shoreward to their mean high water mark that are not specifically listed in the Retained Waters List, including wetlands adjacent thereto landward to the administrative boundary. For purposes of this Agreement, the administrative boundary demarcating the adjacent wetlands over which jurisdiction is retained by the Corps is a 300-foot guide line established from the ordinary high watermark or mean high tide line of the retained water. In the case of a project that involves discharges of dredged or fill material both water ward and landward of the 300-foot guide line, the Corps will retain jurisdiction to the landward boundary of the project for the purposes of that project only.&#8221;</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Army Corps of Engineers</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>441 G Street, NW</address>
          <city>Washington</city>
          <state>DC</state>
          <postal>20314</postal>
        </cntaddr>
        <cntvoice>202-761-0018</cntvoice>
      </cntinfo>
    </ptcontac>
    <datacred>US Corp of Engineering</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
  </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>GeoPlan performed the following geospatial analysis to create this layer: run update command (input = county_dsv_buff2, update = usace_404_assumption) dissolve and name usace_404_notification</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20210219</procdate>
      </procstep>
      <procstep>
        <procdesc>This is layer is based on USACE_404_ASSUMPTION_APR21 dissolved merged with the FLBND (After Erase).</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20210421</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>2</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>USACE_404_NOTIFICATION_APR21</enttypl>
        <enttypd>USACE_404_NOTIFICATION_APR21.DBF</enttypd>
        <enttypds>Producer Defined</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>Shape_Leng</attrlabl>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>GeoPlan added field based on agency</attrdef>
        <attrdefs>Producer Defined</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>Date GeoPlan acquired data from the source.</attrdef>
        <attrdefs>Producer Defined</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>2020-11-30 00:00:00</rdommin>
            <rdommax>2020-11-30 00:00:00</rdommax>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
      </attr>
      <attr>
        <attrlabl>SHAPE.AREA</attrlabl>
      </attr>
      <attr>
        <attrlabl>SHAPE.LEN</attrlabl>
      </attr>
    </detailed>
  </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>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</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>20210421</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>U.S. Army Corps of Engineers</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>441 G Street, NW</address>
          <city>Washington</city>
          <state>DC</state>
          <postal>20314</postal>
        </cntaddr>
        <cntvoice>202-761-0018</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>