<?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 District 5, Data Transfer Solutions, University of Florida GeoPlan Center</origin>
        <pubdate>20061206</pubdate>
        <title>FDOT DISTRICT 5 - FIRE STATIONS</title>
        <geoform>vector digital data</geoform>
        <pubinfo>
          <pubplace>Gainesville, FL</pubplace>
          <publish>University of Florida GeoPlan Center</publish>
        </pubinfo>
        <othercit>FDOT District 5</othercit>
        <onlink>www.edats.com</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset contains fire stations and emergency medical service (EMS) centers locations for the East Central Florida (FDOT District 5) area. This GIS layer was produced by Data Transfer Solutions (DTS) under contract with FDOT District 5 in 2006. This is one of many layers that fall into the general category of "sociocultural" GIS data.</abstract>
      <purpose>Data Transfer Solutions (DTS) is working with the Florida Department of Transportation, District 5 to create regional maps of "sociocultural" features, including hospitals, parks, cemeteries, school boundaries, and others. The maps will provide the FDOT with improved spatial information required for planning roadway projects.</purpose>
      <supplinf>Data development is a component of the Efficient Transportation Decision Making Process (ETDM). The primary objectives of the ETDM initiative include: Effective/timely decision making without compromising environmental quality. Integrating review and permitting process. - Early NEPA reviews and approvals - Full and early participation - Meaningful dispute resolution For more information about these initiatives an on-line search using keyword 'ETDM' will provide a number of resources. A listing of relevant documents and resources is included under: http://fdotenvironmentalstreamlining.urs-tally.com/Library/default.htm. - DTS USE CONSTRAINTS - All provided GIS data is to be considered a generalized spatial representation which is subject to revisions. The feature Boundaries are not to be used to establish legal boundaries or entitlements. For specific information, contact the appropriate department or agency. This information is provided as a visual representation only and is not intended to be used as a legal or official representation of legal boundaries or entitlements. The user assumes all responsibility for determining whether this file is appropriate for a particular purpose.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20060501</caldate>
        </sngdate>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-82.500268</westbc>
        <eastbc>-80.431931</eastbc>
        <northbc>29.635149</northbc>
        <southbc>27.863988</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Fire Stations</themekey>
        <themekey>Fire</themekey>
      </theme>
      <theme>
        <themekt>ISO 19115 Topic Category</themekt>
        <themekey>society</themekey>
      </theme>
      <place>
        <placekt>None</placekt>
        <placekey>Brevard County</placekey>
        <placekey>Osceola County</placekey>
        <placekey>Sumter County</placekey>
        <placekey>Seminole County</placekey>
        <placekey>Flagler County</placekey>
        <placekey>Lake County</placekey>
        <placekey>East Central Florida</placekey>
        <placekey>Marion County</placekey>
        <placekey>Volusia County</placekey>
        <placekey>FDOT District 5</placekey>
        <placekey>Orange County</placekey>
      </place>
      <stratum>
        <stratkt>None</stratkt>
        <stratkey>terrestrial</stratkey>
      </stratum>
    </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 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>FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
      </cntinfo>
    </ptcontac>
    <datacred>FDOT District 5, Data Transfer Solutions (DTS), and the GeoPlan Center at the University of Florida.</datacred>
    <secinfo>
      <secclass>Unclassified</secclass>
      <sechandl>Contact the Florida DOT, District 5 for details.</sechandl>
    </secinfo>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
    <crossref>
      <citeinfo>
        <othercit>FGDL Metadata Explorer http://www.fgdl.org/metadataexplorer/explorer.jsp Data Transfer Solutions http://www.edats.com/index.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 horizontal positional accuracy has not been verified by GeoPlan</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <origin>DTS</origin>
            <pubdate>20061206</pubdate>
            <title>FDOT District 5 - FIRE STATIONS</title>
            <geoform>vector digital data</geoform>
            <pubinfo>
              <pubplace>Orlando, FL</pubplace>
              <publish>DTS</publish>
            </pubinfo>
            <onlink>www.edats.com</onlink>
          </citeinfo>
        </srccite>
        <srcscale>0</srcscale>
        <typesrc>None</typesrc>
        <srctime>
          <timeinfo>
            <rngdates>
              <begdate>20060929</begdate>
              <enddate>20061206</enddate>
            </rngdates>
          </timeinfo>
          <srccurr>publication date</srccurr>
        </srctime>
        <srccitea>DTS</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>Data for Sumter County Process Steps: Collected fire station data for Sumter County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth and http://sumtercounty.gov/fire/stations.htm and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following websites: http://www.lakesumterems.org/about_us/station_locations.aspx In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20060929</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Volusia County Process Steps: Collected fire station data for Volusia County from county GIS site (http://www.volusia.org/gis/Default.htm). Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061006</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Orange County Process Steps: Collected fire station data for Orange County from county GIS site (ftp://ftp.onetgov.net/divisions/Growth_Management/pub/) and from Florida Geogarphic Data Library (http://www.fgdl.org). Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Sites used include: http://www.orangecountyfl.net http://yp.yahoo.com In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061006</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Seminole County Process Steps: Collected fire station data for Seminole County from county GIS site (http://www.seminolecountyfl.gov/pd/commres/gis/layerbib2.asp). Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061006</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Osceola County Process Steps: Collected fire station data for Osceola County from county source and from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Merged the two fire station point files. Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061013</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Brevard County Process Steps: Collected fire station data for Brevard County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061025</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Lake County Process Steps: Collected fire station data for Lake County from county FTP site (ftp://ftp.co.lake.fl.us/) and from Florida Geographic Data Library (FGDL). Reprojected FGDL data set into State Plane Florida East NAD 83, feet. Combined data sets into single point file. Searched Google Earth and county site (http://www.lakegovernment.com/departments/public_safety /fire_rescue/station_location_map.aspx) and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.lakesumterems.org) In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061130</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Flagler County Process Steps: Collected fire station data for Flagler County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth and added missing fire stations found on Google Earth to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.ci.palm-coast.fk.us) (http://yellowpages.superpages.com) In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061201</procdate>
      </procstep>
      <procstep>
        <procdesc>Data for Marion County Process Steps: Collected fire station data for Marion County from county GIS site and from Florida Geographic Data Library (FGDL). Reprojected FGDL data set into State Plane Florida East NAD 83, feet. Searched Google Earth and Marion County site (http://www.marioncountyfl.org/FR526/FR_home.htm) and added missing fire stations found on these sites to the fire station point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data.</procdesc>
        <srcused>DTS</srcused>
        <procdate>20061206</procdate>
      </procstep>
      <procstep>
        <procdesc>GeoPlan Center - Process Steps: GeoPlan received this data, via FTP, and performed the following: -Reprojected to the FGDL Albers HPGN map projection. -Restructured the attribute table to fit the SCE Data Specification Document Standards. -Merged datasets together to create one FDOT District-wide shapefile. -Added FGDLAQDATE field based on the date FGDL acquired the data from the source. -Added DESCRIPT field based on 'NAME'</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20070117</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>478</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>FIRESTAT_D5_JAN07</enttypl>
        <enttypd>FIRESTAT_D5_JAN07.DBF</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>PARCELNO</attrlabl>
        <attrdef>Parcel Identification Number.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>NAME</attrlabl>
        <attrdef>Designation of fire department.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>ADDRESS</attrlabl>
        <attrdef>Facility's physical location.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>CITY</attrlabl>
        <attrdef>Associated city.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>ZIPCODE</attrlabl>
        <attrdef>Zip code of fire station.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>PHONE</attrlabl>
        <attrdef>Phone Number of unit.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>TYPE</attrlabl>
        <attrdef>Category of the Fire Station.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>OPERATING</attrlabl>
        <attrdef>The responsibe organization for management and operation of a facility</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>OP_CLASS</attrlabl>
        <attrdef>Classification of entity : city , state, state-IFIS, county, federal</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>SERVICES</attrlabl>
        <attrdef>Services rendered not typical of the operating entity</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>COMMON_USE</attrlabl>
        <attrdef>Location of two or more uses in one facility or on common grounds so as to share common facilities.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>USE</attrlabl>
        <attrdef>Description of co-located use</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>YR_BUILT</attrlabl>
        <attrdef>Year building was constructed</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>SOURCE</attrlabl>
        <attrdef>The Source of the base dataset from which the existing dataset was derived from.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>NOTES</attrlabl>
        <attrdef>Any notes on the particular feature.</attrdef>
        <attrdefs>DTS</attrdefs>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>Based on 'NAME'.</attrdef>
        <attrdefs>GEOPLAN</attrdefs>
      </attr>
      <attr>
        <attrlabl>FLAG</attrlabl>
        <attrdef>Type of update that occurred</attrdef>
        <attrdefs>GEOPLAN</attrdefs>
        <attrdomv>
          <edom>
            <edomv>A</edomv>
            <edomvd>Attribute edit</edomvd>
          </edom>
          <edom>
            <edomv>S</edomv>
            <edomvd>Spatial edit.</edomvd>
          </edom>
          <edom>
            <edomv>B</edomv>
            <edomvd>Both spatial and attribute edit.</edomvd>
          </edom>
          <edom>
            <edomv>N</edomv>
            <edomvd>New</edomvd>
          </edom>
          <edom>
            <edomv>D</edomv>
            <edomvd>Delete</edomvd>
          </edom>
          <edom>
            <edomv>NIN</edomv>
            <edomvd>Not in the new.</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>UPDATE_DAY</attrlabl>
        <attrdef>The last day the file was updated by the source.</attrdef>
        <attrdefs>GEOPLAN</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>The date FGDL aquired the data from the source.</attrdef>
        <attrdefs>GEOPLAN</attrdefs>
      </attr>
      <attr>
        <attrlabl>AUTOID</attrlabl>
        <attrdef>GeoPlan Center internal feature number</attrdef>
        <attrdefs>GEOPLAN</attrdefs>
      </attr>
      <attr>
        <attrlabl>SHAPE</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </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>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>
        <cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
      </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>
        <cntorgp>
          <cntorg>Data Transfer Solution</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing and physical</addrtype>
          <address>4037 Avalon Park Blvd East</address>
          <city>Orlando</city>
          <state>FL</state>
          <postal>32828</postal>
          <country>US</country>
        </cntaddr>
        <cntvoice>407-382-5222</cntvoice>
        <cntfax>407-382-5420</cntfax>
        <cntemail>general@edats.com</cntemail>
        <cntinst>http://www.edats.com/</cntinst>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
    <metsi>
      <metsc>Unclassified</metsc>
    </metsi>
  </metainfo>
</metadata>