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 school parcel boundaries located in the East Central Florida Region (FDOT District 5). Both public and private facilities are included, along with the education level provided at the location. This GIS layer 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 -82.485789 -80.481491 29.628545 27.864722 None Boundaries School Locations School parcels ISO 19115 Topic Category society None Orange County Sumter County Osceola County Seminole County Brevard County Flagler County Marion County FDOT District 5 East Central Florida Lake County Volusia County None 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

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US Technical Support: http://www.fgdl.org/fgdlfeed.html For FGDL Software: http://www.fgdl.org/software.html FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html Web site: http://www.fgdl.org FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html FDOT District 5, Data Transfer Solutions (DTS), and the GeoPlan Center at the University of Florida. Version 6.2 (Build 9200) ; Esri ArcGIS 10.7.1.11595 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 provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology 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 vertical positional accuracy has not been verified by GeoPlan. 20061206 vector digital data Orlando, FL DTS www.edats.com 0 None 20060929 20061206 publication date DTS Spatial and Attribute Information Data for Sumter County Process Steps: Collected school data for Sumter County from Florida Geographic Data Library (FGDL). From FGDL certain vo/tech schools were deleted (these would include bartending schools, pet schools, hairdressing schools, driving schools, cosmetology schools, typing schools, etc). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Sumter County Property Appraiser parcel database and extracted polygons that could be schools based on owner name. Converted the polygons to points and added to the data obtained from FGDL. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Sumter County School Board (http://www.sumter.k12.fl.us/Schools.html) and added missing schools found on these websites to the school 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.greatschools.net/cgi-bin/fl/district_profile/60 In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20060929 Data for Orange County Process Steps: Collected school data for Orange County from county GIS site (ftp://ftp.onetgov.net/divisions/Growth_Management/pub/). Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Orange County Public Schools (http://www.ocps.k12.fl.us/) and added missing schools found on these websites to the school 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.floridasmart.com http://www.ocps.k12.fl.us/schools.rhtml In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061006 Data for Seminole County Process Steps: Collected school data for Seminole County from county GIS site (http://www.seminolecountyfl.gov/pd/commres/gis/layerbib2.asp). Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Seminole County Public Schools (http://www.scps.k12.fl.us/) and added missing schools found on these websites to the school 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.greatschools.net/schools.page?district=57&state=fl) (http://www.scpafl.org/scpaweb05/index.jsp) (http://www.privateschoolreview.com/county_private_schools/stateid/FL/county/12117) (http://www.floridaschoolchoice.org/Information/directory/schoolreport.asp?id=59) 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 school data for Osceola County from county source and from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Merged the two school point files. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Osceola County Public Schools (http://www.osceola.k12.fl.us/pages_2004/01_01SchoolsList.asp) and added missing schools found on these websites to the school 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.privateschoolreview.com/county_private_schools/stateid/FL/county/12097) 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 school data for Brevard County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Brevard County Public Schools (http://www.brevard.k12.fl.us/#schools) and added missing schools found on these websites to the school 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: (www.privateschoolreview.com) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061025 Data for Volusia County Process Steps: Collected school data for Volusia County from Volusia County (http://www.volusia.org/gis/Default.htm) and Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Volusia County Public Schools (http://schools.volusia.k12.fl.us) and added missing schools found on these websites to the school 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.floridasmart.com/local/counties/volusia/education_preschool.htm) (http://www.metrodaycare.com/content/search/companyid/143870.asp) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061116 Data for Lake County Process Steps: Collected school data for Lake County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Lake County Public Schools (http://www.lake.k12.fl.us/LCSPortal/) and added missing schools found on these websites to the school 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.floridasmart.com) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061130 Data for Flagler County Process Steps: Collected school data for Flagler County from Florida Geographic Data Library (FGDL). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Flagler County Public Schools (http://www.flagler.k12.fl.us/default.aspx?cf=Schools%5cschools) and added missing schools found on these websites to the school 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.floridasmart.com) In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061201 Data for Marion County Process Steps: Collected school data for Marion County from county GIS site and Florida Geographic Data Library (http:///www.fgdl.org). Reprojected data set into State Plane Florida East NAD 83, feet. Searched Google Earth, Florida Department of Education (http://www.fldoe.org/Default.asp?bhcp=1) and Marion County Public Schools (http://www.marion.k12.fl.us/schools/chs/locations.html) and added missing schools found on these websites to the school 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: In-house staff performed QA/QC of data. Point shapefile was used to create polygon shapefile. DTS 20061206 GeoPlan Center - Process Steps: GeoPlan received this data via FTP and performed the following: -Reprojected to the FGDL Albers HPGN map projection -Merged datasets together to create one FDOT District-wide shapefile. -Restructured the attribute table to fit the SCE Data Specification Document Standards. -added FGDLAQDATE field based on the date FGDL acquired the data from the source. -added DESCRIPT field based on 'NAME'. GeoPlan Center 20070117 Vector GT-polygon composed of chains 1673 NAD 1983 HARN Florida GDL Albers 24.0 31.5 -84.0 24.0 400000.0 0.0 coordinate pair 0.0001 0.0001 meter D North American 1983 HARN GRS 1980 6378137.0 298.257222101 SCHOOLBND_D5_JAN07 SCHOOLBND_D5_JAN07.DBF GeoPlan OBJECTID Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. ID Unique identifier number of the School DTS NAME School designation DTS ALTNAME Alternative building name. DTS ALTNAME1 Additional alternative building names. 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 facility's physical location DTS PHONE Phone number of facility. DTS OPERATING The responsible organization for management and operation of a facility DTS OP_CLASS Classification of the operating entity DTS EDUC_LEVEL Education level provided by facility. DTS ENROLLMENT Total number of students attending a school DTS PROGRAMS A program that is distinguishable from the typical program offered by a data entity 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 YR_BUILT The year a structure was built for determining possible historical significance DTS PARCEL_ID Unique parcel identifier number 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 GEOPLAN Attribute edit S GEOPLAN Spatial edit. GEOPLAN B Both spatial and attribute edit. GEOPLAN N New GEOPLAN D Delete NIN Not in the new GEOPLAN UPDATE_DAY The date the data was updated by the Source. GEOPLAN FGDLAQDATE The date FGDL acquired the data from the Source. GEOPLAN AUTOID GeoPlan Center feature identification number. GEOPLAN SHAPE Feature geometry. ESRI Coordinates defining the features. SHAPE.AREA Area GeoPlan SHAPE.LEN Perimeter GeoPlan Florida Geographic Data Library (FGDL) mailing

431 Architecture PO Box 115706

Gainesville Florida 32611-5706 US Web site: http://www.fgdl.org Technical Support: http://www.fgdl.org/fgdlfeed.html Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html For FGDL Software: http://www.fgdl.org/software.html FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.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. 20200303 Data Transfer Solutions Keith Joiner GIS Manager mailing and physical

4037 Avalon Park Blvd East

Orlando FL 32828 US 407-382-5222 407-382-5420 general@edats.com www.edats.com FGDC Content Standard for Digital Geospatial Metadata FGDC-STD-001-1998 local time