Geodataset Name:       GC_GOLFBND_OCT15
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         1124

DATA SOURCE(S):                    University of Florida GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     Varies
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  20151005
TIME PERIOD OF CONTENT:            Begin Date: 20090101    End Date: 20151005
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: GC_GOLFBND_OCT15.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
PARCELID	Parcel Identification Number, derived from either the 2010 or 2012 statewide parcel layers.
NAME	Facility Name.
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	Facility Type. GOLF COURSE = Publicly owned golf course, for both public and private golf courses see the FGDL layer GC_GOLFBND & GC_GOLF.
COURSETYPE	Golf Course Type
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.
ACTYRBLT	Actual Year Built
FSOURCE	Feature Spatial Source.
DATASOURCE	Feature Data/Tabular Source.
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 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/
GCID	The GeoPlan Center identification number that links this polygon feature layer with its corresponding point feature layer.
ACRES	Facility acreage.
DESCRIPT	Field added by FGDL based on NAME.
FLAG	Type of update that occurred. NV = Not Verified V = Verified, in most cases this NAME field verification was based on ESRI/Google Imagery and Google Street View. The exact park boundaries are not verified and in many cases only based on parcel boundaries.
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
SHAPE.AREA	Area in meters
SHAPE.LEN	Perimeter in meters

USER NOTES:

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.

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

REFERENCES:

http://www.golflink.com/

DATA LINEAGE SUMMARY:

The GeoPlan Center Performed the following steps in creating the 2009 Statewide golf course data layer; 1) Parcels were extracted from the available 2009 DOR statewide parcel tax data based on their use code value of 038 (golf courses). 2) GeoPlan spatially related the newest Land Use and Cover files from each of the 5 water management districts (WMD) on the extracted parcels to determine discrepancies in the parcel database. Twenty courses were extracted from the WMD's land use files that were not included the original parcel extraction. 3) Additional information was collected and the dataset was further validated by utilizing Golf Link's online golf course directory. - Searched for courses in Florida at http://www.golflink.com/ - All addresses from the search were copied and pasted into a text file, which was then formatted and imported into Excel and converted into a dbf file format. - The addresses were then geocoded against a 2009 Tel Atlas road database and converted into a shapefile with FGDL Albers HPGN map projection. - GeoPlan spatially related the geocoded shapefile to further determine discrepancies between the extracted parcels and Golf Link's database. Seven golf facilities not included in the extracted parcels and WMD land use were digitized using satellite imagery. - Many times golf clubs have multiple courses. Each course in the Golf Link database has a separate record. This conflicts with the parcel and WMD land use databases which typically aggregate multiple golf courses belonging to the same club into one polygon. For these instances, the NAME field was recorded to indicate each of the course names and golf club represented by the polygon as recorded in the Golf Link geocoded database. The TYPE field was also aggregated to represent the total number of holes and yards across all represented by the polygon. The OP_CLASS field was also populated using the geocoded Golf Link's database. - This dataset contains the final selection and additions from the original parcel dataset with selected fields removed and socio-cultural effect fields and attribute definitions added. - Added the descript field based on NAME - Added the FGDLAQDATE based on the date GeoPlan acquired the data from the source. Process Date: 20100709 The GeoPlan Center performed the following steps in order to create the October 2015 statewide golf course data layer. Golf Course locations were checked using; 2014 parcel data, imagery, and Google Street View, and either marked as Verified or Not Verified in the FLAG field, please see the FLAG field Attribute Definition for more information. New and closed golf courses where discovered via Golf Course Name/Location comparisons with data found on the http://www.golflink.com/ website. New course boundaries were derived from the 2014 statewide parcel data. During the Spatial and Tabular QAQC duplicates were removed. Next GeoPlan Center performed the following attribute table adjustments. -Upper cased all records. -Added DESCRIPT field based on NAME -Socio-Cultural Effect data fields and definitions were updated/populated. FLAG, UPDATE_DAY, NAME, ADDRESS, CITY, ZIPCODE, OPERATING, OP_CLASS, SERVICES, COMMON_USE USE, YR_BUILT, FGDLAQDATE. -Added FGDLAQDATE field and populated it. Process Date: 20151005

MAP PROJECTION PARAMETERS:

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 ARCH BLDG, PO Box 115706
Gainesville, FL
32611



http://www.fgdl.org/
data@fgdl.org
Kate Norris

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