BAS Digital Tribal Respondent Guide

21_BASRespondentGuide_TribalDigital_508.pdf

The Boundary and Annexation Survey (BAS) & Boundary Validation Program (BVP)

BAS Digital Tribal Respondent Guide

OMB: 0607-0151

⚠️ Notice: This form may be outdated. More recent filings and information on OMB 0607-0151 can be found here:

Document [pdf]

Download: pdf | pdf

Boundary and Annexation Survey (BAS)
Tribal Respondent Guide: Digital
Instructions for Participating Digitally in the 2021 Boundary and Annexation Survey
Revised as of November 10, 2020

This page intentionally left blank.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

TABLE OF CONTENTS
Introduction ..........................................................................................................................viii
A.

The Boundary and Annexation Survey ........................................................................ viii

Key Dates for BAS Respondents .................................................................................. viii

Legal Disputes ................................................................................................................ 1

Chapter 1 Digital BAS Requirements ....................................................................................... 2
1.1

Digital BAS Participation Requirements ......................................................................... 2

1.2

Tribal Areas that can be Submitted through BAS ........................................................... 2

1.3

BAS Informational and Tutorial Videos .......................................................................... 3

Chapter 2 Topological Relationships and Spatial Accuracy ...................................................... 4
2.1

Topological Relationships in the MAF/TIGER System ..................................................... 4

2.2

GIS and Spatial Accuracy ................................................................................................ 5

2.3

Census Bureau Topology Training Video ........................................................................ 7

Chapter 3 Census Bureau Provided Shapefiles ........................................................................ 8
3.1

Federal Information Processing Standards (FIPS) Codes ................................................ 8

Chapter 4 Census Bureau GEOCODING ................................................................................... 9
4.1

MAF Structure Point (MSP) Geocoding .......................................................................... 9

4.2

Address Range Geocoding ............................................................................................ 10

Chapter 5 Updating the Census Bureau Shapefiles................................................................ 11
5.1

General File Setup Guidelines ...................................................................................... 11

5.2

Changing the Map Projection ....................................................................................... 11

5.3

Boundary Changes ....................................................................................................... 11

5.3.1 Additions and Deletions ........................................................................................................ 12
5.3.2 Boundary Corrections ............................................................................................................ 12
5.3.3 Tribal Subdivisions ................................................................................................................. 13
5.3.3.1 New Tribal Subdivisions ..................................................................................................................13
5.3.3.2 Criteria for Defining Tribal Subdivisions ..........................................................................................14
5.3.3.3 Updating Tribal Subdivisions ...........................................................................................................14

5.3.4 Geographic Corridors............................................................................................................. 15
5.3.5 Geographic Offsets ................................................................................................................ 16

5.4

Linear Feature Updates ................................................................................................ 17

5.4.1 Adding, Deleting, Renaming, and Recoding Linear Features ................................................ 17
5.4.2 Address Range Updates ......................................................................................................... 17
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.5

Area Landmarks, Hydrographic Areas, and Point Landmarks ....................................... 18

5.5.1 Area Landmark/Hydrographic Area Updates ........................................................................ 18
5.5.2 Point Landmark Updates ....................................................................................................... 20

5.6

Reviewing Changes to the Census Bureau Shapefiles .................................................. 22

5.6.1 Boundary-to-Feature Relationships ...................................................................................... 22
5.6.2 Large Boundary Corrections .................................................................................................. 24
5.6.3 Required Attribute Information ............................................................................................ 25
5.6.4 Appropriate Projection Information ...................................................................................... 25
5.6.5 Linear Feature Updates ......................................................................................................... 25

5.7

Additional Information Review .................................................................................... 26

5.7.1 Submitting Acceptable Documentation ................................................................................ 26
5.7.2 Submitting Digital Data .......................................................................................................... 27
5.7.3 Change Polygon Layer Naming Conventions ......................................................................... 28
5.7.4 Whole Entity Polygon Layer Naming Conventions ................................................................ 28
5.7.5 Linear Feature, Area Landmark/Hydrographic Area, and Point Landmark Updates............. 28
5.7.6 Compressing the Digital Files................................................................................................. 29
5.7.7 Submitting Digital Files through SWIM ................................................................................. 30

Appendices ........................................................................................................................... A-1
Appendix A

Data Dictionary .............................................................................................. A-2

Appendix B

2021 BAS Example Process 1 .......................................................................... B-1

How to Use the BAS Partnership Toolbox ...................................................................B-1

Toolbox Tools Setup ....................................................................................................B-1

Census Data Download Tool........................................................................................B-2

Create Changes Tool ...................................................................................................B-4

Sliver Blaster Tool (Optional).......................................................................................B-6

Format Working MXD Tool (Optional) .........................................................................B-7

Attribute Check Tool ...................................................................................................B-8

Export Submission Tool ...............................................................................................B-9

Submitting Files through the Secure Web Incoming Module (SWIM) .......................B-10

Appendix C

2021 Digital BAS Example Process 2 ............................................................... C-1

Required Census Bureau Shapefiles ............................................................................C-1

Tribal Data ...................................................................................................................C-1

Symbolizing Layers in ArcGIS .......................................................................................C-1

Symbolizing Geographic Areas ....................................................................................C-2

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

iii

Extracting AIA Data from Census Bureau Shapefiles ...................................................C-2

C5.1

Filtering the Data ..................................................................................................................C-2

C5.2

Exporting the Data to a New Shapefile ................................................................................C-3

Merging Multipart Place Data .....................................................................................C-4

Creating Change Polygons ...........................................................................................C-5

C7.1

Creating Change Polygons Using Symmetrical Difference ...................................................C-5

C7.2

Creating Change Polygons Using Union ...............................................................................C-6

Reviewing and Attributing Change Polygons ...............................................................C-8

C8.1

Examples ...............................................................................................................................C-8

Attribute Information ..................................................................................................C-8

C9.1

To Begin Updating Attributes for Additions .........................................................................C-9

C9.2

To Begin Updating Attributes for Deletions .........................................................................C-9

C9.3

To Begin Updating Attributes for Geographic Corridors ......................................................C-9

C9.4

To Begin Updating Attributes for Geographic Offsets..........................................................C-9

C9.5

To Finish Updating Attributes ...............................................................................................C-9

C10 Renaming and Finalizing Change Polygons ................................................................C-10
C10.1 Renaming the shapefile: .....................................................................................................C-10
C10.2 Submitting the shapefile: ...................................................................................................C-10
C10.3 To Begin Updating Attributes for Boundary Corrections ...................................................C-10

Appendix D

U.S. Census Bureau

MTFCC Descriptions ....................................................................................... D-1

Boundary and Annexation Survey Tribal Respondent Guide: Digital

LIST OF TABLES
Table 1: Available Change Types by Government Type ................................................................. 3
Table 2: BAS Shapefile Naming Conventions ................................................................................. 8
Table 3: Additions and Deletions ................................................................................................ 12
Table 4: Boundary Corrections .................................................................................................... 12
Table 5: New Entities .................................................................................................................. 14
Table 6: Geographic Corridors..................................................................................................... 15
Table 7: Geographic Offsets ........................................................................................................ 16
Table 8: Linear Feature Updates ................................................................................................. 17
Table 9: Address Range Updates ................................................................................................. 18
Table 10: Landmarks and Hydrographic Areas ............................................................................ 19
Table 11: Acceptable MTFCCs for New Area Landmarks/Hydrographic Areas ............................ 19
Table 12: Point Landmark Updates ............................................................................................. 21
Table 13: Restricted Point Landmark MTFCC Codes .................................................................... 21
Table 14: Change Polygons ......................................................................................................... 28
Table 15: Whole Entity Polygon Layer Naming Conventions ....................................................... 28
Table 16: Optional Files ............................................................................................................... 28
Table 17: American Indian Areas - Legal (AIAL) Shapefile ......................................................... A-2
Table 18: American Indian Tribal Subdivisions (AITS) Shapefile ................................................ A-2
Table 19: Edges Shapefile.......................................................................................................... A-3
Table 20: Area Landmark Shapefile ........................................................................................... A-4
Table 21: Hydrographic Area Shapefile ..................................................................................... A-4
Table 22: Point Landmark Shapefile .......................................................................................... A-4
Table 23: Geographic Offset Shapefile ...................................................................................... A-5
Table 24: Suggested MTFCC Symbolization ................................................................................C-1
Table 25: MTFCC Code/Class/Decsription ................................................................................. D-1

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

LIST OF FIGURES
Figure 1. Topological Integration of Four Classes .......................................................................... 5
Figure 2. Overlay of Four Feature Classes ..................................................................................... 6
Figure 3. GIS AIA Boundary Does Not Follow Road Feature .......................................................... 6
Figure 4. GPS Method of Geocoding ............................................................................................. 9
Figure 5. Address Range Method of Geocoding .......................................................................... 10
Figure 6. Geographic Corridor Created ....................................................................................... 15
Figure 7. Geographic Corridor Not Created................................................................................. 15
Figure 8. Cadastral Data .............................................................................................................. 16
Figure 9. Same Data Edited to Census Bureau Requirements ..................................................... 16
Figure 10. A Boundary Correction to Park A ................................................................................ 18
Figure 11. Boundary Corrections Not Snapped to Existing Linear Features ................................ 22
Figure 12. Addition Created without Snapping to Centerlines .................................................... 23
Figure 13. Small Spatial Correction Not Incorporated ................................................................. 23
Figure 14. Small Spatial Correction Not Accepted ....................................................................... 24
Figure 15. Large Boundary Corrections ....................................................................................... 24
Figure 16. New Road Features, Not Added to Existing Road ....................................................... 25
Figure 17. New Road Features, Correctly Added ......................................................................... 25
Figure 18. Selecting and Zipping Return Files .............................................................................. 29
Figure 19. Naming the ZIP File..................................................................................................... 30
Figure 20. SWIM Account Registration........................................................................................ 31
Figure 21. SWIM Login Window .................................................................................................. 32
Figure 22. Welcome Screen with Upload History ........................................................................ 32
Figure 23. Geographic Partnership Program Selection Window ................................................. 32
Figure 24. Geographic Level Selection Window .......................................................................... 33
Figure 25. Government Selection Window ................................................................................. 33
Figure 26. File Upload Screen ...................................................................................................... 33
Figure 27. File Browser Dialog Box .............................................................................................. 34
Figure 28. Entering Comments into the File Upload Window ..................................................... 34
Figure 29. Thank You Screen ....................................................................................................... 34
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 30. Partnership BAS Tools Menu .....................................................................................B-2
Figure 31. Partnership BAS Tools Menu with Census Data Download Selected .........................B-2
Figure 32. The Census Data Download Window with ‘Yes’ in the Use Data Downloader Field ..B-3
Figure 33. The Census Data Download Window with ‘No’ in the Use Data Downloader Field ...B-3
Figure 34. Partnership Tools Menu Showing a Folder for the BAS ID in the Projects Folder ......B-3
Figure 35. NAME Field in Census Data vs Local Boundary Data..................................................B-4
Figure 36. Appropriate Attribution for COUSUB or AIANNH Changes ........................................B-4
Figure 37. Partnership Tools Menu with Create Changes Tool Selected ....................................B-5
Figure 38. Create Changes Window ...........................................................................................B-5
Figure 39. Partnership Tools Menu with Geodatabase ..............................................................B-6
Figure 40. Partnership Tools Menu with Sliver Blaster Selected ................................................B-6
Figure 41. Sliver Blaster Window ...............................................................................................B-7
Figure 42. Partnership Tools Menu with Format Working MXD Selected ..................................B-7
Figure 43. Format Working MXD Window .................................................................................B-7
Figure 44. Projects Submenu with mxd file Selected .................................................................B-8
Figure 45. Partnership Tools Menu with Attribute Check Selected ............................................B-8
Figure 46. Attribute Check Window ...........................................................................................B-9
Figure 47. Projects Submenu Showing an attribute_check Text File ..........................................B-9
Figure 48. Partnership Tools Menu with Export Submission Files Selected ...............................B-9
Figure 49. Export Submission Files Window .............................................................................B-10
Figure 50. Suggested Map Symbolization ..................................................................................C-2
Figure 51. Filtering Data .............................................................................................................C-3
Figure 52. Export Data Window .................................................................................................C-4
Figure 53. Finalizing the Merge Process .....................................................................................C-4
Figure 54. Finalizing the Symmetrical Difference Process ..........................................................C-5
Figure 55. Finalizing the Union Process ......................................................................................C-6
Figure 56. Locating the Union Shapefile .....................................................................................C-7
Figure 57. Small Slivers That Should Be Deleted ........................................................................C-8
Figure 58. Polygons (Before and After) Snapped to Roads or Rivers ..........................................C-8

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

vii

INTRODUCTION
A.

The Boundary and Annexation Survey

