Geodataset Name:       CENBLK2010_SF_MAR11
Geodataset Type:       SHAPEFILE
Geodataset Feature:    Polygon
Feature Count:         484481

DATA SOURCE(S):                    U.S. Department of Commerce, U.S. Census Bureau, Geography Division
SCALE OF ORIGINAL SOURCE MAPS:     Varies
GEODATASET EXTENT:                 State of Florida

PUBLICATION DATE:                  2010
TIME PERIOD OF CONTENT:            Begin Date: 201001    End Date: 201007
DOWNLOAD LINK:                     http://www.fgdl.org/metadataexplorer/explorer.jsp

FEATURE ATTRIBUTE TABLES:

Datafile Name: CENBLK2010_SF_MAR11.DBF

FEATURE ATTRIBUTE TABLES CODES AND VALUES:

Item	Item Description
OBJECTID	Internal feature number.
Shape	Feature geometry.
STATEFP10	2010 Census state Federal Information Processing Standards (FIPS) codes
COUNTYFP10	2010 Census county Federal Information Processing Standards (FIPS) code
TRACTCE10	2010 Census census tract code 000000 = Water tract in some coastal and Great Lakes water and territorial sea 000100 to 998999 = Census tract number
BLOCKCE10	2010 Census tabulation block number 0001 to 9999 = tabulation block number
GEOID10	Block identifier; a concatenation of 2010 Census state Federal Information Processing Standards (FIPS) code, county FIPS code, census tract code, and tabulation block number
NAME10	2010 Census tabulation block name; a concatenation of "Block", and the current tabulation block number
MTFCC10	MAF/TIGER feature class code G5040 = Tabulation Block
UR10	2010 Census urban/rural indicator M = Mixed - part of the land area is classified as urban and part is classified as rural N = Not Applicable (water-only and international areas) R = Area is classified as rural U = Area is classified as urban
UACE10	2010 Census urban area code 00001 to 98999 = Urban Area Code
FUNCSTAT10	2010 Census functional status S = Statistical entity
ALAND10	2010 Census land area (square meters) 0 to 9,999,999,999,999 = Blank
AWATER10	2010 Census water area (square meters) 0 to 9,999,999,999,999 = Blank
INTPTLAT10	2010 Census latitude of the internal point 00 = Blank
INTPTLON10	2010 Census longitude of the internal point 00 = Blank
POP2010	Total population
FGDLAQDATE	Date FGDL acquired the data
BLKCHANGE	This field represents the relationship of the 2000 census blocks to the 2010 census blocks. The data in this field was derived from the Census 2000 Tabulation Block to 2010 Census Tabulation Block Relationship File. This file is available as a text file for download from the US Census Bureau. Block relationships between 2000 blocks to 2010 blocks may be one-to-one, many-to-one, one-to-many, or many-to-many. Use the GEOID00 to relate back to STFID field in CENBLK2000. 1 = No change in 2000 block geometry compared to 2010 block geometry (one-to-one). 2 = One 2000 block is represented by multiple 2010 blocks, i.e. the block was split in 2010 (one-to-many). 3 = Multiple 2000 blocks are represented by one 2010 block, i.e. the block was merged in 2010 (many-to-one). 4 = Multiple 2000 blocks are now represented by multiple 2010 blocks (many-to-many).
GEOID00	This field represents the 2000 census block identifier. If you are using CENBLK2000 from FGDL the GEOID00 can be related to the STFID field. Please note: in records where BLKCHANGE = 3 or 4 there will only be one GEOID00 listed of many.
Shape_Length	Length of feature in internal units.
Shape_Area	Area of feature in internal units squared.

This geodatabase contains one feature class representing the 2010 census blocks, five tables of redistricing housing and population data, and five relationship classes linking the tables to the census blocks feature class. Spatial Data: cenblk2010_sf_mar11 - Feature class with 2010 Florida census blocks Tabular Data: redis_h1 - Tabular housing data on total number of housing units and occupancy status from redistricting summary file. This table can be joined to census blocks feature class (cenblk2010_sf_mar11) on the GEOID10 field. redis_p1 - Tabular population data on race and total population from redistricting summary file. This table can be joined to the census blocks feature class (cenblk2010_sf_mar11) on the GEOID10 field. redis_p2 - Tabular population data on hispanic population and race from redistricting summary file. This table can be joined to the census blocks feature class (cenblk2010_sf_mar11) on the GEOID10 field. redis_p3 - Tabular population data on the population over 18 years of age from redistricting summary file. This table can be joined to the census blocks feature class (cenblk2010_sf_mar11) on the GEOID10 field. redis_p4 - Tabular population data on the population over 18 by hispanic origin and race from redistricting summary file. This table can be joined to the census blocks feature class (cenblk2010_sf_mar11) on the GEOID10 field. Relationship Classes: cenblk2010_redis_h1 - Relationship class to link population data in redis_h1 table to the census blocks feature class (cenblk2010_sf_mar11). Link is based on GEOID10 field. cenblk2010_redis_p1 - Relationship class to link population data in redis_p1 table to the census blocks feature class (cenblk2010_sf_mar11). Link is based on GEOID10 field. cenblk2010_redis_p2 - Relationship class to link population data in redis_p2 table to the census blocks feature class (cenblk2010_sf_mar11). Link is based on GEOID10 field. cenblk2010_redis_p3 - Relationship class to link population data in redis_p3 table to the census blocks feature class (cenblk2010_sf_mar11). Link is based on GEOID10 field. cenblk2010_redis_p4 - Relationship class to link population data in redis_p4 table to the census blocks feature class (cenblk2010_sf_mar11). Link is based on GEOID10 field.

