FDOT DISTRICT 5 - PARK BOUNDARIES

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
Florida Department of Transportation District 5, Data Transfer Solutions, University of Florida GeoPlan Center
Publication_Date: 20061206
Title: FDOT DISTRICT 5 - PARK BOUNDARIES
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Gainesville, FL
Publisher: University of Florida GeoPlan Center
Other_Citation_Details: FDOT District 5
Online_Linkage: www.edats.com
Larger_Work_Citation:
Citation_Information:
Description:
Abstract:
This dataset contains park boundaries and 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.
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.
Supplemental_Information:
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.

Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20060929
Ending_Date: 20070117
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -87.429040
East_Bounding_Coordinate: -79.872251
North_Bounding_Coordinate: 30.983191
South_Bounding_Coordinate: 24.492815
Keywords:
Theme:
Theme_Keyword_Thesaurus: NONE
Theme_Keyword: Park
Theme_Keyword: boundary
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Category
Theme_Keyword: planningCadastre
Theme_Keyword: environment
Place:
Place_Keyword: East Central Florida
Place_Keyword: FDOT District 5
Place_Keyword: Flagler County
Place_Keyword: Volusia County
Place_Keyword: Marion County
Place_Keyword: Sumter County
Place_Keyword: Lake County
Place_Keyword: Seminole County
Place_Keyword: Orange County
Place_Keyword: Osceola County
Place_Keyword: Brevard County
Stratum:
Stratum_Keyword: Terrestrial
Access_Constraints: NONE
Use_Constraints:
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>

Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: FGDL Mailing Lists: <http://www.fgdl.org/fgdl-l.html>
Data_Set_Credit:
FDOT District 5, Data Transfer Solutions (DTS), and the GeoPlan Center at the University of Florida.
Security_Information:
Security_Classification: Unclassified
Cross_Reference:
Citation_Information:
Other_Citation_Details:
FGDL Metadata Explorer <http://www.fgdl.org/metadataexplorer/explorer.jsp>

Data Transfer Solutions <http://www.edats.com/index.htm>


Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
GeoPlan relied on the integrity of the attribute information within the original data.
Quantitative_Attribute_Accuracy_Assessment:
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Explanation:
This data is intended for use in the Efficient Transportation 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>.

Logical_Consistency_Report:
The methods used for creating this layer were consistent throughout. 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.
Completeness_Report:
This data is provided 'as is' by GeoPlan and is complete to our knowledge.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
This data is provided "as is" and its horizontal positional accuracy has not been verified by GeoPlan
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report:
This data is provided "as is" and its horizontal positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: DTS
Publication_Date: 20061206
Title: FDOT DISTRICT 5 - PARK BOUNDARIES
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Orlando, FL
Publisher: DTS
Online_Linkage: www.edats.com
Source_Scale_Denominator: VARIES
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 20060929
Ending_Date: 20061206
Source_Currentness_Reference: publication date
Source_Citation_Abbreviation: DTS
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
Data for Flagler County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061201
Process_Step:
Process_Description:
Data for Volusia County Process Steps:

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>).