The U.S. Census Bureau conducts the Boundary and Annexation Survey (BAS) annually to collect
information about selected legally defined geographic areas, such as counties (and equivalent
areas), incorporated places, minor civil divisions (MCDs), federally recognized American Indian
Areas (AIAs) — including reservations, off-reservation trust lands and tribal subdivisions, and
Hawaiian Homelands. BAS also provides an opportunity for participants to review the names
and geographic relationships for these areas. Title 13, Section 6, United States Code authorizes
this survey.
The Census Bureau uses the boundary information collected during BAS to tabulate data for the
decennial and economic censuses, and to support the yearly delivery of the American
Community Survey (ACS) data. Maintaining correct boundaries and boundary-to-feature
relationships through BAS helps ensure that the Census Bureau assigns the appropriate housing
and population counts to each government.
In compliance with the Office of Management and Budget Circular A-16, BAS supports the
Census Bureau’s spatial data steward responsibilities for the Federal Geographic Data
Committee (FGDC) and the Geospatial One-Stop by updating the inventory and boundaries of
governments.
In addition, BAS is the source of up-to-date information on changes to the boundaries, codes
and names of incorporated places, MCDs, counties (and equivalent areas), Hawaiian
Homelands, and federally recognized AIAs, which include reservations and off-reservation trust
lands used by the U.S. Geological Survey (USGS), the National Map, and the Geographic Names
Information System (GNIS). Please visit the BAS program website at
.
For more information on BAS, please view the BAS video series on the Census Bureau’s BAS
website at .

Key Dates for BAS Respondents

January 1—Boundary changes must be legally in effect on or before this date to be reported in
the current survey year.
March 1— Boundary updates returned by this date will be reflected in the ACS and in next
year’s BAS materials.
May 31—Boundary updates returned by this date will be reflected in next year’s BAS materials.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

viii

Legal Disputes

If the Census Bureau discovers that an area of land is in dispute between two or more
jurisdictions, the Census Bureau will not make any boundary corrections until the parties come
to a written agreement, or there is a documented final court decision regarding the dispute.
To learn more, please contact the Census Bureau Legal Office at 1-301-763-9844.
For disputes involving tribal areas, the Census Bureau must defer to the Office of the Solicitor at
the Department of the Interior for a legal opinion. Often complicated land issues require an
extended period of time for resolution, and in those cases, the Census Bureau will retain the
current boundary in the database until a legal opinion is issued by the Solicitor's office.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

CHAPTER 1 DIGITAL BAS REQUIREMENTS
1.1

Digital BAS Participation Requirements
1. All participants must create a new shapefile of boundary change polygons based off of the
current Census Bureau boundary. Submissions containing only a whole entity boundary
shapefile of the current local data will not be accepted.
2. All participants must provide legal documentation (such as trust deeds and Federal Register
Notice) and effective dates for all legal boundary changes (new reservation land and/or offreservation trust land).
3. Each non-legal boundary correction must contain proper update documentation according to
boundary correction guidelines listed below in 1.2, Tribal Areas that can be Submitted through
BAS, or the Census Bureau will not make the correction for this BAS cycle.
4. All participants must use the Secure Web Incoming Module (SWIM) to submit their changes to
the Census Bureau. Due to security requirements, the Census Bureau cannot accept submissions
via File Transfer Protocol (FTP), email or any protocol other than the SWIM site. For details on
registering and using SWIM, please see 5.7.7, Submitting Digital Files through SWIM. To access
SWIM, enter the following URL in a new browser window: .
5. All participants must provide current information for the tribal BAS point of contact, the person
updating the shapefiles, and the name of the Tribal Chairs.

Note:

1.2

For participants already familiar with Geographic Information Systems (GIS) and BAS updating
procedures, Appendix B and Appendix C provide step-by-step guidelines for making updates.

Tribal Areas that can be Submitted through BAS

The following can be updated through Tribal BAS:
•

•

Federal American Indian Reservations are areas that have been set aside by the United States
for the use of tribes, the exterior boundaries of which are more particularly defined in the final
tribal treaties, agreements, executive orders, federal statutes, secretarial orders, or judicial
determinations.
Federal Off-Reservation Trust Lands are areas for which the United States holds title in trust for
the benefit of a tribe (tribal trust land) or for an individual American Indian (individual trust
land).

Note:

Trust lands may be located on or off a reservation; however, the Census Bureau tabulates
data only for off-reservation trust lands. Please do not submit on-reservation trust land
because the Census Bureau can only show the exterior reservation boundary. The Census
Bureau does not identify fee land (or land in fee simple status) or restricted fee lands as
specific geographic areas.

•

Tribal Subdivisions are legal administrative subdivisions of federally recognized American Indian
reservations and off-reservation trust lands, and are described as additions, administrative

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

•

areas, areas, chapters, county districts, communities, districts, or segments. These are internal
units of self-government or administration that serve social, cultural, and/or economic purposes
for the American Indians on the reservations and off-reservation trust lands.
Hawaiian Homelands are areas held in trust for Native Hawaiians by the state of Hawaii,
pursuant to the Hawaiian Homes Commission Act of 1920, as amended.

Table 1 shows the specific changes allowed for each government type.
Table 1: Available Change Types by Government Type
Government Type

Available Change Types

Hawaiian Homeland (HHL)

Reservation / Trust Land

•
•
•
•
•
•
•
•
•

•
•
•

Tribal Subdivision

1.3

•
•
•
•
•
•
•
•
•
•

New Entity
Deleted Entity
Addition
Deletion
Boundary Correction (add)
Boundary Correction (remove)
Geographic Corridor
Geographic Offset
New Entity (No Land previously; Have
Reservation land and adding Trust Lands for
first time, or Have Trust land and are adding
Reservation for first time)
Deleted Entity (changing from Reservation to
Trust land or Trust Land to Reservation)
Addition (adding to type of geography that
already exists)
Deletion (Deleting a portion of Reservation or
Trust Land)
Boundary Correction (add)
Boundary Correction (remove)
Geographic Corridor
Geographic Offset
Adding tribal subdivisions for first time
Deleting tribal subdivisions all together
Addition
Deletion
Boundary Correction (add)
Boundary Correction (remove)

BAS Informational and Tutorial Videos

The Census Bureau created training videos to give BAS participants detailed instructions and
information on how to report and submit BAS changes. These videos are available on the BAS
website at: .
If there are any questions or concerns about the participation requirements, contact the Census
Bureau at 1-800-972-5651 or .

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

CHAPTER 2 TOPOLOGICAL RELATIONSHIPS AND SPATIAL ACCURACY
The Geography Division of the Census Bureau is responsible for developing geographic
applications and executing related activities needed to support the Census Bureau in collecting
and disseminating census data. For more than twenty years, the Census Bureau’s Master
Address File and Topologically Integrated Geographic Encoding and Reference (MAF/TIGER)
system has been a critical resource for supporting the Census Bureau Geographic Partnership
Programs.
The following section will describe how the Census Bureau uses a topologically integrated
system and how this differs from traditional GIS, which use separate layers of data.

2.1

Topological Relationships in the MAF/TIGER System

At the Census Bureau, topology is described as the spatial relationship between different levels
of geography. The MAF/TIGER system is a geographic database in which the topological
structures define the location, connection, and relationships of streets, rivers, railroads, and
other features. These topological structures help define the geographic areas for which the
Census Bureau tabulates data.
Instead of having a separate layer for each feature class (roads, boundaries, etc.) all MAF/TIGER
system information is stored in one layer or file. See Figure 1 for a sample of a topologically
integrated file in the MAF/TIGER system.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 1. Topological Integration of Four Classes
This example shows the topological integration of four different feature
classes into one layer. One road feature represents not only a road, but also
a block boundary, AIA boundary, and a school district boundary.

2.2

GIS and Spatial Accuracy

In a GIS, feature classes are often not topologically integrated; they are separated into
individual layers. When these layers are overlaid in a GIS, there may be boundary
misalignments due to the nature of the data. These non-topologically integrated layers could
cause issues in the MAF/TIGER system. Figure 2 and Figure 3 show how files that are not
topologically integrated might appear in a GIS when overlaid.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 2. Overlay of Four Feature Classes
This example shows an overlay of four different feature classes.
Notice how the topological relationship is compromised. The block,
AIA, and school district boundaries, which are supposed to follow
the road feature, no longer align with the road in several locations.

Figure 3. GIS AIA Boundary Does Not Follow Road Feature
This example shows a situation where a local GIS AIA boundary does
not follow a road feature. Assuming that the boundary follows the
road feature, changing the AIA boundary to match the local file
exactly and become misaligned (see arrows) would dissolve the
topological relationship in the MAF/TIGER system.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

The spatial differences between local GIS data and the Census Bureau’s topologically integrated
file are often very small (less than ten feet) and can create boundary-to-feature relationship
issues for the Census Bureau. Instructions on how to review digital submissions for small spatial
boundary corrections are given in 5.6, Reviewing Changes to the Census Bureau Shapefiles. It
also lists some of the potential consequences of making spatial boundary corrections that
dissolve the topological relationships present in the MAF/TIGER system.
To find step-by-step instructions of suggested methods for correctly making boundary changes,
please see Appendix B and Appendix C.

2.3

Census Bureau Topology Training Video

The Census Bureau created a video on the subject of topology and why topology is important to
BAS. For more information, please go to to watch the video.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

CHAPTER 3 CENSUS BUREAU PROVIDED SHAPEFILES
The Census Bureau provides data layers in Esri shapefile format for download on the BAS
website. Regardless of the number of geographic polygon-based shapefiles each participant
downloads and edits, there is only one shapefile for the linear feature network for each county.
See Table 2 for the names of the shapefiles.
Note: Shapefiles are ‘county’ based so it is necessary to download all the shapefiles for each county in
which the tribe has reservation and/or off-reservation trust lands.
Table 2: BAS Shapefile Naming Conventions
Government Type

Shapefile Naming Convention

Federal Reservations and Off-Reservation Trust Lands

PVS_20_v2_aial_.shp

Tribal Subdivision

PVS_20_v2_aitsl_.shp

Hawaiian Homeland

PVS_20_v2_hhl_.shp

Edges (Roads, Rail, Hydro, etc.)

PVS_20_v2_edges_.shp

Area Landmarks

PVS_20_v2_arealm_.shp

Point Landmarks

PVS_20_v2_pointlm_.shp

Hydrographic Area

PVS_20_v2_water_.shp

Geographic Offsets / Corridors

PVS_20_v2_offset_.shp

Please download shapefiles from the BAS website at

in order to review the boundaries and submit changes.
Note:

represents the two-digit state code and three-digit county code.

All shapefiles provided by the Census Bureau are in the following unprojected geographic-based
coordinate system:
•
•
•
•
•
•
•
•

3.1

