<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet type="text/xsl" href="./fgdc_classic_fgdl.xsl"?>
<!DOCTYPE metadata SYSTEM "http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd">
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Florida Department of Transportation District 5, Data Transfer Solutions, University of Florida GeoPlan Center</origin>
<pubdate>20061206</pubdate>
<title>FDOT DISTRICT 5 - SCHOOL BOUNDARIES</title>
<geoform>vector digital data</geoform>
<pubinfo>
<pubplace>Gainesville, FL</pubplace>
<publish>University of Florida GeoPlan Center</publish>
</pubinfo>
<othercit>FDOT District 5</othercit>
<onlink>www.edats.com</onlink>
<lworkcit>
<citeinfo>
</citeinfo>
</lworkcit>
</citeinfo>
</citation>
<descript>
<abstract>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.</abstract>
<purpose>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.</purpose>
<supplinf>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.</supplinf>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>20060929</begdate>
<enddate>20070117</enddate>
</rngdates>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>As needed</update>
</status>
<spdom>
<bounding>
<westbc>
-87.429040</westbc>
<eastbc>
-79.872251</eastbc>
<northbc>
30.983191</northbc>
<southbc>
24.492815</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>NONE</themekt>
<themekey>School Locations</themekey>
<themekey>parcels</themekey>
<themekey>School</themekey>
<themekey>Boundaries</themekey>
</theme>
<theme>
<themekt>ISO 19115 Topic Category</themekt>
<themekey>society</themekey>
</theme>
<place>
<placekey>FDOT District 5</placekey>
<placekey>East Central Florida</placekey>
<placekey>Flagler County</placekey>
<placekey>Volusia County</placekey>
<placekey>Marion County</placekey>
<placekey>Sumter County</placekey>
<placekey>Lake County</placekey>
<placekey>Seminole County</placekey>
<placekey>Orange County</placekey>
<placekey>Osceola County</placekey>
<placekey>Brevard County</placekey>
</place>
<stratum>
<stratkey>terrestrial</stratkey>
</stratum>
</keywords>
<accconst>NONE</accconst>
<useconst>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</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg>Florida Geographic Data Library (FGDL)</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>431 Architecture PO Box 115706</address>
<city>Gainesville</city>
<state>Florida</state>
<postal>32611-5706</postal>
<country>USA</country>
</cntaddr>
<cntemail>Web site: http://www.fgdl.org</cntemail>
<cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
<cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
<cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
<cntemail>FGDL Mailing Lists: http://www.fgdl.org/fgdl-l.html</cntemail>
</cntinfo>
</ptcontac>
<datacred>FDOT District 5, Data Transfer Solutions (DTS), and the GeoPlan Center at the University of Florida.</datacred>
<crossref>
<citeinfo>
<othercit>FGDL Metadata Explorer
http://www.fgdl.org/metadataexplorer/explorer.jsp

