FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: HOSPITAL FACILITIES IN FLORIDA - 2017 Geodataset Name: GC_HOSPITALS_SEP17 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 349 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): University of Florida GeoPlan Center SCALE OF ORIGINAL SOURCE MAPS: Varies GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: GC_HOSPITALS_SEP17.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
PARCELID
|
40 | String |
FDEM_ID
|
10 | String |
NAME
|
100 | String |
ADDRESS
|
65 | String |
CITY
|
40 | String |
ZIPCODE
|
8 | Double |
COUNTY
|
35 | String |
PHONE
|
20 | String |
TYPE
|
55 | String |
OWNER
|
60 | String |
OPERATING
|
60 | String |
OP_CLASS
|
20 | String |
AHCA_OWNER
|
60 | String |
PROFIT
|
20 | String |
CAPACITY
|
8 | Double |
BEDS
|
8 | Double |
STATE_ID
|
20 | String |
EFCLASS
|
5 | String |
AHCA_NUM
|
20 | String |
CON1_TYPE
|
50 | String |
CON1_UP
|
50 | String |
CON1_DOWN
|
50 | String |
CON2_TYPE
|
50 | String |
CON2_UP
|
50 | String |
CON2_DOWN
|
50 | String |
CON3_TYPE
|
50 | String |
CON3_UP
|
50 | String |
CON3_DOWN
|
50 | String |
NET_CONS
|
5 | String |
WEBSITE
|
100 | String |
ACTYRBLT
|
8 | Double |
FSOURCE
|
100 | String |
DATASOURCE
|
20 | String |
NOTES
|
50 | String |
LAT_DD
|
8 | Double |
LONG_DD
|
8 | Double |
MGRS
|
15 | String |
GCID
|
8 | Double |
ACRES
|
8 | Double |
DESCRIPT
|
100 | String |
FLAG
|
5 | String |
UPDATE_DAY
|
36 | Date |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
PARCELID |
Parcel Identification Number, derived from either the 2014 or 2015 statewide parcel layers. |
|
FDEM_ID |
Florida Department of Emergency Management Idenitification number. |
|
NAME |
Name of the facility. |
|
ADDRESS |
A description of a facility's physical location providing direction for delivery and provision of emergency services. |
|
CITY |
City of facility's physical location. |
|
ZIPCODE |
US postal delivery designation of facility's physical location. |
|
COUNTY |
County of facility's physical location. |
|
PHONE |
The phone number of the facility. |
|
TYPE |
The type of facility. |
|
OWNER |
Entity owner of the facility. |
|
OPERATING |
The responsible organization for management and operation of a facility (e.g., public, private, quasi-public). |
|
OP_CLASS |
Classification of the operating entity. |
|
AHCA_OWNER |
Agency for Healthcare Administration Owner |
|
PROFIT |
Profit status for hospital. |
|
CAPACITY |
Capacity of the facility. |
|
BEDS |
Number of beds in the facility. |
|
STATE_ID |
State Hospital Data ID. For states that contributed data, this attribute is populated with the unique ID used by the state to track hospitals. Duplicate IDs may be possible where TGS has added records which correspond to a state provided record and, therefore, an identical ID was created. |
|
EFCLASS |
Indicates essential facilities classification. The values for this attribute were provided by the Post, Buckley, Schuh, and Jernigan, Incorporated (PBSJ) and TGS did not verify these values.
|
|
AHCA_NUM |
Agency for Health Care Administration number. |
|
CON1_TYPE |
Type of service of first internet connection. |
|
CON1_UP |
Upstream connection speed of first internet connection. |
|
CON1_DOWN |
Downstream connection speed of first internet connection. |
|
CON2_TYPE |
Type of service of second internet connection. |
|
CON2_UP |
Upstream connection speed of second internet connection. |
|
CON2_DOWN |
Downstream connection speed of second internet connection. |
|
CON3_TYPE |
Type of service of third internet connection. |
|
CON3_UP |
Upstream connection speed of third internet connection. |
|
CON3_DOWN |
Downstream connection speed of third internet connection. |
|
NET_CONS |
Total number of internet connections. |
|
WEBSITE |
Web address. |
|
ACTYRBLT |
The actual year built derived from the 2010 parcel database. |
|
FSOURCE |
Feature spatial source. |
|
DATASOURCE |
Feature Data/Tabular Source. |
|
NOTES |
Notes |
|
LAT_DD |
Latitude in decimal degrees. |
|
LONG_DD |
Longitude in decimal degrees. |
|
MGRS |
Military Grid Reference System (MGRS) Coordinate of the Facility. The MGRS is the geocoordinate standard used by NATO militaries for locating points on the Earth. The MGRS provides a means to represent any location on the surface of the Earth using alphanumeric string. Hierarchical references are based on the Universal Transverse Mercator (UTM) Coordinate System. The MGRS is used for the entire Earth. http://mgrs-data.org/ |
|
GCID |
The GeoPlan Center identification number that links this point layer feature with it's corresponding polygon layer feature (GC_HOSPITALSBND). |
|
ACRES |
Facility acreage. |
|
DESCRIPT |
Field added by FGDL based on NAME. |
|
FLAG |
Identifies if the facility's spatial location has been visually verified.
|
|
UPDATE_DAY |
The date the data was last updated by the Source. |
|
FGDLAQDATE |
The date FGDL acquired the data from the Source. |
|
AUTOID |
Unique ID added by GeoPlan |
This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology |
This data is provided 'as is' by GeoPlan and is complete to our knowledge. |
GeoPlan relied on the integrity of the attribute information within the original data. |
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. In the case of this dataset, special attention was given to the position of the resulting x,y point location of the geocoded address. The location of geocoded x,y point was manually moved by GeoPlan Center from the street to on top of the facility building. |
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes. |
This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan |
This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan |
None |
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 |
Hospital and Nursing Home Profiles http://www.hospital-data.com/ Federation of American Hospitals - Florida http://fah.org/# Florida Hospital Association - www.fha.org Florida Department of Health - Environmental Health GIS Data http://www.floridahealth.gov/environmental-health/gis/gis-data.html Florida Agency for Health Care Administration - Facility Locator http://www.floridahealthfinder.gov/facilitylocator/facloc.aspx |
The GeoPlan Center performed the following steps in order to create the 2009 statewide hospitals data layer (GC_HOSPITALS_ARP09). 6 Different Sources Comprise the Hospitals Dataset. The following Sources were either reprojected to the FGDL Albers NAD83 HPGN map projection or if no spatial data existed they were geocoded to a statewide 2008 Tele Atlas Streets dataset. For downloaded county and district wide polygon layers the label points were created and then used for each facility. Once the point sources were created via geocoding or reprojected existing point data they were merged into one statewide layer. Record (facility) duplications were removed by manually viewing and editing the statewide layer's attribute table for each of the 67 counties. Where record duplication existed source information of previously corrected FDEM data took preference followed by, County data, State Data, and finally geocoded data. Geocoded point locations were manually moved by GeoPlan Center from the street to on top of the facility building. Below are the data Sources as described in the Source field in the attribute table for the GC_HOSPITALS_ARP09 layer. Process Date: 20090403 |
Projection ALBERS Datum HPGN Units METERS Spheroid GRS1980 1st Standard Parallel 24 0 0.000 2nd Standard Parallel 31 30 0.000 Central Meridian -84 00 0.000 Latitude of Projection's Origin 24 0 0.000 False Easting (meters) 400000.00000 False Northing (meters) 0.00000
DATA SOURCE CONTACT (S):
Name: Abbr. Name: Address: Phone: Web site: E-mail: Contact Person: Phone: E-mail: |
University of Florida GeoPlan Center GeoPlan 131 Architecture PO Box 115706 Gainesville, FL 32611 |
Name: FLORIDA GEOGRAPHIC DATA LIBRARY Abbr. Name: FGDL Address: Florida Geographic Data Library 431 Architecture Building PO Box 115706 Gainesville, FL 32611-5706 Web site: http://www.fgdl.org Contact FGDL: Technical Support: http://www.fgdl.org/fgdlfeed.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html