Geographic Coordinate System – North American Datum 1983 (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.

Federal Information Processing Standards (FIPS) Codes

The Census Bureau recommends using FIPS codes to identify governments such as counties,
AIAs, etc. Using a standard coding scheme facilitates the digital exchange of data. The Census
Bureau includes these codes in the BAS shapefiles in the fields that end in ‘FP’. The codes can
be found online at . If there are any questions, contact the Census Bureau at 1800-972-5651 or .
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

CHAPTER 4 CENSUS BUREAU GEOCODING
Geocoding is how the Census Bureau codes the location of the population within the legal
boundaries of a geographic area. There are two primary methods of geocoding used by the
Census Bureau, and both of these involve coding an address to a spatial polygon. One uses
Global Positioning System (GPS) technology to create a Master Address File (MAF) structure
point (MSP) and the other uses address ranges for geocoding.

4.1

MAF Structure Point (MSP) Geocoding

A field worker stands in front of a house or living quarters, and records the physical location
with a GPS device (Figure 4). Usually, the GPS point should fall very close to the front door of
the house. However, since GPS points were collected in the field, real-world obstacles like
locked fences, poor satellite reception, or even aggressive dogs might sometimes prevent the
worker from gaining access to the front door. In these circumstances, the worker may have to
take the GPS coordinate from the sidewalk or side of the road.

Figure 4. GPS Method of Geocoding
Notice that it is occasionally not possible for the field worker to go all the
way to the front door due to unforeseen circumstances, like the fence or the
dog shown above. Thus, the MSP (represented here by the red pins) can
sometimes fall within the road or the road right-of-way.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

4.2

Address Range Geocoding

When no MSP is available, the Census Bureau codes houses and living quarters according to a
potential range of addresses associated with the adjacent stretch of road (Figure 5).

Figure 5. Address Range Method of Geocoding
When it is not possible to collect an MSP, houses are geocoded according to
their placement along a range of potential addresses along that road. Since
the address has a relationship with the road, boundaries placed on frontlot-lines will lead to mis-geocoding unless an offset flag is used.

While the two methods of geocoding differ greatly, both rely heavily on the integrated nature
of the MAF/TIGER system. These geocoding methods are affected by the way streets and
boundaries are represented in relation to one another. This interdependence between streets,
boundaries, and geocoding means that Census Bureau representations of legal boundaries may
sometimes differ from other representations (e.g., in local or state GIS). This is especially true
regarding geographic corridors and offsets that follow road right of ways (or the front-lot-lines
of parcels). In both of the examples above, delineating a boundary along the front-lot-line will
tend to increase the risk of incorrect geocoding. As a result, using the road centerline as a
boundary is the safer method.
Important:

U.S. Census Bureau

When completing a BAS submission in which a road or road right-of-way is owned or
maintained by a place or AIA but the adjacent housing is not, the respondent should use
the centerline of the road (not the front-lot-line) as the boundary whenever possible.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

CHAPTER 5 UPDATING THE CENSUS BUREAU SHAPEFILES
Census Bureau shapefiles downloaded from the partnership verification shapefiles (PVS)
download page can be used to create new shapefiles for boundary and/or linear feature
changes that have occurred since the last BAS update. Step-by-step instructions for these
procedures can be found in Appendix B and Appendix C and in BAS video series at
.
Note:

5.1

If there are problems with the processing of returned files, the Census Bureau will email a
feedback document requesting clarification of any issues. If the problem cannot be resolved
before the project deadline, the changes in question will not be made during the current BAS.

General File Setup Guidelines

After downloading the shapefiles from the PVS download page, follow these procedures before
beginning actual updates:
•
•
•

5.2

Open the downloaded ZIP file to verify its contents.
Copy the shapefiles into a directory on a server/hard drive.
Open the shapefiles with GIS software.

Changing the Map Projection

Census Bureau files are in GCS NAD83 format and can be projected into any local coordinate
system/projection. Most GIS software packages will allow users to transform file coordinate
systems and projections. For example, if using ArcGIS, use its ‘Project tool’ in ArcToolbox.
Shapefile extracts contain defined projection information in the *.prj file. ArcGIS accesses the
*.prj file for projection information so there is no need to define these parameters before
changing the file coordinate systems.
When updates are complete, participants may submit the boundary change shapefile using any
local coordinate system/projection if the shapefile contains a *.prj file or spatial reference
materials such as metadata.

5.3

Boundary Changes

In order to update the MAF/TIGER system, participants must create a separate change polygon
layer for each updated government type (AIA, tribal subdivision, or Hawaiian Homeland). Please
create change polygons in relation to the current MAF/TIGER boundary.
Appendix B and Appendix C provide two examples for creating annexation and deannexation,
boundary correction, new incorporation, geographic corridor, and geographic offset change
polygons. See Appendix C for specific tools used to make changes to files.
Additionally, Appendix B covers the steps required to complete a submission using the BAS
Partnership Toolbox. The toolbox includes tools to download Census Bureau data, use the
Union geoprocessing tool to create a changes layer containing all the differences between
Census Bureau and local boundaries, and create a ZIP file for submission through SWIM.
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Please review any boundary change polygons before submitting them (5.7, Additional
Information Review).

5.3.1

Additions and Deletions

The Census Bureau will accept additions and deletions from AIAs and Hawaiian Homelands,
such as new reservation lands and off-reservation trust lands. Each addition or deletion change
polygon must have the required attributes and corresponding change type populated, as seen
in Table 3. The Census Bureau will snap any addition or deletion to a MAF/TIGER feature when
it exists within thirty feet of that feature.
Note:

Enter the name of the jurisdiction (AIA or Hawaiian Homeland) adding or deleting the area in
the NAME field.
Table 3: Additions and Deletions
NAME

CHNG_TYPE

EFF_DATE

AUTHTYPE

DOCU

Addition

X (‘A’)

Deletion

X (‘D’)

RELATE

(Note: ‘X’ = Required Field)

5.3.2

Boundary Corrections

The Census Bureau will also accept specific boundary corrections from AIAs and Hawaiian
Homelands. As with additions and deletions, the participant must create individual change
polygons for each boundary correction. Each boundary correction must also have the required
attributes and corresponding change type populated, as seen in Table 4, or the Census Bureau
will reject them.
Note:

Enter the name of the jurisdiction the boundary correction is for in the NAME field.
Table 4: Boundary Corrections

Boundary
Correction

NAME

CHNG_TYPE

X (‘B’)

EFF_DATE

AUTHTYPE

DOCU

AREA

RELATE
X (’IN’, ‘OUT’)

(Note: ‘X’ = Required Field)

The Census Bureau uses a topologically integrated database. As a result, the Census Bureau
cannot process all types of boundary corrections for inclusion in the MAF/TIGER system. The
Census Bureau will accept and process properly documented boundary corrections during the
current BAS cycle that spatially interact with (abut) other BAS legal changes (addition, deletion,
corridor, offset) and meet both of the following two conditions:
•
•

In situations where the existing boundary has been digitized incorrectly or appears in the
incorrect location due to Census Bureau activities.
Where the overall shape of the geographic area is maintained, and no feature-to-boundary
relationships are dissolved.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

The Census Bureau will reject boundary corrections:
•
•

•
Note:

5.3.3

That dissolve boundary-to-feature relationships (roads, rivers, railroads, etc.) if the difference is
less than thirty feet.
Which are greater than one square mile, or not contiguous with the rest of the government
boundary. These boundary corrections may be part of additions which were never reported to
the Census Bureau. If so, legal documentation should be provided; or
That have a width of less than thirty feet over the entire polygon.
Remember that the Census Bureau will snap any boundary correction to a MAF/TIGER feature
when it exists within thirty feet of that feature.

Tribal Subdivisions

Tribes may submit the boundaries for one type of administrative area within their
reservation(s) and/or off-reservation trust lands (land base) for inclusion in the MAF/TIGER
system. The Census Bureau will consider any type of unit of self-government or administration
as a “tribal subdivision.” Tribal subdivisions should cover all, or most, of the tribe’s land base. If
a tribe has more than one type of distinct administrative area that could qualify as a tribal
subdivision (such as tribal election districts, tribal water districts, or health service areas with
different boundaries), the tribe may submit only one type of subdivision. Tribal subdivisions can
be considered either active (A) or inactive (I). Active subdivisions are defined as having a
functioning government with elected officials that provide programs and services. Inactive
subdivisions have no functioning government or elected officials and receive services solely
from the tribe. Some examples of areas submitted as tribal subdivisions are:
•
•
•
•
•
•
•
•
•

Areas used by a tribe for the election of tribal government officials (such as districts or precincts
used for the election of tribal council members).
Areas used by a tribal government for tax purposes.
Areas used by a tribal government for the provision of general services or specified services,
such as:
Water districts.
Health service areas.
Emergency service delivery areas (such as 911, fire, and/or police); or
Grazing districts or range units.
Historical or traditional areas recognized by a tribal government.
Local tribal community governments.

5.3.3.1 New Tribal Subdivisions
AIA participants may submit new tribal subdivisions through Tribal Digital BAS. As with other
change types, an individual change polygon must be created for each new tribal subdivision and
possess the required attributes and the corresponding change type field must be populated
(see

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Table 5).
Note:

Enter the name of the new jurisdiction in the NAME field.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Table 5: New Entities

New Entity

NAME

CHNG_TYPE

EFF_DATE

AUTHTYPE

DOCU

X
(subdivision
name)

X (‘E’)

X
(date of tribal
resolution)

X
(tribal resolution
number)

RELATE

(Note: ‘X’ = Required Field)

5.3.3.2 Criteria for Defining Tribal Subdivisions
•
•
•
•
•

•

The delineation of tribal subdivisions is restricted to the area contained within reservation(s)
and/or associated off-reservation trust lands (land base).
There is no minimum population threshold for a tribal subdivision.
Tribal subdivisions should cover all, or most, of the tribe’s land base.
A tribal subdivision may be discontinuous.
A tribe may designate only ONE type of tribal subdivision. If a tribe has more than one level of
tribal subdivisions within its land base, the Census Bureau recommends delineating subdivisions
corresponding to the lowest geographic level (those geographic areas containing the smallest
area) of the tribe’s administrative hierarchy.
Tribal subdivisions should not be based solely on land ownership or other cadastral areas, nor
should they consist of divisions based on the U.S. Public Land Survey System (PLSS) of
townships, ranges, and sections, if these areas have no governmental or administrative function
for the tribe.
Some examples of descriptors for tribal subdivisions are:
o District.
o Community.
o Area.
o Chapter.
o Segment.
o Administrative Area.
o Addition.
o County District.

5.3.3.3 Updating Tribal Subdivisions
Tribal Subdivisions are updated in a similar manner to boundary changes (such as additions or
deletions). In order to submit tribal subdivision updates, please create a separate tribal
subdivision change polygon layer. Updates that can be made to tribal subdivisions include
additions, deletions, boundary corrections (adding and removing area), and creating new tribal
subdivisions. Please note that all tribal subdivision updates (additions, deletions, name changes,
and new tribal subdivisions), with the exception of boundary corrections, require a tribal
resolution. Table 8, Table 9, and Table 10 display the required attributes for each of the change
types. Review the example processes in Appendix B and Appendix C for information on how to
create change polygons. Change polygons for tribal subdivisions may be created in the same
manner as for reservations and off-reservation trust lands.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.3.4

Geographic Corridors

The Census Bureau geocodes addresses based on the street centerline. If the geocoding of
these addresses would result in the assignment of population to the incorrect geographic area,
participants should create a geographic corridor.
A geographic corridor is an area that includes only the road right-of-way and does not contain
any structures addressed to either side of the street. Figure 6 shows a corridor (shown in color)
created where the AIA owns the right-of-way, but the housing units are not included within the
AIA. Without a corridor, the housing units along this road would be included in the AIA.
Figure 7 shows that the right-of-way belongs in the unincorporated area, while the housing
units are included in the AIA (shown in color). This is important for some governments because
they are portraying that the government is not responsible for road maintenance. This is not
relevant for Census Bureau tabulations and is not easy to depict in MAF/TIGER system.
This type of corridor should not be included in a BAS response.

Figure 6. Geographic Corridor Created
Figure 7. Geographic Corridor Not Created
The image on the left (Figure 6) shows that a geographic corridor should be
created to allow for proper geocoding of homes. The image on the right
(Figure 7) shows that the geographic corridor should not be created and
features should be snapped to the street centerline.

The Census Bureau will accept new geographic corridors. Please create individual change
polygons for each new geographic corridor. Each change polygon must have the required
attributes and corresponding change type populated, as seen in Table 6. In the NAME field,
enter the name of the jurisdiction gaining or losing the area associated with the corridor. In the
RELATE field, indicate whether the change is adding IN or taking OUT (removing) the corridor.
Table 6: Geographic Corridors

Geographic
Corridor

NAME

CHNG_TYPE

X (‘C’)

EFF_DATE

AUTHTYPE

DOCU

RELATE
X (‘IN’, ‘OUT’)

(Note: ‘X’ = Required Field)

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.3.5

Geographic Offsets

A geographic offset is an area claimed by a government that is only on one side of a road and
does not include structures addressed to that side of the road.
The Census Bureau is aware that many governments base their legal boundaries on cadastral
(parcel-based) right-of-way mapping. The Census Bureau bases their maps on spatial data that
is topologically integrated. This makes the maintenance of geographic offsets inefficient.
Snapping a government boundary to the centerline wherever applicable will help to establish
more accurate population counts. If a boundary is the front-lot-line, Census Bureau strongly
prefers that the boundary be snapped to the road. If a boundary is at the rear of a lot, then
please depict it as such. Figure 8 depicts a cadastral (parcel-based) boundary map and Figure 9
shows how the boundary should be reported when sent to the Census Bureau.

Figure 8. Cadastral Data
Figure 9. Same Data Edited to Census Bureau Requirements
On the left in Figure 8 is an example of cadastral data. Figure 9 on the right,
is the same area shown edited to conform to census requirements.

The Census Bureau will accept new geographic offsets. Please create individual change
polygons for each new geographic offset. Each change polygon must have the required
attributes and corresponding change type populated, as seen in Table 7. In the NAME field,
enter the name of the jurisdiction gaining or losing the area. In the RELATE field, indicate
whether the change is adding IN or taking OUT (removing) the area represented as an offset.
Table 7: Geographic Offsets

Geographic
Offset

NAME

CHNG_TYPE

X (‘F’)

EFF_DATE

AUTHTYPE

DOCU

RELATE
X (’IN’, ‘OUT’)

(Note: ‘X’ = Required Field)

The Census Bureau has included an “offset” shapefile in the BAS materials
(PVS_20_v2_offset_.shp), so that the participants’ jurisdiction can be checked for any
existing corridors or offsets. While the Census Bureau prefers that new offsets are not created,
(see above), this information can be helpful in determining if current boundaries are correct.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.4

Linear Feature Updates

The Census Bureau will accept linear feature modifications when needed. The easiest method
of updating linear features is to edit the PVS_20_v2_edges_.shp included in the
partnership shapefiles and export the modified or added records to a new separate linear
feature update layer. This will ensure all required fields are present and populated before
submission. The general guidelines for updating linear features are:
•
•
•

Note:

5.4.1

If a road, subdivision, etc. is missing from the Census Bureau’s feature network, add the
feature(s), enter ‘AL’ in the CHNG_TYPE field, and provide the name (FULLNAME) and MTFCC.
If a feature that does not exist is in the Census Bureau’s feature network, mark the feature for
deletion by entering ‘DL’ in the CHNG_TYPE field.
If a feature is in the incorrect location in the Census Bureau’s feature network, mark the feature
for deletion 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 other features.
A video on updating linear features is available in the BAS video series at
.

Adding, Deleting, Renaming, and Recoding Linear Features

Each linear feature update must have the required attributes and corresponding change type
populated as seen in Table 8. Preserve the TIGER/Line ID (TLID) in the TLID field when
requesting to modify or delete features to ensure the correct features are affected. A TLID is
not required for any features being added though an MTFCC is required for new features.
Table 8: Linear Feature Updates
CHNG_TYPE

Note:

5.4.2

TLID

Add Feature

X (‘AL’)

Delete Feature

X (‘DL’)

Rename Feature

X (‘CA’)

Recode Feature
X (‘CA’)
(Note: ‘X’ = Required Field)

FULLNAME

MTFCC

X
X

A list of MAF/TIGER Feature Classification Code (MTFCC) codes can be found in Appendix D.

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. As existing address ranges cannot be shown in the
Census Bureau’s outgoing shapefiles, it is recommended that participants only add address
ranges to new features (see Table 9).

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Table 9: Address Range Updates

Address Ranges

CHNG_TYPE

FULLNAME

MTFCC

LTOADD

RTOADD

LFROMADD

RFROMADD

X (‘AL’)

(Note: ‘X’ = Required Field)

5.5

Area Landmarks, Hydrographic Areas, and Point Landmarks

5.5.1

Area Landmark/Hydrographic Area Updates

The Census Bureau accepts updates to area landmarks and hydrographic areas in a similar
manner to legal boundary changes. However, area landmarks and hydrographic areas are not
legal governments, so no documentation or effective dates are required.
In order to submit area landmark and hydrographic area updates, create a separate change
polygon layer. Updates to area landmarks and hydrographic areas include:
•
•
•
•

Boundary corrections (adding and removing area).
Creating a new area landmark or hydrographic area.
Removing an area landmark or hydrographic area.
Name changes.

Figure 10. A Boundary Correction to Park A

Each area landmark or hydrographic area update must have the required attributes and
corresponding change type populated. Preserve the Area ID in the AREAID field when
requesting to modify or delete landmarks to ensure the correct areas are affected. An AREAID is
not required for any areas being added though an MTFCC is required for new landmarks (refer
to Table 10).

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Table 10: Landmarks and Hydrographic Areas

Boundary Correction
(Add Area)
Boundary Correction
(Remove Area)

FULLNAME

CHNG_TYPE

RELATE

X (‘B’)

X (‘IN’)

X (‘B’)

X (‘OUT’)

Delete Landmark

MTFCC

AREAID

X (‘D’)

X
X

Change Landmark Name

X (‘G’)

New Landmark

X (‘E’)

(Note: ‘X’ = Required Field)

The steps in Appendix C provide information on how to create change polygons using ArcGIS.
While the sample processes are written for legal boundary changes, the same methods apply
for creating change polygons for area landmarks and hydrographic areas. When adding new
area landmarks or hydrographic areas, only add the following types of areas:
•
•
•
•
•
•

Water bodies.
Glaciers.
Airports.
Cemeteries.
Golf courses.
Parks.

The Census Bureau cannot add other types of areas at this time (although some may already
exist in the MAF/TIGER system). The acceptable MTFCC codes for new area landmarks or
hydrographic areas are listed in Table 11.
Table 11: Acceptable MTFCCs for New Area Landmarks/Hydrographic Areas
MTFCC
H2030*
H2040*
H2041*
H2051*
H2081*
C3023
K1231
K1235
K1236
K1237
K2110
K2180*
K2181
K2182
K2183
K2184
K2185
K2186
K2187
K2188
U.S. Census Bureau

Description
Lake/Pond
Reservoir
Treatment Pond
Bay/Estuary/Gulf/Sound
Glacier
Island
Hospital/Hospice/Urgent Care Facility
Juvenile Institution
Local Jail or Detention Center
Federal Penitentiary, State Prison, or Prison Farm
Military Installation
Park
National Park Service Land
National Forest or Other Federal Land
Tribal Park, Forest, or Recreation Area
State Park, Forest, or Recreation Area
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
Boundary and Annexation Survey Tribal Respondent Guide: Digital

MTFCC

Description

K2189
Private Park, Forest, or Recreation Area
K2190
Other Park, Forest, or Recreation Area (quasi-public, independent park, commission, etc.)
K2424
Marina
K2540
University or College
K2457*
Airport – Area Representation
K2561
Golf Course
K2582*
Cemetery
*May not be edited.

Note:

If adding an MTFCC K2457 (Airport – Area Representation) area landmark, please limit the
updates to major airports (major regional and international airports). The feature should show
the full extent of the airport facility, that it, do not limit the addition to simply the landing
strips.

Area Landmark/Hydrographic Area Changes May Be Delayed
The Census Bureau prioritizes boundary changes to legal areas to meet ACS and BAS deadlines.
Therefore, there may be delays in incorporating area landmark and hydrographic area changes to the
MAF/TIGER System. Please do not resubmit any changes that were sent during the previous year’s BAS.
The Census Bureau is working on incorporating those changes, and they will be reflected in the next
year’s BAS materials.

5.5.2

Point Landmark Updates

The Census Bureau accepts updates to point landmarks. Please submit point landmark updates
as a separate point landmark update layer. Updates to point landmarks include:
•
•
•

Adding a new point landmark.
Deleting an existing point landmark.
Renaming a point landmark.

The Census Bureau also cannot delete or modify any point landmarks imported from the USGS
GNIS database. Changes submitted for the following types of landmarks may be left unchanged:
•
•
•
•
•

K2451 (Airport).
K2582 (Cemetery).
C3022 (Summit or Pillar).
C3081 (Locale or Populated Place).
C3061 (Cul-de-sacs).

Each point landmark update must have the required attributes and corresponding change type
populated. Preserve the POINTID in the POINTID field when requesting to modify or delete
point landmarks to ensure the correct landmarks are affected. A POINTID is not required for
any landmarks being added though an MTFCC is required for new landmarks.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Table 12: Point Landmark Updates

New Point Landmark

FULLNAME

CHNG_TYPE

MTFCC

X (‘E’)

Delete Point Landmark
Change Name

POINTID

X (‘D’)

X (‘G’)

(Note: ‘X’ = Required Field)

Due to Title 13 privacy concerns, any landmark with an MTFCC shown in Table 13: Restricted
Point Landmark MTFCC Codes below cannot be added to the MAF/TIGER System as a point
landmark. The MAF/TIGER System no longer maintains any point landmarks with these MTFCCs.
Landmarks with these codes could identify a residence or private business. Thus, it is also
important not to add any of the point landmark types shown in the table using alternative
MTFCCs.
Table 13: Restricted Point Landmark MTFCC Codes
MTFCC
K1100
K1121
K1122
K1223
K1226
K1227
K1228
K1229
K1232
K1233
K1234
K1235
K1241
K1251
K1299
K2100
K2197
K2300
K2361
K2362
K2363
K2364
K2366
K2464
K2500
K2564

U.S. Census Bureau

Description
Housing Unit Location
Apartment Building or Complex
Rooming or Boarding House
Trailer Court or Mobile Home Park
Housing Facility/Dormitory for Workers
Hotel, Motel, Resort, Spa, Hostel, YMCA, or YWCA
Campground
Shelter or Mission
Halfway House/Group Home
Nursing Home, Retirement Home, or Home for the Aged
County Home or Poor Farm
Juvenile Institution
Sorority, Fraternity, or College Dormitory
Military Group Quarters
Other Group Quarters Location
Governmental
Mixed Use/Other Non-residential
Commercial Workplace
Shopping Center or Major Retail Center
Industrial Building or Industrial Park
Office Building or Office Park
Farm/Vineyard/Winery/Orchard
Other Employment Center
Marina
Other Workplace
Amusement Center

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Point Landmark Changes May Be Delayed
The Census Bureau prioritizes boundary changes to legal areas to meet ACS and BAS deadlines. Therefore,
there may be delays in incorporating point landmark changes to the MAF/TIGER system. Please do not
resubmit any changes that were sent during the previous year’s BAS. The Census Bureau is working on
incorporating those changes, and they will be reflected in the next year’s BAS materials.

5.6

Reviewing Changes to the Census Bureau Shapefiles

Please review all changes to ensure that they are intentional and correct. The Census Bureau
has created videos with information on many of the topics below. Videos can be found on the
web at: .

5.6.1

Boundary-to-Feature Relationships

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 (see 2.1, Topological
Relationships in the MAF/TIGER system). Therefore, snap boundaries to street centerlines (or
rivers, railroads, etc.) wherever applicable. This will help establish a more accurate population
count for tribal governments.
Figure 11 and Figure 12 show situations where boundary changes should be snapped to existing
linear features. The Census Bureau will snap boundary changes to any linear feature that is
correctly located within thirty feet of the change.

Figure 11. Boundary Corrections Not Snapped to Existing Linear Features
These boundary corrections are not snapped to existing linear features in
the MAF/TIGER system. Both boundary corrections should be snapped to
centerlines or population may be assigned to incorrect governments.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 12. Addition Created without Snapping to Centerlines
This is an example of an addition created without snapping to existing
centerlines in the MAF/TIGER system. Unless the boundary is snapped to
centerlines, some of the population may be assigned to an incorrect
government.

The Census Bureau will not accept boundary corrections that dissolve the current relationship
between an existing boundary and linear feature without specific instructions that the
relationship is incorrect. The Census Bureau will not incorporate any boundary corrections that
create thirty feet or less of gap or overlap between the existing linear feature and boundary
into the MAF/TIGER system. Figure 13 and Figure 14 show examples of changes that will not be
accepted.

Figure 13. Small Spatial Correction Not Incorporated
Small spatial boundary corrections would dissolve the relationship with the
river. These boundary corrections will not be incorporated into the
MAF/TIGER system.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 14. Small Spatial Correction Not Accepted
Small spatial boundary corrections would dissolve the boundary-to-feature
relationship with multiple streets. Incorporating these changes would affect
the population counts for the area. Therefore, the Census Bureau will not
accept these small boundary corrections.

5.6.2

Large Boundary Corrections

The Census Bureau will not accept large boundary corrections to a government without the
appropriate legal documentation (such as Trust Deed, Executive Order, new legal opinion, Act
of Congress or Federal Register Notice) and effective dates. These large boundary corrections
(Figure 15) may be legal boundary changes that occurred in the past and were never reported
to the Census Bureau. Please submit the appropriate legal documentation number and
effective date so that the changes may be incorporated into the MAF/TIGER system.

Figure 15. Large Boundary Corrections
Without the appropriate documentation, the Census Bureau will not accept
large boundary corrections.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Note:

5.6.3

There may be a few instances when large boundary corrections need to be made because of
incorrect digitizing or where the boundary appears in the incorrect location due to other
Census Bureau activities.

Required Attribute Information

It is important to review each change polygon and confirm that the correct attribute
information is included. Without the correct attribute information, the Census Bureau will be
unable to process and incorporate the changes into the MAF/TIGER system. See 5.3, Boundary
Changes for the required attribute information and corresponding change type codes.

5.6.4

Appropriate Projection Information

It is important that the appropriate projection information is included. Each update layer
submitted should contain a correct *.prj file so that the Census Bureau can convert the
projection back to GCS_NAD83. If the GIS being used cannot create a *.prj file, include the
projection information in metadata. This is critical for the Census Bureau to be able to process
the file and incorporate the updates into the MAF/TIGER system.

5.6.5

Linear Feature Updates

Please review linear feature changes to ensure that they align with the features currently in the
MAF/TIGER system. If linear feature changes do not align with current MAF/TIGER linear
features, the Census Bureau may not incorporate the submitted updates (Figure 16 and
Figure 17).

Figure 16. New Road Features, Not Added to Existing Road
Figure 17. New Road Features, Correctly Added
The image on the left (Figure 16) shows new road features added to the
existing feature network, but not connected to existing road features. The
image on the right (Figure 17) shows the correction connecting the new
roads to the existing road features.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.7

Additional Information Review

The Census Bureau will not make any boundary change that affects adjacent legal governments
without the appropriate documentation. Please review any change polygons that affect
adjacent governments to determine if they are intentional legal changes.
Note:

5.7.1

The Census Bureau will snap any addition, deletion, or boundary correction to a MAF/TIGER
feature when it exists within thirty feet of that feature. This helps maintain the boundary-tofeature relationships in the MAF/TIGER system and will ensure correct housing tabulation
counts for governments.

Submitting Acceptable Documentation

The Census Bureau is responsible for depicting reservation and off-reservation trust land
boundaries but because the Census Bureau is not the authority on the boundaries, it requires
documentation to update reservation and off-reservation trust land boundaries.
The following changes require documentation:
•
•
•
•
•
•

New off-reservation trust land.
New reservation land.
Changes from off-reservation trust land to reservation land and changes from reservation land
to off-reservation trust land.
Large changes to existing off-reservation trust land.
Large changes to existing reservation land.
Boundary corrections to off-reservation trust land or reservation land that do not follow the
general shape of the boundary.

For off-reservation trust land, the most common documentation is a trust deed or a letter from
the Bureau of Indian Affairs (BIA). Documents should state that the land is “in trust” for the
tribe.
For reservation land, documentation examples include (but are not limited to) federal register
notice, Act of Congress, Executive Order, or a new legal opinion issued by the BIA. When
submitting large boundary corrections to an existing reservation, please submit the reservation
document.
If no documentation is available, please contact the tribe’s regional BIA office to obtain
documentation. The Census Bureau will treat legal opinions issued in writing from the BIA as
documentation since the BIA is the authority on reservation and off-reservation trust land
boundaries. If the Census Bureau cannot interpret a document, such as a treaty, the Census
Bureau will contact the BIA for assistance.
For questions about documentation, please call the Census Bureau at 1-800-972-5651 or email
. To contact the BIA, please reach out to the nearest regional office, see
.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.7.2

Submitting Digital Data

Participants reporting changes to the BAS are required to submit at least the change polygon
shapefile. The total number of shapefiles submitted depends on what types of changes are
reported. The following is a list of change files that may needed:
1. Change Polygon Layers (AIA, tribal subdivisions, Hawaiian homelands)
• These layers consist of the changes that the Census Bureau needs to make.
• A layer of change polygons should be created for each level of geography (AIA, tribal
subdivisions, etc.) for which changes are being submitted.
2. Whole Modified Entity Layers (AIA, tribal subdivisions, and Hawaiian Homelands)
• These layers should only contain the complete and current boundary for the government
being updated.
• A whole entity layer should be created for each level of geography for which change
polygons are being created.
3. Tribal Feature Network, Parcel, and Boundary Layers (optional)
• These layers will help the Census Bureau resolve any questionable change polygons and
establish the correct boundary-to-feature relationships.
4. Feature Update Layer (only if there are feature (road, river, railroad, etc.) additions, deletions,
name changes, recodes, or address range updates)
• Include a linear feature update layer with only feature segments requiring a correction.
5. Area Landmarks/Hydrographic Areas Update Layer
• An area landmark/hydrographic area update layer should be submitted only if there are
area landmark and/or hydrographic area updates.
6. Point Landmark Update Layer
• A point landmark update layer should be submitted only if there are point landmark
updates.
7. BAS Contact Text File (if the BAS point of contact (the person that receives the BAS Annual
Response Email) has changed).
• This can be updated online at:
.
• This BAS Contact update should include the following information:
o First Name.
o Last Name.
o Department.
o Position.
o Shipping Address.
o City.
o State.
o ZIP Code.
o Phone: xxx-xxx-xxxx.
o Fax: xxx-xxx-xxxx.
o Email.
o Tribal Chair Term Expires: mm/yyyy.
o Tribal Chair Term Length: x years.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.7.3

Change Polygon Layer Naming Conventions

The following table provides change polygon naming conventions for AIAs and Hawaiian
Homelands. The in the change polygon layer naming conventions represents the BAS
ID, found on the BAS Annual Response email or online from this link:
.
Table 14: Change Polygons
Participant

5.7.4

Changes Submitted For:

Shapefile Naming Conventions

AIA

bas21__changes_aiannh

AIA

Tribal Subdivisions

bas21__changes_tribalsub

Hawaiian Homelands

bas21__changes_hhl

Whole Entity Polygon Layer Naming Conventions

The following table provides the whole entity polygon naming conventions for AIAs and
Hawaiian Homelands. The in the whole entity polygon layer naming conventions
represents the participant’s BAS ID, found on the BAS Annual Response email or online from
this link: .
Table 15: Whole Entity Polygon Layer Naming Conventions
Participant

5.7.5

Changes Submitted For:

Shapefile Naming Conventions

AIA

bas21__WholeEntity_aiannh

AIA

Tribal Subdivision

bas21__WholeEntity_trialsub

Hawaiian Homelands

bas21__WholeEntity_hhl

Linear Feature, Area Landmark/Hydrographic Area, and Point Landmark
Updates

The following table provides the update layer naming conventions for the edges, area
landmark, and point landmark update layers (not required). The in the naming
conventions for the edges, area landmark, and point landmark update layers represents the
participant’s BAS ID found on the BAS Annual Response email or online from this link:
.
Table 16: Optional Files
Participant

Changes Submitted For:

Shapefile Naming Conventions

All Participants

Edges

bas21__LN_Changes

All Participants

Area Landmarks /
Hydrographic Areas

bas21__Alndk_Changes

All Participants

Point Landmarks

bas21__Plndk_Changes

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

5.7.6

Compressing the Digital Files

The Census Bureau requires participants to submit all BAS returns through SWIM as
compressed (zipped) files. Please compress ALL update materials (including change polygon
shapefiles, whole entity shapefiles, linear feature updates, landmark updates, local government
feature network and boundary layers, any supporting documentation (e.g., trust deeds), and
the text or other file with the participant’s updated BAS contact information) as zipped files.
Note:

Centerline files or any additional information that may be helpful for the Census Bureau to
process the participant’s file is optional. One example where this would be helpful is if a
particular polygon was not snapped to a river or road because the boundary does not follow
the river or road.

Refer to Figure 18 and the steps listed below to compress digital files:
1. Navigate to the directory with the shapefiles.
2. Select all files and right click on the selection.
3. Select WinZip, and then Add to ZIP file.

Figure 18. Selecting and Zipping Return Files

Note:

Versions of WinZip may vary so the interface may be slightly different. Software other than
WinZip (e.g., 7zip) may be used to ZIP the return files.

4. In the Add window, in the Add to archive field, type the filename in the proper naming
convention: bas21__return and then click Add.
Note:

Look for the BAS ID number on the BAS Annual Response email or online from this link:
.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Important:

New format for references that include a date with a year. X will represent the current
year (i.e., all images where 202x is used).

Figure 19. Naming the ZIP File

5. Check the folder where the ZIP file was saved to verify that it was created properly. If the ZIP file
is correct, then the return file is ready for submission.
Note:

5.7.7

If assistance is required in preparing or zipping the BAS return files, please call the Census
Bureau at 1-800-972-5651 or email .

Submitting Digital Files through SWIM

SWIM is a one-stop location for submitting geographic program files to the Census Bureau. The
Census Bureau now requires that all BAS participants use the Census Bureau’s SWIM for
submitting update materials.
Do not send submissions as an email attachment, as the Census Bureau cannot accept them
due to security policy.
The Census Bureau will email the BAS contact a SWIM registration token and digital submission
instructions five days after the BAS contact responds to the BAS Annual Response indicating
that they have changes to report. To respond online, please fill out the online form at
. The five-day waiting
period will give the Census Bureau staff time to update the BAS contact record if necessary, so
that the email reaches the right person.
This token is good for one personal account within the SWIM. Once participants have registered
for an account in SWIM, they will no longer need the token to login into the system. If
participants require additional individual SWIM accounts within their organization, please
contact the Census Bureau at 1-800-972-5651 or email .

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Current SWIM Users
If participants are participating in other Census Bureau partnership programs, or have participated in
previous BAS years, and already have SWIM accounts, they may use their current account to submit files
for BAS. They do not need to set up a new account.
Participants will not be able to upload a file larger than 250 MB.
SWIM blocks participants from uploading a ZIP file that contains another ZIP file.

Follow the instructions listed below:
1. In a web browser, navigate to .
2. Log in:
3. New Users: Participants must have a registration token to create a new account. (Please see
above on how to obtain a SWIM token). Once participants have their token, they should sign-up
by clicking the ‘Register Account’ button. Registration is self-serve but does require the new user
to enter a registration token to validate their rights to the system.

Figure 20. SWIM Account Registration

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

4. Existing Users: If participants already have a registered account from a previous BAS year, they
should login with their user credentials.

Figure 21. SWIM Login Window

5. If participants have submitted files before, SWIM lists them on the startup screen upon login.
Click 'Start New Upload' to continue.

Figure 22. Welcome Screen with Upload History

6. On the next screen, select the “Boundary Annexation Survey (BAS)” option as the geographic
partnership program, and click ‘Next’ to continue.

Figure 23. Geographic Partnership Program Selection Window
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

7. On this screen, participants will select a geographic level. This is the geography type of their
agency. Select ‘Tribal Area’. Click 'Next' to continue.

Figure 24. Geographic Level Selection Window

8. Participants will find the name of their government using the drop-down selectors. These
options dynamically update based on the geography type selected from the previous screen.
Click ‘Next’ to continue.

Figure 25. Government Selection Window

9. On the file upload screen, please click on the ‘+ Add file', and a file browser dialog will appear.

Figure 26. File Upload Screen

10. In the file browser dialog box, select the ZIP file that is to be uploaded. Please be aware that the
SWIM website only accepts ZIP files. Click 'Open' to continue.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

Figure 27. File Browser Dialog Box

11. At this time, participants may enter any comments that they wish to include with their file. Click
'Next' to upload the submission.

Figure 28. Entering Comments into the File Upload Window

12. The final screen will be a ‘Thank You’ screen confirming receipt of the file submission. If this
screen does not appear, or issues occur during this upload process, please contact the Census
Bureau at 1-800-972-5651 or .

Figure 29. Thank You Screen

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

APPENDICES

This page intentionally left blank.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

A-1

APPENDIX A

DATA DICTIONARY
Table 17: American Indian Areas - Legal (AIAL) Shapefile

ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

AIANNHCE

String

Census AIANNH Code

COMPTYP

String

Indicates if Reservation, Trust Land, or both are
Present

AIANNHFSR

String

Flag Indicating Level of Recognition of an AIA

NAMELSAD

100

String

Name with Translated LSAD

AIANNHNS

String

ANSI numeric identifier for AIA areas

LSAD

String

Legal / Statistical Area Description

FUNCSTAT

String

Functional Status

CLASSFP

String

FIPS 55 Class Code Describing an Entity

PARTFLG

String

Part Flag Indicator

CHNG_TYPE

String

Type of Area Update

AUTHTYPE

String

Authorization Type (O – Ordinance, R – Resolution, L –
Local Law, S – State Level Action, X – Other)

EFF_DATE

Date

Effective Date

DOCU

120

String

Supporting Documentation

RECORD_ID

String

(GUPS Only)

AREA

Double

Acreage of Area Update

RELATE

120

String

Relationship Description

JUSTIFY

150

String

Justification of Change

NAME

100

String

AIA name

VINTAGE

String

Vintage of the Data

Table 18: American Indian Tribal Subdivisions (AITS) Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

AIANNHCE

String

Census AIANNH Code

TRIBALSUBCE

String

Census Tribal Subdivision Code

NAMELSAD

100

String

Name with translated LSAD

AIANNHNS

String

ANSI Numeric Identifier for AIANNH Areas

LSAD

String

Legal / Statistical Area Description

FUNCSTAT

String

Functional Status

CLASSFP

String

FIPS 55 Class Code Describing an Entity

PARTFLG

String

Part Flag Indicator

CHNG_TYPE

String

Type of Area Update

EFF_DATE

Date

Effective Date

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

A-2

ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

AUTHTYPE

String

Authorization Type (O – Ordinance, R – Resolution, L –
Local Law, S – State Level Action, X – Other)

DOCU

120

String

Supporting Documentation

RECORD_ID

String

(GUPS Only)

AREA

Double

Acreage of Area Update

RELATE

120

String

Relationship Description

JUSTIFY

150

String

Justification of Change

NAME

100

String

Tribal subdivision name

VINTAGE

String

Vintage of the Data

AIANNHFSR

String

Flag Indicating Level of Recognition of an AIA

Table 19: Edges Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

TLID

Double

Permanent edge ID

TFIDL

Double

Permanent face ID (left)

TFIDR

Double

Permanent face ID (right)

MTFCC

String

MAF/TIGER Feature Class Code

FIDELITY

String

Indication to a respondent when their government
boundary has changed through spatial enhancement

FULLNAME

String

Decoded feature name with abbreviated qualifier,
direction, and feature type

SMID

String

Spatial Theta ID

SMIDTYPE

String

SMIDTYPE Code

BBSPFLG

String

Redistricting data project participant’s submitted
request of an EDGE for selection as a block boundary

CBBFLG

String

Indicates the status of an EDGE for a selection as a
block boundary

BBSP_2010

String

New BBSP flag

CHNG_TYPE

String

Type of linear feature update

JUSTIFY

150

String

Justification of change

LTOADD

String

Left To Address

RTOADD

String

Right To Address

LFROMADD

String

Left From Address

RFROMADD

String

Right From Address

ZIPL

String

Left ZIP Code

ZIPR

String

Right ZIP Code

EXTTYP

Char

Extension type

MTUPDATE

Date

Date of last update to the edge

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

A-3

Table 20: Area Landmark Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

MTFCC

String

MAF/TIGER Feature Class Code

FULLNAME

120

String

Area landmark name

PARTFLG

String

Indicates if only part of a feature is represented

AREAID

String

Object ID

ANSICODE

String

ANSI code for area landmarks

CHNG_TYPE

String

Type of area landmark update

EFF_DATE

Date

Effective date or vintage

RELATE

120

String

Relationship description

JUSTIFY

150

String

Justification of change

BAG

String

Block area grouping

Table 21: Hydrographic Area Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

ANSICODE

String

ANSI code for hydrography area

MTFCC

String

MAF/TIGER Feature Class Code

FULLNAME

120

String

Hydro landmark name

CHNG_TYPE

String

Type of hydrographic area update

HYDROID

String

Object ID

RELATE

120

String

Relationship description

JUSTIFY

150

String

Justification of change

Table 22: Point Landmark Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

POINTID

String

Object ID

ANSICODE

String

ANSI code for point landmarks

MTFCC

String

MAF/TIGER Feature Class Code

FULLNAME

120

String

Point landmark name

CHNG_TYPE

String

Type of point landmark update

JUSTIFY

150

String

Justification of change

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

A-4

Table 23: Geographic Offset Shapefile
ATTRIBUTE FIELD

LENGTH

TYPE

DESCRIPTION

TFID

Integer

Permanent Face ID

STATEFP

String

FIPS State Code

COUNTYFP

String

FIPS County Code

OFFSET

String

Geographic Offset / Corridor Flag

ADDEXCLUDE

String

Address Exclusion Indicator

CHNG_TYPE

String

Type of area update

EFF_DATE

Date

Effective date or vintage

RELATE

120

String

Relationship description

JUSTIFY

150

String

Justification of change

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

A-5

APPENDIX B

2021 BAS EXAMPLE PROCESS 1

The 2021 BAS Partnership Toolbox provides step-by-step instructions to facilitate the updating
process. These instructions are best used in conjunction with the Boundary and Annexation
Survey (BAS) Respondent Guide: Digital. For best results, use the toolbox in ArcGIS 10.0 and
higher (not including ArcGIS Pro).

How to Use the BAS Partnership Toolbox

In an effort to ease the burden of creating BAS updates, a toolbox was developed for ArcGIS.
This toolbox simplifies the updating process by automating the downloading of data, creating
changes, removing slivers, formatting and checking attribution, and preparing/exporting files
for submission. Before running these tools, users will need the following:
•

•
•

•

The Boundary and Annexation Survey (BAS) Respondent Guide: Digital which can be
downloaded at: download the guide at:
.
The BAS Partnership Toolbox, which can be downloaded at:
.
The BAS ID for the government being processed. This can be found on the BAS Annual
Response email or online at: .
A shapefile or feature class showing the legal boundary of the government.
o Data in this layer should have data including the name of the government being
processed formatted to agree with the Census Bureau’s naming convention for the
same government as found in the NAME field or the NAMELSAD field for Minor Civil
Division (MCD) and American Indian / Alaska Native / Native Hawaiian (AIANNH).
The 2021 BAS Partnership Shapefiles located at:
.

Toolbox Tools Setup

These toolbox tools were designed primarily for use in ArcCatalog though they run in ArcMap as
well. The instructions for most steps are assuming use in ArcCatalog.
Unzip the BAS Partnership Tools.zip to the C: drive or other preferred working folder. The folder
location does not matter as long as it can be accessed from ArcCatalog. Inside there will be a
folder called DBAS, containing all the files to work with for a government. Open ArcCatalog and
connect to the DBAS folder. When expanded, the following should be visible:

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-1

Figure 30. Partnership BAS Tools Menu

Note:

To connect to a folder in ArcCatalog, click on the Connect to Folder button on the Standard
Toolbar, find the DBAS folder, and then click OK.

Census Data Download Tool

The Census Data Download tool will gather all the partnership shapefile data needed to create
changes from the Census Bureau website. If the data is on a Census Bureau provided disc, this
tool will also work but only if the data is loaded to the computer before running the tool. This
tool can also use the ZIP files downloaded from the 2021 BAS Partnership Shapefiles site:

and outlined in Chapter 3. Please follow the steps below to run the Census Data Download tool.
Expand the DBAS folder and the setup subfolder. In the setup folder, find the Partnership
Toolbox. Expand the toolbox and double click on the 1) Census Data Download tool.

