This dataset contains 2016 records of public lodging establishments (i.e., hotels, motels, rooming houses, bed & breakfasts, apartments, resort condominiums and resort dwellings) in the state of Florida. The data used to create this layer was downloaded from the Florida Department of Business and Professional Regulation (DBPR) and only contains lodging facilities registered with DBPR. This dataset contains fields denoting the physical address, number of units/rooms, and contact information for lodging facilities in Florida. This data is meant to be used for planning purposes only and is not intended to represent a 100% inventory of lodging facilities in Florida. Lodging facility locations that have been verified are marked with the letter V in the FLAG field. This dataset is an update to the GC_HOTELS_JUN11 layer.
The data was created to serve as base information for use in GIS systems for a variety of planning and analytical purposes.
The Department of Business and Professional Regulation is the agency charged with licensing and regulating businesses and professionals in the State of Florida, such as cosmetologists, veterinarians, real estate agents and pari- mutual wagering facilities. Our mission is to license efficiently, regulate fairly, and we strive to meet this goal in our day-to-day operation. The Department is under the executive branch of the Governor and is governed by Chapter 120, F.S. The Department is structured according to the requirements of Section 20.165, F.S. ******************************************************************************** Please Note: The following point data represents only Geocoded features, these points HAVE NOT been validated via QAQC methods such as aerials or Google Street View. Records that have been marked with a FLAG = V are locations that have a geocoded match result of 100%. ******************************************************************************** Please Note: Duplicate address points may exist where more than one hotel occurs. ******************************************************************************** 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.
publication date
Under Chapter 119, Florida Statutes, the Department of Business and Professional Regulation (DBPR) is required to make available for inspection and copying any public record regardless of physical format, which is not otherwise exempted from public access by general law. To fulfill this obligation, the DBPR provides copies of electronic records to the public through free download. DBPR is only required to provide data in the format in which it is maintained and, as a result, does not provide paper copies of this information. In addition, the DBPR is not required to reformat its records to meet a requestor's particular needs. Section 119.01(2)(b), F.S., requires only that the agency provide electronic data in some common format such as, but not limited to, the American Standard Code for Information Interchange (ASCII) text format. As, the download files provided by DBPR are formatted as ASCII text, quote/comma delimited.
131 Architecture PO Box 115706
www.fgdl.org
Department of Business and Professional Regulation (DBPR)
GeoPlan relied on the integrity of the attribute information within the original data.
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.
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
Spatial and Attribute Information
GeoPlan Center Process Steps: Lodging information was obtained from the Florida Department of Business and Professional Regulation (DBPR) via their Lodging Public Records Site here: http://www.myfloridalicense.com/dbpr/sto/file_download/public-records-lodging.html Seven separate tables were downloaded representing different licensing and inspection districts across Florida in CSV format. These CSV files were combined into one comprehensive file. There were 39390 records in the combined table. This file was then exported to a DBF and geocoded using a composite geocoder utilizing parcel data, navteq streets, and tiger roads. After geocoding, the following steps were taken to process the results: - Points that were not matched to an address and had no spatial location were removed from the dataset, bringing the total record count to 35142. - Points that were matched using parcel data and which received a score of 100 were flagged as verified (V), all other records were flagged as not verified (NV). This information is found in the FLAG field which was added by GeoPlan. - This dataset was spatially joined with data from the 2015 parcels layer produced by GeoPlan, which can be found here: www.fgdl.org. - Multiple fields were moved around, removed, or added in order to meet the desired table structure for geocoded layers. - The FGDLAQDATE field was added based on the time GeoPlan acquired the data. The UPDATE_DAY field was added based on the date the data was updated by DBPR. The DESCRIPT field was added based on the NAME field. - All records were uppercased. Basic information about the original tables downloaded from DBPR can be seen below: - District 1, 7770 records - District 2, 5320 records - District 3, 7307 records - District 4, 10512 records - District 5, 2578 records - District 6, 3106 records - District 7, 2797 records Original table structure: - Board Code (200 identifies HR within the department) - License Type Code (see tables below) - Licensee Name - Rank Code (see tables below) - Modifier Code (see tables below) - Mailing Name (if different from Licensee Name) - Mailing Street Address Line 1 - Mailing Address Line 2 - Mailing Address Line 3 - Mailing City - Mailing State - Mailing Zip Code - Mailing County Code (see table below) - Primary Telephone Number - Business Name (Location) - Filler - Location Street Address Line 1 - Location Address Line 2 - Location Address Line 3 - Location City - Location State - Location Zip Code - Location County Code (see table below) - Secondary Telephone Number - District - Region - License Number - Primary Status Code (see table below) - Secondary Status Code (see table below) - Expiry Date - Last Inspection Date - Number of Seats (food service) or Rental Units (lodging)
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
Esri
Esri item which denotes the status of the geocoded address (whether it was matched or not)
Esri
Matched
Tie
Esri item which denotes the score with which the address was matched to a feature in the reference data.
Esri
Esri item which denotes the side of the street to which an address was matched, if the address locator thatt was used matched the address to a street.
Esri
Left
Not specified
In parcel
Right
Esri item which donates the address that the matched location actually resides based on the information of the matched candidate.
Esri
Parcel Identification Number, derived from the 2015 statewide parcel layer.
GeoPlan
License Number.
DBPR
Name of the lodging facility.
GeoPlan
A description of a facility's physical location providing direction for delivery and provision of emergency services.
GeoPlan
City of facility's physical location.
GeoPlan
US postal delivery designation of facility's physical location.
GeoPlan
County of facility's physical location.
GeoPlan
The phone number of the facility.
GeoPlan
The Type of facility.
GeoPlan
Bed & Breakfast
Resort Condominium
Resort Dwelling
Hotel
Motel
Nontransient Apartment
Transient Apartment
Entity owner of the facility.
GeoPlan
The responsible organization for management and operation of a facility (e.g., FEDERAL, STATE, COUNTY, MUNICIPAL, PRIVATE, WMD, etc).
GeoPlan
Classification of the operating entity. (e.g., public, private, quasi-public).
GeoPlan
Modifier code.
DBPR
Collective
Group
Single
Number of rental units.
DBPR
Feature spatial source.
GeoPlan
Feature data/tabular source.
GeoPlan
Latitude in decimal degrees.
GeoPlan
Longitude in decimal degrees.
GeoPlan
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 an 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/
GeoPlan
GeoPlan Center identification number.
GeoPlan
Facility acreage.
GeoPlan
Field added by GeoPlan based on NAME.
GeoPlan
Type of update that occurred. Please Note: The following point data represents only Geocoded features, these points HAVE NOT been validated via QAQC methods such as aerials or Google Street View. Records that have been marked with a FLAG = V are locations that have a geocoded match result of 100%.
GeoPlan
Verified.
GeoPlan
Not verified
GeoPlan
The date the data was last updated by the source.
GeoPlan
The date GeoPlan acquired the data from the source.
GeoPlan
Unique ID added by GeoPlan
GeoPlan
County Codes by Region: REGION 1 - Dade (23), Monroe (54) REGION 2 - Broward (16), Martin (53), Palm Beach (60) REGION 3 - Citrus (19), Hernando (37), Hillsborough (39), Pasco (61), Pinellas (62), Polk (63), Sumter (70) REGION 4 - Brevard (15), Indian River (41), Lake (45), Orange (58), Osceola (59), St. Lucie (66), Seminole (69), Volusia (74) REGION 5 - Alachua (11), Baker (12), Bradford (14), Clay (20), Columbia (22), Dixie (25), Duval (26), Flagler (28), Gilchrist (31), Hamilton (34), Lafayette (44), Levy (48), Marion (52), Nassau (55), Putnam (64), St. Johns (65), Suwannee (71), Union (73) REGION 6 - Bay (13), Calhoun (17), Escambia (27), Franklin (29), Gadsden (30), Gulf (33), Holmes (40), Jackson (42), Jefferson (43), Leon (47), Liberty (49), Madison (50), Okaloosa (56), Santa Rosa (67), Taylor (72), Wakulla (75), Walton (76), Washington (77) REGION 7 - Charlotte (18), Collier (21), Desoto (24), Glades (32), Hardee (35), Hendry (36), Highlands (38), Lee (46), Manatee (51), Okeechobee (57), Sarasota (68)
431 Architecture PO Box 115706
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
131 Architecture PO Box 115706
www.fgdl.org