<?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 Transportation</origin>
        <pubdate>20090728</pubdate>
        <title>FDOT EXISTING AND PROPOSED WILDLIFE CROSSINGS IN FLORIDA - 2009</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Tallahassee, FL</pubplace>
          <publish>Florida Department of Transportation</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
        <onlink>http://www.dot.state.fl.us/emo/pubs/APPROVED-Wildlife%20Crossing%20Guidelines3-13.pdf</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains Florida Department of Transportation (FDOT) existing and proposed wildlife crossings in the State of Florida. Wildlife crossings serve as connections between landscapes divided by roadways. These structures play a critical role in decreasing the barrier effect of roadways and increasing the permeability of roads for wildlife. Several types of crossings have been constructed throughout the state of Florida including culverts, underpasses, overpasses, and expanded bridges. Wildlife crossings that consist of overpass or underpass systems appear to have the most effective designs for accommodating the needs of a broad range of wildlife. Crossings coupled with barrier fencing may increase effectiveness and reduce the amount of road mortality.</abstract>
      <purpose>The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.</purpose>
      <supplinf>TYPES OF WILDLIFE CROSSINGS Underpasses and Culverts Underpasses serve as corridors that connect spatially separated habitats and enhance the efficacy of wildlife movement. Wildlife underpasses are typically 20 feet long or greater. Larger than most upland culverts, underpasses provide relatively unconfined passage for some wildlife species. Animals pass under an intersecting roadway through a bridge which forms part of the roadway. If sized appropriately, wildlife underpasses provide adequate air flow and light. Also, wildlife underpasses with open medians provide a certain amount of intermediate habitat for small mammals, reptiles, and amphibians. In some cases, very large culverts also serve as underpasses. Culverts can be modified to accommodate wildlife passage across roadways. Box culverts have four sides, including a bottom, and may be arranged in a horizontal series of small culverts or multiple chambers. Bottomless culverts consist of square or rectangular corrugated metal pipe culverts with a natural surface bottom. Oversized culverts may be used to accommodate wildlife passage of streams and small rivers. Overpass Structures More recently, overpass structures, also called ecoducts or green bridges, have been used to facilitate passage for a wide range of species. These structures provide relatively unconfined passage for wildlife while simultaneously providing plenty of light and air movement; however, prolonged exposure may lead to desiccation for some amphibian species. Expanded Bridges Expanded bridges that provide upland travel corridors adjacent to waterways provide passage for many terrestrial wildlife species as well as aquatic species that utilize stream corridors for travel. There are a variety of expanded bridges including single-span bridges, multi-span bridges, viaducts, and causeways. A single-span bridge, also known as an open-span bridge, consists of a structure that rests on abutments with no intermediate support columns. A multi-span bridge is similar, but has one or more intermediate support columns between the abutments. A viaduct is also known as a multi-span bridge but provides increased length to the bridge structure. A causeway is a form of viaduct that is usually constructed over wetlands. Fencing The most effective way to prevent wildlife-vehicular collisions is to utilize a combination of fencing and crossings. The use of animal fencing is usually necessary for wildlife crossings to be effective. Typically, wildlife fencing is installed on both sides of the roadway in a winged pattern connected to each end of a crossing structure. Animals that encounter the fence will travel along it and eventually be guided to the passageway system as opposed to entering the roadway. If an animal may become trapped on the roadway, fencing may also include one-way gates to provide an escape route through the fence and away from roadway. Fencing is a cost-effective solution for protecting wildlife from vehicular traffic on roadways. However, it is often not aesthetically pleasing to the public and may lead to highly fragmented and isolated wildlife populations if used in the absence wildlife crossings. Where possible, fencing is installed in and around existing vegetative cover to minimize the visual impact of the fencing. District 1 Proposed Wildlife Crossings Design and Coordination Report.pdf</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20090728</caldate>
        </sngdate>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-84.358555</westbc>
        <eastbc>-80.003338</eastbc>
        <northbc>30.529142</northbc>
        <southbc>24.626584</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Expanded Bridges</themekey>
        <themekey>Wildlife</themekey>
        <themekey>Crossing</themekey>
        <themekey>Underpasses</themekey>
        <themekey>Culverts</themekey>
        <themekey>Overpass Structures</themekey>
        <themekey>Fencing</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>structure</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Florida</placekey>
      </place>
    </keywords>
    <accconst>None</accconst>
    <useconst>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</useconst>
    <ptcontac>
      <cntinfo>
        <cntorgp>
          <cntorg>Florida Department of Transportation</cntorg>
        </cntorgp>
        <cntpos>Environmental Management Office (EMO)</cntpos>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>605 Suwannee St MS 37</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399-0450</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>850-414-4447</cntvoice>
        <cntfax>850-414-4443</cntfax>
        <cntemail>emo@dot.state.fl.us</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>AGENCY COORDINATION Considerable coordination is required among the FDOT, USFWS, FWC, Water Management Districts (WMD), and the U.S. Army Corps of Engineers (USACE) to firstly agree on the need for a particular wildlife crossing site, and subsequently, to select the appropriate design type and strategic placement of the crossing. To date, multi-agency task teams have successfully created wildlife crossings throughout the state of Florida that have enabled wildlife movement and reduced road kill.</datacred>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>Florida Department of Transportation Wildlife Crossing Guidelines http://www.dot.state.fl.us/emo/pubs/APPROVED-Wildlife%20Crossing%20Guidelines3-13.pdf District 1 Proposed Wildlife Crossings Design and Coordination Report.pdf</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>None</typesrc>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Kisinger Campo &amp; Associates Corp. developed a GIS base map of existing FDOT wildlife crossings with data attached (e.g., size, type, etc.). Wildlife Crossing GIS Database Mark Easley Sr. Project Manager Kisinger Campo &amp; Associates Corp. 201 N. Franklin Street, Suite 400 Tampa, FL 33602 (813) 871-5331 Ext. 4144 http://www.kisingercampo.com/CorporateOffice.html</procdesc>
        <srcused>KCA</srcused>
        <procdate>20090417</procdate>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Kisinger Campo &amp; Associates Corp.</cntorg>
              <cntper>Mark Easley</cntper>
            </cntorgp>
            <cntpos>Sr. Project Manager</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>201 N. Franklin Street, Suite 400</address>
              <city>Tampa</city>
              <state>FL</state>
              <postal>33602</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>(813) 871-5331 Ext. 4144</cntvoice>
            <cntemail>MEasley@kisingercampo.com</cntemail>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>The GeoPlan Center received via email the statewide wildlife crossings data layer from the Florida Department of Transportation (http://www.dot.state.fl.us/) on February 18th, 2011. Wildlife_Xings.zip The Wildlife_Xings.zip contained the following layer, WildlifeXing.shp, and it was in the NAD_1983_UTM_Zone_17N projection. This layer was then reprojected to the FGDL albers projection NAD83 HARN. The layer was renamed to wildlifexing_jul09.shp A DESCRIPT field was then added based on DOTNAME and XINGNUM. A FGDLAQDATE field was also added and populated. All fields were UPPER Cased.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20110218</procdate>
      </procstep>
      <procstep>
        <procdesc>Data imported to ArcSDE and exported as a shapefile.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20110303</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>175</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>WILDLIFEXING_JUL09</enttypl>
        <enttypd>WILDLIFEXING_JUL09.DBF</enttypd>
        <enttypds>FDOT</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>XINGNUM</attrlabl>
        <attrdef>Crossing Identification Number.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>XINGTYPE</attrlabl>
        <attrdef>Crossing Status Type.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>DOTNAME</attrlabl>
        <attrdef>FDOT Name / FM Number.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>FDOTDSCT</attrlabl>
        <attrdef>FDOT District Number.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>LATIT</attrlabl>
        <attrdef>Latitude</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>LONGIT</attrlabl>
        <attrdef>Longitude</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>FDOTTRNU</attrlabl>
        <attrdef>Not Defined By Source.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>CNTYNAME</attrlabl>
        <attrdef>County Name.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>HIGHWAY</attrlabl>
        <attrdef>Highway Name.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>LOCATION</attrlabl>
        <attrdef>Location written discription.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>BRDGNUM</attrlabl>
        <attrdef>Bridge Number.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>TGTSPECI</attrlabl>
        <attrdef>Target Species.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>XINGSIZE</attrlabl>
        <attrdef>Crossing Size.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>XINGSHP</attrlabl>
        <attrdef>Crossing Shape.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>EXCLUDEV</attrlabl>
        <attrdef>Crossing Exclusionary Devices.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>AGNCYREQ</attrlabl>
        <attrdef>Agency Requiring.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>CONCOST</attrlabl>
        <attrdef>Construction Cost.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>COMPDATE</attrlabl>
        <attrdef>Completion Date.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>PLANSET</attrlabl>
        <attrdef>Not Defined By Source.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>RPTS</attrlabl>
        <attrdef>Not Defined By Source.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>MONITORD</attrlabl>
        <attrdef>Monitored Status.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>ROADWAY</attrlabl>
        <attrdef>RCI Section.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>PTDMI</attrlabl>
        <attrdef>RCI Milepost.</attrdef>
        <attrdefs>FDOT</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Based on the Fields DOTNAME and XINGNUM.</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>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>
    </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>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 Transportation</cntorg>
        </cntorgp>
        <cntpos>Environmental Management Office</cntpos>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>605 Suwannee St MS 37</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32399-0450</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>850-414-4447</cntvoice>
        <cntfax>850-414-4443</cntfax>
        <cntemail>emo@dot.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>