This data is intended for use in the Efficient Transporation 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>.
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
Sub-zones not provided by the cities.
ALACHUA: Used Alachua County Growth Management "Municipal" shape file from their web site downloads, select by attribute "Gainesville, Alacuha, High Springs, Waldo" which are cities with their own police force. The used the "Florida Counties" shape file from GeoPlan and selected "Alachua County". Performed a "union' on the resiltant seltects from "counties and municipals" to create data set "Q" which is all municipalities and the rest of the county. From the Alachua County Property Appraiser "2005 Parcel" data set, "select by attribute" all parcels whos "GIS.Lastname" was equal to "STATE UNIVERSITY" or "STATE OF FLORIDA IIF" or "UNIVERSITY ATHLETIC ASSOCIATION" or STATE OF FLA IIF" or "U OF F FOUNDATION INC" or "U OF F FOUNDATION TRUSTEE" or "UNIVERSITY OF FLORIDA" or "STATE BOARD OF EDUCATION" or "SANTA FE COMMUNITY COLLEGE" or "DISTRICT BOARD OF TRUSTEES OF" or "SOUTHEASTERN HEATHCARE FOUNDATION" or "SHANDS TEACHING HOSPITAL &". Classified parcels as UF or SANTA FE, then did a dissolve on the parcels and did a "union" to the "Q" data set to create the final "AC_leszones" shapefile.
ALACHUA: Intersected the file with Alachua County E911 sheriff zone map.
BRADFORD: Used county EOC provided shapefile to determine boundaries and coverage area.
COLUMBIA: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time.
DIXIE: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time.
GILCHRIST: Copied Gilchrist county property appreaiser cities data set and FGDL county data set and selected Gilchrist county and Trenton and Trenton Annex. Exported selected to new shape file. Dissolved Trenton and Trenton Annex. to have 2 zone.
HAMILTON: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time. Used Hamilton county provided data set to digitize clean polygons for data set and identify zomes.
LAFEYETTE: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time.
LEVY: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time.
MADISON: Used county EOC provided shapefile to determine boundaries and coverage area.
SUWANNEE: Used information from talking to Suwannee County EOC to determine boundaries and coverage area. Used cities 2002 for LEZ coverage area.
TAYLOR: selected in parcel shapefile the parcels with cities that have police departments and cut a polygon around the feature for city boundaries. Rest of county handled by sheriff dept, and no subzones are available at publication time.
UNION: Used county EOC provided shapefile to determine boundaries and coverage area.
The polygons were obtained from the respective agencies then the St. Johns River Water District county boundaries polygon coverage was used as the defining boundary between each county. Some of the boundaries had to be appended in order to clip each seperate county to match the SJRWMD county boundary. After each county was clipped to it's respective SJRWMD county boundary all of the counties were merged together as a singel featureclass(shapefile).
GeoPlan received this data and performed the following:
-Reprojected to the FGDL Albers HPGN map projection -Merged datasets together to create one FDOT District-wide shapefile. -added the fields 'COUNTY' based on actual county. -added FGDLAQDATE field based on the date FGDL acquired the data from the source. -added DESCRIPT field based on 'NAME'.