FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: FLORIDA NURSING HOMES 2010 Q1 Geodataset Name: FDEM_NURSINGHOME_FEB10 Geodataset Type: SHAPEFILE Geodataset Feature: Point Feature Count: 3904 |
|
GENERAL DESCRIPTION:
|
|
DATA SOURCE(S): Florida Division of Emergency Management SCALE OF ORIGINAL SOURCE MAPS: VARIOUS GEODATASET EXTENT: State of Florida |
FEATURE ATTRIBUTE TABLES:
Datafile Name: FDEM_NURSINGHOME_FEB10.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
4 | Geometry |
ID
|
50 | String |
SECCLASS
|
30 | String |
NAME
|
254 | String |
TELEPHONE
|
12 | String |
ADDRESS
|
80 | String |
ADDRESS2
|
80 | String |
CITY
|
120 | String |
STATE
|
2 | String |
ZIP
|
5 | String |
ZIPP4
|
4 | String |
COUNTY
|
50 | String |
FIPS
|
5 | String |
DIRECTIONS
|
254 | String |
EMERGTITLE
|
50 | String |
EMERGTEL
|
15 | String |
EMERGEXT
|
10 | String |
CONTDATE
|
36 | Date |
CONTHOW
|
10 | String |
GEODATE
|
36 | Date |
GEOHOW
|
10 | String |
NAICSCODE
|
6 | String |
NAICSDESCR
|
120 | String |
GEOLINKID
|
10 | String |
X
|
8 | Double |
Y
|
8 | Double |
ST_VENDOR
|
10 | String |
ST_VERSION
|
10 | String |
GEOPREC
|
32 | String |
PHONELOC
|
3 | String |
QC_QA
|
14 | String |
WEBSITE
|
254 | String |
GNIS_ID
|
32 | String |
SOURCE
|
32 | String |
FAC_TYPE
|
254 | String |
TOT_STAFF
|
8 | Double |
TOT_RES
|
8 | Double |
BEDS
|
8 | Double |
EXC_BEDS
|
8 | Double |
OWNERSHIP
|
32 | String |
MEDICAIDID
|
32 | String |
MEDICAREID
|
32 | String |
STATELICID
|
32 | String |
SUPFACTYPE
|
254 | String |
USNG_FL_1K
|
10 | String |
DESCRIPT
|
85 | String |
FGDLAQDATE
|
36 | Date |
AUTOID
|
4 | Integer |
FEATURE ATTRIBUTE TABLES CODES AND VALUES:
Item | Item Description | |
OBJECTID |
Internal feature number. |
|
Shape |
Feature geometry. |
|
ID |
Unique identifier for feature assigned by TechniGraphics. These identifiers are intended to be unique across all layers on which TechniGraphics has worked. |
|
SECCLASS |
Security classification of feature.
|
|
NAME |
Name of entity. |
|
TELEPHONE |
Ten (10) digit telephone number for entity formatted as nnn-nnn-nnnn. |
|
ADDRESS |
Physical street address for entity. "PO Box", "General Delivery", "Rural Route", and "Highway Contract" addresses are not considered physical addresses and should not appear in this field. Some areas do not have regular city style addressing, so entities in those areas may not have a street number. In such cases, the name of the road on which they are located is listed in this field. Some rural areas may not have named roads. In these rare cases, this field will be blank. |
|
ADDRESS2 |
Location within physical address, e.g., floor, suite, building. |
|
CITY |
The name of the city associated with the entity's physical address. For physical addresses that the U.S. Postal Service (USPS) delivers to, this should be a "city" acceptable to the USPS as defined in their Address Information System (AIS). Sometimes the USPS does not deliver mail to a physical address but recognizes the location (i.e., they list the location as "undeliverable"). The cities associated with these locations are acceptable. In some cases, the USPS does not recognize individual physical addresses in a city; rather, they list the city as having "General Delivery". In these cases, the city and associated zip code are acceptable (the entity's [ADDRESS] field will contain a street address, not "general delivery"). The entity may not actually be located within the city limits of the "city" specified in its [CITY] field. Instead, it may actually be located within the city limits of another city. In some cases, the "city" that appears in this field may not even be a city in an administrative sense, but it is still an acceptable "city" to the USPS. An example of this is "Notre Dame, IN". There is no city in Indiana called "Notre Dame", but this is considered an acceptable city by the USPS for any delivery going to the University of Notre Dame which is actually located in the city of South Bend. "Notre Dame", like most USPS cities, is an easily recognized place, and it gives the user of the data a good general idea of where the entity is located (if the entity is located in a small municipality, the USPS "city" may be more recognizable than the name of the municipality), and it would be part of the address one would use to send a shipment to the entity's location. Using the USPS acceptable "city" also allows someone to do a logical consistency check between the zip code and the city by using the USPS AIS.
Sometimes an entity may report a city that is not accepted by the USPS, and although TechniGraphics has tried to replace those cities with an acceptable alternative, some of them may remain in this dataset. |
|
STATE |
Two (2) character abbreviation for state associated with the entity's physical address. In almost all cases, this is the same as the state where the entity has been depicted geospatially. However, there are cases, particularly where an entity is part of a larger facility that cuts across state lines, where the entity's location may be depicted in a state other than the one indicated in this field. Also, the state in which an entity appears to be located may change depending on the scale of the state boundary theme being used. |
|
ZIP |
Five (5) digit USPS zip code for entity's physical location. |
|
ZIPP4 |
Four (4) digit USPS zip code extension. These values are automatically assigned using the entity's physical address and USPS address information system (AIS) data. |
|
COUNTY |
County name where entity is located. |
|
FIPS |
Five (5) digit FIPS (Federal Information Processing Standards) Code for the County where entity is located. The first two (2) digits represent the state and the last three (3) digits identify the county within the state. |
|
DIRECTIONS |
A description of the entity's location or status. |
|
EMERGTITLE |
Title of person or name of office for emergency point of contact. |
|
EMERGTEL |
Ten (10) digit telephone number of emergency point of contact formatted as nnn-nnn-nnnn. All alphabetic characters have been translated to the corresponding numeric digit. |
|
EMERGEXT |
Telephone extension for emergency point of contact. |
|
CONTDATE |
Date entity was contacted by TechniGraphics. |
|
CONTHOW |
Method by which entity was contacted.
|
|
GEODATE |
Date entity was geocoded by TechniGraphics. |
|
GEOHOW |
Method by which entity was geocoded.
|
|
NAICSCODE |
NAICS (North American Industry Classification System) Code for entity. NAICS Codes (and NAICS Descriptions) have been assigned based upon the entity's primary function, regardless of if that is the function that qualified it to be included in this dataset. |
|
NAICSDESCR |
NAICS (North American Industry Classification System) Description for entity. The "Index Entries" that appear on the NAICS webpage (http://www.census.gov/epcd/www/naics.html) are being used to populate this attribute as opposed to the "NAICS Title". While there is a one to one correspondence between NAICS Codes and "NAICS Titles", there is a one to many relationship between NAICS Codes and the "Index Entries". By using the "Index Entries", we have placed the entities that make up this layer into more specific categories; however, the user of this data should be aware that this was not the intended purpose of these "Index Entries". The "Index Entries" were intended as a way to search the NAICS database and as a way of enumerating ways in which establishments falling under the given NAICS Code may be named. Thus, there are often two or more "Index Entries" that are synonyms, for example: "Prisons" and "Penitentiaries". In cases like this, we have standardized on one "Index Entry". NAICS Descriptions (and NAICS Codes) have been assigned based upon the entity's primary function, regardless of the function that qualified it to be included in this dataset.
|
|
GEOLINKID |
Link ID for the street segment to which the entity was geocoded. Refer to the [ST_VENDOR] and [ST_VERSION] fields for the street vendor and version that was used to geocode the entity. |
|
X |
Longitude in WGS 84 Decimal Degrees. |
|
Y |
Latitude in WGS 84 Decimal Degrees. |
|
ST_VENDOR |
Indicates name of vendor providing original street data used for geocoding.
|
|
ST_VERSION |
Indicates the year and quarter of streets used for geocoding.
|
|
GEOPREC |
Geocoding precision.
|
|
PHONELOC |
Indicates whether the phone number in the [TELEPHONE] field rings to the actual location of the entity.
|
|
QC_QA |
Organization that performed Quality Control/Quality Assurance on the record.
|
|
WEBSITE |
Uniform Resource Locator (URL) for website associated with facility. |
|
GNIS_ID |
Geographic Names Information System ID
A permanent, unique number assigned to a geographic feature for the sole purpose of uniquely identifying that feature as a record in any information system database, dataset, file, or document and for distinguishing it from all other feature records so identified. The number is assigned sequentially (highest existing number plus one) to new records as they are created in the Geographic Names Information System. The number, by design, carries no information or association to the content of the feature record and therefore is not subject to change as attribute values change. Once assigned to a feature, the number is never changed or withdrawn, and never reassigned. The Feature ID can be applied in conjunction with system-unique record identifiers in any database or system, thus providing a national standard common reference identifier across multiple datasets. The Feature ID is stored in the GNIS database as an integer with a maximum of ten digits. |
|
SOURCE |
Original source of entity record.
|
|
FAC_TYPE |
Type of facility.
|
|
TOT_STAFF |
Total Staff
Total number of staff at the nursing home or assisted living facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
TOT_RES |
Total Residents
Total number of residents at the nursing home or assisted living facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
BEDS |
Number of Beds
Number of beds at the nursing home or assisted living facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
EXC_BEDS |
Excess Beds
Number of excess beds at the nursing home or assisted living facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
OWNERSHIP |
Ownership Category
Indicates the type of ownership for the nursing home or assisted living facility.
|
|
MEDICAIDID |
Medicaid ID
The Medicaid ID for the facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
MEDICAREID |
Medicare ID
The Medicare ID for the facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
STATELICID |
State License ID
The state license ID for the facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
SUPFACTYPE |
Supplied Facility Type
The supplied type of facility.
The values in this field were taken from source data and have not been verified by TechniGraphics. |
|
USNG_FL_1K |
Facility's 1-kilometer United States National Grid (USNG) address. The USNG is an alpha-numeric reference system based on the UTM coordinate system and is similar to the Military Grid Reference System. Use of the USNG ensures a uniform grid mapping and positional reporting system for search and rescue, emergency planning, response, and recovery. How to Read a United States National Grid (USNG) Spatial Address Website - http://www.fgdc.gov/usng/how-to-read-usng/index_html |
|
DESCRIPT |
Based on NAME. |
|
FGDLAQDATE |
The date FGDL acquired the data from the Source. |
|
AUTOID |
Unique ID added by GeoPlan |
TechniGraphics, Inc. Attribute Accuracy Report: For entities that were verified through alternate resources, the name, address, city, state, and five (5) digit zip codes were verified to be correct as of the date indicated by the [CONTDATE] field. The existence of the entity was also verified, as well as whether or not it met the criteria for inclusion in this dataset. Four (4) digit zip code extensions were derived from USPS (United States Postal Service) data and were not verified. ID Check: The [ID] field is not blank and each of its values is unique. Coordinate Check: Coordinates are not null or zero and the [X] and [Y] fields match the shape. Basic Address Check: Physical addresses were verified to be non blank and to not be a "PO Box", "General Delivery", "Highway Contract", or "Rural Route" address. Highway Address without Type Check: Physical addresses containing the word "Highway" or "Route" were verified to also contain a type designator such as "State", "US", or "County", if one actually exists for the highway or route. These type designators are often missing from addresses, leading to confusion if more than one "Highway" of the given number exists in an area. Basic Name Check: Entity name is not blank, is not the same as entity city, and has a minimum of two (2) characters. Name does not contain punctuation characters that can interfere with database operations, such as " (quote) and * (asterisk). City Check: Entity's [CITY] field is not blank, and entity is located within 25 miles of its tabular city as found in the NAVTEQ Named Places reference file. State Check: The entity is located within its tabular state. County Check: The entity is located within its tabular county. FIPS Check: The tabular FIPS Code matches the entity's tabular county and tabular state. County in Name vs. Geographic Location Check: If an entity's [NAME] field contains the word "county" or "co", the same county value should also be in the entity's [COUNTY] field. Basic Phone Check: All phone numbers (including the area code) are ten (10) numeric digits. Alphabetic characters have been converted to the corresponding numeric digit. NPA_NXX Check: Area codes (sometimes called "Number Planning Areas", or NPA's) and central office codes (sometimes known as exchanges, or NXX's) were validated against data from the North American Number Planning Administration (NANPA). In some cases, NPA-NXX combinations did not show up in the NANPA data but were verified to work. Area Code Distance Check: The entity's area code (NPA) is valid, and the entity is not more than 25 miles from its area code boundary, as defined by data from the North American Number Planning Administration (NANPA), unless TechniGraphics has previously verified that the phone number rings to a headquarters location or otherwise does not ring to the entity's location. Zip Code Check: The entity's zip code is five (5) or nine (9) numeric digits, is listed in the postal database, is in the same state as indicated by the entity's [STATE] value, and is not a PO Box only zip code. Zip City Check: The entity's zip code and its city were verified to match according to the USPS Address Information System (AIS). Zip Code Distance Check: The entity is located within 25 miles of its zip code boundary, as defined by the U.S. Census Bureau's 1999 Zip Code file. NAICS Code Check: The NAICS field is not blank, the NAICS Code is one of the accepted codes for this layer, the NAICS Description is an acceptable Index Entry for the NAICS Code, and certain key words in the entity name do not conflict with the NAICS Code. Collocation Check: Entities with different addresses must not share the exact same geospatial location. Geographic Spell Check: Words that appear in the entity name were checked against a standard English word list (and Spanish word list for entities in Puerto Rico). Words not appearing in these standard word lists were then checked against names appearing in the Geographic Names Information System (GNIS) of geographic features that are located within 25 miles of the entity. Proper names were manually reviewed for correct spelling. Supplied Coordinates Distance Check: Entity is located within 3 miles of coordinates supplied by the original source. |
TechniGraphics, Inc. Logical Consistency Report: See "Attribute_Accuracy_Report". Many of the checks described in that section check for both attribute accuracy and logical consistency. |
TechniGraphics, Inc. Completeness Report: If a facility is licensed by a state and holds multiple licenses, it is represented once in this dataset for each license, even if the licenses are for the same location. This dataset does not include retirement communities, adult daycare facilities, or rehabilitation facilities. Nursing Homes that are operated by and co-located with a hospital are also excluded because the locations are included in the hospital dataset. TechniGraphics was not tasked with ensuring the completeness of this layer. |
GeoPlan relied on the integrity of the attribute information within the original data. |
For purposes of this dataset, an assisted living facility is defined as a facility where the elderly, who are not related to the operator, reside and receive care, treatment, or services. Although not at the level of a nursing home, the services are above the level of an independent living community. They may include several hours per week of supportive care, personal care, or nursing care per resident. Generally, an assisted living facility offers help in daily living (laundry, cooking, cleaning, etc.) and personal assistance (bathing, eating, clothing, etc.). Many assisted living facilities offer assistance with medication and a lesser level of nursing care than what is offered at a nursing home. Assisted living facilities may be regulated by size restrictions depending on which type of assisted living facility it is considered to be in the state in which it exists. For example, Adult Family Homes in Wisconsin have between 3-4 elderly residents while Community Based Residential Facilities have 5 or more. Almost every state has different terminology to describe their version of the assisted living facility system. The structures in which assisted living facilities exist are varied as well. Depending on the type, an assisted living facility may operate out of a personal residence or a nursing home style structure, and it may be set up as apartment style living or as a campus setting in a continuing care retirement community. Multiple assisted living facilities may exist at one location or may be co-located with nursing homes and/or other similar health care facilities. If a facility is licensed by a state and holds multiple licenses, it is represented once in this dataset for each license, even if the licenses are for the same location. This dataset does not include retirement communities, adult daycare facilities, or rehabilitation facilities. Nursing Homes that are operated by and co-located with a hospital are also excluded because the locations are included in the hospital dataset. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. "#" and "*" characters were automatically removed from standard fields populated by TechniGraphics. Double spaces were replaced by single spaces in these same fields. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics. The currentness of this dataset is indicated by the [CONTDATE] field. Based on this field, the oldest record dates from 09/22/2009 and the newest record dates from 01/21/2010. FDEM Critical Facilities GIS Layers: To assist in emergency response and planning, the GIS Lab, working with local, state, and federal agencies maintains shelters, emergency operations centers, critical facilities, and hazardous material facilities datasets. "Critical facilities" are defined as those structures from which essential services and functions for victim survival, continuation of public safety actions, and disaster recovery are performed or provided. Shelters, emergency operation centers, public health, public drinking water, sewer and wastewater facilities are examples of critical facilities. Though not explicitly included in the definition, supporting life-line infrastructure essential to the mission of critical facilities must also be included in the inventory when appropriate. "Critical infrastructure" is defined as those systems and assets, whether physical or virtual, so vital that the incapacity or destruction of such systems and assets would have a debilitating impact on security, economy, public health or safety, or any combination of these elements. The Homeland Security Infrastructure Program (HSIP) is a collection of base map layers and homeland security related geospatial data. Currently, the emphasis of this program is on sharing and improving data to create uniform state & federal information. Working with contractors, the GIS Lab is providing data from state and local sources for QA/QC under the HSIP Freedom project. For more information, please see: http://www.floridadisaster.org/gis/criticalfacilities/index.htm |
Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1. A resource for evacuation planning and emergency management in the event of an emergency. 2. A threat against nursing homes has been identified and measures must be taken to protect these types of facilities. 3. A disaster has occurred, or is in the process of occurring, and facilities in the vicinity with people needing evacuation assistance must be identified. |
TechniGraphics, Inc. Accuracy Report: The horizontal accuracy is indicated by the [GEOPREC] field. Values are either "APPROXIMATE" or "ONENTITY". Based on the accuracy of the ortho imagery available to TechniGraphics, points are placed "ONENTITY" at the center of the main building. If the main building is not readily identifiable, points are placed "APPROXIMATE" at the center of the core building complex within the overall facility. If no specific core building complex is readily identifiable due to the size of the facility area or there being multiple building clusters, the point is placed "APPROXIMATE" in the center of the overall facility area. If the center of the overall facility area is unable to be determined, the point is placed "APPROXIMATE" along the correct street segment (block) on the correct side of the street. Records with "-DOD" appended to the end of the [NAME] value are located on a military base, as defined by the Defense Installation Spatial Data Infrastructure (DISDI) military installations and military range boundaries. |
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 |
Mike Thompson TechniGraphics, Inc. - Director of Geospatial Datasets mthompson@tgstech.com TechniGraphics, Inc. 3351 Eastbrook Drive Fort Collins, CO 80525 970-224-4996 8am - 5pm, Monday - Friday, Mountain Time http://www.tgstech.com/gis.asp Florida Division of Emergency Management http://www.floridadisaster.org/index.asp http://www.floridadisaster.org/gis/index.asp |
1) At the onset of processing, TechniGraphics attempted to contact all entities to determine or verify their name, physical address, city, state, five (5) digit zip code, ten (10) digit phone number, and geospatial location. 2) On 10/23/09, TechniGraphics ceased making phone calls to the entity. Entities were verified through alternate resources, such as maps and ortho imagery, or phone calls to alternative resources, such as city halls and county assessors. 3) All text fields were set to all upper case. 4) Leading and trailing spaces were trimmed from all text fields. 5) Non printable and diacritic characters were removed from all text fields. Process Date: 20100226 |
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: |
TechniGraphics, Inc. TGS 3351 Eastbrook Drive Fort Collins, CO 80525 970-224-4996 |
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