Figure 31. Partnership BAS Tools Menu with Census Data Download Selected

There are two ways to use this tool: one that downloads the data from the Census Bureau for
the user and one that takes in a folder with the Census Bureau data already downloaded. If you
have already downloaded the data, you must unzip the downloaded pvs batch ZIP file (e.g.
pvs_batch_from_) to display the partnership shapefiles ZIP files (e.g.
partnership_shapefiles_20v2_ and partnership_shapefiles_20v2_). The tool will look
for these partnership_shapefiles ZIP files when it runs.
• Enter the 11-digit BAS ID in the User’s BAS ID field. If you are a county participant,
responding for the governments within your jurisdiction, you will enter the County BAS ID.
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-2

•
•

Select Yes or No under the Use Data Downloader? field. If you select No, you must enter a
path to the already downloaded partnership shapefiles in the next field.
Navigate or drag the folder into Path to ZIP files field. Make sure the folder only contains
the Census Bureau ZIP files to ensure there are no future data issues.

This example shows how a user would complete the fields to have data downloaded for them.

Figure 32. The Census Data Download Window with ‘Yes’ in the Use Data Downloader Field

This example shows how a user would complete the fields if they already have the partnership
shapefiles downloaded and saved on their computer.

Figure 33. The Census Data Download Window with ‘No’ in the Use Data Downloader Field