Converted the polygons to points and added to the data obtained from county website.

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061006
Process_Step:
Process_Description:
Data for Marion County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061206
Process_Step:
Process_Description:
Data for Sumter County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20060929
Process_Step:
Process_Description:
Data for Lake County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061130
Process_Step:
Process_Description:
Data for Seminole County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061006
Process_Step:
Process_Description:
Data for Orange County Process Steps:

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061006
Process_Step:
Process_Description:
Data for Osceola County Process Steps:

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 and added missing parks and recreation facilities found on these websites to the parks point file. (<http://www.osceola.org/index.cfm?lsFuses=department/Parks/Parks_Facilites>)

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061013
Process_Step:
Process_Description:
Data for Brevard County Process Steps:

Collected parks data for Brevard County from Florida Geographic Data Library (FGDL).

Reprojected data set into State Plane Florida East NAD 83, feet.

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.

Source_Used_Citation_Abbreviation: DTS
Process_Date: 20061025
Process_Step:
Process_Description:
GeoPlan Center - Process Steps:

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'

Source_Used_Citation_Abbreviation: GeoPlan Center
Process_Date: 20070117

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 5063

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Albers Conical Equal Area
Albers_Conical_Equal_Area:
Standard_Parallel: 24.000000
Standard_Parallel: 31.500000
Longitude_of_Central_Meridian: -84.000000
Latitude_of_Projection_Origin: 24.000000
False_Easting: 400000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.002048
Ordinate_Resolution: 0.002048
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: D_North_American_1983_HARN
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Vertical_Coordinate_System_Definition:
Altitude_System_Definition:
Altitude_Resolution: 1.000000
Altitude_Encoding_Method:
Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: PARKBND_D5_JAN07
Entity_Type_Definition: PARKBND_D5_JAN07.DBF
Entity_Type_Definition_Source: GeoPlan
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: NAME
Attribute_Definition: Park Designation
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: ADDRESS
Attribute_Definition:
A description of a facility's physical location providing direction for delivery and provision of emergency services
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: CITY
Attribute_Definition: City of facility's physical location
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: ZIPCODE
Attribute_Definition:
US postal delivery designation of factility's physical location.
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: PHONE
Attribute_Definition: Phone number of entity
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: TYPE_DESC
Attribute_Definition: Physical site description
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: REC_USE
Attribute_Definition:
Primary focus of recreational activity (activity-based--sports fields; resource-based--beaches)
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: OPERATING
Attribute_Definition:
The responsible organization for management and operation of a facility (e.g., public, private, quasi-public
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: OP_CLASS
Attribute_Definition: Classification of the operating entity
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: HOURS
Attribute_Definition: The hours in which the park is open to the public
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: YEAR
Attribute_Definition: 4-digit year when park began operations
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: HISTORIC
Attribute_Definition:
Indicates if park includes a site containing artifacts from past human life and activities that may or may not be listed by the Florida Division of Historical Resources on the Florida Master Site File
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: COMMON_USE
Attribute_Definition:
Location of two or more uses in one facility or on common grounds so as to share common facilities
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: USE
Attribute_Definition: Description of co-located use, if applicable
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: SOURCE
Attribute_Definition:
The Source of the base dataset from which the existing dataset was derived from.
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: NOTES
Attribute_Definition: Any notes on the particular feature.
Attribute_Definition_Source: DTS
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: Based on 'NAME'.
Attribute_Definition_Source: GEOPLAN
Attribute:
Attribute_Label: FLAG
Attribute_Definition: Type of update that occurred
Attribute_Definition_Source: GEOPLAN
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: A
Enumerated_Domain_Value_Definition: Attribute edit
Enumerated_Domain:
Enumerated_Domain_Value: S
Enumerated_Domain_Value_Definition: Spatial edit.
Enumerated_Domain:
Enumerated_Domain_Value: B
Enumerated_Domain_Value_Definition: Both spatial and attribute edit.
Enumerated_Domain:
Enumerated_Domain_Value: N
Enumerated_Domain_Value_Definition: New
Enumerated_Domain:
Enumerated_Domain_Value: D
Enumerated_Domain_Value_Definition: Delete
Enumerated_Domain:
Enumerated_Domain_Value: NIN
Enumerated_Domain_Value_Definition: Not in the new
Attribute:
Attribute_Label: UPDATE_DAY
Attribute_Definition: The last day the file was updated by the source
Attribute_Definition_Source: GEOPLAN
Attribute:
Attribute_Label: FGDLAQDATE
Attribute_Definition: The date FGDL aquired the data from the source.
Attribute_Definition_Source: GEOPLAN
Attribute:
Attribute_Label: AUTOID
Attribute_Definition: GeoPlan Center internal feature number.
Attribute_Definition_Source: GEOPLAN
Attribute:
Attribute_Label: SHAPE
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: SHAPE.AREA
Attribute_Definition: Area
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Perimeter
Attribute_Definition_Source: GeoPlan

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Florida Geographic Data Library (FGDL)
Contact_Address:
Address_Type: mailing address
Address: 431 Architecture PO Box 115706
City: Gainesville
State_or_Province: Florida
Postal_Code: 32611-5706
Country: United States
Contact_Electronic_Mail_Address: Web site: <http://www.fgdl.org>
Contact_Electronic_Mail_Address: Technical Support: <http://www.fgdl.org/fgdlfeed.html>
Contact_Electronic_Mail_Address: For FGDL Software: <http://www.fgdl.org/software.html>
Contact_Electronic_Mail_Address:
FGDL Frequently Asked Questions: <http://www.fgdl.org/fgdlfaq.html>
Contact_Electronic_Mail_Address: Mailing list for FGDL: <http://www.fgdl.org/fgdl-l.html>
Resource_Description: DOWNLOADABLE DATA
Distribution_Liability:
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.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 16.919
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.

Metadata_Reference_Information:
Metadata_Date: 20070205
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Data Transfer Solutions
Contact_Address:
Address_Type: mailing address
Address: 4037 Avalon Park Blvd East
City: Orlando
State_or_Province: FL
Postal_Code: 32828
Country: USA
Contact_Voice_Telephone: 407-382-5222
Contact_Facsimile_Telephone: 407-382-5420
Contact_Electronic_Mail_Address: general@edats.com
Contact_Instructions: www.edats.com
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.8.6 on Mon Feb 05 18:36:49 2007