Geodataset Name:       TDSP_D2_JUN06
Geodataset Type:       Shapefile
Geodataset Feature:    POLYGON
Feature Count:         18

DATA SOURCE(S):                    NCFRPC, NEFRPC, WRPC, GeoPlan Center
SCALE OF ORIGINAL SOURCE MAPS:     VARIES
DATE OF AUTOMATION OF SOURCE:      20060614
GEODATASET EXTENT:                 FDOT District 2

FEATURE ATTRIBUTE TABLES:

Datafile Name: TDSP_D2_JUN06.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
AUTOID	GeoPlan Center internal feature number.
Shape	Feature geometry.
FIPS	State and county FIP # for each county.
COUNTY	County name.
NAME	The designation of the organization accountable for the plan.
JURISTD	Classification of responsible authority.
PLAN_DATE	The month, day, and year when the plan was published.
SUBCONTRS	Subcontractor(s) or operator name(s).
DESCRIPT	Based on NAME.
SOURCE	The Source of the Data.
FGDLAQDATE	The date FGDL acquired the data from the Source.
OBJECTID	Internal feature number.
SHAPE	Feature geometry.
SHAPE.AREA	No description
UPDATE_DAY	The last time the data was updated by the Source.
SHAPE.LEN	No description

USER NOTES:

This data is provided 'as is'. GeoPlan relied on the integrity of the original data layer's topology The incorporated area is mapped in a uniform and consistent method.

This data is provided 'as is' by GeoPlan and is complete to our knowledge. County boundaries are used to represent the boundaries of each service provider area, as this is a county-wide function. All counties in the project area are included. Sub areas, if they exist within or between counties, are not included.

GeoPlan relied on the integrity of the attribute information within the original data.

This data is provided 'as is' and its horizontal positional accuracy has not been verified by GeoPlan County boundaries are generalized in order to show each county as a single polygon. The seaward boundary on the Gulf side does not represent the actual coast, but includes a large strip of water attributed to each county.

This data is provided 'as is' and its vertical positional accuracy has not been verified by GeoPlan

A note concerning data scale: Scale is an important factor in data usage. Certain scale datasetsare 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:250000 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 analyses. Every effort has been made to supply the user with data documentation. For additional information, see the References sectionand the Data Source Contact section of this documentation. For more information regarding scale and accuracy, see our web pages at: http://www.geoplan.ufl.edu/education.html

REFERENCES:

North Central Florida Regional Planning Council NCFRPC 2009 N.W. 67th Place, Suite A Gainesville, FL 32653 407-314-8683 http://www.ncfrpc.org/ Carol Laine laine@ncfrpc.org Northeast Florida Regional Planning Council NEFRPC 6850 Belfort Oaks Place Jacksonville, FL 32216 (904) 279-0880 Fax (904) 279-0881 http://www.nefrpc.org/ info@nefrc.org Keith Joiner KJoiner@nefrc.org

DATA LINEAGE SUMMARY:

North Central Florida Regional Planning Council - Process Steps: The county boundaries available from the US Census Bureau were downloaded from the University of Florida Geoplan website at www.fgdl.org. Attribute fields were deleted and added to conform to sociocultural data specs. The attribute fields were populated based on information received from the Planning Councils. February, 2005 to June, 2005 Process Date: 20050601 Northeast Florida Regional Planning Council - Process Steps: The polygons from the St. Johns River Water management District representing county boundaries were downloaded and attributed. They were then exported as a shapefile. Process Date: 20060501 GeoPlan Center - Process Steps: GeoPlan received this data, via CDROM, 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. Process Date: 20060614 Metadata imported. Process Date:

MAP PROJECTION PARAMETERS:

Projection                          ALBERS
Datum                               HPGN
Units                               METERS
Spheroid                            GRS1980
1st Standard Parallel               24  0  0.000
2nd Standard Parallel               31 30  0.000
Central Meridian                   -84 00  0.000
Latitude of Projection's Origin     24  0  0.000
False Easting (meters)              400000.00000
False Northing (meters)             0.00000

DATA SOURCE CONTACT (S):

Name:
Abbr. Name:
Address:


Phone:

Web site:
E-mail:
Contact Person:
         Phone:
        E-mail:

GeoPlan Center - University of Florida
GeoPlan Center
431 ARCH BLDG
Gainesville, Florida
32611




image@fgdl.org
Kate Norris

Name:                   FLORIDA GEOGRAPHIC DATA LIBRARY
Abbr. Name:             FGDL
Address:                Florida Geographic Data Library
                        431 Architecture Building
                        PO Box 115706
                        Gainesville, FL  32611-5706
Web site:               http://www.fgdl.org

Contact FGDL: 

      Technical Support:	        http://www.fgdl.org/fgdlfeed.html
      FGDL Frequently Asked Questions:  http://www.fgdl.org/fgdlfaq.html
      FGDL Mailing Lists:		http://www.fgdl.org/fgdl-l.html
      For FGDL Software:                http://www.fgdl.org/software.html