FLORIDA GEOGRAPHIC DATA LIBRARY DOCUMENTATION TITLE: 2010 U.S. CENSUS BLOCK GROUPS IN FLORIDA (FILE GEODATABASE WITH ASSOCIATED REDISTRICTING TABLES) Geodataset Name: CENBLKGRP2010_SF_MAR11 Geodataset Type: SHAPEFILE Geodataset Feature: Polygon Feature Count: 11442 |
|
GENERAL DESCRIPTION:
|
|
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 |
FEATURE ATTRIBUTE TABLES:
Datafile Name: CENBLKGRP2010_SF_MAR11.DBF
ITEM NAME | WIDTH | TYPE |
OBJECTID
|
4 | OID |
Shape
|
0 | Geometry |
STATEFP10
|
2 | String |
COUNTYFP10
|
3 | String |
TRACTCE10
|
6 | String |
BLKGRPCE10
|
1 | String |
GEOID10
|
12 | String |
NAMELSAD10
|
13 | String |
MTFCC10
|
5 | String |
FUNCSTAT10
|
1 | String |
ALAND10
|
8 | Double |
AWATER10
|
8 | Double |
INTPTLAT10
|
11 | String |
INTPTLON10
|
12 | String |
POP2010
|
4 | Integer |
Shape_Length
|
8 | Double |
Shape_Area
|
8 | Double |
FGDLAQDATE
|
8 | Date |
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
|
|
BLKGRPCE10 |
2010 Census block group number
|
|
GEOID10 |
Census block group identifier; a concatenation of 2010 Census
state Federal Information Processing Standards (FIPS) code,
county FIPS code, census tract code, and block group number |
|
NAMELSAD10 |
2010 Census translated legal/statistical area description and
the block group number |
|
MTFCC10 |
MAF/TIGER feature class code
|
|
FUNCSTAT10 |
2010 Census functional status
|
|
ALAND10 |
2010 Census land area (square meters)
|
|
AWATER10 |
2010 Census water area (square meters)
|
|
INTPTLAT10 |
2010 Census latitude of the internal point
|
|
INTPTLON10 |
2010 Census longitude of the internal point
|
|
POP2010 |
Total population |
|
Shape_Length |
Length of feature in internal units. |
|
Shape_Area |
Area of feature in internal units squared. |
|
FGDLAQDATE |
Date FGDL acquired the data |
This geodatabase contains one feature class representing the 2010 census block groups, five tables of redistricing housing and population data, and five relationship classes linking the tables to the census block groups feature class. GEODATABASE CONTENTS: Spatial Data: cenblkgrp2010_sf_mar11 - Feature class with 2010 Florida census block groups 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 block groups feature class (cenblkgrp2010_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 block groups feature class (cenblkgrp2010_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 block groups feature class (cenblkgrp2010_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 block groups feature class (cenblkgrp2010_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 block groups feature class (cenblkgrp2010_sf_mar11) on the GEOID10 field. Relationship Classes: cenblkgrp2010_redis_h1 - Relationship class to link population data in redis_h1 table to the census block groups feature class (cenblkgrp2010_sf_mar11). Link is based on GEOID10 field. cenblkgrp2010_redis_p1 - Relationship class to link population data in redis_p1 table to the census block groups feature class (cenblkgrp2010_sf_mar11). Link is based on GEOID10 field. cenblkgrp2010_redis_p2 - Relationship class to link population data in redis_p2 table to the census block groups feature class (cenblkgrp2010_sf_mar11). Link is based on GEOID10 field. cenblkgrp2010_redis_p3 - Relationship class to link population data in redis_p3 table to the census block groups feature class (cenblkgrp2010_sf_mar11). Link is based on GEOID10 field. cenblkgrp2010_redis_p4 - Relationship class to link population data in redis_p4 table to the census block groups feature class (cenblkgrp2010_sf_mar11). Link is based on GEOID10 field. |
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 Block Groups, 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). Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. 2000 Census Block Groups generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas. |
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 |
Technical Documentation - Redistricting Data http://www.census.gov/prod/cen2010/doc/nsfrd.pdf |
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: 2010 |
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 |
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