Click OK to run.
When this tool is complete, there should now be a folder for the BAS ID in the projects folder.
Inside that folder, there will be a geodatabase with reference data in it and an archive folder.

Figure 34. Partnership Tools Menu Showing a Folder for the BAS ID in the Projects Folder
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-3

Note:

The archive folder contains other Census Bureau data that may be useful as well.

Create Changes Tool

Once the necessary Census Bureau data is obtained, run the 2) Create Changes tool to create
the change polygons. Before this tool can successfully complete, there must be an attribute
field in the local boundary layer that contains the name of the government or governments as
they appear in Census Bureau records (Figure 35). This includes matching capitalization,
spacing, and in the case of MCDs a descriptor of the geography (e.g. township, village, borough,
etc.) which can be found in the NAMELSAD field of the bas_cousub layer (or bas_aial layer for
AIANNH updates) in the reference feature dataset (Figure 36). If it is a new entity or the legal
name is changing, it does not need to agree though other attribution must be updated to
reflect this change.

Figure 35. NAME Field in Census Data vs Local Boundary Data
The bas_place layer on the left shows how the Census Bureau NAME
field is populated for all the places in Butler County, PA while the local
places data shows how local data may need to be manipulated to agree
with the Census Bureau NAME field.

Figure 36. Appropriate Attribution for COUSUB or AIANNH Changes
The bas_cousub attribution on the left in the NAMELSAD field shows
how the local MUNICIPALI field on the right should be formatted to
ensure that the Create Changes tool works for the MCD changes in
Butler County, PA.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-4

