<?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 NATURAL AREAS INVENTORY</origin>
        <pubdate>19910101</pubdate>
        <title>TNC Ecological Resource Conservation Areas</title>
        <edition>20010000</edition>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <publish>FLORIDA NATURAL AREAS INVENTORY</publish>
        </pubinfo>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains priority ecological resource areas as identified by the workshop of January 1991 sponsored by The Nature Conservancy, Florida Audubon Society and the Department of Natural Resources.</abstract>
      <purpose>This dataset contains priority ecological resource areas as identified by the workshop of January 1991 sponsored by The Nature Conservancy, Florida Audubon Society and the Department of Natural Resources. This dataset contains priority ecological resource areas as identified by the workshop of January 1991 sponsored by The Nature Conservancy, Florida Audubon Society and the Department of Natural Resources. The workshop consisted of a group of 40 experts in ecology, botany, zoology, geology, hydrology and land planning and management who were asked to identify their priority ecological resource areas on a series of maps. The final map which resulted from extensive debate and revision, identifies three categories of land: existing public land and private conservation areas; recommended P-2000 acquisition areas; and areas of conservation interest where less-than-fee-simple techniques should be used in addition to puchase. The conservation interest areas are not propesed for acquisition, but represent landscapes of mixed land use where compatible activities such as forest land, range land, public land, low intensity agriculture and some urban areas should be integrated properly to allow ecosystems to sustain an adequate level of functional stability and to provide connecting habitat corridors for the movement of species and maintenance of biological diversity. This dataset was produced only as a tool to be used in identifying ecologically significant areas as determined by this group of individuals. Over time, it is anticipated that other experts will add to, delete or otherwise modify the data to reflect a wider range of perspectives on priority ecological resources. The user can use either PRIORITY or INTEREST for shading. The reason that there are two attributes for the same purpose is that in some parts of the data there is a slight overlap between the priority ecological resource conservation areas and the conservation interest areas</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>19910101</caldate>
        </sngdate>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.637599</westbc>
        <eastbc>-79.918079</eastbc>
        <northbc>31.039455</northbc>
        <southbc>24.500246</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>biota</themekey>
        <themekey>environment</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>biota</themekey>
        <themekey>environment</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Southeast United States</placekey>
        <placekey>Florida</placekey>
        <placekey>Southeast U.S</placekey>
      </place>
      <temporal>
        <tempkt>None</tempkt>
        <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>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>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
      </cntinfo>
    </ptcontac>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <origin>FLORIDA NATURAL AREAS INVENTORY</origin>
        <pubdate>19910101</pubdate>
        <title>Unavailable</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 NATURAL AREAS INVENTORY</origin>
            <pubdate>19910101</pubdate>
            <title>Unavailable</title>
            <geoform>Map</geoform>
          </citeinfo>
        </srccite>
        <srcscale>500000</srcscale>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <sngdate>
              <caldate>19910101</caldate>
            </sngdate>
          </timeinfo>
          <srccurr>ground condition</srccurr>
        </srctime>
        <srccitea>FNAI</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.</procdesc>
        <procdate>unknown</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>442</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>INTEREST</attrlabl>
        <attrdef>Idicates whether or not the polygon is part of the conservation interest areas, where:</attrdef>
        <attrdefs>Unknown</attrdefs>
        <attrdomv>
          <edom>
            <edomv>INT</edomv>
            <edomvd>Polygon is part of the conservation interest areas</edomvd>
            <edomvds>Same</edomvds>
          </edom>
          <edom>
            <edomv>OUT</edomv>
            <edomvd>Polygon is not part of the conservation interest areas, i.e is part of the priority ecological resource conservation areas</edomvd>
            <edomvds>Same</edomvds>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>PRIORITY</attrlabl>
        <attrdef>Indicates whether or not the polygon is part of the priority ecological resource conservation areas</attrdef>
        <attrdefs>Unknown</attrdefs>
        <attrdomv>
          <edom>
            <edomv>PRI</edomv>
            <edomvd>Polygon is part of the priority ecological resource conservation areas</edomvd>
            <edomvds>Same</edomvds>
          </edom>
          <edom>
            <edomv>OUT</edomv>
            <edomvd>Polygon is not part the priority ecological resource conservation areas i.e is part of the conseravation interest areas</edomvd>
            <edomvds>Same</edomvds>
          </edom>
        </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>AUTOID</attrlabl>
      </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>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.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>20200302</metd>
    <metc>
      <cntinfo>
        <cntperp>
          <cntper>Operator</cntper>
        </cntperp>
        <cntaddr>
          <addrtype>physical</addrtype>
          <address>1018 Thomasville Road</address>
          <city>Tallahassee</city>
          <state>FL</state>
          <postal>32303</postal>
        </cntaddr>
        <cntvoice>(850) 224-8207</cntvoice>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>