USER NOTES:

The Census Bureau performed automated tests to ensure logical consistency and limits of shapefiles. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. All polygons are tested for closure. The Census Bureau uses its internally developed geographic update system to enhance and modify spatial and attribute data in the Census MAF/TIGER database. Standard geographic codes, such as FIPS codes for states, counties, municipalities, county subdivisions, places, American Indian/Alaska Native/Native Hawaiian areas, and congressional districts are used when encoding spatial entities. The Census Bureau performed spatial data tests for logical consistency of the codes during the compilation of the original Census MAF/TIGER database files. Most of the codes for geographic entities except states, counties, urban areas, Core Based Statistical Areas (CBSAs), American Indian Areas (AIAs), and congressional districts were provided to the Census Bureau by the USGS, the agency responsible for maintaining FIPS 55. Feature attribute information has been examined but has not been fully tested for consistency. For the TIGER/Line Shapefiles, the Point and Vector Object Count for the G-polygon SDTS Point and Vector Object Type reflects the number of records in the shapefile attribute table. For multi-polygon features, only one attribute record exists for each multi-polygon rather than one attribute record per individual G-polygon component of the multi-polygon feature. TIGER/Line Shapefile multi-polygons are an exception to the G-polygon object type classification. Therefore, when multi-polygons exist in a shapefile, the object count will be less than the actual number of G-polygons.

Data completeness of the TIGER/Line Shapefiles reflects the contents of the Census MAF/TIGER database at the time the TIGER/Line Shapefiles were created.

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

This dataset contains 2010 Census Blocks, which are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces. The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands).

To analyze demographic and census data from the 2010 U.S. Census.

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

The TIGER/Line Shapefile products are not copyrighted however TIGER/Line and Census TIGER are registered trademarks of the U.S. Census Bureau. These products are free to use in a product or publication, however acknowledgement must be given to the U.S. Census Bureau as the source. The boundary information in the TIGER/Line Shapefiles are for statistical data collection and tabulation purposes only; their depiction and designation for statistical purposes does not constitute a determination of jurisdictional authority or rights of ownership or entitlement and they are not legal land descriptions. Coordinates in the TIGER/Line shapefiles have six implied decimal places, but the positional accuracy of these coordinates is not as great as the six decimal places suggest.

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

REFERENCES:

Technical Documentation - Redistricting Data http://www.census.gov/prod/cen2010/doc/nsfrd.pdf

DATA LINEAGE SUMMARY:

TIGER/Line Shapefiles are extracted from the Census MAF/TIGER database by nation, state, county, and entity. Census MAF/TIGER data for all of the aforementioned geographic entities are then distributed among the shapefiles each containing attributes for line, polygon, or landmark geographic data. Process Date: 201003 GeoPlan downloaded the Redistricting Summary File in .pl format from the Census Bureau: http://www2.census.gov/census_2010/01-Redistricting_File--PL_94-171/Florida/ The database was compiled using the process steps in http://www.census.gov/rdo/pdf/0HowToUseMicrosoftAccessShells.pdf The 2010 TIGER line files were downloaded from the following site: http://www.census.gov/geo/www/tiger/tgrshp2010/tgrshp2010.html When received the data was in Geographic Lat/Long projection. The data was projected to Albers HPGN. Relationship classes were created for each associated table. The relationship class is included in the GeoDatabase to help facilitate the identification, querying, relating, and joining of records while using the data within ArcMap. For more information on using relationship classes within ArcMap 9.3, please see the following link: http://webhelp.esri.com/arcgisserver/9.3/dotnet/index.htm#geodatabases/relati-1485884924.htm The following QAQC procedures were performed: - exported original shapefile to file GeoDatabase - Added field FGDLAQDATE based on date GeoPlan acquired data from Census Bureau - Added field BLKCHANGE field based on data derived from the Census 2000 Tabulation Block to 2010 Census Tabulation Block Relationship File. This file is available as a text file for download from the US Census Bureau. - Added field GEOID00 from data taken from 2010 Census Tabulation Block Relationship File. This field links back to CENBLK2000 using the STFID field. - Changed dataset name from tl_2010_12_tabblock10.shp to CENBLK2010_MAR11 Process Date: 20110405 Rexported feature classes in geodatabase in order to fix corrupt geodatabase table redis_p1. Process Date: 20111222

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:

U.S. Department of Commerce, U.S. Census Bureau, Geography Division, Geographic Products Branch
MAF/TIGER
4600 Silver Hill Road, Stop 7400
Washington, DC
20233-7400
301-763-1128


http://www.census.gov/geo/www/tiger
geo.tiger@census.gov

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