Florida Department of Transportation District 5, Data Transfer Solutions, University of Florida GeoPlan Center 20061206 vector digital data Gainesville, FL University of Florida GeoPlan Center FDOT District 5 www.edats.com This dataset contains park boundaries and was produced by Data Transfer Solutions (DTS) under contract with FDOT District 5 in 2006. This is one of many layers that fall into the general category of "sociocultural" GIS data. 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. 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. 20060929 20070117 publication date Complete As needed -87.429040 -79.872251 30.983191 24.492815 NONE Park boundary ISO 19115 Topic Category planningCadastre environment East Central Florida FDOT District 5 Flagler County Volusia County Marion County Sumter County Lake County Seminole County Orange County Osceola County Brevard County Terrestrial NONE 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 Florida Geographic Data Library (FGDL) mailing address

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html FDOT District 5, Data Transfer Solutions (DTS), and the GeoPlan Center at the University of Florida. Unclassified FGDL Metadata Explorer http://www.fgdl.org/metadataexplorer/explorer.jsp Data Transfer Solutions http://www.edats.com/index.htm GeoPlan relied on the integrity of the attribute information within the original data. This data is intended for use in the Efficient Transportation Decision Making Process (ETDM), which includes the development of an on-line application called the Environmental Screening Tool. The primary objective of the program include: Effective/timely decision making without compromising environmental quality Integrating review and permitting processe. 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. 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. 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 DTS 20061206 vector digital data Orlando, FL DTS www.edats.com VARIES 20060929 20061206 publication date DTS Spatial and Attribute Information 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. DTS 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). Converted the polygons to points and added to the data obtained from county website. 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. DTS 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. DTS 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. DTS 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. DTS 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. DTS 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. DTS 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 and added missing parks and recreation facilities found on these websites to the parks point file. (http://www.osceola.org/index.cfm?lsFuses=department/Parks/Parks_Facilites) 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. DTS 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 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. DTS 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' GeoPlan Center 20070117 Vector G-polygon 5063 Albers Conical Equal Area 24.000000 31.500000 -84.000000 24.000000 400000.000000 0.000000 coordinate pair 0.002048 0.002048 meters D_North_American_1983_HARN Geodetic Reference System 80 6378137.000000 298.257222 1.000000 Explicit elevation coordinate included with horizontal coordinates PARKBND_D5_JAN07 PARKBND_D5_JAN07.DBF GeoPlan OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. NAME Park Designation DTS ADDRESS A description of a facility's physical location providing direction for delivery and provision of emergency services DTS CITY City of facility's physical location DTS ZIPCODE US postal delivery designation of factility's physical location. DTS PHONE Phone number of entity DTS TYPE_DESC Physical site description DTS REC_USE Primary focus of recreational activity (activity-based--sports fields; resource-based--beaches) DTS OPERATING The responsible organization for management and operation of a facility (e.g., public, private, quasi-public DTS OP_CLASS Classification of the operating entity DTS HOURS The hours in which the park is open to the public DTS YEAR 4-digit year when park began operations DTS 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 DTS COMMON_USE Location of two or more uses in one facility or on common grounds so as to share common facilities DTS USE Description of co-located use, if applicable DTS SOURCE The Source of the base dataset from which the existing dataset was derived from. DTS NOTES Any notes on the particular feature. DTS DESCRIPT Based on 'NAME'. GEOPLAN FLAG Type of update that occurred GEOPLAN 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 GEOPLAN FGDLAQDATE The date FGDL aquired the data from the source. GEOPLAN AUTOID GeoPlan Center internal feature number. GEOPLAN SHAPE Feature geometry. ESRI Coordinates defining the features. SHAPE.AREA Area GeoPlan SHAPE.LEN Perimeter GeoPlan Florida Geographic Data Library (FGDL) mailing address

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 United States Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html DOWNLOADABLE DATA THE FGDL DATA AS PROVIDED BY CONTRIBUTING ORGANIZATIONS AND ANY PROGRAMMING SOFTWARE CREATED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER (COLLECTIVELY THE 'MATERIALS') ARE COPYRIGHTED BY THE UNIVERSITY OF FLORIDA GEOPLAN CENTER FOR THE FGDL CONTRIBUTING AGENCIES AND ORGANIZATIONS (THE 'DATA PROVIDERS'). DO NOT REPRODUCE, REDISTRIBUTE OR RESELL THE MATERIALS, OR PROVIDE THE MATERIALS FOR FREE TO CUSTOMERS OR CLIENTS, OR PLACE THE MATERIALS FOR DOWNLOAD ON A WEBSITE. ADDITIONALLY, WHEN USING FGDL DATA OR SOFTWARE IN PROJECTS, MAPS, ETC.; YOU AGREE TO ACKNOWLEDGE THE FGDL AS A DATA SOURCE. THE MATERIALS ARE PROVIDED 'AS IS'. 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 MAKES NO WARRANTIES, GUARANTIES OR REPRESENTATIONS AS TO THE TRUTH, ACCURACY OR COMPLETENESS OF THE DATA PROVIDED BY THE FGDL CONTRIBUTING ORGANIZATIONS. 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. 16.919 This data is intended for use with a Geographic Information Systems or Remote Sensing software package. 20070205 Data Transfer Solutions mailing address

4037 Avalon Park Blvd East

Orlando FL 32828 USA 407-382-5222 407-382-5420 general@edats.com www.edats.com FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998 local time http://www.esri.com/metadata/esriprof80.html ESRI Metadata Profile