<?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>20110307</pubdate>
        <title>Florida Hospitals Broadband Connectivity - March 2011</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>http://www.floridahealthfinder.gov/index.html</onlink>
      </citeinfo>
    </citation>
    <descript>
      <abstract>This dataset represents Florida Hospital locations and their broadband connections and capacity.</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>What is Geocoding? Geocoding is term used to describe the act of address matching. Geocoding is the process of finding a geographic location (x, y point) for an address (such as street number and name, city, state, and ZIP Code) on a map. Geocoding is based off the typical address scheme for the US, in which one side of the street contains even house numbers while the other side of the street contains odd house numbers. The geocoding process uses an algorithm to find the geographic location of addresses. First, a street segment is identified using the zip code and street name. Next, the geographic location of the address is matched using the building number to determine how far down the street and on which side of the street the building is located. Geocoding Accuracy The locational accuracy of geocoded addresses may vary from urban to rural areas due to the algorithm used to generate the geographic locations of addresses. The algorithm assumes that the size of parcels are equivalent along a road route. This assumption tends to be more consistent in urban areas, where the size of parcels vary less than in rural areas. Consequently, the results of geocoded addresses in urban areas are usually more reliable than those in rural areas. For example, the locational accuracy of rural addresses can be slightly off because some parcels along a rural route may be 15 acres while others may be 2.5 acres, but the geocoding algorithm assumes that the addresses are distributed evenly along the route.</supplinf>
    </descript>
    <timeperd>
      <timeinfo>
        <sngdate>
          <caldate>20110307</caldate>
        </sngdate>
      </timeinfo>
      <current>publication date</current>
    </timeperd>
    <status>
      <progress>Complete</progress>
      <update>As needed</update>
    </status>
    <spdom>
      <bounding>
        <westbc>-87.246532</westbc>
        <eastbc>-79.893358</eastbc>
        <northbc>30.984492</northbc>
        <southbc>24.527389</southbc>
      </bounding>
    </spdom>
    <keywords>
      <theme>
        <themekt>None</themekt>
        <themekey>Hospitals</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>University of Florida GeoPlan Center</cntorg>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611</postal>
        </cntaddr>
      </cntinfo>
    </ptcontac>
    <native> Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595</native>
  </idinfo>
  <dataqual>
    <attracc>
      <attraccr>GeoPlan relied on the integrity of the attribute information within the original data.</attraccr>
    </attracc>
    <logic>This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology</logic>
    <complete>This data is provided 'as is' by GeoPlan and is complete to our knowledge.</complete>
    <posacc>
      <horizpa>
        <horizpar>This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan</horizpar>
      </horizpa>
      <vertacc>
        <vertaccr>This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan</vertaccr>
      </vertacc>
    </posacc>
    <lineage>
      <srcinfo>
        <srccite>
          <citeinfo>
            <pubdate>20110301</pubdate>
            <title>Hospital Broadband Final CBS1.xlsx</title>
            <othercit>State of Florida</othercit>
            <onlink>http://www.floridahealthfinder.gov/index.html</onlink>
          </citeinfo>
        </srccite>
        <srcscale>0</srcscale>
        <typesrc>onLine</typesrc>
        <srccitea>GeoPlan</srccitea>
        <srccontr>Spatial and Attribute Information</srccontr>
      </srcinfo>
      <procstep>
        <procdesc>GeoPlan received this dataset from (insert name here) via email in March 2011. GeoPlan downloaded this data in an excel format and converted it to a dbf. The dbf was then geocoded against Navteq Roads and converted into a shapefile with the FGDL Albers HPGN map projection. Original file contained 286 records. There were problems with the geocoding of 30 records due to improperly formed addresses or incorrect zip codes. Of these 30, all 30 were corrected. - All records were upcased. - Changed original layer name from Hospital Broadband Final CBS1.xlsx to bb_hospitals - A DESCRIPT field was added based on NAME - A FGDLAQDATE field was added based on date GeoPlan downloaded the data</procdesc>
        <srcused>GeoPlan</srcused>
        <procdate>20110307</procdate>
      </procstep>
    </lineage>
  </dataqual>
  <spdoinfo>
    <direct>Vector</direct>
    <ptvctinf>
      <sdtsterm>
        <sdtstype>Entity point</sdtstype>
        <ptvctcnt>286</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>BB_HOSPITALS</enttypl>
        <enttypd>BB_HOSPITALS.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>Shape</attrlabl>
        <attrdef>Feature geometry.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <udom>Coordinates defining the features.</udom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Status</attrlabl>
        <attrdef>ESRI item which denotes the status of the geocoded address (whether it was matched or not).</attrdef>
        <attrdefs>ESRI</attrdefs>
      </attr>
      <attr>
        <attrlabl>Score</attrlabl>
        <attrdef>ESRI item which denotes the score with which the address was matched to a feature in the reference data.</attrdef>
        <attrdefs>ESRI</attrdefs>
      </attr>
      <attr>
        <attrlabl>Match_type</attrlabl>
        <attrdef>A code showing how an adddress was matched.</attrdef>
        <attrdefs>ESRI</attrdefs>
        <attrdomv>
          <edom>
            <edomv>A</edomv>
            <edomvd>Automatic</edomvd>
          </edom>
          <edom>
            <edomv>M</edomv>
            <edomvd>Manual</edomvd>
          </edom>
          <edom>
            <edomv>PP</edomv>
            <edomvd>Pick by point. Interactive map was used to place point.</edomvd>
          </edom>
        </attrdomv>
      </attr>
      <attr>
        <attrlabl>Side</attrlabl>
        <attrdef>ESRI item which denotes the side of the street to which the address was matched (for geocoding service styles that can match an address to a particular side of a street).</attrdef>
        <attrdefs>ESRI</attrdefs>
      </attr>
      <attr>
        <attrlabl>Match_addr</attrlabl>
        <attrdef>The address that the matched location actually resides based on the information of the matched candidate.</attrdef>
        <attrdefs>ESRI</attrdefs>
      </attr>
      <attr>
        <attrlabl>ARC_Zone</attrlabl>
        <attrdef>The zip code that the matched location actually resides based on the information of the matched candidate.</attrdef>
        <attrdefs>ESRI</attrdefs>
      </attr>
      <attr>
        <attrlabl>AHCA_NUM</attrlabl>
        <attrdef>Agency for Health Care Administration number</attrdef>
      </attr>
      <attr>
        <attrlabl>TYPE</attrlabl>
        <attrdef>Point type</attrdef>
      </attr>
      <attr>
        <attrlabl>NAME</attrlabl>
        <attrdef>Name of hospital</attrdef>
      </attr>
      <attr>
        <attrlabl>ADDRESS</attrlabl>
        <attrdef>Address</attrdef>
      </attr>
      <attr>
        <attrlabl>CITY</attrlabl>
        <attrdef>City</attrdef>
      </attr>
      <attr>
        <attrlabl>STATE</attrlabl>
        <attrdef>State</attrdef>
      </attr>
      <attr>
        <attrlabl>ZIP</attrlabl>
        <attrdef>Zip code</attrdef>
      </attr>
      <attr>
        <attrlabl>COUNTY</attrlabl>
        <attrdef>County</attrdef>
      </attr>
      <attr>
        <attrlabl>PHONE</attrlabl>
        <attrdef>Phone number</attrdef>
      </attr>
      <attr>
        <attrlabl>MAIL_ADD</attrlabl>
        <attrdef>Mailing address</attrdef>
      </attr>
      <attr>
        <attrlabl>MAIL_CITY</attrlabl>
        <attrdef>Mailing city</attrdef>
      </attr>
      <attr>
        <attrlabl>MAIL_ST</attrlabl>
        <attrdef>Mailing state</attrdef>
      </attr>
      <attr>
        <attrlabl>MAIL_ZIP</attrlabl>
        <attrdef>Mailing zip code</attrdef>
      </attr>
      <attr>
        <attrlabl>MAIL_CNTY</attrlabl>
        <attrdef>Mailing county</attrdef>
      </attr>
      <attr>
        <attrlabl>LIC_STAT</attrlabl>
        <attrdef>License status</attrdef>
      </attr>
      <attr>
        <attrlabl>OWNER</attrlabl>
        <attrdef>Owner</attrdef>
      </attr>
      <attr>
        <attrlabl>ADMIN</attrlabl>
        <attrdef>Administrator or CEO</attrdef>
      </attr>
      <attr>
        <attrlabl>BEDS</attrlabl>
        <attrdef>Number of beds</attrdef>
      </attr>
      <attr>
        <attrlabl>PROF_STAT</attrlabl>
        <attrdef>Profit status</attrdef>
      </attr>
      <attr>
        <attrlabl>WEBSITE</attrlabl>
        <attrdef>Web address</attrdef>
      </attr>
      <attr>
        <attrlabl>CON1_TYPE</attrlabl>
        <attrdef>Type of service of first internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON1_UP</attrlabl>
        <attrdef>Upstream connection speed of first internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON1_DOWN</attrlabl>
        <attrdef>Downstream connection speed of first internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON2_TYPE</attrlabl>
        <attrdef>Type of service of second internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON2_UP</attrlabl>
        <attrdef>Upstream connection speed of second internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON2_DOWN</attrlabl>
        <attrdef>Downstream connection speed of second internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON3_TYPE</attrlabl>
        <attrdef>Type of service of third internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON3_UP</attrlabl>
        <attrdef>Upstream connection speed of third internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>CON3_DOWN</attrlabl>
        <attrdef>Downstream connection speed of third internet connection</attrdef>
      </attr>
      <attr>
        <attrlabl>NET_CONS</attrlabl>
        <attrdef>Total number of internet connections</attrdef>
      </attr>
      <attr>
        <attrlabl>DESCRIPT</attrlabl>
        <attrdef>FGDL added field based on NAME</attrdef>
        <attrdefs>GeoPlan</attrdefs>
      </attr>
      <attr>
        <attrlabl>FGDLAQDATE</attrlabl>
        <attrdef>FGDL added field based on date downloaded from 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>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
        <cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
        <cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
        <cntemail>Web site: http://www.fgdl.org</cntemail>
        <cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
      </cntinfo>
    </distrib>
    <resdesc>DOWNLOADABLE DATA</resdesc>
    <distliab>The Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist. Furthermore, the GIS data available in the FGDL are provided 'as is'. The University of Florida GeoPlan Center makes no warranties, guaranties or representations as to the truth, accuracy or completeness of the data provided by the data sources. The University of Florida GeoPlan Center makes no representations or warranties about the quality or suitability of the materials, either expressly or implied, including but not limited to any implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The University of Florida GeoPlan Center shall not be liable for any damages suffered as a result of using, modifying, contributing or distributing the materials. A note about data scale: Scale is an important factor in data usage. Certain scale datasets are not suitable for some project, analysis, or modeling purposes. Please be sure you are using the best available data. 1:24000 scale datasets are recommended for projects that are at the county level. 1:24000 data should NOT be used for high accuracy base mapping such as property parcel boundaries. 1:100000 scale datasets are recommended for projects that are at the multi-county or regional level. 1:125000 scale datasets are recommended for projects that are at the regional or state level or larger. Vector datasets with no defined scale or accuracy should be considered suspect. Make sure you are familiar with your data before using it for projects or analysis. Every effort has been made to supply the user with data documentation. For additional information, see the References section and the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our webpage at: http://geoplan.ufl.edu/education.html</distliab>
  </distinfo>
  <metainfo>
    <metd>20200302</metd>
    <metc>
      <cntinfo>
        <cntorgp>
          <cntorg>University of Florida GeoPlan</cntorg>
          <cntper>Danny Downing</cntper>
        </cntorgp>
        <cntaddr>
          <addrtype>mailing</addrtype>
          <address>431 Architecture PO Box 115706</address>
          <city>Gainesville</city>
          <state>FL</state>
          <postal>32611</postal>
        </cntaddr>
      </cntinfo>
    </metc>
    <metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
    <metstdv>FGDC-STD-001-1998</metstdv>
    <mettc>local time</mettc>
  </metainfo>
</metadata>