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.
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>
Data Transfer Solutions <http://www.edats.com/index.htm>
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>.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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'