Data Transfer Solutions
http://www.edats.com/index.htm</othercit>
</citeinfo>
</crossref>
</idinfo>
<dataqual>
<attracc>
<attraccr>GeoPlan relied on the integrity of the attribute information within
the original data.</attraccr>
<qattracc>
</qattracc>
</attracc>
<logic>This data is provided 'as is'. GeoPlan relied on the integrity of the 
original data layer's topology</logic>
<complete>This data is provided 'as is' by GeoPlan and is complete to 
our knowledge.</complete>
<posacc>
<horizpa>
<horizpar>This data is provided 'as is' and its horizontal positional accuracy 
has not been verified by GeoPlan.</horizpar>
</horizpa>
<vertacc>
<vertaccr>This data is provided 'as is' and its vertical positional accuracy 
has not been verified by GeoPlan.</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<pubdate>20061206</pubdate>
<title>FDOT DISTRICT 5 - SCHOOL BOUNDARIES</title>
<geoform>vector digital data</geoform>
<pubinfo>
<pubplace>Orlando, FL</pubplace>
<publish>DTS</publish>
</pubinfo>
<onlink>www.edats.com</onlink>
</citeinfo>
</srccite>
<srcscale>VARIOUS</srcscale>
<srctime>
<timeinfo>
<rngdates>
<begdate>20060929</begdate>
<enddate>20061206</enddate>
</rngdates>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccitea>DTS</srccitea>
<srccontr>Spatial and Attribute Information</srccontr>
</srcinfo>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061201</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061116</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061206</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20060929</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061130</procdate>
</procstep>
<procstep>
<procdesc>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&amp;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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061006</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061006</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061013</procdate>
</procstep>
<procstep>
<procdesc>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.</procdesc>
<srcused>DTS</srcused>
<procdate>20061025</procdate>
</procstep>
<procstep>
<procdesc>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'.</procdesc>
<srcused>GeoPlan Center</srcused>
<procdate>20070117</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>G-polygon</sdtstype>
<ptvctcnt>1673</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<mapproj>
<mapprojn>Albers Conical Equal Area</mapprojn>
<albers>
<stdparll>24.000000</stdparll>
<stdparll>31.500000</stdparll>
<longcm>-84.000000</longcm>
<latprjo>24.000000</latprjo>
<feast>400000.000000</feast>
<fnorth>0.000000</fnorth>
</albers>
</mapproj>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.002048</absres>
<ordres>0.002048</ordres>
</coordrep>
<plandu>meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>D_North_American_1983_HARN</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altres>1.000000</altres>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
SCHOOLBND_D5_JAN07</enttypl>
<enttypd>SCHOOLBND_D5_JAN07.DBF</enttypd>
<enttypds>GeoPlan</enttypds>
</enttyp>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ID</attrlabl>
<attrdef>Unique identifier number of the School</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>NAME</attrlabl>
<attrdef>School designation</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>ALTNAME</attrlabl>
<attrdef>Alternative building name.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>ALTNAME1</attrlabl>
<attrdef>Additional alternative building names.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>ADDRESS</attrlabl>
<attrdef>A description of a facility's physical location providing direction for delivery and provision of emergency services</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>CITY</attrlabl>
<attrdef>City of facility's physical location</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>ZIPCODE</attrlabl>
<attrdef>US postal delivery designation of facility's physical location</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>PHONE</attrlabl>
<attrdef>Phone number of facility.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>OPERATING</attrlabl>
<attrdef>The responsible organization for management and operation of a facility</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>OP_CLASS</attrlabl>
<attrdef>Classification of the operating entity</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>EDUC_LEVEL</attrlabl>
<attrdef>Education level provided by facility.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>ENROLLMENT</attrlabl>
<attrdef>Total number of students attending a school</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>PROGRAMS</attrlabl>
<attrdef>A program that is distinguishable from the typical program offered by a data entity</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>COMMON_USE</attrlabl>
<attrdef>Location of two or more uses in one facility or on common grounds so as to share common facilities</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>USE</attrlabl>
<attrdef>Description of co-located use if applicable</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>YR_BUILT</attrlabl>
<attrdef>The year a structure was built for determining possible historical significance</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>PARCEL_ID</attrlabl>
<attrdef>Unique parcel identifier number</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>SOURCE</attrlabl>
<attrdef>The Source of the base dataset from which the existing dataset was derived from.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>NOTES</attrlabl>
<attrdef>Any notes on the particular feature.</attrdef>
<attrdefs>DTS</attrdefs>
</attr>
<attr>
<attrlabl>DESCRIPT</attrlabl>
<attrdef>Based on 'NAME'.</attrdef>
<attrdefs>GEOPLAN</attrdefs>
</attr>
<attr>
<attrlabl>FLAG</attrlabl>
<attrdef>Type of update that occurred</attrdef>
<attrdefs>GEOPLAN</attrdefs>
<attrdomv>
<edom>
<edomv>A</edomv>
<edomvd>Attribute edit</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>S</edomv>
<edomvd>Spatial edit.</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>B</edomv>
<edomvd>Both spatial and attribute edit.</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>N</edomv>
<edomvd>New</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>D</edomv>
<edomvd>Delete</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>NIN</edomv>
<edomvd>Not in the new</edomvd>
<edomvds>GEOPLAN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>UPDATE_DAY</attrlabl>
<attrdef>The date the data was updated by the Source.</attrdef>
<attrdefs>GEOPLAN</attrdefs>
</attr>
<attr>
<attrlabl>FGDLAQDATE</attrlabl>
<attrdef>The date FGDL acquired the data from the Source.</attrdef>
<attrdefs>GEOPLAN</attrdefs>
</attr>
<attr>
<attrlabl>AUTOID</attrlabl>
<attrdef>GeoPlan Center feature identification number.</attrdef>
<attrdefs>GEOPLAN</attrdefs>
</attr>
<attr>
<attrlabl>SHAPE</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>SHAPE.AREA</attrlabl>
<attrdef>Area</attrdef>
<attrdefs>GeoPlan</attrdefs>
</attr>
<attr>
<attrlabl>SHAPE.LEN</attrlabl>
<attrdef>Perimeter</attrdef>
<attrdefs>GeoPlan</attrdefs>
</attr>
</detailed>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Florida Geographic Data Library (FGDL)</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>431 Architecture PO Box 115706</address>
<city>Gainesville</city>
<state>Florida</state>
<postal>32611-5706</postal>
<country>United States</country>
</cntaddr>
<cntemail>Web site: http://www.fgdl.org</cntemail>
<cntemail>Technical Support: http://www.fgdl.org/fgdlfeed.html</cntemail>
<cntemail>For FGDL Software: http://www.fgdl.org/software.html</cntemail>
<cntemail>FGDL Frequently Asked Questions: http://www.fgdl.org/fgdlfaq.html</cntemail>
<cntemail>Mailing list for FGDL: http://www.fgdl.org/fgdl-l.html</cntemail>
</cntinfo>
</distrib>
<resdesc>DOWNLOADABLE DATA</resdesc>
<distliab>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.</distliab>
<stdorder>
<digform>
<digtinfo>
<transize>2.138</transize>
</digtinfo>
</digform>
</stdorder>
<techpreq>This data is intended for use with a Geographic Information Systems or Remote Sensing software package.</techpreq>
</distinfo>
<metainfo>
<metd>20070205</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Data Transfer Solutions</cntorg>
<cntper>Keith Joiner</cntper>
</cntorgp>
<cntpos>GIS Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>4037 Avalon Park Blvd East</address>
<city>Orlando</city>
<state>FL</state>
<postal>32828</postal>
<country>USA</country>
</cntaddr>
<cntvoice>407-382-5222</cntvoice>
<cntfax>407-382-5420</cntfax>
<cntemail>general@edats.com</cntemail>
<cntinst>www.edats.com</cntinst>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>
