Geodataset Name:       PARKS_D5_JAN07
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Point
Feature Count:         1845

DATA SOURCE(S):                    FDOT District 5, DTS, GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     VARIES
DATE OF AUTOMATION OF SOURCE:      20061206
GEODATASET EXTENT:                 FDOT District 5

FEATURE ATTRIBUTE TABLES:

Datafile Name: PARKS_D5_JAN07.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
NAME	Park Designation
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 factility's physical location.
PHONE	Phone number of entity
TYPE_DESC	Physical site description
REC_USE	Primary focus of recreational activity (activity-based--sports fields; resource-based--beaches)
OPERATING	The responsible organization for management and operation of a facility (e.g., public, private, quasi-public
OP_CLASS	Classification of the operating entity
HOURS	The hours in which the park is open to the public
YEAR	4-digit year when park began operations
HISTORIC	Indicates if park includes a site containing artifacts from past human life and activities that may or may not be listed by the Florida Division of Historical Resources on the Florida Master Site File
COMMON_USE	Location of two or more uses in one facility or on common grounds so as to share common facilities
USE	Description of co-located use, if applicable
SOURCE	The Source of the base dataset from which the existing dataset was derived from.
NOTES	Any notes on the particular feature.
DESCRIPT	Based on 'NAME'.
FLAG	Type of update that occurred A = Attribute edit S = Spatial edit. B = Both spatial and attribute edit. N = New D = Delete NIN = Not in the new
UPDATE_DAY	The last day the file was updated by the source
FGDLAQDATE	The date FGDL aquired the data from the source.
AUTOID	GeoPlan Center internal feature number.
SHAPE	Feature geometry.

USER NOTES:

The methods used for creating this layer were consistent throughout. Areas used for wildlife preservation were not included unless it is a publicly know area for recreation. Areas for watershed protection were not included unless they were known areas of public recreation as well. The same sources were used throughout the process of determining recreational areas.

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.

Data development is a component of the Efficient Transportation Decision Making Process (ETDM). The primary objectives of the ETDM initiative include: Effective/timely decision making without compromising environmental quality. Integrating review and permitting process. - Early NEPA reviews and approvals - Full and early participation - Meaningful dispute resolution For more information about these initiatives an on-line search using keyword 'ETDM' will provide a number of resources. A listing of relevant documents and resources is included under: http://fdotenvironmentalstreamlining.urs-tally.com/Library/default.htm. - DTS USE CONSTRAINTS - All provided GIS data is to be considered a generalized spatial representation which is subject to revisions. The feature Boundaries are not to be used to establish legal boundaries or entitlements. For specific information, contact the appropriate department or agency. This information is provided as a visual representation only and is not intended to be used as a legal or official representation of legal boundaries or entitlements. The user assumes all responsibility for determining whether this file is appropriate for a particular purpose.

Data Transfer Solutions (DTS) is working with the Florida Department of Transportation, District 5 to create regional maps of "sociocultural" features, including hospitals, parks, cemeteries, school boundaries, and others. The maps will provide the FDOT with improved spatial information required for planning roadway projects.

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 horizontal positional accuracy has not been verified by GeoPlan

THE DATA INCLUDED IN FGDL ARE 'AS IS' AND SHOULD NOT BE CONSTRUED AS LEGALLY BINDING. 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:

FGDL Metadata Explorer http://www.fgdl.org/metadataexplorer/explorer.jsp Data Transfer Solutions http://www.edats.com/index.htm

DATA LINEAGE SUMMARY:

Data for Flagler County Process Steps: Collected parks data for Flagler County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Flagler County Property Appraiser parcel database and extracted polygons that could be golf courses based on VALUE. Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth, Google (http://maps.google.com) and Flagler County (http://www.flaglerparks.com) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.floridapets.net/Flagler.html) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061201 Data for Volusia County Process Steps: Collected parks data for Volusia County from county GIS site (http://www.volusia.org/gis/Default.htm) and Florida Geographic Data Library (http://www.fgdl.org). Searched Google Earth, Google (http://maps.google.com) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061006 Data for Marion County Process Steps: Collected parks data for Marion County from county GIS site and Florida Geographic Data Library (http:///www.fgdl.org). Searched Google Earth, Google (http://maps.google.com), and Marion County Parks (http://www.marioncountyfl.org/PR612/PR_home.htm) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061206 Data for Sumter County Process Steps: Collected parks data for Sumter County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Sumter County Property Appraiser parcel database and extracted polygons that could be parks based on owner name (e.g. SFWMD, TIITF, etc). Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth, Google (http://maps.google.com) and Sumter County (http://sumtercountyfl.gov/cs/parks/index.htm) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: http://www.golfable.com/golfcourses/county/sumter_county_fl In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20060929 Data for Lake County Process Steps: Collected parks data for Lake County from county FTP site (ftp://ftp.co.lake.fl.us/) and from Florida Geographic Data Library (FGDL). Reprojected FGDL data set into State Plane Florida East NAD 83, feet. Searched Brevard County Property Appraiser parcel database and extracted polygons that could be golf courses based on LANDUSE. Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth, Google (http://maps.google.com) and Lake County (http://www.co.lake.fl.us/departments/public_works/parks/) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.lakegovernment.com) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061130 Data for Seminole County Process Steps: Collected parks data for Seminole County from county GIS site (http://www.seminolecountyfl.gov/pd/commres/gis/layerbib2.asp). Searched Seminole County Property Appraiser parcel database and extracted polygons that could be parks based on owner name (e.g. ST JOHNS WATER MANAGEMENT DISTRICT, TIITF, etc). Converted the polygons to points and added to the data obtained from county website. Searched Google Earth, Google (http://maps.google.com) and Seminole County (http://www.seminolecountyfl.gov/lls/parks/parks.asp) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061006 Data for Orange County Process Steps: Collected parks data for Orange County from county GIS site (ftp://ftp.onetgov.net/divisions/Growth_Management/pub/) and Florida Geographic Data Library (http:///www.fgdl.org). Searched Google Earth, Google (http://maps.google.com) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Additional sites included: http://www.cityoforlando.net In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061006 Data for Osceola County Process Steps: Collected parks data for Osceola County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Osceola County Property Appraiser parcel database and extracted polygons that could be parks based on LUCDESC (e.g. REC/PARK LAND, FOREST/PARK/REC, etc). Converted the polygons to points and added data to the parks point file. Searched Google Earth, Google (http://maps.google.com) and Osceola County (http://www.osceola.org/index.cfm?lsFuses=department/Parks/Parks_Facilites) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. Staff found additional features from the following web-sites: (http://www.stcloud.org/index.asp?NID=6) (http://www.kissimmee.org/uploadedFiles/Work/Departments_and_Services/ Parks_and_Recreation/Program%20Guide%20Spring%202006.pdf) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061013 Data for Brevard County Process Steps: Collected parks data for Brevard County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Brevard County Property Appraiser parcel database and extracted polygons that could be golf courses based on USE_CODE. Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth, Google (http://maps.google.com) and Brevard County (http://www.brevardparks.com/parks/index) and added missing parks and recreation facilities found on these websites to the parks point file. This point file was plotted on a base map for use in field verification. Base maps were given to field crew to verify. Field crew drove all state roads and higher twice to verify existing data and collect new data (this was a search for new facilities). Field crew drove local roads twice to verify existing data and collect new data if something is seen (this was not an active search). Field crew returned marked up maps to in-house staff. In-house staff modified the shapefiles for existing data and created new shapefiles for new data obtained in the field. In-house staff then searched the internet for any additional features and additional information (if available) for verified features. In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. Process Date: 20061025 GeoPlan Center - Process Steps: GeoPlan received this data, via FTP, and performed the following: -Reprojected to the FGDL Albers HPGN map projection. -Restructured the attribute table to fit the SCE Data Specification Document Standards. -Merged datasets together to create one FDOT District-wide shapefile. -Added FGDLAQDATE field based on the date FGDL acquired the data from the source. -Added DESCRIPT field based on 'NAME' Process Date: 20070117

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:

Data Transfer Solutions
DTS
4037 Avalon Park Blvd East
Orlando, FL
32828
407-382-5222


www.edats.com
general@edats.com

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