Download:
pdf |
pdfBlock Boundary Suggestion Project
Participant Guide
Instructions
for
Using the
Instructions
for
Participants
Geographic
Update
Partnership Software
With
User Supplied
GIS
(GUPS)
Software
2020 Redistricting Data Program
00…….
Phase
One
Block Boundary Suggestion Project
September 2015
U.S. Department of Commerce
Economic and Statistics Administration
U.S. CENSUS BUREAU
census.gov
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Table of Contents
Introduction ........................................................................................................ 3
1 Planned 2020 Census Tabulation Block Boundaries ............................... 5
2 Suggested BBSP Workflow ........................................................................ 7
2.1 Acquiring the Geospatial Data ........................................................................ 9
2.2 RDP Liaison Delegates Work ......................................................................... 9
2.3 Linear Feature Review................................................................................... 10
2.4 Area Landmark and Area Hydrography Review ........................................ 12
2.5 Legal Boundary Review and Update (New for 2020) ............................... 12
2.6 Point Landmark Review................................................................................. 15
2.7 2010 Linear Feature Extension Review ...................................................... 15
2.8 Block Size Review (New for 2020) .............................................................. 17
2.9 Block Boundary Suggestion Flagging (Must Hold and Do Not Hold) ..... 18
2.10
Block Area Grouping Delineation (Updated for 2020) .......................... 20
2.11
Block Boundary Review ............................................................................. 21
2.12
Validation Check ......................................................................................... 21
2.13
Work Delegated........................................................................................... 21
3 Create Data Submission Files .................................................................. 23
3.1 Linear Feature Updates and Block Boundary Suggestions ..................... 23
3.2 Area Landmarks and Area Hydrology Updates ......................................... 23
3.3 Legal Boundary Updates ............................................................................... 24
3.4 Point Feature Updates ................................................................................... 25
3.5 Block Area Grouping Updates ...................................................................... 25
3.6 Create .ZIP File ............................................................................................... 25
4 File Submission Through SWIM ............................................................... 27
4.1 Login Page....................................................................................................... 28
4.2 If you already have a SWIM Account: ......................................................... 28
4.3 If you do not yet have a SWIM Account:..................................................... 29
4.4 Welcome Page ................................................................................................ 30
4.5 Geographic Program Page ........................................................................... 31
4.6 Select a State .................................................................................................. 31
4.7 Select a .ZIP File to Upload .......................................................................... 32
4.8 Thank You Page ............................................................................................. 33
APPENDIX A: UPDATES ALLOWED, BY MTFCC .......................................... 34
A.1 Area Landmark Updates Permitted ................................................................ 34
A.2 Linear Feature Updates Permitted ................................................................. 35
A.3 Point Landmark Updates Permitted ................................................................ 36
APPENDIX B: MTFCC DESCRIPTIONS - COMPLETE LIST ........................... 37
APPENDIX C: PARTNERSHIP SHAPEFILE DATA DICTIONARY .................. 50
APPENDIX D: ACRONYMS .............................................................................. 68
APPENDIX E: BBSP PARTICIPANT SUPPORT .............................................. 69
APPENDIX F: COUNTY COMPLETION TRACKING SHEET........................... 70
Paperwork Reduction Act (PRA) Statement:
View Table of Contents
2 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
A federal agency may not conduct or sponsor, nor shall a person be subject to a penalty for failure to
comply with a collection of information subject to the requirements of the Paperwork Reduction Act unless
that collection of information displays a current valid OMB Control Number. This collection is voluntary.
The authority for conducting this collection comes from Title 13 U.S.C, Sections 16, 141, and 193.
The OMB Control Number for this information collection is 0607-XXXX. Public reporting for this collection of
information is estimated to be approximately 186 hours per response, including the time for reviewing
instructions, completing and reviewing the collection of information.
Comments concerning the accuracy of this burden and suggestions for reducing the burden should be
directed to: Paperwork Reduction 0607-XXXX, United States Census Bureau, 4600 Silver Hill Road, Room
3K138, Washington, DC 20233. You may email comments to [email protected]; use “Paperwork
Project 0607-XXXX” as the subject.
View Table of Contents
3 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Introduction
Public Law 94-171 stipulates that the U.S. Census Bureau work in a nonpartisan
manner with the states to identify and provide the small-area data population counts
necessary for legislative redistricting to the governor and the officers or public bodies
having responsibility for redistricting of each state one year after the Census. For the
2020 Census, the Census Bureau must deliver the counts by April 1, 2021.
The Census Redistricting & Voting Rights Data Office implements the requirements of
P.L. 94-171 through five phases of the Redistricting Data Program:
Phase 1:
Phase 2:
Phase 3:
Phase 4:
Phase 5:
Block Boundary Suggestion Project (BBSP)
Voting District Project (VTDP)
Delivery of the 2020 P.L. 94-171 Redistricting Data Files
Collection of Post-2020 Redistricting Plans
Review of 2020 Census Redistricting Data Program and Recommendations
for Census 2030
This document addresses Phase 1: Block Boundary Suggestion Project of the
Redistricting Data Program. It is intended for state participants their own Geographic
Information System (GIS) software, rather than the Geographic Update Partnership
Software (GUPS), for modifying the Census Bureau supplied shapefiles. The GUPS is
the Census Bureau’s recommended tool for submission and review of Block Boundary
Suggestions.
It is assumed that if you are not using the GUPS, you are skilled in the use of your own
GIS software. The Census Bureau requires that entities update Census Bureau
shapefiles, rather than submitting a shapefile from a local GIS.
View Table of Contents
4 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
1 Planned 2020 Census Tabulation Block Boundaries
Census tabulation block boundaries primarily follow visible features, such as roads and
rivers, as well as any edges that bound legal or statistical geographic areas or selected
area landmarks stored in the MAF/TIGER System. Census blocks nest within all other
tabulated census geographic entities and are the basis for all data tabulated for the
decennial census, the American Community Survey, and other Census Bureau
programs and surveys.
The table below lists the feature and boundary types currently planned as 2020 Census
tabulation block boundaries.
2020 CENSUS PLANNED TABULATION BLOCK BOUNDARIES BY
MAF/TIGER FEATURE CLASSIFICATION CODE (MTFCC)
G2120 Hawaiian Home Land
G5200 Congressional District
G2130 Alaska Native Village Statistical Area
G5210 State Legislative District (Upper Chamber)
G2140 Oklahoma Tribal Statistical Area
G5220 State Legislative District (Lower Chamber)
G2150 State-designated Tribal Statistical Area
G5240 Voting District
G2160 Tribal Designated Statistical Area
G5400 Elementary School District
G2170 American Indian Joint Use Area
G5410 Secondary School District
G2200 Alaska Native Regional Corporation
G5420 Unified School District
G2300 Tribal Subdivision
G6330 Urban Growth Area
G2400 Tribal Census Tract
K2110 Military Installation
G2410 Tribal Block Group
K2181 National Park Service Land
G4000 State or State Equivalent
K2182 National Forest or Other Federal Land
G4020 County or State Equivalent
K2540 University or College
G4040 County Subdivision
K1235 Juvenile Institution
G4050 Estate
G4110 Incorporated Place
K1236 Local Jail or Detention Center
K1237 Federal Penitentiary, State Prison, or Prison
Farm
K1238 Other Correctional Institution
G4120 Consolidated City
S1100 Primary Road
G5020 Census Tract
S1200 Secondary Road
G4060 Sub-Minor Civil Division
G5035 Block Area Grouping
Table 1.1: Planned 2020 Tabulation Block Boundaries
Please note that primary and secondary roads (MTFCCs S1100 and S1200) are
planned 2020 Census tabulation block boundaries. Other features, such as local roads,
alleys, railroads, and perennial water, may or may not qualify as 2020 Census
tabulation block boundaries based on the established criteria. These features can be
selected as “must hold” or “do not hold” block boundaries. You can determine whether
View Table of Contents
5 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
a feature is planned block boundary by the feature symbolization in the map or the
feature’s value in the CBBFLG field in the attribute table. A CBBFLG value of “4”
indicates the feature is a planned 2020 block boundary, while a CCBFLG value of “9”
indicates the feature is ineligible as a 2020 tabulation block boundary.
The technical details for reviewing features and assigning block boundary suggestion
flags are contained in Part 2, Chapter 6.
Note: Appendix B: MTFCC Descriptions - Complete List, contains the list of MTFCC
values in the partnership shapefiles and their descriptions.
View Table of Contents
6 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2 Suggested BBSP Workflow
Figure 3.1 depicts the suggested workflow for reviewing and updating Census Bureau
data for the Block Boundary Suggestion Project.
There is a separate chapter outlining the activities associated with each of the workflow
process (square) boxes. The BBSP participant is not required to perform all the update
activities shown in the flowchart.
Work is performed at a county level and should be submitted to the Census Bureau on
a flow basis, as you complete each county. Submitting work on flow basis permits the
Census Bureau to review the files early in the process, provide feedback as necessary,
and facilitates our file processing.
View Table of Contents
7 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
GUPS & Geospatial Data
Available on Web
RDP Liaison
Delegates Work?
NO
RDP Liaison Completes Work
YES
Designee Completes Work
Linear Feature
Review
Area Landmark
Review
Legal Boundary
Review
Point Landmark
Review
Geographic DaPa Reviews
2010 Feature
Extension Review
YES
Block Size Review
(manual process)
Block Area
Grouping
Delineation
Block Boundary
Flagging
BBSP UpdaPe AcPiviPies
Block Boundary
Review
Validation
Check
QualiPy ConProl
Changes
Needed?
Submit Work to
RDP Liaison
Designee Creates
Data Output Fifle
YES
Was Work
Delegated?
NO
NO
Submit Data to
Census
Create Data
Submission File
Figure 2.1 Suggested BBSP Workflow
View Table of Contents
8 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2.1
Acquiring the Geospatial Data
To download the Spatial Data, visit the Census Redistricting and Voting Rights Data
Office website: http://www.census.gov/rdo/data/ and follow the directions posted.
To download the Census Bureau’s partnership shapefiles in ESRI format 1 for your
state, visit:
http://www.census.gov/geo/partnerships/bas/bas_download.html
Shapefile Projection
It is recommended that participants re-project their data files to match those provided by
the Census Bureau to ensure correct alignment of the data. However, returned
shapefiles may be in any projection as long as the projection information and the *.prj
file are provided. A complete data dictionary is provided at the end of this attachment.
All shapefiles provided by the Census Bureau are in the following unprojected
geographic based coordinate system:
•
•
•
•
•
•
•
•
2.2
GCS_NAD83
Angular Unit: Degree (0.017453292519943299)
Prime Meridian: Greenwich (0.000000000000000000)
Datum: D_North_American_1983
Spheroid: GRS_1980
Semi-major Axis: 6378137.000000000000000
Semi-minor Axis: 6356752.314140356100000000
Inverse Flattening: 298.257222101000020000
RDP Liaison Delegates Work
The State Redistricting Data Program Liaison may choose to delegate work to an
agency, a county or counties, or a contractor. In this document, these persons as
collectively referred to as designees. Regardless of who performs the BBSP work, the
file updating process is the same. The difference is that only the State RDP Liaison may
submit completed work to the Census Bureau. The information regarding the data
output creation is contained in Section 6.
1
The use of brand names does not represent an endorsement of a company or its products by the U.S.
government. Due to the wide use of ESRI products by our partners in the GIS community, and the ubiquitous
use of the shapefile format as a medium for GIS data exchange, the Census Bureau is providing this data in
shapefile format. You should encounter no problems when importing these shapefiles into your local GIS
software. However, if you are using GIS software that does not contain a shapefile translator, please contact the
Census Bureau for further instructions (301-763-1099) or e-mail [email protected].
View Table of Contents
9 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2.3
Linear Feature Review
You should review the Census Bureau’s linear features (all edges layer) to determine
whether there are features missing or features that should be deleted. Pay particular
attention to any areas that have experienced population growth, where there may be
new housing or subdivisions that are not reflected in the Census Bureau’s geospatial
data.
The Census Bureau will also accept attribute updates (name, classification code, and
address ranges) for selected features. Added road features with MTFCC S1100Primary Road, or S1200-Secondary Road, require a feature name.
Please be aware that the Census Bureau will not process the wholesale spatial
realignment of features to enhance spatial accuracy. If a feature is in the incorrect
location in the Census Bureau’s feature network, delete the feature and add it in the
correct location. Take this action only if the feature is over 7.6 meters off or interferes
with the relationship with other features.
Participants should begin by making a copy of the Census Bureau Edges Shapefile
Layer for editing. This will be referred to as the linear feature update layer. It is
suggested that you symbolize the ‘edges’ layer based on the MTFCC. A description of
all MTFCCs can be found in Attachment B. The basic groupings of the MTFCCs are as
follows: Sxxxx = Roads; Rxxxx = Railroads; Pxxxx = Nonvisible Features; Lxxxx =
Other Linear Features; and Hxxxx = Hydrography. Once the edges layer is copied an
symbolized, bring in other Census provided shapefiles (e.g., CD, SLDL, SLDU,
incorporated places, etc.) and any local data layers that may be helpful.
Participants should submit linear feature updates in the linear feature update layer.
Each linear feature update must have the required attributes and corresponding change
type populated. The change type field (CHNG_TYPE) must be populated with either
‘AL’, indicating an added line, ‘DL’, indicating a deleted line, or ‘CA’, indicating the
feature was renamed or recoded. In the TLID field, preserve the existing TLID for the
feature. Provide the feature name and MTFCC code in the FULLNAME and MTFCC
fields.
CHNG_TYPE
TLID
Add Feature
X(‘AL’)
Delete Feature
X(‘DL’)
X
Rename Feature
X(‘CA’)
X
Recode Feature
X(‘CA’)
X
FULLNAME
MTFCC
X
X
X
X
Note: X = Required Field
View Table of Contents
10 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Linear Feature Update Criteria
•
•
•
If a road, subdivision, etc. is missing from the Census Bureau’s feature network,
add the feature(s) and provide the name and MTFCC. Feature name is required
for all primary and secondary roads (MTFCC = s1100 or s1200).
If a feature that does not exist is in the Census Bureau’s feature network, delete
the feature by updating the attribute table with “DL” in the CHNG_TYPE field.
Do not actually delete the feature in the file.
If a feature is in the incorrect location in the Census Bureau’s feature network,
delete the feature and re-add it in the correct location. Only do this if the feature
is very far off or in the wrong position relative to boundaries or features, or if the
assignment of housing units to the correct geography (census block, tract, legal
entity) is affected.
Address Range Updates
The Census Bureau accepts address range data as part of the linear feature update
layer. As with other linear feature updates, address ranges must have the required
attributes and corresponding change type populated.
We recommend that participants only add address ranges to new features. Existing
address ranges are not shown in our outgoing shapefiles; however, address ranges can
be found in the ADDR.dbf table and can be joined to the edges shapefile through a
many-to-one join.
Each address range update must have the required attributes and corresponding
change type populated.
.
Address Ranges
CHNG_TYPE
LTOADD
RTOADD
LFROMADD
RFROMADD
X(‘CA’)
X
X
X
X
Note: X = Required Field
Appendix A2: Linear Feature Updates Permitted, lists the feature updates the Census
Bureau will accept.
View Table of Contents
11 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2.4
Area Landmark and Area Hydrography Review
The Census Bureau accepts updates to area landmarks and area hydrography as part
of the Block Boundary Suggestion Project.
Allowable updates include:
• Boundary corrections (adding and removing area).
• Creating a new area landmark or hydrographic area.
• Removing an area landmark or hydrographic area.
• Changing or adding a name.
If your state plans to reallocate prisoners during redistricting, you may wish to review
the existing area landmarks with MTFCCs K1235, K1236, K1237, and K1238, which
represent areas with prison populations.
In order to submit area landmark and area hydrography updates, participants must
create a separate change polygon layer.
Each area landmark or area hydrography update must have the required attributes and
corresponding change type populated. In the AREAID field, preserve the existing
AREAID for the feature.
FULLNAME
CHNG_TYPE
RELATE
X
X(‘B’)
X(‘IN’)
X
X
X(‘B’)
X(‘OUT’)
X
Boundary Correction
(Add Area)
Boundary Correction
(Remove Area)
Delete Landmark
MTFCC
AREAID
X(‘D’)
X
X
Change Landmark
Name
X
X(‘G’)
New Landmark
X
X(‘E’)
X
Note: X = Required Field
Appendix A1: Area Landmark Updates Permitted, lists the feature updates the Census
Bureau will accept.
2.5
Legal Boundary Review and Update (New for 2020)
At the recommendation of many states, the Census Bureau is introducing a Boundary
and Annexation Survey (BAS) review as part of Phase 1 (BBSP) and Phase 2 (VTD) of
the Redistricting Data Program.
View Table of Contents
12 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
During the initial delineation phase and the subsequent verification phase of the Block
Boundary Suggestion Project, state redistricting participants may submit legal boundary
updates (annexations, de-annexations, incorporations and dis-incorporations) and
boundary corrections. The Census Bureau will assume the responsibility for reconciling
the updates with the appropriate local governments as part of our 2016 and 2017
Boundary and Annexation Surveys.
You may submit legal boundary updates for county subdivisions, incorporated places,
and consolidated cities. Although legal documentation (effective date, authority type,
and ordinance number) is not required for boundary updates submitted through the
BBSP, we strongly encourage you to submit the documentation to expedite our ability to
reconcile and process any legal updates reported. Annexations, de-annexations,
incorporations and dis-incorporations being submitted without documentation should all
be submitted as boundary corrections.
You do not have to provide the legal paperwork for a legal change, just the effective
date, authorization type, and ordinance number for changes to be processed as a Legal
Change.
Annexations and Deannexations
An individual change polygon must be created for each annexation, deannexation, and
boundary correction. Change polygons should represent the spatial differences
between the current Census Bureau MAF/TIGER boundaries and local boundaries.
The change polygon must be appropriately coded with the required attributes and
corresponding change type populated, as seen below.
The ‘Name’ field should be populated with the name of the geographic entity effected.
The ‘Change Type’ field should indicate whether the change is an annexation (A) or
deannexation (D).
If available, the authorization type field (AUTHTYPE) should be populated the type of
documentation (i.e., ordinance, resolution, local law, other). The effective date field
(EFF_DATE) should be populated with the date of the ordinance, resolution, or local
law. The documentation field (DOCU) should be populated with the documentation
number.
NAME
CHNG_TYPE
EFF_DATE
AUTHTYPE
DOCU
Annexation
X
X(‘A’)
If available
If available
If available
Deannexation
X
X(‘D’)
If available
If available
If available
RELATE
Note: X = Required Field
Boundary Corrections
View Table of Contents
13 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
The Census Bureau will also accept specific boundary corrections for county
subdivisions, incorporated places, and consolidated cities. As with annexations and
deannexations, the participant must create individual change polygons for each
boundary correction. Each boundary correction must have the required attributes and
corresponding change type. The name field (NAME) must be populated with the name
of the corrected legal entity. The change type field (CHNG_TYPE) must be populated
with a ‘B’ to indicated boundary correction. The relate field (RELATE) must be
populated with ‘IN’, indicating the corrected area is within the named legal entity, or
‘OUT’, indicating the corrected area is outside of the named legal entity.
NAME
Boundary
X
Correction
(Add Area)
Boundary
X
Correction
(Remove Area)
Note: X = Required Field
CHNG_TYPE
EFF_DATE
AUTHTYPE
DOCU
RELATE
X(‘B’)
X(‘IN’)
X(‘B’)
X(‘OUT’)
Please review all changes to ensure that the correct boundary-to-feature relationships
are being created or maintained. The Census Bureau is aware that many governments
base their legal boundaries on cadastral (parcel-based) right-of-way mapping; however,
the Census Bureau bases maps on spatial data that is topologically integrated.
Therefore, snap boundaries to street centerlines (or rivers, railroads, etc.) wherever
applicable. This will help establish a more accurate population count for entities.
Boundary Correction Criteria
The Census Bureau uses a topologically integrated database. As a result, the Census
Bureau cannot process all types of boundary corrections for inclusion in MAF/TIGER.
The following are types of boundary corrections that the Census Bureau will accept,
process, and update or reject.
The Census Bureau will accept and process boundary corrections that:
• spatially interact with (abut) other legal changes (annexation, deannexation) and
meet both of the following two conditions:
o the existing boundary has been digitized incorrectly or appears in the
incorrect location.
o the overall shape of the geographic entity is maintained and no featureto-boundary relationships are dissolved.
The Census Bureau will not accept boundary corrections that:
• are along county boundaries unless there is a written agreement between the
two counties that documents the correct location of the boundary.
• dissolve boundary-to-feature relationships (roads, rivers, railroads, etc.) if the
difference is less than thirty feet.
• have a width of less than thirty feet over the entire polygon.
View Table of Contents
14 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Note: The Census Bureau will snap any entity boundary correction to a MAF/TIGER
feature when it exists within thirty feet of that feature.
2.6
Point Landmark Review
Point landmark review is an optional activity. Because many of the point landmarks
contained in the Census Bureau’s MAF/TIGER System originate from the Geographic
Names Information System (GNIS), the official vehicle for names use by the Federal
Government, permitted updates are very limited.
Each point landmark update must have the required attributes and corresponding
change type populated. In the POINTID field, preserve the existing POINTID for the
feature.
New Point Landmark
FULLNAME
CHNG_TYPE
MTFCC
X
X(‘E’)
X
Delete Point Landmark
Change Name
X
POINTID
X(‘D’)
X
X(‘G’)
X
Note: X = Required Field
Appendix A3: Point Landmark Updates Permitted, lists the feature updates the Census
Bureau will accept.
2.7
2010 Linear Feature Extension Review
All block boundary suggestions are contingent upon the lines intersecting to form a
closed polygon at the time the Census Bureau creates tabulation blocks. As a result, all
block boundary suggestions, when combined with other features and planned holds,
must form a closed polygon.
For Census 2010, BBSP participants could place a “must-hold” on an existing feature
that did not form a closed a polygon. By adding a feature extension to close the
polygon, they then created a new block. The 2010 feature extensions are included in
the 2020 BBSP files for review and update.
You are not required to review the 2010 feature extensions. However, please be aware
that if you would like a 2010 feature extension held as 2020 block boundary, you must
take an action on the feature extension.
The 2010 feature extensions can be identified by selecting all edges with attributes of
BBSPFLG = 1 and an MTFCC = P0001.
View Table of Contents
15 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
If you choose to review the 2010 feature extensions, you may:
•
Hold the 2010 feature extension for 2020. The feature from which the extension
originates should also be flagged as a must-hold block boundary, along with the
extension, in order to form a closed polygon. If you determine that the 2010 feature
extension should be held again in 2020, assign the attribute BBSP_2020 with a
value of 1 and a CHNG_TYPE = CA.
•
Delete the 2010 feature extension. The 2010 feature extensions marked for
deletion by participants will help the Census Bureau remove features from the
MAF/TIGER System that no longer serve a current data tabulation purpose. If you
determine that the 2010 feature extension should not be held as a feature
extension, flag the extension with a CHNG_TYPE = DL and leave the attribute
BBSP_2020 blank.
•
Ignore the 2010 feature extension. Be aware that 2010 feature extensions and the
features with which they are associated may not be held as 2020 tabulation block
boundaries. If you take no action on a 2010 feature extension, the Census Bureau
will determine whether to hold the extension and the feature associated with it as a
2020 block boundary.
All updates should be saved in the linear feature update layer.
For complete instructions on flagging linear features, refer to Section 2.9 - Block
Boundary Suggestion Flagging (Must Hold and Do Not Hold).
View Table of Contents
16 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2.8
Block Size Review (New for 2020)
To facilitate your BBSP work, the Census Bureau assigned the 2020 planned tabulation
blocks a block size. The block size indicator is based on a range of the number of
housing units in the block. It is important to note that although discrete numbers have
been established in order to assign each block a size value, the actual number of
housing units in a block is approximate. Blocks with letters “A” through “H” represent
potentially large blocks, blocks with a letter “I” represent medium-sized blocks, and
blocks with the letter “Z” may contain no housing units.
Factors considered when establishing the block sizes were the criteria for blocks
groups, with a minimum housing unit count threshold of 240 and a maximum of 1200,
and the census tract criteria, with a minimum housing unit count of 480, optimum count
of 1,600, and a maximum of 3,200.
The table below lists the block size categories. Discrete number ranges were
established for the purposes of assigning a block size category to each block. Again,
the actual number of housing units in a block is approximate.
A
Approximate Number
Housing Units
Greater than 2000 housing units
B
1,600-1,999
C
1,200-1,599
D
1,000-1,199
E
700-999
F
480-699
G
400-479
H
240-399
Size
I
Z
1-239
Potential “0” housing unit block
Factors to consider when reviewing block size are the block boundaries necessary for
the 2020 Participant Statistical Areas Program. For example, you may wish to review
planned blocks in the “A” and “B” size categories because they are near or exceed the
optimum 2020 census tract housing unit count. You may also choose to review blocks
in the C through H categories to suggest block boundaries, as appropriate, for the
delineation of the 2020 block groups.
The block size indicator is found in the BLKSZIND field of the
gups15_2014_block_ shapefile.
View Table of Contents
17 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
2.9
Block Boundary Suggestion Flagging (Must Hold and Do Not Hold)
The Census Bureau has identified features planned as 2020 tabulation block
boundaries, as reflected in the provided BBSP data files. You can refer to Section 1,
Planned 2020 Tabulation Block Boundaries, for the complete feature list. The planned
tabulation block boundaries may change if the criteria change, or if a feature’s attributes
are updated through other Census programs.
The Census Bureau has also identified features that are ineligible as 2020 block
boundaries.
There are features with no block boundary status assigned. You are not required to
assign a BBSP flag (must hold or do not hold) to every feature, including street
features, in the file.
Assigning a Must Hold Flag:
You may assign a must hold flag to features to suggest them as 2020 tabulation block
boundaries. Candidates for assigning a must hold block boundary suggestion flag are:
•
•
•
Newly added features
Features that are not currently planned as block boundaries (no status
assigned)
Features that are already planned as 2020 block boundaries but you want held
should their status change
You may wish to assign a must hold flag to features that are planned 2020 block
boundaries. If the block definition criteria change between the time Phase 1 BBSP
occurs and when the Census Bureau creates 2020 census tabulation blocks, assigning
a must hold to a planned block boundary feature will increase the likelihood that the
feature will become a 2020 block boundary.
Be aware that assigning a must hold flag to a feature that is ineligible to be a block
boundary does not ensure that the Census Bureau will honor your request but we will
reevaluate the feature’s status based on your suggestion.
All must hold block boundary suggestions are contingent upon the lines intersecting to
form a closed polygon at the time the Census Bureau creates the 2020 tabulation
blocks.
In order to assign a Must Hold Flag, participants must edit the linear feature update
layer.
The linear feature update layer contains three BBSP attributes: The first attribute field
(BBSPFLG) indicates previously identified “Must Holds” and “Do Not Holds” from the
2010 Census. A second attribute field (CBBFLG) identifies all currently planned 2020
Census block boundary lines and ineligible lines. A third attribute field (BBSP_2020) is
designed to capture participant suggested 2020 Census block boundaries.
View Table of Contents
18 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Block boundary suggestions are made by assigning a value of “1” for Must Hold or “2”
for Do Not Hold to the BBSP_2020 field of the lines for which you want to make a
suggestion. These lines must be included along with any added or deleted lines in the
returned changed lines shapefile.
Add New 2020 Feature Extensions
If you wish to hold a feature as a 2020 block boundary but the feature does not form a
closed polygon, you may add a feature extension to close the polygon. Feature
extensions must meet the following criteria:
•
•
•
•
Extensions, combined with other features and planned holds, must form a
closed polygon
Extensions must be no longer than 300 feet (if an extension needs to be longer
than 300 feet, participants must provide justification in the JUSTIFY field of the
attribute table
Extensions must be a straight line originating from the end of a road feature
Extensions must terminate on a non-road feature, with the exception of
highways (i.e., extensions may terminate on highways)
Digitize new 2020 feature extensions in the linear feature update layer and code each
feature with a CHNG_TYPE = AL and BBSP_2020 = 1.
Assigning a Do Not Hold Flag:
You may assign “do not hold” flags to features that that you do not want to become
2020 tabulation block boundaries. Potential candidates for assigning a “do not hold”
block boundary suggestion flag may include:
•
•
•
Private roads, trails, and unimproved roads
Hydrographic features with no area, shown as a single-line feature, such as a
stream or creek.
Any feature creating unnecessary blocks, such as highway ramps, traffic circles
shown as open circles or “lollipops” in the Census geospatial files, and similar
features.
Be aware that assignment of a “do-not-hold” flag to a feature that is a 2020 planned
block boundary does not ensure that the Census Bureau will honor your request.
In order to assign a Do Not Hold Flag, participants must edit the ‘edges’ shapefile (e.g.,
PVS_2015_edges_ssccc.shp).
The ‘edges’ shapefile contains three BBSP attributes: The first attribute field
(BBSPFLG) indicates previously identified “Must Holds” and “Do Not Holds” from the
2010 Census. A second attribute field (CBBFLG) identifies all currently planned 2020
Census block boundary lines and ineligible lines. A third attribute field (BBSP_2020) is
designed to capture participant suggested 2020 Census block boundaries.
View Table of Contents
19 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Block boundary suggestions are made by assigning a value of “1” for Must Hold or “2”
for Do Not Hold to the BBSP_2020 field of the lines for which you want to make a
suggestion. These lines must be included along with any added or deleted lines in the
returned changed lines shapefile.
BBSP Legal Conditional Values
BBSPFLG=1
2010 Census Must Hold
BBSPFLG=2
2010 Census Do not Hold
BBSP_2020 = 1
2020 Must-Hold Block Boundary
BBSP_2020 = 2
2020 Do Not Hold Block Boundary
CBBFLG = 4
2020 Planned Block Boundary
CBBFLG = 9
2020 Ineligible Block Boundary
Block Boundary Criteria
•
All participant-provided 2020 Census “Holds” (BBSP_2020 = 1 in the ‘edges’
file), combined with existing features and other planned block boundaries, must
form closed polygons.
•
2020 Census planned tabulation block boundaries (CBBFLG = 4 in the ‘edges’
file), are an indication of what we would plan to use as a 2020 Census tabulation
block boundary if they were defined today. The planned tabulation block
boundaries may change if the criteria changes, or if the attributes are updated
through other Census programs.
•
Participant provided 2020 Census “Do Not Holds” (BBSP_2020 = 2 in the
‘edges’ file) will not be accepted if the line they are placed on needs to be held
for other purposes. For example, if a “Do Not Hold” were placed on an
incorporated place boundary, the “Do Not Hold” would not be accepted.
•
Whenever possible, participants are to use Census Bureau provided lines
(edges) to designate “Holds.” Features in your files may appear in a spatially
different location from the same features in the Census file.
2.10 Block Area Grouping Delineation (Updated for 2020)
During the 2020 Census tabulation block creation, the Census Bureau will automatically
group islands to form a single tabulation block if they have no road features and the
islands fall within a 5 kilometer radius.
You may also group specific islands to create a single 2020 Census tabulation block,
called a Block Area Grouping (BAG). The criteria for creating a Block Area Grouping
are:
•
•
BAG must consist of two or more islands.
BAG perimeter must be entirely over water.
View Table of Contents
20 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
•
•
BAGs cannot overlap.
BAGs cannot cross the boundary of other tabulation geographies, such as
county or incorporated place boundaries.
Grouping selected islands to create a unique block identification is done by delineating
a polygon around the selected islands. When creating a BAG, digitize the polygon
around the set of desired islands making sure not to cross any land areas or an existing
BAG perimeter, but you can connect a new BAG to the side of an existing one. If it
crosses any other tabulations areas, it will be split along that line as well.
The BAG layer you create should be a simple polygon shapefile named
BBSP__BAG_changes.* where the is the two digit FIPS state
code and the three digit county code. The shapefile should have 2 text fields; BAGCE
(length of 3), and MTFCC (length of 5). When creating your BAGs provide each with a
number in the BAGCE field. Start with 001 and increment by 1 for each BAG created.
The MTFCC should always be G5035.
Block Area Grouping delineation is optional, and probably most appropriate for states
with hydrographic areas that contain a number of islands.
Note: Because the State of Washington was the only state to delineate Block Area
Groupings for Census 2010, this is the only state with existing BAGs for review. All
other states may delineate new Block Area Groupings for Census 2020.
2.11 Block Boundary Review
You should review your block boundary suggestions before submitting an updated
county to the Census Bureau (if you are the designated State redistricting Liaison) or to
the State (if you have been delegated by the state to perform work).
We recommend that you systematically review all must hold and do not hold features
prior to submitting a county return.
2.12 Validation Check
The Census Bureau recommends that you check for any non-closed polygons prior to
submitting a county return. A non-closed polygon is a polygon where you have placed
one or more “must-hold” block boundary flags on features but the features, when
combined with the planned block boundaries, do not “close” to form a census block.
The Census Bureau cannot accept a suggested block boundary if non-closed polygons
are present.
2.13 Work Delegated
View Table of Contents
21 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
The Census Bureau works with the State Redistricting Data Program nonpartisan
Liaison who is designated by the governor and legislative leadership of the state. To
maintain this nonpartisan relationship, the Census Bureau only accepts completed work
from the designated State Restricting Data Program Liaison.
YES: Work was performed by someone other than the State Redistricting Data
Program (RDP) Liaison.
Any work performed on behalf of the State Redistricting Data Program Liaison, such as
by a county or a contractor, must be submitted to the State for review and approval.
The State RDP Liaison will submit the work to the Census Bureau if they approve the
work. If the State RDP Liaison determines that BBSP work completed by a designee
requires changes or additional work, it is the State’s responsibility to decide whether to
make the changes at the state level or return the project to the original delineator for
further updates.
NO: State RDP LIAISON performed the work.
The State RDP Liaison submits completed, county-level files on flow basis to the
Census Bureau through the Bureau’s Secure Web Incoming Module (SWIM). Do not
hold files to submit all at once. Submit data submission files as you complete them,
especially at the beginning of the update process, so that the Census Bureau can
provide feedback if there are errors, omissions, or other concerns.
View Table of Contents
22 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
3 Create Data Submission Files
The Census Bureau requires that the returned shapefiles have specific attributes and
characteristics in order for us to accept them as legitimate submissions. Below is a list
of shapefile types and specifications that should be included in your BBSP submission,
depending on the type of updates made.
All returned shapefiles and whole entity shapefiles, as well as any supporting
documentation, should be placed in a .zip file named bbsp__return.zip
prior to submitting the return to the Census Bureau.
3.1
Linear Feature Updates and Block Boundary Suggestions
Once all updates are complete in the linear feature Update layer, including block
boundary suggestions, select by attribute to select all lines that have a value in the
CHNG_TYPE field. Export the selected set of edges as the returned lines shapefile
called ‘bbsp__LN_Changes’ where the is the state and county FIPS
code.
Verify that all block boundary suggestions and feature extensions are attributed with the
correct attributes (i.e., BBSP_2020 field populated). Verity that any added lines are
attributed with the appropriate MTFCC code (e.g., P0001 for an invisible legal/statistical
boundary) and the appropriate CHNG_TYPE. Once this is completed, the
‘bbsp__LN_Changes’ shapefile is ready for submission.
The submission file should include:
All Linear Features (edges) where BBSP_2020 field is populated with:
1 (Must Hold) or
2 (Do Not Hold)
and
All Linear Features (edges) where CHNG_TYPE Field is populated with:
AL (Add Line) or
DL (Delete Line) or
CA (Change Attribute: for Name, MTFCC, and/or Address Range)
File name: bbsp__LN_changes.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
3.2
Area Landmarks and Area Hydrology Updates
If any updates were completed for area landmarks or area hydrology, select by attribute
to select records that have a value in the CHNG_TYPE field. Export the selected set of
records as the returned shapefile called ‘bbsp__alndk’ where the is the
state and county FIPS code.
View Table of Contents
23 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
The file should include all Area Landmark polygons where CHNG_TYPE Field is
populated with:
B (Boundary Correction) or
D (Delete) or
E (New Landmark) or
G (Change Name or MTFCC)
File name: bbsp_alndk_changes.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
3.3
Legal Boundary Updates
If reporting legal boundary changes and/or corrections, the Census Bureau requires
that participants submit a change polygon file and a whole entity file. The whole entity
file should show the complete legal boundary of the entity after updates. The total
number of layers submitted depends on what types of changes are reported.
If you made legal boundary updates, then include the following files in your submission,
as applicable to the type of legal boundary update made:
County Subdivision Transaction Polygon Shapefile (includes MCDs)
The file should include all change polygons where CHNG_TYPE Field is populated
with:
A (Annexation) or
D (Deannexation) or
B (Boundary Correction)
File Names:
bbsp__changes_cousub.shp
bbsp__wholeentity_cousub.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
Incorporated Place Transaction Polygon Shapefile
The file should include change polygons where CHNG_TYPE Field is populated with:
A (Annexation) or
D (Deannexation) or
B (Boundary Correction)
File Names:
bbsp__changes_incplace.shp
bbsp__wholeentity_ incplace.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
View Table of Contents
24 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Consolidated City Transaction Polygon Shapefile
Includes change polygons where CHNG_TYPE Field is populated with:
A (Annexation) or
D (Deannexation) or
B (Boundary Correction)
File Names:
bbsp__changes_ concity.shp
bbsp__wholeentity_ concity.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
3.4
Point Feature Updates
If any updates were completed for point landmarks, select by attribute to select records
that have a value in the CHNG_TYPE field. Export the selected set of records as the
returned shapefile called ‘bbsp__plndk’ where the is the state and
county FIPS code.
The file should include All Point Landmarks where CHNG_TYPE Field is populated with:
D (Delete) or
E (New Point Landmark) or
G (Change Attribute)
File name: bbsp_plndk_changes.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state.
3.5
Block Area Grouping Updates
If you made updates to the block area grouping layer, then include all polygons where
MTFCC = G5035 and CHNG_TYPE Field is populated with:
B (Boundary Correction) or
D (Delete) or
E (New Block Area Grouping)
File name: bbsp__bag_changes.shp
Where equals year, = the two digit state FIPS code and the three digit
county code within state
3.6
Create .ZIP File
View Table of Contents
25 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
All returned shapefiles and whole entity shapefiles, as well as any supporting
documentation, should be placed in a .zip file prior to submitting the return to the
Census Bureau.
File Name: bbsp__return.zip
where equals year, and = the two digit state FIPS code and the three
digit county code within state.
View Table of Contents
26 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4 File Submission Through SWIM
The Secure Web Incoming Module (SWIM) is a tool for U.S. Census Bureau partners to
send their geospatial data to a Census Bureau server. For security reasons, we cannot
accept files sent via email or through our former ftp site.
The Census Bureau provides each State Redistricting Data Program Liaison a SWIM
token to establish a personal SWIM account. Once registered, you will no longer need
the token to log into the system. You will use your SWIM account to submit updates for
all phases of the 2020 Redistricting Data Program. If you are a participant for other
Census Bureau geographic programs, you may use your SWIM account to submit files
for these other geographic programs, too.
NOTE: For the Redistricting Data Program, including the Phase 1 Block Boundary
Suggestion Project, the Census Bureau will only accept files submitted by the State
RDP Liaison. If a county, agency, or contractor performs work on behalf of the state,
the files must be sent to the State for review, approval, and submission.
To establish a SWIM account, you must first be provided a registration token by the
Census Bureau, which is a unique, single-use 12-digit number associated to an
individual. Every user must have their own token in order to register. Once the token
has been used to establish your account, it is no longer required to access your
account.
To access the SWIM, enter the following URL in a new browser window:
https://respond.census.gov/swim/.
Follow the directions below for account access and file upload.
View Table of Contents
27 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.1
Login Page
The Login page is the first page you will see:
If you already have a
SWIM account, enter your
Email, Password, then
click Login.
If you do not have a SWIM
account, click Register
Account. You must first
have a SWIM token to
create your account.
Figure 4.1: SWIM Login Screen
4.2
If you already have a SWIM Account:
1. Enter your Email address and Password
2. Click the Login button, which directs you to the Welcome page.
View Table of Contents
28 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.3
If you do not yet have a SWIM Account:
1. Click the Register Account button, which directs you to the Account
Registration page.
2. Enter the 12 digit Registration Token number provided to you by the Census
Bureau.
3. Complete all other fields.
4. Click the Submit button.
Enter the Registration Token number
provided to you by the Census Bureau.
The name you enter as “First Name”
will be the name that appears on the
Welcome Page.
Figure 4.2: SWIM Account Registration Screen
View Table of Contents
29 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.4
Welcome Page
The Welcome page is where you initiate the file upload process. Because the SWIM
tracks files submitted and the submission date, the page appearance will change after
you have successfully uploaded files.
1. To submit a file, click the Start New Upload button.
This is the name you entered in the “First Name” field.
Figure 4.3: SWIM Welcome Screen (no previous files uploaded)
.
If you previously uploaded files, the list of files appears here.
Figure 4.4: SWIM Welcome Screen (files previously uploaded)
View Table of Contents
30 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.5
Geographic Program Page
The Geographic Program Page allows you to select the partnership program for which
you are submitting data.
1. Click on the radio button next to Redistricting Data Program (RDP).
2. Click the Next button.
Click the RDP radio button, then Next button.
Figure 4.5: SWIM Geographic Program Page
4.6
Select a State
After choosing the Redistricting Data Program (RDP), you will be directed to specify the
state for which you are submitting data.
1. From the drop down list, click on your state name.
2. Click on the Next button.
Click on the arrow to choose your state,
then click the Next button.
Figure 4.6: SWIM Select a State Page (for RDP)
View Table of Contents
31 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.7
Select a .ZIP File to Upload
Files for upload must be in a .zip format. You can upload only one .zip file at a time.
For the Redistricting Data Program, the GUPS will automatically create a separate .zip
file for each county.
1. Click on the + Add File button.
2. Navigate to the directory on your computer to choose the .zip file to upload.
3. Complete the Comments box, including pertinent information about data
projection or supporting documentation.
4. Click on the Next button.
Click Add File button, then go to the directory on your computer to
select the file to upload.
The filename appears here after you have selected the file from
your computer directory.
Enter pertinent notes in the Comments box.
When done, click the Next button.
Figure 4.7: Select a .ZIP File to Upload Page
View Table of Contents
32 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
4.8
Thank You Page
The “Thank You” page confirms the receipt of your file submission.
If you do not have any additional files to upload, click on Log Out. The Census Bureau
will acknowledge the receipt of the uploaded file.
If you have additional files to upload, click on Upload Form. This choice returns
you to the Welcome screen.
If you have more files to upload, click the
Upload Form link, which returns you to the
Welcome Screen to start a new upload.
If you’re done uploading files, click the
Log Out link.
Figure 4.8: Thank You Page
View Table of Contents
33 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX A: UPDATES ALLOWED, BY MTFCC
A.1 Area Landmark Updates Permitted
C3023
Island
Y
Can
You
DELETE?
Y
H2030
Lake/Pond
Y
Y
Y
H2040
Reservoir
Y
Y
Y
MTFCC
DESCRIPTION
Can You
ADD?
Can You
MODIFY
ATTRIBUTES?
Y
H2041
Treatment Pond
Y
Y
Y
H2051
Bay/Estuary/Gulf/Sound
Y
Y
Y
H2081
Glacier
Y
Y
Y
K1231
Hospital
Y
Y
Y
K1235
Juvenile Institution
Y
Y
Y
K1236
Y
Y
Y
Y
Y
Y
K2110
Local Jail or Detention Center
Federal Penitentiary, State Prison, or
Prison Farm
Military Installation
Y
Y
Y
K2131
Hospital/Hospice/Urgent Care Facility
Y
Y
Y
K2180
Park
Y
Y
Y
K2181
National Park Service Land
Y
Y
Y
K2182
National Forest or Other Federal Land
Y
Y
Y
K1237
K2183
Tribal Park, Forest, or Recreation Area
Y
Y
Y
K2184
State Park, Forest, or Recreation Area
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
K2185
K2186
K2187
K2188
K2189
K2190
Regional Park, Forest, or Recreation
Area
County Park, Forest, or Recreation
Area
County Subdivision Park, Forest, or
Recreation Area
Incorporated Place Park, Forest, or
Recreation Area
Private Park, Forest, or Recreation
Area
Other Park, Forest, or Recreation Area
(quasi-public, independent park,
commission, etc.)
K2424
Marina
Y
Y
Y
K2457
Airport - Area Representation
Y
Y
Y
K2540
University or College
Y
Y
Y
K2561
Golf Course
Y
Y
Y
K2582
Cemetery
Y
Y
Y
View Table of Contents
34 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
A.2 Linear Feature Updates Permitted
Can
You
ADD?
Y
Can
Can You
You
MODIFY
DELETE? ATTRIBUTES?
Y
Y
MTFCC
DESCRIPTION
C3024
Levee
C3027
Dam
Y
Y
Y
H3010
Stream/River
Y
Y
Y
H3013
Braided Stream
Y
Y
Y
H3020
Canal, Ditch, or Aqueduct
Y
Y
Y
K2432
Pier/Dock
Y
Y
Y
K2459
Runway/Taxiway
Y
Y
Y
L4010
Pipeline
Y
Y
Y
L4020
Power Line
Y
Y
Y
L4040
Conveyor
N
N
N
L4110
Fence Line
Y
Y
Y
L4121
Ridge Line
Y
Y
Y
L4125
Cliff/Escarpment
Y
Y
Y
L4130
Point-to Point Line
Y
Y
Y
L4140
Property/Parcel Line (includes PLSS)
Y
Y
Y
L4165
Ferry Crossing
Y
Y
Y
P0001
Nonvisible Legal/Statistical Boundary
Y
Y
Y
P0002
Perennial Shoreline
Y
Y
Y
P0003
Intermittent Shoreline
Y
Y
Y
P0004
Other non-visible bounding edge (e.g.,
Census water boundary, boundary of areal
feature
Y
Y
Y
R1011
Railroad Feature (Main, Spur, or Yard
Y
Y
Y
R1051
Carline, Streetcar Tract Monorail, Other Mass
Y
Y
Y
R1052
Cog Rail Line, Incline Rail Line, Tram
Y
Y
Y
S1100
Primary Road
Y
Y
Y
S1200
Secondary Road
Y
Y
Y
S1400
Local Neighborhood Road, Rural Road, City
Street
Y
Y
Y
S1500
Vehicular Trail (4WD)
Y
Y
Y
S1630
Ramp
Y
Y
Y
S1640
Service Drive usually along a limited access
highway
Y
Y
Y
S1730
Alley
Y
Y
Y
S1740
Private Road for service vehicles (logging, oil
fields, ranches, etc.)
Y
Y
Y
S1820
Bike Path or Trail
Y
Y
Y
View Table of Contents
35 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
A.3 Point Landmark Updates Permitted
Can
You
ADD?
Can
You
DELETE?
Can You
MODIFY
ATTRIBUTES?
MTFCC
DESCRIPTION
C3022
Mountain Peak or Summit
Y
N
N
C3061
Cul-de-sac
Y
Y
Y
C3062
Traffic Circle
Y
Y
Y
K2451
Airport of Airfield * Modifications or
deletions not allowed because sourced
from GNIS
Y
N
N
View Table of Contents
36 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX B: MTFCC DESCRIPTIONS - COMPLETE LIST
The MAF/TIGER Feature Classification Code (MTFCC) is a 5-digit code assigned by
the Census Bureau to classify and describe geographic objects or features in Census
Bureau MAF/TIGER products. The table below describes each code. A more
comprehensive version of the table can be downloaded at
http://www.census.gov/geo/reference/mtfcc.html
MTFCC
Feature Class
Feature Class Description
C3022
Mountain Peak or Summit
A prominent elevation rising above the surrounding level of the
Earth's surface.
C3023
Island
An area of dry or relatively dry land surrounded by water or low
wetland. [including archipelago, atoll, cay, hammock, hummock, isla,
isle, key, moku and rock]
C3024
Levee
An embankment flanking a stream or other flowing water feature to
prevent overflow.
C3026
Quarry (not water-filled),
Open Pit Mine or Mine
An area from which commercial minerals are or were removed from
the Earth; not including an oilfield or gas field.
C3027
Dam
A barrier built across the course of a stream to impound water and/or
control water flow.
C3061
Cul-de-sac
An expanded paved area at the end of a street used by vehicles for
turning around. For mapping purposes, the U.S. Census Bureau
maps it only as a point feature.
C3062
Traffic Circle
A circular intersection allowing for continuous movement of traffic at
the meeting of roadways.
C3066
Gate
A movable barrier across a road.
C3067
Toll Booth
A structure or barrier where a fee is collected for using a road.
C3070
Tower/Beacon
A manmade structure, higher than its diameter, generally used for
observation, storage, or electronic transmission.
C3071
Lookout Tower
A manmade structure, higher than its diameter, used for observation.
C3072
Transmission Tower
A manmade structure, higher than its diameter, used for electronic
including cell, radio and TV transmission.
C3073
Water Tower
A manmade structure, higher than its diameter, used for water
storage.
C3074
Lighthouse Beacon
A manmade structure, higher than its diameter, used for
transmission of light and possibly sound generally to aid in
navigation.
C3075
Tank/Tank Farm
One or more manmade structures, each higher than its diameter,
used for liquid (other than water) or gas storage or for distribution
activities.
C3076
Windmill Farm
One or more manmade structures used to generate power from the
wind.
C3077
Solar Farm
One or more manmade structures used to generate power from the
sun.
C3078
Monument or Memorial
A manmade structure to educate, commemorate, or memorialize an
event, person, or feature.
View Table of Contents
37 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
C3079
Boundary Monument Point A material object placed on or near a boundary line to preserve and
identify the location of the boundary line on the ground.
C3080
Survey Control Point
A point on the ground whose position (horizontal or vertical) is known
and can be used as a base for additional survey work.
C3081
Locality Point
A point that identifies the location and name of an unbounded locality
(e.g., crossroad, community, populated place or locale).
C3085
Alaska Native Village
Official Point
A point that serves as the core of an Alaska Native village and is
used in defining Alaska Native village statistical areas.
C3088
Landfill
A disposal facility at which solid waste is placed on or in the land.
G2100 American Indian Area
A legally defined state- or federally recognized reservation and/or
off-reservation trust land (excludes statistical American Indian
areas).
G2101 American Indian Area
(Reservation Only)
American Indian Area (Reservation Only)
G2102 American Indian Area (Off- American Indian Area (Off-Reservation Trust Land Only)
Reservation Trust Land
Only)
G2120 Hawaiian Home Land
A legal area held in trust for the benefit of Native Hawaiians.
G2130 Alaska Native Village
Statistical Area
A statistical geographic entity that represents the residences,
permanent and/or seasonal, for Alaska Natives who are members of
or receiving governmental services from the defining legal Alaska
Native Village corporation.
G2140 Oklahoma Tribal Statistical A statistical entity identified and delineated by the Census Bureau in
Area
consultation with federally recognized American Indian tribes that
have no current reservation, but had a former reservation in
Oklahoma.
G2150 State-designated Tribal
Statistical Area
A statistical geographic entity identified and delineated for the
Census Bureau by a state-appointed liaison for a state-recognized
American Indian tribe that does not currently have a reservation
and/or lands in trust.
G2160 Tribal Designated
Statistical Area
A statistical geographic entity identified and delineated for the
Census Bureau by a federally recognized American Indian tribe that
does not currently have a reservation and/or off-reservation trust
land.
G2170 American Indian Joint Use
Area
An area administered jointly and/or claimed by two or more
American Indian tribes.
G2200 Alaska Native Regional
Corporation
Corporate entities established to conduct both business and
nonprofit affairs of Alaska Natives pursuant to the Alaska Native
Claims Settlement Act of 1972 (Public Law 92-203). There are
twelve geographically defined ANRCs and they are all within and
cover most of the State of Alaska (the Annette Island Reserve-an
American Indian reservation-is excluded from any ANRC). The
boundaries of ANRCs have been legally established.
G2300 Tribal Subdivision
Administrative subdivisions of federally recognized American Indian
reservations, off-reservation trust lands, or Oklahoma tribal statistical
areas (OTSAs). These entities are internal units of self-government
or administration that serve social, cultural, and/or economic
purposes for the American Indians on the reservations, offreservation trust lands, or OTSAs.
G2400 Tribal Census Tract
A relatively small and permanent statistical subdivision of a federally
recognized American Indian reservation and/or off-reservation trust
View Table of Contents
38 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
land, delineated by American Indian tribal participants or the Census
Bureau for the purpose of presenting demographic data.
MTFCC
Feature Class
Feature Class Description
G2410 Tribal Block Group
A cluster of census blocks within a single tribal census tract
delineated by American Indian tribal participants or the Census
Bureau for the purpose of presenting demographic data
G3100 Combined Statistical Area
A grouping of adjacent metropolitan and/or micropolitan statistical
areas that have a degree of economic and social integration, as
measured by commuting.
G3110 Metropolitan and
Micropolitan Statistical
Area
An area containing a substantial population nucleus together with
adjacent communities having a high degree of economic and social
integration with that core, as measured by commuting. Defined using
whole counties and equivalents.
G3120 Metropolitan Division
A county or grouping of counties that is a subdivision of a
Metropolitan Statistical Area containing an urbanized area with a
population of 2.5 million or more.
G3200 Combined New England
City and Town Area
A grouping of adjacent New England city and town areas that have a
degree of economic and social integration, as measured by
commuting.
G3210 New England City and
Town Metropolitan and
Micropolitan Statistical
Area
An area containing a substantial population nucleus together with
adjacent communities having a high degree of economic and social
integration with that core, as measured by commuting. Defined using
Minor Civil Divisions (MCDs) in New England.
G3220 New England City and
Town Division
A grouping of cities and towns in New England that is a subdivision
of a New England City and Town Area containing an urbanized area
with a population of 2.5 million or more.
G3500 Urban Area
Densely settled territory that contains at least 2,500 people. The
subtypes of this feature are Urbanized Area (UA), which consists of
50,000 + people and Urban Cluster, which ranges between 2,500
and 49,999 people.
G4000 State or Equivalent Feature The primary governmental divisions of the United States. The District
of Columbia is treated as a statistical equivalent of a state for census
purposes, as is Puerto Rico.
G4020 County or Equivalent
Feature
The primary division of a state or state equivalent area. The primary
divisions of 48 states are termed County, but other terms are used
such as Borough in Alaska, Parish in Louisiana, and Municipio in
Puerto Rico. This feature includes independent cities, which are
incorporated places that are not part of any county.
G4040 County Subdivision
The primary divisions of counties and equivalent features for the
reporting of Census Bureau data. The subtypes of this feature are
Minor Civil Division, Census County Division/Census Subarea, and
Unorganized Territory. This feature includes independent places,
which are incorporated places that are not part of any county
subdivision.
G4050 Estates
Estates are subdivisions of the three major islands in the United
States Virgin Islands (USVI).
G4060 Subbarrio (Subminor Civil
Division)
Legally defined divisions (subbarrios) of minor civil divisions (barriospueblo and barrios) in Puerto Rico.
G4110 Incorporated Place
A legal entity incorporated under state law to provide generalpurpose governmental services to a concentration of population.
Incorporated places are generally designated as a city, borough,
municipality, town, village, or, in a few instances, have no legal
description.
View Table of Contents
39 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
G4120 Consolidated City
View Table of Contents
An incorporated place that has merged governmentally with a county
or minor civil division, but one or more of the incorporated places
continues to function within the consolidation. It is a place that
contains additional separately incorporated places.
40 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
G4210 Census Designated Place
A statistical area defined for a named concentration of population
and the statistical counterpart of an incorporated place
G4300 Economic Census Place
The lowest level of geographic area for presentation of some types
of Economic Census data. It includes incorporated places,
consolidated cities, census designated places (CDPs), minor civil
divisions (MCDs) in selected states, and balances of MCDs or
counties. An incorporated place, CDP, MCD, or balance of MCD
qualifies as an economic census place if it contains 5,000 or more
residents, or 5,000 or more jobs, according to the most current data
available.
G5020 Census Tract
Relatively permanent statistical subdivisions of a County or
equivalent feature delineated by local participants as part of the
Census Bureau's Participant Statistical Areas Program.
G5030 Block Group
A cluster of census blocks having the same first digit of their fourdigit identifying numbers within a Census Tract. For example, block
group 3 (BG 3) within a Census Tract includes all blocks numbered
from 3000 to 3999.
G5040 Tabulation Block
The lowest-order census defined statistical area. It is an area, such
as a city block, bounded primarily by physical features but
sometimes by invisible city or property boundaries. A tabulation
block boundary does not cross the boundary of any other geographic
area for which the Census Bureau tabulates data. The subtypes of
this feature are Count Question Resolution (CQR), current, and
census.
G5200 Congressional District
The 435 areas from which people are elected to the U.S. House of
Representatives. Additional equivalent features exist for state
equivalents with nonvoting delegates or no representative. The
subtypes of this feature are 106th, 107th, 108th, 109th, and 111th
Congressional Districts, plus subsequent Congresses.
G5210 State Legislative District
(Upper Chamber
Areas established by a state or equivalent government from which
members are elected to the upper or unicameral chamber of a state
governing body. The upper chamber is the senate in a bicameral
legislature, and the unicameral case is a single house legislature
(Nebraska).
G5220 State Legislative District
(Lower Chamber)
Areas established by a state or equivalent government from which
members are elected to the lower chamber of a state governing
body. The lower chamber is the House of Representatives in a
bicameral legislature.
G5240 Voting District
The generic name for the geographic features, such as precincts,
wards, and election districts, established by state, local, and tribal
governments for the purpose of conducting elections.
G5400 Elementary School District
A geographic area within which officials provide public elementary
grade-level educational services for residents.
G5410 Secondary School District
A geographic area within which officials provide public secondary
grade-level educational services for residents.
G5420 Unified School District
A geographic area within which officials provide public educational
services for all grade levels for residents.
G6100 Public-Use Microdata Area A decennial census area with a population of at least 100,000 or
more persons for which the Census Bureau provides selected
extracts of household-level data that are screened to protect
confidentiality.
G6300 Traffic Analysis District
View Table of Contents
An area delineated by Metropolitan Planning Organizations (MPOs)
and state Departments of Transportation (DOTs) for tabulating
journey-to-work and place-of-work data. A Traffic Analysis District
41 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
(TAD) consists of one or more Traffic Analysis Zones (TAZs).
View Table of Contents
42 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
G6320 Traffic Analysis Zone
An area delineated by Metropolitan Planning Organizations (MPOs)
and state Departments of Transportation (DOTs) for tabulating
journey-to-work and place-of-work data.
G6330 Urban Growth Area
An area defined under state authority to manage urbanization that
the U.S. Census Bureau includes in the MAF/TIGER® Database in
agreement with the state.
G6340 ZIP Code Tabulation Area
(Three-Digit)
An approximate statistical-area representation of a U.S. Postal
Service (USPS) 3-digit ZIP Code service area.
G6350 Zip Code Tabulation Area
(Five-Digit)
An approximate statistical-area representation of a U.S. Postal
Service (USPS) 5-digit ZIP Code service area.
G6400 Commercial Region
For the purpose of presenting economic statistical data, municipios
in Puerto Rico are grouped into commercial regions.
H1100
Connector
A known, but nonspecific, hydrographic connection between two
nonadjacent water features.
H2025
Swamp/Marsh
A poorly drained wetland, fresh or saltwater, wooded or grassy,
possibly covered with open water. [includes bog, cienega, marais
and pocosin]
H2030
Lake/Pond
A standing body of water that is surrounded by land.
H2040
Reservoir
An artificially impounded body of water.
H2041
Treatment Pond
An artificial body of water built to treat fouled water.
H2051
Bay/Estuary/Gulf/Sound
A body of water partly surrounded by land. [includes arm, bight, cove
and inlet]
H2053
Ocean/Sea
The great body of salt water that covers much of the earth.
H2060
Gravel Pit/Quarry filled with A body of water in a place or area from which commercial minerals
water
were removed from the Earth.
H2081
Glacier
A body of ice moving outward and down slope from an area of
accumulation; an area of relatively permanent snow or ice on the top
or side of a mountain or mountainous area. [includes ice field and ice
patch]
H3010
Stream/River
A natural flowing waterway. [includes anabranch, awawa, branch,
brook, creek, distributary, fork, kill, pup, rio, and run]
H3013
Braided Stream
A natural flowing waterway with an intricate network of interlacing
channels.
H3020
Canal, Ditch or Aqueduct
An artificial waterway constructed to transport water, to irrigate or
drain land, to connect two or more bodies of water, or to serve as a
waterway for watercraft. [includes lateral]
K1121
Apartment Building or
Complex
A building or group of buildings that contain multiple living quarters
generally for which rent is paid.
K1223
Trailer Court or Mobile
Home Park
An area in which parking space for house trailers is rented, usually
providing utilities and services.
K1225
Crew-of-Vessel Location
A point or area in which the population of military or merchant marine
vessels at sea are assigned, usually being at or near the home port
pier.
K1226
Housing Facility/Dormitory
for Workers
A structure providing housing for a number of persons employed as
semi-permanent or seasonal laborers.
K1227
Hotel, Motel, Resort, Spa,
Hostel, YMCA, or YWCA
A structure providing transient lodging or living quarters, generally for
some payment.
View Table of Contents
43 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
K1228
Campground
An area used for setting up mobile temporary living quarters
(camp) or holding a camp meeting, sometimes providing utilities
and other amenities.
K1229
Shelter or Mission
A structure providing low-cost or free living quarters established
by a welfare or educational organization for the needy people of
a district.
K1231
Hospital/Hospice/Urgent Care
Facility
One or more structures where the sick or injured may receive
medical or surgical attention. [including infirmary]
K1233
Nursing Home, Retirement
Home, or Home for the Aged
A structure to house and provide care for the elderly.
K1234
County Home or Poor Farm
One or more structures administered by a local government that
serve as living quarters for the indigent.
K1235
Juvenile Institution
A facility (correctional or non-correctional) where groups of
juveniles reside; this includes training schools, detention centers,
residential treatment centers and orphanages.
K1236
Local Jail or Detention Center
One or more structures that serve as a place for the confinement
of adult persons in lawful detention, administered by a local
(county, municipal, etc.) government.
K1237
Federal Penitentiary, State
Prison, or Prison Farm
An institution that serves as a place for the confinement of adult
persons in lawful detention, administered by the federal
government or a state government.
K1238
Other Correctional Institution
One or more structures that serve as a place for the confinement
of adult persons in lawful detention, not elsewhere classified or
administered by a government of unknown jurisdiction.
K1239
Convent, Monastery, Rectory,
Other Religious Group
Quarters
One or more structures intended for use as a residence for those
having a religious vocation.
K1241
Sorority, Fraternity, or College One or more structures associated with a social or educational
Dormitory
organization that serve as living quarters for college students.
K2100
Governmental
A place where employees are employed in federal, state, local,
or tribal government.
K2110
Military Installation
An area owned and/or occupied by the Department of Defense
for use by a branch of the armed forces (such as the Army, Navy,
Air Force, Marines, or Coast Guard), or a state owned area for
the use of the National Guard.
K2165
Government Center
A place used by members of government (either federal, state,
local, or tribal) for administration and public business.
K2167
Convention Center
An exhibition hall or conference center with enough open space
to host public and private business and social events.
K2180
Park
Parkland defined and administered by federal, state, and local
governments.
K2181
National Park Service Land
Area—National parks, National Monuments, and so forth—under
the jurisdiction of the National Park Service.
K2182
National Forest or Other
Federal Land
Land under the management and jurisdiction of the federal
government, specifically including areas designated as National
Forest, and excluding areas under the jurisdiction of the National
Park Service.
K2183
Tribal Park, Forest, or
Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of an
American Indian tribe.
View Table of Contents
44 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
K2184
State Park, Forest, or
Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of a
state government.
K2185
Regional Park, Forest, or
Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of a
regional government.
K2186
County Park, Forest, or
Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of a
county government.
K2187
County Subdivision Park,
Forest, or Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of a
minor civil division (town/township) government.
K2188
Incorporated Place Park,
Forest, or Recreation Area
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of a
municipal government.
K2189
Private Park, Forest, or
Recreation Area
A privately owned place or area set aside for recreation or
preservation of a cultural or natural resource.
K2190
Other Park, Forest, or
Recreation Area (quasi-public,
independent park,
commission, etc.)
A place or area set aside for recreation or preservation of a
cultural or natural resource and under the administration of some
other type of government or agency such as an independent park
authority or commission.
K2191
Post Office
An official facility of the U.S. Postal Service used for processing
and distributing mail and other postal material.
K2193
Fire Department
Fire Department.
K2194
Police Station
Police Station.
K2195
Library
Library.
K2196
City/Town Hall
City/Town Hall.
K2300
Commercial Workplace
A place of employment for wholesale, retail, or other trade.
K2361
Shopping Center or Major
Retail Center
A group of retail establishments within a planned subdivision
sharing a common parking area.
K2362
Industrial Building or Industrial One or more manufacturing establishments within an area zoned
Park
for fabrication, construction, or other similar trades.
K2363
Office Building or Office Park
K2364
Farm/Vineyard/Winery/Orchard An agricultural establishment where crops are grown and/or
animals are raised, usually for food.
K2366
Other Employment Center
A place of employment not elsewhere classified or of unknown
type.
K2400
Transportation Terminal
A facility where one or more modes of transportation can be
accessed by people or for the shipment of goods; examples of
such a facility include marine terminal, bus station, train station,
airport and truck warehouse.
K2424
Marina
A place where privately owned, light-craft are moored.
K2432
Pier/Dock
A platform built out from the shore into the water and supported
by piles. This platform may provide access to ships and boats, or
it may be used for recreational purposes.
K2451
Airport or Airfield
A manmade facility maintained for the use of aircraft. [including
airstrip, landing field and landing strip]
View Table of Contents
One or more structures housing employees performing business,
clerical, or professional services.
45 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
View Table of Contents
46 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
K2452
Train Station, Trolley or
Mass Transit Rail Station
A place where travelers can board and exit rail transit lines, including
associated ticketing, freight, and other commercial offices.
K2453
Bus Terminal
A place where travelers can board and exit mass motor vehicle
transit, including associated ticketing, freight, and other commercial
offices.
K2454
Marine Terminal
A place where travelers can board and exit water transit or where
cargo is handled, including associated ticketing, freight, and other
commercial offices.
K2455
Seaplane Anchorage
A place where an airplane equipped with floats for landing on or
taking off from a body of water can debark and load.
K2456
Airport—Intermodal
Transportation
Hub/Terminal
A major air transportation facility where travelers can board and exit
airplanes and connect with other (i.e. non-air) modes of
transportation.
K2457
Airport—Statistical
Representation
The area of an airport adjusted to include whole 2000 census blocks
used for the delineation of urban areas.
K2458
Park and Ride
Facility/Parking Lot
A place where motorists can park their cars and transfer to other
modes of transportation.
K2459
Runway/Taxiway
A fairly level and usually paved expanse used by airplanes for taking
off and landing at an airport.
K2460
Helicopter Landing Pad
A fairly level and usually paved expanse used by helicopters for
taking off and landing.
K2540
University or College
A building or group of buildings used as an institution for postsecondary study, teaching, and learning. [including seminary]
K2545
Museum, Visitor Center,
Cultural Center, or Tourist
Attraction
An attraction of historical, cultural, educational or other interest that
provides information or displays artifacts.
K2561
Golf Course
A place designed for playing golf.
K2564
Amusement Center
A facility that offers entertainment, performances or sporting events.
Examples include arena, auditorium, theater, stadium, coliseum,
race course, theme park, fairgrounds and shooting range.
K2582
Cemetery
A place or area for burying the dead. [including burying ground and
memorial garden]
K2586
Zoo
A facility in which terrestrial and/or marine animals are confined
within enclosures and displayed to the public for educational,
preservation, and research purposes.
K3544
Place of Worship
A sanctified place or structure where people gather for religious
worship; examples include church, synagogue, temple, and mosque.
L4010
Pipeline
A long tubular conduit or series of pipes, often underground, with
pumps and valves for flow control, used to transport fluid (e.g., crude
oil, natural gas), especially over great distances.
L4020
Powerline
One or more wires, often on elevated towers, used for conducting
high-voltage electric power.
L4031
Aerial Tramway/Ski Lift
A conveyance that transports passengers or freight in carriers
suspended from cables and supported by a series of towers.
L4040
Conveyor
A mechanical apparatus that uses a moving belt to transport items
from one place to another.
L4110
Fence Line
A man-made barrier enclosing or bordering a field, yard, etc., usually
made of posts and wire or wood, used to prevent entrance, to
confine, or to mark a boundary.
View Table of Contents
47 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
L4121
Ridge Line
The line of highest elevation along a ridge.
L4125
Cliff/Escarpment
A very steep or vertical slope. [including bluff, crag, head, headland,
nose, palisades, precipice, promontory, rim and rimrock]
L4130
Point-to-Point Line
A line defined as beginning at one location point and ending at
another, both of which are in sight.
L4140
Property/Parcel Line
(Including PLSS)
This feature class may denote a nonvisible boundary of either public
or private lands (e.g., a park boundary) or it may denote a Public
Land Survey System or equivalent survey line.
L4150
Coastline
The line that separates either land or Inland water from Coastal,
Territorial or Great Lakes water. Where land directly borders Coastal,
Territorial or Great Lakes water, the shoreline represents the
Coastline. Where Inland water (such as a river) flows into Coastal,
Territorial or Great Lakes water, the closure line separating the Inland
water from the other class of water represents the Coastline.
L4165
Ferry Crossing
The route used to carry or convey people or cargo back and forth
over a waterbody in a boat.
R1011
Railroad Feature (Main,
Spur, or Yard)
A line of fixed rails or tracks that carries mainstream railroad traffic.
Such a rail line can be a main line or spur line, or part of a rail yard.
R1052
Cog Rail Line, Incline Rail
Line, Tram
A special purpose rail line for climbing steep grades that is typically
inaccessible to mainstream railroad traffic. Note that aerial tramways
and streetcars (which may also be called “trams”) are accounted for
by other MTFCCs and do not belong in R1052.
S1100
Primary Road
Primary roads are generally divided, limited-access highways within
the interstate highway system or under state management, and are
distinguished by the presence of interchanges. These highways are
accessible by ramps and may include some toll highways.
S1200
Secondary Road
Secondary roads are main arteries, usually in the U.S. Highway, State
Highway or County Highway system. These roads have one or more
lanes of traffic in each direction, may or may not be divided, and
usually have at-grade intersections with many other roads and
driveways. They often have both a local name and a route number.
S1400
Local Neighborhood Road, Generally a paved non-arterial street, road, or byway that usually has
Rural Road, City Street
a single lane of traffic in each direction. Roads in this feature class
may be privately or publicly maintained. Scenic park roads would be
included in this feature class, as would (depending on the region of
the country) some unpaved roads.
S1500
Vehicular Trail (4WD)
An unpaved dirt trail where a four-wheel drive vehicle is required.
These vehicular trails are found almost exclusively in very rural areas.
Minor, unpaved roads usable by ordinary cars and trucks belong in
the S1400 category.
S1630
Ramp
A road that allows controlled access from adjacent roads onto a
limited access highway, often in the form of a cloverleaf interchange.
These roads are unaddressable.
S1640
Service Drive usually
along a limited access
highway
A road, usually paralleling a limited access highway, that provides
access to structures along the highway. These roads can be named
and may intersect with other roads.
S1710
Walkway/Pedestrian Trail
A path that is used for walking, being either too narrow for or legally
restricted from vehicular traffic.
S1720
Stairway
A pedestrian passageway from one level to another by a series of
steps.
S1730
Alley
A service road that does not generally have associated addressed
structures and is usually unnamed. It is located at the rear of buildings
and properties and is used for deliveries.
View Table of Contents
48 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
MTFCC
Feature Class
Feature Class Description
S1740
Private Road for service
A road within private property that is privately maintained for service,
vehicles (logging, oil fields, extractive, or other purposes. These roads are often unnamed.
ranches, etc.)
S1750
Internal U.S. Census
Bureau use
Internal U.S. Census Bureau use.
S1780
Parking Lot Road
The main travel route for vehicles through a paved parking area.
S1820
Bike Path or Trail
A path that is used for manual or small, motorized bicycles, being
either too narrow for or legally restricted from vehicular traffic.
S1830
Bridle Path
A path that is used for horses, being either too narrow for or legally
restricted from vehicular traffic.
S2000
Road Median
The unpaved area or barrier between the carriageways of a divided
road.
P0001
Nonvisible Linear
A legal/statistical boundary line that does not correspond to a
Legal/Statistical Boundary shoreline or other visible feature on the ground.
P0002
Perennial Shoreline
The more-or-less permanent boundary between land and water for a
water feature that exists year-round.
P0003
Intermittent Shoreline
The boundary between land and water (when water is present) for a
water feature that does not exist year-round.
P0004
Other non-visible bounding
Edge (e.g., Census water
boundary, boundary of an
areal feature)
A bounding Edge that does not represent a legal/statistical boundary,
and does not correspond to a shoreline or other visible feature on the
ground. Many such Edges bound area landmarks, while many others
separate water features from each other (e.g., where a bay meets the
ocean).
View Table of Contents
49 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX C: PARTNERSHIP SHAPEFILE DATA DICTIONARY
-Partnership ShapefilesShapefile Layer
Geographic
Level
Name
American Indian Areas (AIA) - Legal
County/State
Aial
American Indian / Alaska Native Areas (AIANA) - Statistical
County/State
Aias
American Indian Tribal Subdivisions (AITS) - Legal
County/State
Aitsl
American Indian Tribal Subdivisions (AITS) - Statistical
County/State
Aitss
Alaska Native Regional Corporations (ANRC)
County/State
Anrc
Area Landmark
County only
Arealm
Bag
Block Area Grouping
County/State
Census Block Groups
County only
Bg
Block Size Indicator
County only
Block
Metropolitan/ Micropolitan Statistical Area
County/State
Cbsa
County Subdivisions – Statistical
County/State
Ccd
Congressional Districts (CD)
County/State
Cd
Census Designated Places (CDP)
County/State
Cdp
Consolidated Cities
County only
Concity
Counties and Equivalent Areas
County/State
County
Census Tracts
County only
Curtracts
Edges (All Lines)
County only
Edges
School Districts (Elementary)
County/State
Elsd
County Subdivisions – Legal
County/State
Mcd
New England City and Town Area
County/State
Necta
Offsets
County only
Offset
Incorporated Places
County/State
Place
Point Landmarks
County only
Pointlm
Public Use Microdata Areas – Census 2010
County/State
Puma2010
School Districts (Secondary)
County/State
Scsd
State Legislative Districts (Lower/House)
County/State
Sldl
State Legislative Districts (Upper/Senate)
County/State
Sldu
States and Equivalent Areas
State only
State
Subbarrios
County only
Submcd
Census Blocks - Current
County only
Tabblock
Census Blocks – Census 2010
County only
Tabblock2010
Traffic Analysis Districts – Census 2010
County only
Tad2010
Traffic Analysis Zone
County only
Taz2010
Tribal Block Group
County/State
Tbg
Census Tracts – Census 2010
County/State
Tracts2010
Urban Area/ Urban Cluster – Census 2010
County/State
Uac
Urban Growth Areas (UGA)
County only
Uga
School Districts (Unified)
County/State
Unsd
Hydrography - Area
County only
Water
View Table of Contents
50 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
Address Ranges (Relationship Table)
County
Addr
Linear Feature Names (Relationship Table)
County
Allnames
Topological Faces - Area Landmark Relationship
County
Areafaces
Topological Faces (Listing of faces with all geocodes)
County
Faces
Topological Faces - Area Hydrography Relationship
County
Hydrofaces
-American Indian Areas – Legal -Alaska Native Regional Corporations (Alaska Only)ATTRIBUTE
FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
ANRCFP
5
String
FIPS ANRC Code (State Based)
ANRCCE
2
String
Current Census ANRC Code
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS55 class code describing entity
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting documentation
FORM_ID
4
Record ID for any boundary update
AREA
10
RELATE
120
String
Numeric (3
decimal places)
String
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
AIANHFSR
1
String
Vintage updated with returned data
Flag indicating level of recognition of an American
Indian, Alaska Native, or Native Hawaiian tribe or
group.
ATTRIBUTE
FIELD
STATEFP
Acreage of area update
Relationship description
LENGTH
TYPE
DESCRIPTION
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
AIANNHCE
4
String
COMPTYP
1
String
AIANNHFSR
1
String
NAMELSAD
100
String
Census AIANNH Code
Indicates if reservation (or equivalent) or offreservation trust land is present, or both
Flag indicating level of recognition of an American
Indian, Alaska Native, or Native Hawaiian tribe or
group.
Name with translated LSAD
View Table of Contents
51 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-American Indian Areas – Legal AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS55 class code describing entity
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting documentation
FORM_ID
4
Record ID for any boundary update
AREA
10
RELATE
120
String
Numeric (3
decimal places)
String
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
Acreage of area update
Relationship description
-American Indian / Alaska Native Areas – StatisticalATTRIBUTE
FIELD
STATEFP
LENGTH
TYPE
DESCRIPTION
2
String
FIPS State Code
3
String
FIPS County Code
4
String
COUNTYFP*
AIANNHCE
COMPTYP
1
AIANNHFSR
1
NAMELSAD
100
String
Census AIANNH Code
Indicates if reservation (or equivalent) or offreservation trust land is present, or both
Flag indicating level of recognition of an American
Indian, Alaska Native, or Native Hawaiian tribe or
group.
Name with translated LSAD
AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
LSAD
2
String
Legal/Statistical Area Description
1
String
Functional Status
FIPS55 class code describing entity
String
String
FUNCSTAT
CLASSFP
2
String
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
8
String
Effective Date or Vintage
Relationship description
Justification
EFF_DATE
RELATE
120
String
JUSTIFY
150
VINTAGE
2
Char
String
Vintage updated with returned data
100
String
Name
NAME
-American Indian Tribal Subdivisions - LegalATTRIBUTE
FIELD
LENGTH
View Table of Contents
TYPE
DESCRIPTION
52 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-American Indian Tribal Subdivisions - LegalSTATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
AIANNHCE
4
String
Census AIANNH Code
TRIBSUBCE
1
String
Census Tribal subdivision
NAMELSAD
100
String
Name with translated LSAD
AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS55 class code describing entity
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting documentation
FORM_ID
4
Record ID for any boundary update
AREA
10
RELATE
120
String
Numeric (3
decimal
places)
String
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
AIANNHFSR
1
String
Vintage updated with returned data
Flag indicating level of recognition of an American
Indian, Alaska Native, or Native Hawaiian tribe or
group.
Acreage of area update
Relationship description
-American Indian Tribal Subdivisions - StatisticalATTRIBUTE
FIELD
STATEFP
LENGTH
TYPE
DESCRIPTION
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
AIANNHCE
4
String
Census AIANNH Code
TRIBSUBCE
1
String
Census Tribal subdivision
NAMELSAD
100
String
Name with translated LSAD
AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS55 class code describing entity
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting documentation
FORM_ID
4
Record ID for any boundary update
AREA
10
String
Numeric (3
decimal
View Table of Contents
Acreage of area update
53 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-American Indian Tribal Subdivisions - Statisticalplaces)
RELATE
120
String
Relationship description
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
AIANNHFSR
1
String
Vintage updated with returned data
Flag indicating level of recognition of an American
Indian, Alaska Native, or Native Hawaiian tribe or
group.
-Block Size IndicatorATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
TRACTCE
6
String
Census Tract Code
BLOCKCE
4
String
BLOCKID
19
String
Tabulation Block Number
FIPS State Code, FIPS County Code, Census Tract
Code, Tabulation Block Number, Census Block
Suffix 1, Census Block Suffix 2
AREALAND
14
AREAWATER
10
LWBLKTYP
1
String
PERIMETER
9
String
SHAPEIDX
9
String
BLKSZIND
1
String
Numeric (3
decimal
places)
Numeric (3
decimal
places)
Current Area Land in Square Meters
Current Area Water in Square Meters
Land/Water Block Type: B = Both Land and Water; L
= Land; W = Water
Perimeter of Block in Square Meters
(√ (4πA/P2), where A=Area of block & P = Perimeter
of block
Block Size Indicator
-Congressional DistrictsATTRIBUTE
FIELD
STATEFP
LENGTH
TYPE
DESCRIPTION
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
CDFP
2
String
Congressional District Code
CDTYP
1
String
Congressional District Type
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
CHNG_TYPE
2
String
Type of Area Update
EFF_DATE
8
String
Effective date or vintage
NEW_CODE
2
String
New Congressional District Code
RELTYPE1
2
String
Relationship Type 1
RELTYPE2
2
String
Relationship Type 2
RELTYPE3
2
String
Relationship Type 3
View Table of Contents
54 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Congressional DistrictsRELTYPE4
2
String
Relationship Type 4
RELTYPE5
2
String
Relationship Type 5
REL_ENT1
8
String
Relationship Entity 1
REL_ENT2
8
String
Relationship Entity 2
REL_ENT3
8
String
Relationship Entity 3
REL_ENT4
8
String
Relationship Entity 4
REL_ENT5
8
String
Relationship Entity 5
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
CDSESSN
3
String
Congressional District Session Code
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
FUNCSTAT
1
String
Functional Status
-Hawaiian Home Lands (Hawaii Only)ATTRIBUTE
FIELD
STATEFP
LENGTH
TYPE
DESCRIPTION
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
AIANNHCE
4
String
COMPTYP
1
String
NAMELSAD
100
String
Census AIANNH Code
Indicates if reservation (or equivalent) or off-reservation
trust land is present, or both
Name with translated LSAD
AIANNHNS
8
String
ANSI numeric identifier for AIANNH Areas
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS55 class code describing entity
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting documentation
FORM_ID
4
Record ID for any boundary update
AREA
10
RELATE
120
String
Numeric (3
decimal
places)
String
JUSTIFY
150
Char
Justification
VINTAGE
2
String
AIANNHFSR
1
String
NAME
100
String
Vintage updated with returned data
Flag indicating level of recognition of an American Indian,
Alaska Native, or Native Hawaiian tribe or group.
Name
Acreage of area update
Relationship description
-School Districts (Elementary, Secondary, Unified)ATTRIBUTE
FIELD
LENGTH
View Table of Contents
TYPE
DESCRIPTION
55 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-School Districts (Elementary, Secondary, Unified)STATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
SDLEA
5
String
Current Local Education Agency Code
NAME
100
String
Name of School District
LSAD
2
Integer
HIGRADE
2
String
LOGRADE
2
String
PARTFLG*
1
String
POLYID
4
String
CHNG_TYPE
1
String
Legal/Statistical Area Description
Highest grade for which the district is financially
responsible
Lowest grade for which the district is financially
responsible
Part Flag Indicator
Record ID for each update polygon for linking back to the
submission log
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
RELATE
120
String
Relationship description
JUSTIFY
150
Char
Justification
FUNCSTAT
3
String
Functional Status
VINTAGE
2
String
Vintage updated with returned data
-State Legislative Districts (Upper/Senate)ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
SLDUST
3
String
SLD Upper Chamber Code
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
NEW_NAME
100
String
New SLDU Name
NEW_CODE
3
String
New SLDU Code
RELTYPE1
2
String
Relationship Type 1
RELTYPE2
2
String
Relationship Type 2
RELTYPE3
2
String
Relationship Type 3
RELTYPE4
2
String
Relationship Type 4
RELTYPE5
2
String
Relationship Type 5
REL_ENT1
8
String
Relationship Entity 1
REL_ENT2
8
String
Relationship Entity 2
REL_ENT3
8
String
Relationship Entity 3
REL_ENT4
8
String
Relationship Entity 4
REL_ENT5
8
String
Relationship Entity 5
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
View Table of Contents
56 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-State Legislative Districts (Upper/Senate)LSY
4
String
Legislative Session Year
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
FUNCSTAT
1
String
Functional Status
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
-State Legislative Districts (Lower/Senate)-
COUNTYFP*
3
String
FIPS County Code
SLDLST
3
String
SLD Lower Chamber Code
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
PARTFLG*
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
NEW_NAME
100
String
New SLDL Name
NEW_CODE
3
String
New SLDL Code
RELTYPE1
2
String
Relationship Type 1
RELTYPE2
2
String
Relationship Type 2
RELTYPE3
2
String
Relationship Type 3
RELTYPE4
2
String
Relationship Type 4
RELTYPE5
2
String
Relationship Type 5
REL_ENT1
8
String
Relationship Entity 1
REL_ENT2
8
String
Relationship Entity 2
REL_ENT3
8
String
Relationship Entity 3
REL_ENT4
8
String
Relationship Entity 4
REL_ENT5
8
String
Relationship Entity 5
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
LSY
4
String
Legislative Session Year
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
FUNCSTAT
1
String
Functional Status
View Table of Contents
57 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Urban Growth AreasATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
UGACE
5
String
Urban Growth Area Code
UGATYP
1
String
Urban Growth Area Type
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
AREA
10
Double
Acreage of Update
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
VINTAGE
2
String
Vintage updated with returned data
NAME
100
String
Name
-Census Block GroupsATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
TRACTCE
6
String
Census Tract Code
BLKGRPCE
1
String
BLKGRPID
12
String
CHNG_TYPE
2
String
Block Group Code
FIPS State Code, FIPS County Code, Census Tract
Code, Block Group Code
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
BGTYP
1
String
Block Group Characteristic Flag
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
VINTAGE
2
String
Vintage updated with returned data
-Census Blocks – CurrentATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
STATEFP10
2
String
FIPS 2010 State Code
COUNTYFP10
3
String
FIPS 2010 County Code
TRACTCE10
6
String
Census Tract Code
BLOCKCE
4
String
Tabulation Block Number
SUFFIX1CE
2
String
Census Block Suffix 1
View Table of Contents
58 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Census Blocks – CurrentSUFFIX2CE
2
String
BLOCKID
19
String
Census Block Suffix 2
FIPS State Code, FIPS County Code, Census Tract
Code, Tabulation Block Number, Census Block
Suffix 1, Census Block Suffix 2
-Census Blocks – Census 2010ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP10
2
String
FIPS 2010 State Code
COUNTYFP10
3
String
FIPS 2010 County Code
TRACTCE10
6
String
Census Tract Code
BLOCKCE
4
String
BLOCKID10
15
String
PARTFLG
1
String
Tabulation Block Number
FIPS State Code, FIPS County Code, Census Tract
Code, Tabulation Block Number
Part Flag Indicator
HOUSING10
9
Integer
2010 Housing
POP10
9
Integer
Census 2010 population count
-Census TractsATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
TRACTCE
6
String
Census Tract Code
NAME
100
String
TRACTID
11
String
CHNG_TYPE
2
String
Name
FIPS State Code, FIPS County Code, Census Tract
Code
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
TRACTTYP
1
String
Tract Characteristic Flag
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
TRACTLABEL
7
String
Tract number used for LUCA geocoding
VINTAGE
2
String
Vintage updated with returned data
-Census Designated PlacesATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
PLACEFP
5
String
FIPS 55 Place Code
PLACENS
5
String
ANSI feature code for the place
NAMELSAD
100
String
Name with translated LSAD
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
View Table of Contents
59 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Census Designated PlacesCLASSFP
2
String
FIPS 55 Class Code describing an entity
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
-Consolidated City ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
CONCITYFP
5
String
FIPS 55 Place Code
CONCITYCE
4
String
Census Consolidated City Code
NAMELSAD
100
String
Name with translated LSAD
PLACENS
8
String
ANSI feature code for the place
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code describing an entity
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting Documentation
FORM_ID
4
String
(MTPS and Web BAS only)
AREA
10
Double
Acreage of Update
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
-County and Equivalent Areas ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
COUNTYNS
8
String
NAMELSAD
100
String
FIPS County Code
ANSI Feature Code for the County or Equivalent
Feature
Name with translated LSAD code
LSAD
2
String
Legal/Statistical Area Description code
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code describing an entity
CHNG_TYPE
1
String
Type of area update
EFF_DATE
8
String
Effective Date or Vintage
View Table of Contents
60 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-County and Equivalent Areas ShapefileDOCU
120
String
Supporting Documentation
FORM_ID
4
String
(MTPS / Web BAS only)
AREA
10
Double
Acreage of Area Update
RELATE
120
String
Relationship description
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
-County Subdivisions Shapefile – Legal (MCD)ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
COUSUBFP
5
String
FIPS County Subdivision Code
NAMELSAD
100
String
Name with translated LSAD
COUSUBNS
8
String
ANSI feature code for the county subdivision
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code describing an entity
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting Documentation
FORM_ID
4
String
(MTPS and Web BAS only)
AREA
10
Double
Acreage of Update
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
-County Subdivisions Shapefile –Statistical (CCD)ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
COUSUBFP
5
String
FIPS County Subdivision Code
NAMELSAD
100
String
Name with translated LSAD
COUSUBNS
8
String
ANSI feature code for the county subdivision
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code describing an entity
CHNG_TYPE
1
String
Type of Area Update
RELATE
120
String
Relationship Description
View Table of Contents
61 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-County Subdivisions Shapefile –Statistical (CCD)JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP*
3
String
FIPS County Code
PLACEFP
5
String
FIPS 55 Place Code
NAMELSAD
100
String
Name with translated LSAD
PLACENS
8
String
ANSI feature code for the place
-Incorporated Place Shapefile-
LSAD
2
String
Legal/Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code describing an entity
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
DOCU
120
String
Supporting Documentation
FORM_ID
4
String
(MTPS and Web BAS only)
AREA
10
Double
Acreage of Update
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
-States and Equivalent AreasATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
STATEUSPS
2
String
FIPS State Code
3
String
USPS State Abbreviation
NAME
10
Integer
Name
LSAD
5
String
Legal/Statistical Area Description
STATENS
120
String
ANSI feature code for the state
-SubbarriosATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
COUSUBFP
5
String
FIPS County Subdivision Code
SUBMCDFP
5
String
FIPS Sub-minor Civil Division Code
NAMELSAD
100
String
Name with translated LSAD
View Table of Contents
62 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-SubbarriosSUBMCDNS
8
String
ANSI feature code for the sub-minor civil division
LSAD
2
String
Legal/Statistical Area Description
CHNG_TYPE
1
String
Type of Area Update
EFF_DATE
8
String
Effective Date or Vintage
AREA
10
Double
Acreage of Update
RELATE
120
String
Relationship Description
JUSTIFY
150
Char
Justification
FORM_ID
4
String
(MTPS and Web BAS only)
NAME
100
String
Name
VINTAGE
2
String
Vintage updated with returned data
FUNCSTAT
1
String
Functional Status
-Edges (All Lines) ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
State FIPS Code
COUNTYFP
3
String
County FIPS Code
TLID
10
Integer
Permanent Edge ID
TFIDL
10
Integer
Permanent Face ID (Left)
TFIDR
10
Integer
Permanent Face ID (Right)
MTFCC
5
String
FIDELITY
1
String
FULLNAME
120
String
SMID
22
String
MAF/TIGER Feature Class Code
Indication to a respondent when their entity
boundary has changed through spatial enhancement
Prefix qualifier code, prefix direction code, prefix type
code, base name, suffix type code, suffix qualifier
code
Spatial Tmeta ID
BBSPFLG
1
String
2010 block boundary suggestion
CBBFLG
1
String
BBSP_2020
1
String
CHNG_TYPE
2
String
Planned 2020 block boundary
BBSP Participant suggested 2020 Census block
boundary
Type of linear update
JUSTIFY
150
Char
Justification
LTOADD
10
String
Left To Address
RTOADD
10
String
Right To Address
LFROMADD
10
String
Left From Address
RFROMADD
10
String
Right From Address
ZIPL
5
String
Left Zip Code
ZIPR
5
String
Right Zip Code
-Area Landmark ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
View Table of Contents
63 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Area Landmark ShapefileCOUNTYFP
3
String
FIPS County Code
MTFCC
5
String
FULLNAME
120
String
AREAID
10
Integer
MAF/TIGER Feature Class Code
Prefix direction code, prefix type code, base name,
suffix type code, suffix direction code
Landmark identification number
ANSICODE
8
String
ANSI code for area landmarks
CHNG_TYPE
1
String
Type of Area Landmark update
EFF_DATE
8
String
Effective Date or Vintage
RELATE
120
String
Relationship description
JUSTIFY
150
Char
Justification
BAG
3
String
Block Area Grouping
-Hydrography Area ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
ANSICODE
8
String
ANSI code for hydrography area
MTFCC
5
String
FULLNAME
120
String
CHNG_TYPE
1
String
MAF/TIGER Feature Class Code
Prefix direction code, prefix type code, base name,
suffix type, suffix type code, suffix direction code
Type of Area Update
HYDROID
10
String
Hydrography Identification Number
RELATE
120
String
Relationship description
JUSTIFY
150
Char
Justification
-Point Landmarks ShapefileATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
COUNTYFP
2
String
FIPS State Code
3
String
FIPS County Code
POINTID
10
Integer
Point Landmark Identification Number
ANSICODE
8
Char
Official Code for Federal Agency use
MTFCC
5
String
MAF/TIGER Feature Class Code
FULLNAME
120
String
Prefix type code, base name, suffix type code
CHNG_TYPE
1
String
Type of Area Update
JUSTIFY
150
Char
Justification
-Topological Faces – Geographic Entity Relationships TableATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
TFID
20
Integer
Permanent Face ID
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
View Table of Contents
64 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Topological Faces – Geographic Entity Relationships TableTRIBSUBCE
3
String
Census Tribal Subdivision
TTRACTCE
6
String
Tribal Census Tract Code
TBLKGRPCE
1
String
Tribal Census Block Group Code
AIANNHCE
4
String
COMPTYP
1
String
ANRCCE
5
String
Census AIANNH Code
Indicates if reservation (or equivalent) or offreservation trust land is present, or both
FIPS ANRC Code
SLDUST
3
String
SLD Upper Chamber Code
SLDLST
3
String
ELSD
5
String
SCSD
5
String
UNSD
5
String
CDFP
2
String
SLD Lower Chamber Code
Current ELSD Local Education Agency (LEA)
Code
Current SCSD Local Education Agency (LEA)
Code
Current UNSD Local Education Agency (LEA)
Code
Congressional District Code
TRACTCE
6
String
Census Tract Code
UACE
5
String
Census Urban Area Code
BLKGRPCE
1
String
Census Block Group Code
BLOCKCE
4
String
Tabulation Block Number
SUFFIX1CE
2
String
Census Block Suffix 1
SUFFIX2CE
2
String
Census Block Suffix 2
TAZCE
6
String
Traffic Analysis Zone Code
SUBMCDFP
5
String
FIPS 55 Sub-minor Civil Division Code
UGACE
5
String
Urban Growth Area Code
VTDST10
6
String
2010 Voting District Code
STATEFP10
2
String
FIPS 2010 State Code
COUNTYFP10
3
String
FIPS 2010 County Code
TRACTCE10
6
String
Census 2010 Tract Code
PLACEFP
5
String
FIPS 55 Place Code
COUSUBFP
5
String
FIPS 55 County Subdivision Code
CONCITYFP
5
String
FIPS 55 Place Code
LWFLG
1
String
Land/Water Flag
-Topological Faces – Area Landmark Relationships TableATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
TFID
20
Integer
Permanent Face ID
AREAID
22
Integer
Object ID
-Topological Faces – Hydrography Area Relationships TableATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
TFID
20
Integer
Permanent Face ID
HYDROID
22
Integer
Object ID
View Table of Contents
65 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Address Ranges Table ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
TLID
22
Integer
TIGER Line ID
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
FROMHN
12
String
From House Number
TOHN
12
String
To House Number
SIDE
1
String
Side Indicator Flag
ZIP
5
String
5-digit ZIP Code
PLUS4
4
String
ZIP+4 Code
LFROMADD
10
String
Left From Address
LTOADD
10
String
Left To Address
RFROMADD
10
String
Right From Address
RTOADD
10
String
Right To Address
ZIPL
5
String
Left 5-digit ZIP Code
ZIPR
5
String
Right 5-digit ZIP Code
ZIP4L
4
String
Left ZIP+4 Code
ZIP4R
4
String
Right ZIP+4 Code
View Table of Contents
66 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
-Linear Feature Names Table ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
OID
22
Integer
Object ID
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
NAME
100
String
Name
PREDIR
2
String
Prefix Direction code component of feature name
PRETYP
3
String
Prefix Type code component of feature name
PREQUAL
2
String
Prefix Qualifier code component of feature name
SUFDIR
2
String
Suffix Direction code component of feature name
SUFTYP
3
String
Suffix Type code component of feature name
SUFQUAL
2
String
Suffix Qualifier code component of feature name
MTFCC
5
String
MAF/TIGER Feature Class Code
PAFLAG
1
String
Primary/Alternate flag
View Table of Contents
67 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX D: ACRONYMS
Acronym
BAS
BAG
BBSP
CCBFLG
CRVRDO
GNIS
GUPS
MAF/TIGER
MCD
MTFCC
OGC
SWIM
URL
VTD
View Table of Contents
Explanation
Boundary and Annexation Survey
Block Area Grouping
Block Boundary Suggestion Program
Census Block Boundary Flag
Census Redistricting and Voting Rights Data Office
Geographic Names Information System
Geographic Update Partnership Software
Master Address File/Topologically Integrated Geographic and Encoding
Reference (System)
Minor Civil Division
MAF TIGER Feature Classification Code
Open Geospatial Consortium
Secure Web Incoming Module
Uniform Resource Locator
Voting District Project
68 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX E: BBSP PARTICIPANT SUPPORT
Direct all questions regarding the Block Boundary Suggestion Project, including
procedural and GUPS technical questions, to:
Census Redistricting and Voting Rights Data Office (301) 763-4039
View Table of Contents
69 | Page
Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3
APPENDIX F: COUNTY COMPLETION TRACKING SHEET
BBSP Participants can use these sheets to track completed work and submissions to
the state (for designees) or the Census Bureau (RDP Liaison). Please note that there
are several even numbered County FIPS codes, included to accommodate states that
have them. These rows are highlighted for your convenience and to avoid population
errors. This worksheet is available as a downloadable Excel file.
View Table of Contents
70 | Page
| File Type | application/pdf |
| File Title | Block Boundary Suggestion Project User Supplied GIS User’s Guide_DRAFT V 0.3 |
| Author | [email protected] |
| File Modified | 2015-09-18 |
| File Created | 2015-08-28 |