FLORIDA COUNTY BOUNDARIES - STATEWIDE JULY 2011

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator: United States Census Bureau
Publication_Date: 1990
Title: FLORIDA COUNTY BOUNDARIES - STATEWIDE JULY 2011
Edition: 20010000
Geospatial_Data_Presentation_Form: SHAPE
Publication_Information:
Publication_Place: Washington DC
Publisher: U.S. Census Bureau
Other_Citation_Details: State of Florida
Online_Linkage: <http://www.census.gov/ftp/pub/geo/www/tiger>
Larger_Work_Citation:
Citation_Information:
Other_Citation_Details: 1990
Description:
Abstract:
This dataset contains the boundaries of Floridies 67 counties. It is an update of the FGDL Version 2003 County Boundaries dataset.
Purpose:
This dataset provides location and attribute information on all 67 of Florida's counties.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 1990
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: ISO 19115 Topic Category
Theme_Keyword: boundaries
Theme_Keyword: planningCadastre
Place:
Place_Keyword_Thesaurus: NONE
Place_Keyword: Florida
Place_Keyword: Southeast United States
Place_Keyword: Southeast U.S
Temporal:
Temporal_Keyword_Thesaurus: NONE
Temporal_Keyword: 2000
Access_Constraints: NONE
Use_Constraints: NONE
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: United States Census Bureau
Contact_Address:
Address_Type: mailing address
Address: 4600 Silver Hill Road
City: Washington, DC
State_or_Province: District of Columbia
Postal_Code: 20233
Country: US
Contact_Voice_Telephone: (301) 457-1128 (Geography)
Contact_Voice_Telephone: (301) 457-4100 (Customer Service)
Native_Data_Set_Environment:
Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.4000
Cross_Reference:
Citation_Information:
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:
Attribute_Accuracy_Explanation:
Previous inconsistencies in previous versions of the county borders of Hernando, Sumter, Polk, and Osceola counties have been corrected.
Since the last version of this datasets release, Dade County has changed its name from DADE to MIAMI-DADE. The new FIPS county code for Miami-Dade is 86; its previous FIPS code was 13. The FGDL Code has remained the same: C13.
Logical_Consistency_Report:
Certain node/geometry and topology (GT)-polygon/chain relationships are collected or generated to satisfy topological requirements. Some of these requirements include: chains must begin and end at nodes, chains must connect to each other at nodes, chains do not extend through nodes, left and right GT-polygons are defined for each chain element and are consistent throughout the transfer, and the chains representing the limits of the file (neatline) are free of gaps. The neatline is generated by connecting the four corners of the digital file, as established during initialization of the digital file. All data outside the enclosed region are ignored and all data crossing these geographically straight lines are clipped at the neatline. (Exception: During the QA/QC process all data is examined and if errors are found and corrections are possible, then data is corrected accordingly. This process is documented in the Process_Step.) Data within a specified tolerance of the neatline are snapped to the neatline. Neatline straightening aligns the digitized edges of the digital data with the generated neatline, that is, with the longitude/latitude lines in geographic coordinates. All internal polygons are tested for closure. Certain attributes and/or entities, e.g. closure line, convey data quality information. When information to be encoded in the subfield is known to be not applicable (undefined, not relevant), then the subfield is valued by a string of "9s"; and when the information to be encoded is relevant but unknown (or missing), then the subfield is valued by a string of "9s."
Completeness_Report:
Relied on the integrity of the attribute information within the original data layer.
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 vertical positional accuracy has not been verified by GeoPlan
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: UNITED STATES CENSUS BUREAU-TIGER/Line Files
Publication_Date: 19900000
Title: FLORIDA COUNTY BOUNDARIES
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: <http://www.census.gov/ftp/pub/geo/www/tiger>
Source_Scale_Denominator: 100000
Type_of_Source_Media: online
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1990
Ending_Date: 1990
Source_Currentness_Reference: Ground conditions
Source_Citation_Abbreviation: USCB
Source_Contribution: Spatial and Attribute Information
Process_Step:
Process_Description:
This data layer was originally created by the US Census Bureau. The GeoPlan Center acquired this dataset from the Florida Department of Environmental Protection GIS Division. This dataset was previously released in FGDL Version 3 (released July 2000), and there was an error in the eastern border of Polk County/ western border of Osceola. The border has been corrected and updated for this new version of the dataset.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 2002
Process_Step:
Process_Description:
The originating agencies created the original spatial coverage. GeoPlan, during the QA/QC process included the following aspects:
(1) Reprojected data to FGDL Albers (2) Set Precision to DOUBLE (3) Set Tolerances to FGDL Standards. (4) Changed DADE county name to MIAMI-DADE; also changed FIPS code from 13 to 86
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 2002
Process_Step:
Process_Description:
GeoPlan corrected Hernando and Sumter County boundaries in September 2004.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20040900
Process_Step:
Process_Description:
Dissolved layer based on county name in order to convert single part shapes to multipart shapes. This reduced the polygon count to 67. In addition, deleted small island polygons that had name Franklin but were located on the western border of Wakulla County.
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20080612
Process_Step:
Process_Description:
Fixed Palm Beach / Broward border. Made corrections based on the following two layers: fl_countyshore.shp (FDEP) CountyBoundary.shp (Broward County GIS)
Source_Used_Citation_Abbreviation: GeoPlan
Process_Date: 20110601
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: 67
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: CNTBND_JUN11
Entity_Type_Definition: CNTBND_JUN11.DBF
Entity_Type_Definition_Source: USCB
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: County Name
Attribute_Definition_Source: Unknown
Attribute:
Attribute_Label: FGDLCODE
Attribute_Definition: County Code used by FGDL (coincides with alphabetical order)
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: FIPS
Attribute_Definition:
Federal Informational Processing Standard Code. Unique county code used by the Census Bureau.
Attribute_Definition_Source: Unknown
Attribute:
Attribute_Label: DESCRIPT
Attribute_Definition: GeoPlan added field based on NAME
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: AUTOID
Attribute_Definition: Unique ID added by GeoPlan
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.AREA
Attribute_Definition: Area in meters
Attribute_Definition_Source: GeoPlan
Attribute:
Attribute_Label: SHAPE.LEN
Attribute_Definition: Perimeter in meters
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 Florida Geographic Data Library is a collection of Geospatial Data compiled by the University of Florida GeoPlan Center with support from the Florida Department of Transportation. GIS data available in FGDL is collected from various state, federal, and other agencies (data sources) who are data stewards, producers, or publishers. The data available in FGDL may not be the most current version of the data offered by the data source. University of Florida GeoPlan Center makes no guarantees about the currentness of the data and suggests that data users check with the data source to see if more recent versions of the data exist.
Furthermore, the GIS data available in the FGDL are provided 'as is'. 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 data sources. 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 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>
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 4.152
Technical_Prerequisites:
This data is intended for use with a Geographic Information Systems or Remote Sensing software package.
Metadata_Reference_Information:
Metadata_Date: 19900000
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: United States Census Bureau
Contact_Person: Operator
Contact_Address:
Address_Type: physical address
Address: 4600 Silver Hill Road
City: Washington D.C.
State_or_Province: District of Columbia
Postal_Code: 20233
Contact_Voice_Telephone: (301) 457-1128 (Geography)
Contact_Voice_Telephone: (301) 457-4100 (Customer Service)
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.9.6 on Fri Jun 01 14:27:33 2012