Double click on 2) Create Changes tool.

Figure 37. Partnership Tools Menu with Create Changes Tool Selected

In the Create Changes window:
• In the Local Boundary File field, enter the path or navigate to the full boundary polygon.
• Enter the 11-digit BAS ID in the BAS ID field.
• Under Changes Being Processed, choose the type of changes to create from the dropdown
options:
a. Incplace (incorporated place).
b. County.
c. Cousub (MCDs).
d. AIANNH (Tribal areas).
•

For the Name Field in Local Data, the boundary file may need to be modified to agree with a
field in the Census Bureau’s data. Type the name of the field (as it appears in ArcCatalog)
containing the information matching the Census Bureau’s NAME field. If processing an MCD
or AIANNH file where the Census Bureau NAME field contains duplicates, match the Census
Bureau’s NAMELSAD.

Figure 38. Create Changes Window

Click OK to run the tool.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-5

Once the tool is complete, the output will be placed in the geodatabase under the submission
feature dataset.

Figure 39. Partnership Tools Menu with Geodatabase

Repeat steps for any other levels of geography that need changes created.

Sliver Blaster Tool (Optional)

The Sliver Blaster tool is useful for governments that have numerous very small change
polygons that are time consuming to manually parse through for deletion. to Since the Census
Bureau cannot guarantee inclusion of changes under 30 feet at their widest point, use this tool
to remove changes that are lower than that threshold. Participants can also change the
tolerance for slivers if they know there are small changes that need to be included. This
automated tool will vary in processing time depending on the number of features in the entity.
Double click on the 3) Sliver Blaster tool.

Figure 40. Partnership Tools Menu with Sliver Blaster Selected

In the Sliver Blaster tool window:
• The Changes File refers to the file created in the previous step, found in the submission
feature dataset.
• The Census Edges feature class is found in the referenced feature dataset and is called
bas_edges.
• The Buffer Distance field is set to 30 feet by default, but this can be adjusted to
accommodate smaller changes.
Click OK to run.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-6

Figure 41. Sliver Blaster Window

Format Working MXD Tool (Optional)

The intent of this tool is to create a map document (.mxd) for users containing their change file
and the reference layers they will need to finalize a submission. If users would prefer to use
their own .mxd, this step is not required.
Double click on the 4) Format Working MXD tool.

Figure 42. Partnership Tools Menu with Format Working MXD Selected

The only input for this tool is the Working Folder, which is the folder with the governments BAS
ID as its name.

Figure 43. Format Working MXD Window
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-7

Click OK to run the tool.
Open the ne .mxd and begin working with the change polygons.

Figure 44. Projects Submenu with mxd file Selected

Attribute Check Tool

This tool is used to verify that there are no inconsistencies with the data included in the
submission. Run this tool during or after change polygons have been reviewed for spatial
accuracy to produce a report of attribution errors (see 5.6 for guidance on conducting a spatial
review). It may also run for all levels of geography that have changes since it is run on each
individual change file.
Double click on the 5) Attribute Check tool.

Figure 45. Partnership Tools Menu with Attribute Check Selected

In the Attribute Check window:
• The Change File should be the change file created in tool 2) Create Changes for which to
generate a report.
• In Geography Type, chose the type of geography being worked on from the dropdown. The
same options as the Create Changes tool are available here.
• The last input is the optional check box for Includes Changes in Georgia. This box only needs
to be checked if responding in the state of Georgia.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-8

Figure 46. Attribute Check Window

Click OK to run the tool.
There should now be a text file in the working folder called attribute_check_.txt
containing all the discrepancies identified in the change file that still need to be fixed.

Figure 47. Projects Submenu Showing an attribute_check Text File

Export Submission Tool

Upon review of the changes file and the attribute error report, the finalized changes may be
exported for submission to the Census Bureau. This tool can also be used to provide updated
contact information with the submission.
Note:

This tool does not submit the changes, it just makes a file for submission. Please follow Step 9
for submission guidelines.
Double click on the 6) Export Submission Files tool.

Figure 48. Partnership Tools Menu with Export Submission Files Selected

In the Export Submission Files tool window:
• Enter the 11-digit BAS ID in the BAS ID field.
• Under Additional Files, drag in or navigate to any additional files to be included in the
submission. This can include parcel data, legal documentation, or any other helpful
supporting data. This is an optional field so it can also be left blank. There is no need to add
the changes layers here as the tool will handle those already based on the BAS ID.
• For BAS Contact, Entity Name, Contact Title or Department Name, Address, Email, and
Phone Number, please include any or all contact information updates that are to be sent to
the Census Bureau. These fields can be left blank if there are no updates, though if someone
other than the BAS Contact prepared the submission, include the contact information.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-9

Figure 49. Export Submission Files Window

Click OK to run the tool.

Submitting Files through the Secure Web Incoming Module (SWIM)

The Census Bureau requires participants to submit updated BAS materials as ZIP files using the
Census Bureau’s SWIM site. Please submit only the ZIP file(s). SWIM is located at
. For instructions on how to use SWIM, see 5.7.7,
Submitting Digital Files through SWIM.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

B-10

APPENDIX C

2021 DIGITAL BAS EXAMPLE PROCESS 2

The 2021 Digital BAS Example Process 2 provides step-by-step instructions for participants
creating their own change shapefiles using ArcGIS.

Required Census Bureau Shapefiles

When downloading shapefiles for the 2021 BAS, shapefiles will begin with the prefix PVS
(e.g., PVS_20_v2_edges_.shp). Throughout this guide, Census Bureau uses the prefix of
bas_2021, but the PVS files are exactly the same.
Copy the data to a hard drive/server and unzip the data to ensure that the correct data was
downloaded. For an AIA, these layers are critical:
•
•
Note:

PVS_20_v2_aial_.shp
PVS_20_v2_edges_.shp
represents the two-digit state code and three-digit county code.

The shapefiles should include the home county for all reservations and off-reservation trust
lands as well as all adjacent counties (if necessary).
Note:

The Census Bureau suggests that participants make an extra copy of the data as an emergency
backup.

Tribal Data

The minimum data necessary is a jurisdiction polygon shapefile showing only the outer
boundary or boundaries. Local parcel files are not acceptable for this method. If each
jurisdiction’s boundaries are contiguous, the file should contain only one polygon for each
government; if some of the governments within the jurisdiction are non-contiguous, they may
be saved as a multi-part polygon or consist of one polygon for each disjointed part. Other local
data layers that may be helpful, if available, include centerline data, hydrographic, railroad or
other linear feature data, and imagery.

Symbolizing Layers in ArcGIS

The following are suggestions for symbolizing Census Bureau data in ArcGIS. For the Edges
layer, symbolize the linear features by grouping like MTFCC codes (codes sharing the same first
character). See Table 24.
Table 24: Suggested MTFCC Symbolization
MTFCC 1st Character

U.S. Census Bureau

Linear Feature Type

Hydrographic

Non-Visible Feature (boundary)

Railroad

Road
Boundary and Annexation Survey Tribal Respondent Guide: Digital

Symbol

C-1

Symbolizing Geographic Areas

Symbolize the AIAL layer by “COMPTYP” field to show reservation and off-reservation trust
land.
Note:

AIA participants working on changes for tribal subdivisions may want to use different colors to
distinguish one from another.

Figure 50. Suggested Map Symbolization

Extracting AIA Data from Census Bureau Shapefiles

C5.1 Filtering the Data
1. In ArcMap, click Selection and then click Select by Attributes.
2. In the Select By Attributes window:
• From the Layer dropdown, select PVS_20_v2_aial_.shp.
• Double click “NAME.”
• Left click the = button.
• Click the Get Unique Values button.
• In the list, locate and double click the name of the government (It will appear in the
formula).
• Click OK.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-2

Figure 51. Filtering Data

C5.2 Exporting the Data to a New Shapefile
1. In the Table of Contents right click the AIA layer, select Data, and then click Export Data.
2. In the Export Data window:
• From the Export dropdown, choose Selected Features.
• In the Output shapefile or feature class field, enter a location to save the shapefile.
• Click OK.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-3

Figure 52. Export Data Window

Note:

If the AIA spans more than one county, it will need to be exported from each county’s AIA
shapefile and merged. Follow the instructions in we used C7.1, Creating Change Polygons
Using Symmetrical Difference if the AIA needs to be merged, otherwise skip to C7.2, Creating
Change Polygons Using Union.

Merging Multipart Place Data
1. In ArcToolbox, double-click Data Management Tools, then double-click General, and then
double-click Merge.
2. In the Merge window:
• Next to the Input Datasets field, click the arrow and select each layer (or use the Browse
button to the right of the field to find the layers.)
• In the Output Dataset field, browse to and select a location to save the shapefile.
o Name the shapefile Export_Output_Final or Merged, or anything easy to
find/remember.
• Click OK.

