<?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>University of Florida GeoPlan Center</origin>
        <pubdate>20100301</pubdate>
        <title>MILITARY LANDS IN FLORIDA BUFFERED BY 10 MILES - FOR USE WITH ETDM NOTIFICATION TOO</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Gainesville, Fl</pubplace>
          <publish>University of Florida GeoPlan Center</publish>
        </pubinfo>
        <othercit>State of Florida</othercit>
        <onlink>www.fgdl.org</onlink>
        <lworkcit>
          <citeinfo>
            <origin>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</origin>
            <pubdate>20060101</pubdate>
            <title>National Transportation Atlas Databases (NTAD) 2006</title>
            <geoform>vector digital data</geoform>
            <pubinfo>
              <pubplace>Washington, DC</pubplace>
              <publish>Research and Innovative Technology Administration's Bureau of Transportation Statistics (RITA/BTS)</publish>
            </pubinfo>
            <onlink>http://www.bts.gov/programs/geographic_information_services/</onlink>
          </citeinfo>
        </lworkcit>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains locations of United States Military Installations in Florida buffered by 10 miles. This layer has been created for ETDM to be used for notification purposes</abstract>
      <purpose>To provide graphic representation, location and attribute data for analysis, modeling and simulation, and studies.</purpose>
    </descript>
    <timeperd>
      <timeinfo>
        <rngdates>
          <begdate>20060101</begdate>
          <enddate>20100301</enddate>
        </rngdates>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.612977</westbc>
        <eastbc>-79.765155</eastbc>
        <northbc>30.915292</northbc>
        <southbc>24.371377</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Base</themekey>
        <themekey>Military Facilities</themekey>
        <themekey>Military Bases</themekey>
        <themekey>Installation</themekey>
        <themekey>Facility</themekey>
        <themekey>Military Installations</themekey>
        <themekey>Military</themekey>
      </theme>
      <theme>
        <themekt>None</themekt>
        <themekey>intelligenceMilitary</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Categories</themekt>
        <themekey>intelligenceMilitary</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>US</placekey>
        <placekey>United States</placekey>
        <placekey>USA</placekey>
      </place>
      <stratum>
        <stratkt>None</stratkt>
        <stratkey>ground</stratkey>
      </stratum>
      <temporal>
        <tempkt>None</tempkt>
        <tempkey>2006</tempkey>
      </temporal>
    </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 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>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</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>Web site: http://www.fgdl.org</cntemail>
        <cntinst>State of Florida</cntinst>
      </cntinfo>
    </ptcontac>
    <secinfo>
      <secsys>None</secsys>
      <secclass>Unclassified</secclass>
      <sechandl>N/A</sechandl>
    </secinfo>
    <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>
      <qattracc>
        <attraccv>unknown</attraccv>
        <attracce>None</attracce>
      </qattracc>
    </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>GeoPlan received data from a 5th source, Todd Horton, on 11/16/2006. This data took precedence over the existing data. If data from Todd Horton existed in an area then the existing data was deleted and Horton's data was appended. The resulting shapefile was named MILITR_DEC06. The following notes show the polygons that had to be deleted from MILITR_2006 in order to make room for Todd Horton's data nsa_panama_city: -delete NAV COASTAL SYS CTR, PANAMA CITY polygon from MILITR_2006 ns_mayport: -delete NAVAL STATION MAYPORT STATION polygon from MILITR_2006 nsa_orlando: -no problems nas_whiting_field: -delete WHITING FIELD NAS from MILITR_2006 polygon from MILITR_2006 -some over lap with EGLIN AIR FORCE BASE from MILITR_2006 nas_pensacola: delete the following polygons from MILITR_2006 -PENSACOLA NAVAL COMPLEX -BLUE ANGEL NAVAL RECREATION AR -NAVAL EDUCATION AND TRAINING -NAVAL TECHNICAL TRAINING CENTE NAS_Key_West_alb: delete the following from polygons from MILITR_2006 -NAVAL AIR STATION, KEY WEST -FLEMING KEY -MILITARY PROPERTY -TRUMAN ANNEX (KEY WEST NAVAL S -NAVAL HOUSING AREA -NAVAL MEDICAL CLINIC KEY WEST -TRUMBO POINT ANNEX NAS_Jacksonville: delete the following polygons from MILITR_2006 -JACKSONVILLE NAVAL COMPLEX -WHITEHOUSE FIELD Fort_Lauderdale: delete the following polygons from MILITR_2006 -US NAVAL RESERVATION Blount_Island: delete the following polygons from MILITR -BLOUNT ISLAND</procdesc>
        <srcused>GeoPlan</srcused>
      </procstep>
      <procstep>
        <procdesc>GeoPlan received data from a 6th source, Sara Leitman Neihaus (Sara.Leitman@dca.state.fl.us) of Florida Communities Trust, on 3/18/2010. This data took precedence over the existing data. If data from Sara Leitman Neihaus existed in an area then the existing data was deleted and Sara's data was appended. The resulting shapefile was named MILITR_MAR10. The following notes show the polygons that had to be modified from MILITR_DEC06 in order to represent Sara's data NAS JACKSONVILLE -merge 3 polygons to one NAS KEY WEST -merged 69 polygons to form Boca Chica -deleted 14 records of surrounding parcels through the keys NS MAYPORT -merged 2 polygons -deleted 2 polygons PATRICK AIR FORCE BASE -Sara indicated that MILITR needed to delete "off-base housing parcels" but these parcels could not be located HOMESTEAD AIR FORCE RESERVE BASE -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for HOMESTEAD AIR FORCE RESERVE BASE EGLIN AIR FORCE BASE and HURLBURT FIELD -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for EGLIN AIR FORCE BASE RESERVE NOLF SAUFLEY FIELD -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for NOLF SAUFLEY NOLF SANTA ROSA -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for NOLF SANTA ROSA NOLF HOLLEY -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for NOLF HOLLEY NAS WHITING FIELD -deleted existing data, added FCT Major Military Installations FF10 with data source.shp for NAS WHITING FIELD A dissolve was then run on all fields. This created multi-part shapes for some bases. In all cases but 1, the multi-part features are adjacent or very close to adjacent. In the case of NSWC FT LAUDERDALE the multi-part features are about 2.5 miles apart.</procdesc>
        <srcused>GeoPlan</srcused>
      </procstep>
      <procstep>
        <procdesc>Florida Department of Community Affairs combined data from the older FGDL layer MILITR.shp and MILITARY_BASES.shp from the Florida Division of Emergency Management. The following are notes taken by the DCA when combining the two layers: GeoPlan 1. Avon Park: not accurate 2. Blount Island: missing 3. Camp Blanding: good 4. Eglin: good; but the outline includes a large blob on the NW edge of the base that crosses I-10; I don't know what that is. 5. Homestead: old map; base is now smaller 6. MacDill: minor boundary errors 7. Jacksonville: I don't have a good map, but looks generally OK 8. Key West: Look OK. 9. Mayport: Generally OK; note that there is an area of Navy Enlisted Housing and an area of Navy Exchange and Commissary just south of the map base that is missing from this layer. 10. Panama City: Missing 11. Pensacola: looks OK 12. Whiting Field: Missing (also there are several NOLFs that are missing) 13. Patrick/Cape Canaveral: Patrick look OK; Cape Canaveral is missing 14. Tyndall: missing some land to the NW of the main base Note: layer shows Cecil Field which is no longer military, so delete, FDEM layer 1. Avon Park: look OK (better than GeoPlan) 2. Blount Island: looks OK 3. Camp Blanding: looks OK 4. Eglin: looks OK 5. Homestead: 6. MacDill: looks OK 7. Jacksonville: looks OK 8. Key West: looks OK. 9. Mayport: same comment as GeoPlan 10. Panama City: looks OK. 11. Pensacola: looks OK 12. Whiting Field: looks OK 13. Patrick/Cape Canaveral: Patrick OK; Cape Canaveral missing 14. Tyndall: same comment as GeoPlan</procdesc>
        <procdate>unknown</procdate>
      </procstep>
      <procstep>
        <procdesc>Military installation boundaries were added from TIGER data and topologically integrated. The dataset was checked for completeness and accuracy in ArcInfo and was converted to polygon shapefile format.</procdesc>
        <srcused>TIGER</srcused>
        <procdate>20060101</procdate>
        <srcprod>MILBASE</srcprod>
        <proccont>
          <cntinfo>
            <cntorgp>
              <cntorg>Military Traffic Management Command Transportation Engineering Agency (MTMCTEA)</cntorg>
              <cntper>Darryl Hampton</cntper>
            </cntorgp>
            <cntpos>Civil Engineer/GIS Analyst</cntpos>
            <cntaddr>
              <addrtype>mailing and physical</addrtype>
              <address>720 Thimble Shoals Blvd., Suite 130</address>
              <city>Newport News</city>
              <state>VA</state>
              <postal>23606</postal>
              <country>US</country>
            </cntaddr>
            <cntvoice>757-599-1171</cntvoice>
          </cntinfo>
        </proccont>
      </procstep>
      <procstep>
        <procdesc>GeoPlan received this dataset from 4 different sources: 1) email from Florida Department of Community Affairs in October 2006. The data was received in shapefile format and was in the following projection: Geographic NAD27. 2) NTAD cd-rom retrieved from source 8/9/2006. The data was received in shapefile format in the following projection: Geographic WGS84. 3) Avon Park boundary received in shapefile format via email from Brent Bonner. 4) PineCastle Bombing Range was digitized by GeoPlan based on in house imagery and information gathered from the following website: http://www.globalsecurity.org/military/facility/pinecastle.htm - NTAD data was renamed from MILBASE to MILITR_2006 and other sources were appended to this layer. All military installation boundaries that were in the FDEM layer but not in the NTAD layer were appended to MILITR_2006. - Cecil Field was deleted - All records were upcased. - A DESCRIPT field was added based on NAME - A FGDLAQDATE field was added based on date of download for each source.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20061106</procdate>
      </procstep>
      <procstep>
        <procdesc>Buffered militr_mar10 by 10 miles. This layer has been created for ETDM to be used for notification purposes</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20100324</procdate>
      </procstep>
      <procstep>
        <procdesc>Data imported to ArcSDE and exported as a shapefile.</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20100421</procdate>
      </procstep>
      <procstep>
        <procdesc>EGLIN update selected EGLIN from MILITR (_MAR10) select all counties that intersect dissolved counties to create clip layers merged dissolved, clipped layers extended countybnds to account for EGLIN buffer clipped EGLIN into 3 loaded 3 new clipped polys to MILITR_BUFF (appended AUTOIDs) deleted previous existing poly for EGLIN AFB (AUTOID=11) note: No change to MILITR HURLBURT FIELD update Couldn't find any existing geometry Digitized new poly based on image found in google search (modified from extracted EGLIN poly) Appended to existing etat.MILITR Buffered Hurlburt poly (10 mile) Appended buffered poly to MILITR_BUFF did not change name of layer, it stayed with MILITR_BUFF_MAR10</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20201028</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>GT-polygon composed of chains</sdtstype>
        <ptvctcnt>49</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>MILITR_BUFF_MAR10<enttyp>
        <enttypl>MILITR_BUFF_MAR10</enttypl>
        <enttypd>MILITR_BUFF_MAR10</enttypd>
        <enttypds>GeoPlan</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>FAC_NAME</attrlabl>
        <attrdef>The name of the military installation.</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>List of Official Military Installation Names</codesetn>
            <codesets>MTMCTEA</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ST_NAME</attrlabl>
        <attrdef>The state or U.S. territory in which the military installation is located.</attrdef>
        <attrdefs>RITA/BTS</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>List of U.S. States and Territories</codesetn>
            <codesets>RITA/BTS</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>ST_ABBR</attrlabl>
        <attrdef>The abbreviation for the state or U.S. Territory in which the military facility is located.  This is the two-letter official postal abbreviation.</attrdef>
        <attrdefs>RITA/BTS</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>List of Official US State and Territory Postal Abbreviations</codesetn>
            <codesets>U.S. Post Office</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>FAC_TYPE</attrlabl>
        <attrdef>Facility description.</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>Geolocation File</codesetn>
            <codesets>MTMCTEA</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>CLOSURE</attrlabl>
        <attrdef>The closure date of the installation due to a Base Realignment and Closure round</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <udom>Character Value</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>REALIGN</attrlabl>
        <attrdef>The realignment date of the installation due to a Base Realignment and Closure round</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <udom>Character Value</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>BRAC</attrlabl>
        <attrdef>The round of Base Realignment and Closure that affected the installation</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <udom>Character Value</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>BRANCH</attrlabl>
        <attrdef>Military organization category.</attrdef>
        <attrdefs>MTMCTEA</attrdefs>
        <attrdomv>
          <edom>
            <edomv>Air Force</edomv>
            <edomvd>Air Force Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>Army</edomv>
            <edomvd>Army Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>Coast Guard</edomv>
            <edomvd>Coast Guard Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>DLA</edomv>
            <edomvd>Defense Logistics Agency Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>Marine Corps</edomv>
            <edomvd>Marine Corps Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>National Guard</edomv>
            <edomvd>National Guard Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>Navy</edomv>
            <edomvd>Naval Facility</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
          <edom>
            <edomv>Other</edomv>
            <edomvd>Facility operated by an organization not belonging to one of the seven "Branch" categories enumerated above.</edomvd>
            <edomvds>MTMCTEA</edomvds>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>STFIPS</attrlabl>
        <attrdef>The state FIPS code for the state or U.S. territory in which the military installation is located.</attrdef>
        <attrdefs>FIPS Pub 6-4</attrdefs>
        <attrdomv>
          <codesetd>
            <codesetn>FIPS (Federal Information Processing Standard) Pub 6-4</codesetn>
            <codesets>Bureau of the Census (BOC)</codesets>
          </codesetd>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>VERSION</attrlabl>
        <attrdef>The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed.</attrdef>
        <attrdefs>RITA/BTS</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>00</rdommin>
            <rdommax>99</rdommax>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>REVISION</attrlabl>
        <attrdef>REVISION is a 2-digit number that will be incremented individually for each record whenever a change is made to one of its fields.</attrdef>
        <attrdefs>RITA/BTS</attrdefs>
        <attrdomv>
          <rdom>
            <rdommin>00</rdommin>
            <rdommax>99</rdommax>
          </rdom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>SOURCE</attrlabl>
        <attrdef>Field added by GeoPlan indicating original source for record</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Field added by GeoPlan based on FAC_NAME</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>Date GeoPlan acquired data from 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>
  </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>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</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>
    <stdorder>
      <fees>None</fees>
    </stdorder>
    <availabl>
      <timeinfo>
        <sngdate>
          <caldate>20060101</caldate>
        </sngdate>
      </timeinfo>
    </availabl>
  </distinfo>
  <metainfo>
    <metd>20201028</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan Center</cntorg>
          <cntper>Sam Palmer</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>431 Architecture Building</address>
          <city>Gainesville</city>
          <state>Fl</state>
          <postal>32611</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>352-392-3246</cntvoice>
        <cntfax>352-392-3308</cntfax>
        <cntemail>data@fgd.org</cntemail>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>