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>
Northeast Florida Regional Planning Council NEFRPC 6850 Belfort Oaks Place Jacksonville, FL 32216 (904) 279-0880 Fax (904) 279-0881 <http://www.nefrpc.org/> info@nefrc.org Keith Joiner KJoiner@nefrc.org
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 througout. 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.
Specifications and oversight were provided by FDOT and by the Geoplan Center at the University of Florida.
Parks are defined in the SocioCultural Effects Data Specificiations Document as "Grounds used for recreation". The areas may be based on activities (ie. Sports fields) or natural resources (ie. Beaches). Both public, private and quasi-public facilities are included in the layer. The areas may be affiliated with local neighborhoods or regional jurisdictions.
Types of features that are included are:
-Portions of local/county/state/federal parks used for public recreation. Portions used primarily for other purposes, such as silviculture, bombing ranges, etc. are not included. Private access areas, such as hunting clubs are also not included. -Recreational springs -Campgrounds, including those for RVs. -Hiking trails and other linear recreational facilities -Golf courses -Boat ramps, marinas and other aquatic based recreational facilities -Sports and athletic fields, not including stadiums, arenas, theme parks, or other public venues intended for special events or entertainment. -Playgrounds -Open areas used for non-specific recreation, and public access areas (eg. picnic area) associated with open areas.
This layer does not include the following:
-Areas not open to general public access. -Features included under Religious Facilities, such as religious retreats, camps, sanctuaries, daycare facilities. -Features included under the Schools layer, including school athletic fields -Features included under Civic Centers/Multi-use Facilities/Theme Parks/Major Attractors, such as stadiums and arenas.
Exceptions and changes: Under this contract privately owned facilities are not included.
ALACHUA: Alachua parks were obtained by using an existing shapefile acquired from the public works department. The shapefile with existing polygons was used since parks were to be represented with poly. In addition to those files, a shapefile of parks and golf courses were obtained from Gainesville Regional Utilities. Boat ramps were found by using a combination of the parks from public works and the Florida Atlas. An historic layer was also utilized showing historic features in or near parks. This consisted of information from the Florida Master Sites File and the cemetery layer created by the NCFRPC.
GILCHRIST: Gilchrist parks were mapped by taking the parcel layer for Gilchrist and querying out use codes such as: 700, 3500, and those over 8000. Those that did not fit park criteria, such as agricultural properties or timber lands, were eliminated. In addition, the map created by the chamber of commerce and the Florida atlas, which had spring and boat ramp locations, were used. A guide from the Gilchrist county library contained four public community parks that were included in the shapefile as well. Boat ramps were found by using various paper maps and atlases. An historic layer was also utilized showing historic features in or near parks. This consisted of information from the Florida Master Sites File and the cemetery layer created by the NCFRPC.
1. Compiled GIS layers from multiple governing agencies
2. Created a featureclass and table schema to match representing the final layer Appended all of the layers obtained from other sources into the single featureclass.
3. Calculated the necessary attribution and dropped the fields that did not match the schema as defined by GeoPlan.
4. Researched for missing locations by polling local municipalities for local playgrounds and parks.
5. Added missing features and attributed them accordingly.
6. Dissolved the final layer based on the park name.
7. Checked the final layer for quality control and made any necessary adjustments.
GeoPlan received this data, via CDROM, 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 'REC_USE'