Figure 53. Finalizing the Merge Process

Creating Change Polygons

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C- 4

There are two methods used for creating change polygons. Symmetrical Difference is the
recommended method for single geographic areas and those with an appropriate ArcGIS
license. Steps for using a symmetrical difference are outlined in C7.1, Creating Change Polygons
Using Symmetrical Difference. Otherwise, the Union method is acceptable and outlined in
C7.2, Creating Change Polygons Using Union.

C7.1 Creating Change Polygons Using Symmetrical Difference
1. In ArcToolbox, double-click Analysis Tools, then double-click Overlay, and then double-click
Symmetrical Difference.
2. In the Symmetrical Difference window:
• In the Input Features field, click the arrow (or browse) and select the layer created in C6,
Merging Multipart Place Data.
• In the Update Features field, click the arrow (or browse) and select the tribal government
boundary layer (the participant’s data).
• In the Output Feature Class field, browse to and select a location to save the shapefile.
• Name the shapefile Differences_between_BAS_tribal, Differences1, or anything easy to
find/remember.
• Click OK.

Figure 54. Finalizing the Symmetrical Difference Process

Note:

This process creates a layer that contains all of the differences between Census Bureau and
local tribal boundaries. However, the Symmetrical Difference tool creates multipart polygons
that need to be broken up and individually coded.

3. Turn on Editing (using the Editing dropdown in the Editor toolbar). Select all the records in the
layer that were created in the Symmetrical Difference step.
4. On the Advanced Editing toolbar, click the Explode tool
separate record for each change.
U.S. Census Bureau

. The layer will now contain a

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-5

The created layer shows individual change polygons representing the differences between the
Census Bureau and tribal government boundaries. Please review these differences and code
them appropriately.
Skip to C8, Reviewing and Attributing Change Polygons.

C7.2 Creating Change Polygons Using Union
1. In ArcToolbox, double-click Analysis Tools, then double-click Overlay, and then double-click
Union.
2. In the Union window:
• In the Input Features field, click the arrow (or browse) and select PVS_20_v2_aial_,
and the tribe’s own layer.
• In the Output Feature Class, browse to and select a location to save the shapefile.
o Name the shapefile Export_Output_union, or Union, or anything easy to
find/remember.
• Click OK.

Figure 55. Finalizing the Union Process

The union operation will create records that contain differences as well as areas that are in
common between the Census Bureau and local tribal boundary layers.
The next step is selecting and deleting the areas in common between the Census Bureau and
local tribal boundary layers.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-6

1. On the Editor toolbar, click Editor, and then click Start Editing.
2. If a Start Editing window opens, in the top pane, click to highlight the union shapefile, and then
click OK.

Figure 56. Locating the Union Shapefile

3. In ArcMap, in the Tools toolbar, click the Select Features
button.
• Locate features on the map that the Census Bureau and the tribal layers have in common.
• Select each feature individually or click and hold the left mouse button and drag a box to
highlight the common features.
• Press Delete.
• Repeat these steps until only the features that have changed are left in the map.
4. Once all of the areas in common have been removed from the union shapefile, on the Editor
toolbar, click Editor, and then click Save Edits.
5. Select all of the remaining records in the layer that was created in the Union step.
6. On the Advanced Editing toolbar, click the Explode tool
separate record for each change.

. The layer will now contain a

The new layer shows individual change polygons representing the differences between the
Census Bureau and the tribal government’s representation of the boundaries. Please review
these differences make sure they are coded appropriately. Continue to the next section for
instructions on reviewing and coding change polygons.
U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-7

Reviewing and Attributing Change Polygons

After the individual change polygons have been created, each must be reviewed and
appropriately coded. When reviewing the polygons, please refer to 5.3, Boundary Changes in
the main part of this guide to look for polygons that should be deleted from the submission, as
well as those that should be snapped to nearby visible features to maintain boundary-tofeature relationships.

C8.1 Examples
These examples show very small sliver polygons that should be deleted during review as they
eliminate boundary-to-feature relationships with a river (left) and a road (right). Furthermore,
these boundary corrections also are not located near legal changes or corridor/offset changes
(type ‘A’, ‘D’, ‘C’, ‘F’), so they should be removed from consideration.

Figure 57. Small Slivers That Should Be Deleted
Figure 57 shows examples of small slivers that should be deleted along
rivers (left) or roads (right).

Figure 58. Polygons (Before and After) Snapped to Roads or Rivers
The two examples one the left show polygons that should be snapped to
rivers (left) or roads (right). The two examples on the right show how a
snapped area will look.

C9
Note:

Attribute Information
All updates MUST be attributed. Table 3, Table 4, and Table 5 in 5.3, Boundary Changes cover
the required attributes.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-8

C9.1 To Begin Updating Attributes for Additions
•

On the Editor Toolbar, click Editor, and then click Start Editing.

•

On the Editor Toolbar, click the Edit Tool

•
•

On the Editor Toolbar, click the Attributes
button.
In the Attributes window, fill out the mandatory fields required for an addition:
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
o The CHNG_TYPE for an addition is A.

button and select the addition polygon.

C9.2 To Begin Updating Attributes for Deletions
•

On the Editor Toolbar, click the Edit Tool

•
•

On the Editor Toolbar, click the Attributes
button.
In the Attributes window, fill out the mandatory fields required for a deletion:
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
o The CHNG_TYPE for a deletion is D.

button and select the deletion polygon.

C9.3 To Begin Updating Attributes for Geographic Corridors
•

On the Editor Toolbar, click the Edit Tool

•
•

On the Editor Toolbar, click the Attributes
button.
In the Attributes window, fill out the mandatory fields required for a corridor:
o NAME, CHNG_TYPE, RELATE.
o The CHNG_TYPE for a corridor changes is C.
o In the RELATE field, enter IN if the change is adding corridor area to the place or OUT if
the change is removing corridor area.

button and select the corridor polygon.

C9.4 To Begin Updating Attributes for Geographic Offsets
•

On the Editor Toolbar, click the Edit Tool

•
•

On the Editor Toolbar, click the Attributes
button.
In the Attributes window, fill out the mandatory fields required for an offset:
o NAME, CHNG_TYPE, RELATE.
o The CHNG_TYPE for an offset change is F.
o In the RELATE field, enter IN if the change is adding offset area to the place or OUT if the
change is removing offset area.

button and select the offset polygon.

C9.5 To Finish Updating Attributes
•

Once all of the attribute changes have been made, in the ArcMap menu, click Editor, and then
click Stop Editing. (In the Save window, click Yes.)

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-

C10

Renaming and Finalizing Change Polygons

After creating and coding all change polygons, please rename the change polygon layer prior to
its submission to the Census Bureau. This process must be completed for each level of
geography (AIA, tribal subdivision) that has changes.

C10.1 Renaming the shapefile:

1. In ArcMap, open the ArcCatalog
tab.
2. In ArcCatalog, navigate to shapefile, right-click and select Rename.
3. Save the output shapefile in the proper naming convention:
bas21__changes_.
Note:

The BAS ID numbers can be found on the BAS Annual Response email or online from this link:
.

Note:

See 5.7.6, Compressing the Digital Files for instructions on zipping updates.

C10.2 Submitting the shapefile:
The Census Bureau requires participants submit BAS return ZIP files using the Census Bureau’s
SWIM site. Please submit only the ZIP file. The SWIM is located at
. For instructions on how to use SWIM, see 5.7.7,
Submitting Digital Files through SWIM of this respondent guide

C10.3 To Begin Updating Attributes for Boundary Corrections

Note:

•

On the Editor Toolbar, click the Edit Tool
polygon.

•
•

On the Editor Toolbar, click the Attributes
button.
In the Attributes window, fill out the mandatory fields required for a boundary correction:
o NAME, CHNG_TYPE, RELATE.
o The CHNG_TYPE for a boundary correction is B.
o In the RELATE field, enter IN if the boundary correction is adding area or OUT if the
boundary correction is removing area.

button and select the boundary correction

If a boundary correction to one tribal subdivision affects or takes land from another, use
RELATE = IN and NAME = . This is due to the fact that RELATE = OUT
leaves a question as to whether or not there should be a gap between the two governments.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

C-3

APPENDIX D

MTFCC DESCRIPTIONS

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.
Table 25: MTFCC Code/Class/Decsription
MTFCC

Feature Class

Feature Class Description

C3022

Mountain Peak or Summit

C3023

Island

C3024

Levee

C3026
C3027

Quarry (not water-filled),
Open Pit Mine or Mine
Dam

C3061

Cul-de-sac

C3062

Traffic Circle

C3066
C3067
C3070

Gate
Toll Booth
Tower/Beacon

C3071
C3072
C3073

Lookout Tower
Transmission Tower
including cell, radio and TV
Water Tower

C3074

Lighthouse Beacon

C3075

Tank/Tank Farm

C3076

Windmill Farm

C3077

Solar Farm

C3078

Monument or Memorial

C3079
C3080

Boundary Monument
Point
Survey Control Point

C3081

Locality Point

C3085

Alaska Native Village
Official Point

A prominent elevation rising above the surrounding level of the Earth’s
surface.
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].
An embankment flanking a stream or other flowing water feature to
prevent overflow.
An area from which commercial minerals are or were removed from
the Earth; not including an oilfield or gas field.
A barrier built across the course of a stream to impound water and/or
control water flow.
An expanded paved area at the end of a street used by vehicles for
turning around. For mapping purposes, the Census Bureau maps it only
as a point feature.
A circular intersection allowing for continuous movement of traffic at
the meeting of roadways.
A movable barrier across a road.
A structure or barrier where a fee is collected for using a road.
A manmade structure, higher than its diameter generally used for
observation, storage, or electronic transmission.
A manmade structure, higher than its diameter, used for observation.
A manmade structure, higher than its diameter, used for electronic
transmission.
A manmade structure, higher than its diameter, used for water
storage.
A manmade structure, higher than its diameter, used for transmission
of light and possibly sound generally to aid in navigation.
One or more manmade structures, each higher than its diameter, used
for liquid (other than water) or gas storage or for distribution activities.
One or more manmade structures used to generate power from the
wind.
One or more manmade structures used to generate power from the
sun.
A manmade structure to educate, commemorate, or memorialize an
event, person, or feature.
A material object placed on or near a boundary line to preserve and
identify the location of the boundary line on the ground.
A point on the ground whose position (horizontal or vertical) is known
and can be used as a base for additional survey work.
A point that identifies the location and name of an unbounded locality
(e.g., crossroad, community, populated place or locale).
A point that serves as the core of an Alaska Native village and is used in
defining Alaska Native village statistical areas.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-1

MTFCC

Feature Class

C3088
G2100

Landfill
American Indian Area

G2101

American Indian Area
(Reservation Only)
American Indian Area (OffReservation Trust Land
Only)
Hawaiian Homeland
Alaska Native Village
Statistical Area

G2102

G2120
G2130

G2140

Oklahoma Tribal Statistical
Area

G2150

State-designated Tribal
Statistical Area

G2160

Tribal Designated
Statistical Area

G2170

American Indian Joint Use
Area
Alaska Native Regional
Corporation

G2200

G2300

Tribal Subdivision

G2400

Tribal Census Tract

G2410

Tribal Block Group

G3100

Combined Statistical Area

G3110

Metropolitan and
Micropolitan Statistical
Area

U.S. Census Bureau

Feature Class Description
A disposal facility at which solid waste is placed on or in the land.
A legally defined state- or federally recognized reservation and/or offreservation trust land (excludes statistical American Indian areas).
American Indian Area (Reservation Only)
American Indian Area (Off-Reservation Trust Land Only)

A legal area held in trust for the benefit of Native Hawaiians.
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.
A statistical entity identified and delineated by the Census Bureau in
consultation with federally recognized American Indian tribes that have
no current reservation but had a former reservation in Oklahoma.
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.
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.
An area administered jointly and/or claimed by two or more American
Indian tribes.
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.
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, off-reservation trust
lands, or OTSAs.
A relatively small and permanent statistical subdivision of a federally
recognized American Indian reservation and/or off-reservation trust
land, delineated by American Indian tribal participants or the Census
Bureau for the purpose of presenting demographic data.
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.
A grouping of adjacent metropolitan and/or micropolitan statistical
areas that have a degree of economic and social integration, as
measured by commuting.
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.
Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-2

MTFCC

Feature Class

G3120

Metropolitan Division

G3200

Combined New England
City and Town Area
New England City and
Town Metropolitan and
Micropolitan Statistical
Area
New England City and
Town Division

G3210

G3220

G3500

Urban Area

G4000

State or Equivalent
Feature

G4020

County or Equivalent
Feature

G4040

County Subdivision

G4050

Estate

G4060
G4110

Subbarrio (Subminor Civil
Division)
Incorporated Place

G4120

Consolidated City

G4210

Census Designated Place

G4300

Economic Census Place

U.S. Census Bureau

Feature Class Description
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.
A grouping of adjacent New England city and town areas that have a
degree of economic and social integration, as measured by commuting.
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.
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.
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.
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.
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.
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.
Estates are subdivisions of the three major islands in the United States
Virgin Islands (USVI).
Legally defined divisions (subbarrios) of minor civil divisions (barriospueblo and barrios) in Puerto Rico.
A legal entity incorporated under state law to provide general-purpose
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.
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.
A statistical area defined for a named concentration of population and
the statistical counterpart of an incorporated 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.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-3

MTFCC

Feature Class

G5020

Census Tract

G5030

Block Group

G5040

Tabulation Block

G5200

Congressional District

G5210

State Legislative District
(Upper Chamber)

G5220

State Legislative District
(Lower Chamber)

G5240

Voting District

G5400

Elementary School District

G5410

Secondary School District

G5420

Unified School District

G6100

Public-Use Microdata Area

G6300

Traffic Analysis District

G6320

Traffic Analysis Zone

G6330

Urban Growth Area

G6340

ZIP Code Tabulation Area
(Three-Digit)

U.S. Census Bureau

Feature Class Description
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.
A cluster of census blocks having the same first digit of their four-digit
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.
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.
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.
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).
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.
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.
A geographic area within which officials provide public elementary
grade-level educational services for residents.
A geographic area within which officials provide public secondary
grade-level educational services for residents.
A geographic area within which officials provide public educational
services for all grade levels for residents.
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.
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
(TAD) consists of one or more Traffic Analysis Zones (TAZs).
An area delineated by Metropolitan Planning Organizations (MPOs)
and state Departments of Transportation (DOTs) for tabulating
journey-to-work and place-of-work data.
An area defined under state authority to manage urbanization that the
Census Bureau includes in the MAF/TIGER® System in agreement with
the state.
An approximate statistical-area representation of a U.S. Postal Service
(USPS) 3-digit ZIP Code service area.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-4

MTFCC
G6350

Feature Class

G6400

ZIP Code Tabulation Area
(Five-Digit)
Commercial Region

H1100

Connector

H2025

Swamp/Marsh

H2030
H2040
H2041
H2051

Lake/Pond
Reservoir
Treatment Pond
Bay/Estuary/Gulf/Sound

H2053
H2060
H2081

Ocean/Sea
Gravel Pit/Quarry filled
with water
Glacier

H3010

Stream/River

H3013

Braided Stream

H3020

Canal, Ditch or Aqueduct

K1121

Apartment Building or
Complex
Trailer Court or Mobile
Home Park
Crew-of-Vessel Location

K1223
K1225
K1226

K1228

Housing Facility/Dormitory
for Workers
Hotel, Motel, Resort, Spa,
Hostel, YMCA or YWCA
Campground

K1229

Shelter or Mission

K1231

Hospital/Hospice/Urgent
Care Facility
Nursing Home, Retirement
Home, or Home for the
Aged
County Home or Poor
Farm

K1227

K1233

K1234

U.S. Census Bureau

Feature Class Description
An approximate statistical-area representation of a U.S. Postal Service
(USPS) 5-digit ZIP Code service area.
For the purpose of presenting economic statistical data, municipios in
Puerto Rico are grouped into commercial regions.
A known, but nonspecific, hydrographic connection between two
nonadjacent water features.
A poorly drained wetland, fresh or saltwater, wooded or grassy,
possibly covered with open water [includes bog, cienega, marais, and
pocosin].
A standing body of water that is surrounded by land.
An artificially impounded body of water.
An artificial body of water built to treat fouled water.
A body of water partly surrounded by land [includes arm, bight, cove
and inlet].
The great body of salt water that covers much of the earth.
A body of water in a place or area from which commercial minerals
were removed from the Earth.
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].
A natural flowing waterway [includes anabranch, awawa, branch,
brook, creek, distributary, fork, kill, pup, rio, and run].
A natural flowing waterway with an intricate network of interlacing
channels.
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].
A building or group of buildings that contain multiple living quarters
generally for which rent is paid.
An area in which parking space for house trailers is rented, usually
providing utilities and services.
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.
A structure providing housing for a number of persons employed as
semi-permanent or seasonal laborers.
A structure providing transient lodging or living quarters, generally for
some payment.
An area used for setting up mobile temporary living quarters (camp) or
holding a camp meeting, sometimes providing utilities and other
amenities.
A structure providing low-cost or free-living quarters established by a
welfare or educational organization for the needy people of a district.
One or more structures where the sick or injured may receive medical
or surgical attention [including infirmary].
A structure to house and provide care for the elderly.

One or more structures administered by a local government that serve
as living quarters for the indigent.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-5

MTFCC

Feature Class

K1235

Juvenile Institution

K1236

Local Jail or Detention
Center

K1237

Federal Penitentiary, State
Prison, or Prison Farm

K1238

Other Correctional
Institution

K1239

K2100

Convent, Monastery,
Rectory, Other Religious
Group Quarters
Sorority, Fraternity, or
College Dormitory
Governmental

K2146

Community Center

K2110

Military Installation

K2165

Government Center

K2167

Convention Center

K2180

Park

K2181

National Park Service Land

K2182

National Forest or Other
Federal Land

K2183

Tribal Park, Forest, or
Recreation Area

K2184

State Park, Forest, or
Recreation Area
Regional Park, Forest, or
Recreation Area

K1241

K2185

K2186

County Park, Forest, or
Recreation Area

K2187

County Subdivision Park,
Forest, or Recreation Area

U.S. Census Bureau

Feature Class Description
A facility (correctional and non-correctional) where groups of juveniles
reside; this includes training schools, detention centers, residential
treatment centers and orphanages.
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.
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.
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.
One or more structures intended for use as a residence for those
having a religious vocation.
One or more structures associated with a social or educational
organization that serve as living quarters for college students.
A place where employees are employed in federal, state, local, or tribal
government.
A meeting place used by members of a community for social, cultural,
or recreational purposes.
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.
A place used by members of government (either federal, state, local, or
tribal) for administration and public business.
An exhibition hall or conference center with enough open space to host
public and private business and social events.
Parkland defined and administered by federal, state, and local
governments.
Area—National parks, National Monuments, and so forth—under the
jurisdiction of the National Park Service.
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.
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.
A place or area set aside for recreation or preservation of a cultural or
natural resource and under the administration of a state government.
A place or area set aside for recreation or preservation of a cultural or
natural resource and under the administration of a regional
government.
A place or area set aside for recreation or preservation of a cultural or
natural resource and under the administration of a county
government.
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.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-6

MTFCC

Feature Class

Feature Class Description

K2188

Incorporated Place Park,
Forest, or Recreation Area

K2189

Private Park, Forest, or
Recreation Area
Other Park, Forest, or
Recreation Area (quasipublic, independent park,
commission, etc.)
Post Office

A place or area set aside for recreation or preservation of a cultural or
natural resource and under the administration of a municipal
government.
A privately owned place or area set aside for recreation or preservation
of a cultural or natural resource.
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.
An official facility of the U.S. Postal Service used for processing and
distributing mail and other postal material.
Fire Department.
Police Station.
Library.
City/Town Hall.
A place of employment for wholesale, retail, or other trade
A group of retail establishments within a planned subdivision sharing a
common parking area.
One or more manufacturing establishments within an area zoned for
fabrication, construction, or other similar trades.
One or more structures housing employees performing business,
clerical, or professional services
An agricultural establishment where crops are grown and/or animals
are raised, usually for food.
A place of employments not elsewhere classified or of unknown type.
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.
A place where privately owned, light-craft are moored.
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.
A manmade facility maintained for the use of aircraft [including
airstrip, landing field and landing strip].
A place where travelers can board and exit rail transit lines, including
associated ticketing, freight, and other commercial offices.
A place where travelers can board and exit mass motor vehicle transit,
including associated ticketing, freight, and other commercial offices.
A place where travelers can board and exit water transit or where
cargo is handled, including associated ticketing, freight, and other
commercial offices.
A place where an airplane equipped with floats for landing on or taking
off from a body of water can debark and load.
A major air transportation facility where travelers can board and exit
airplanes and connect with other (i.e. non-air) modes of transportation.

K2190

K2191
K2193
K2194
K2195
K2196
K2300
K2361

K2366
K2400

Fire Department
Police Station
Library
City/Town Hall
Commercial Workplace
Shopping Center or Major
Retail Center
Industrial Building or
Industrial Park
Office Building or Office
Park
Farm/Vineyard/Winery/Or
chard
Other Employment Center
Transportation Terminal

K2424
K2432

Marina
Pier/Dock

K2451

Airport or Airfield

K2452
K2453

Train Station, Trolley or
Mass Transit Rail Station
Bus Terminal

K2454

Marine Terminal

K2455

Seaplane Anchorage

K2456

Airport—Intermodal
Transportation
Hub/Terminal
Airport—Statistical
Representation
Park and Ride
Facility/Parking Lot

K2362
K2363
K2364

K2457
K2458

U.S. Census Bureau

The area of an airport adjusted to include whole 2000 census blocks
used for the delineation of urban areas.
A place where motorists can park their cars and transfer to other
modes of transportation.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-7

MTFCC

Feature Class

K2459

Runway/Taxiway

K2460

Helicopter Landing Pad

K2540

University or College

K2543

School or Academy

K2545

K2561
K2564

Museum, Visitor Center,
Cultural Center, or Tourist
Attraction
Golf Course
Amusement Center

K2582

Cemetery

K2586

Zoo

K3544

Place of Worship

L4010

Pipeline

L4020

Powerline

L4031

Aerial Tramway/Ski Lift

L4110

Fence Line

L4121
L4125

Ridge Line
Cliff/Escarpment

L4130

Point-to-Point Line

L4140

Property/Parcel Line
(Including PLSS)

L4150

Coastline

L4165

Ferry Crossing

P0001

Nonvisible Linear
Legal/Statistical Boundary

U.S. Census Bureau

Feature Class Description
A fairly level and usually paved expanse used by airplanes for taking off
and landing at an airport.
A fairly level and usually paved expanse used by helicopters for taking
off and landing.
A building or group of buildings used as an institution for postsecondary study, teaching, and learning [including seminary].
A building or group of buildings used as an institution for preschool,
elementary or secondary study, teaching, and learning [including
elementary school and high school].
An attraction of historical, cultural, educational or other interest that
provides information or displays artifacts.
A place designed for playing golf.
A facility that offers entertainment performances or sporting events.
Examples include arena, auditorium, theater, stadium, coliseum,
racecourse, theme park, fairgrounds, and shooting range.
A place or area for burying the dead [including burying ground and
memorial garden].
A facility in which terrestrial and/or marine animals are confined within
enclosures and displayed to the public for educational, preservation,
and research purposes.
A sanctified place or structure where people gather for religious
worship; examples include church, synagogue, temple, and mosque.
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.
One or more wires, often on elevated towers, used for conducting
high-voltage electric power.
A conveyance that transports passengers or freight in carriers
suspended from cables and supported by a series of towers.
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.
The line of highest elevation along a ridge.
A very steep or vertical slope [including bluff, crag, head, headland,
nose, palisades, precipice, promontory, rim and rimrock].
A line defined as beginning at one location point and ending at
another, both of which are in sight.
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.
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.
The route used to carry or convey people or cargo back and forth over
a waterbody in a boat.
A legal/statistical boundary line that does not correspond to a
shoreline or other visible feature on the ground.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-8

MTFCC

Feature Class

P0002

Perennial Shoreline

P0003

Intermittent Shoreline

P0004

Other non-visible
bounding Edge (e.g.,
Census water boundary,
boundary of an aerial
feature)
Railroad Feature (Main,
Spur, or Yard)
Carline, Streetcar Track,
Monorail, Other Mass
Transit
Cog Rail Line, Incline Rail
Line, Tram

R1011
R1051
R1052

S1100

Primary Road

S1200

Secondary Road

S1400

Local Neighborhood Road,
Rural Road, City Street

S1500

Vehicular Trail (4WD)

S1630

Ramp

S1640

Service Drive usually along
a limited access highway

S1710

Walkway/Pedestrian Trail

S1720

Stairway

S1730

Alley

S1740

Private Road for service
vehicles (logging, oil fields,
ranches, etc.)
Internal U.S. Census
Bureau use

S1750

U.S. Census Bureau

Feature Class Description
The more-or-less permanent boundary between land and water for a
water feature that exists year-round.
The boundary between land and water (when water is present) for a
water feature that does not exist year-round.
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).
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.
Mass transit rail lines (including lines for rapid transit, monorails,
streetcars, light rail, etc.) that are typically inaccessible to mainstream
railroad traffic and whose tracks are not part of a road right-of-way.
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.
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.
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.
Generally, a paved non-arterial street, road, or byway that usually has 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.
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.
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 and do not carry a name in the MAF/TIGER
System.
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.
A path that is used for walking, being either too narrow for or legally
restricted from vehicular traffic.
A pedestrian passageway from one level to another by a series of
steps.
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.
A road within private property that is privately maintained for service,
extractive, or other purposes. These roads are often unnamed.
Internal U.S. Census Bureau use.

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-9

MTFCC
S1780
S1820

Feature Class
Parking Lot Road
Bike Path or Trail

S1830

Bridle Path

S2000

Road Median

Note:

Feature Class Description
The main travel route for vehicles through a paved parking area.
A path that is used for manual or small, motorized bicycles, being
either too narrow for or legally restricted from vehicular traffic.
A path that is used for horses, being either too narrow for or legally
restricted from vehicular traffic.
The unpaved area or barrier between the carriageways of a divided
road.

The information in this table was last updated in November 2020.

U.S. Census Bureau

Boundary and Annexation Survey Tribal Respondent Guide: Digital

D-10

File Type	application/pdf
File Title	Boundary and Annexation Survey (BAS) Tribal Respondent Guide: Digital
Author	U.S. Census Bureau
File Modified	2020-12-07
File Created	2020-11-27