Boundary and Annexation Survey (BAS) 

Respondent Guide: Digital

Instructions for Participating in the 2018 Boundary and Annexation Survey

Revised as of February 28, 2018

U.S. Department of Commerce

Economic and Statistics Administration

U.S. CENSUS BUREAU

census.gov
This page intentionally left blank
Boundary and Annexation Survey Respondent Guide: Digital Page i

Table of Contents

Paperwork Reduction Act Statement........................................................................................v

Introduction................................................................................................................................vi

A. The Boundary and Annexation Survey........................................................................................ vi

B. What’s New for the 2018 BAS? ................................................................................................... vi

C. Key Dates for BAS Respondents................................................................................................. vi

D. BAS State Agreements................................................................................................................vii

E. Legal Disputes .............................................................................................................................vii

Part 1: Digital BAS Requirements .........................................................................................1

1.1 Digital BAS Participation Requirements .......................................................................................1

1.2 BAS Informational and Tutorial Videos.........................................................................................1

Part 2: Topological Relationships and Spatial Accuracy....................................................2

2.1 Topological Relationships in MAF/TIGER ....................................................................................2

2.2 GIS and Spatial Accuracy.............................................................................................................3

2.3 Census Bureau Topology Training Video.....................................................................................5

Part 3: Census Bureau Provided Shapefiles ........................................................................6

Part 4: Census Bureau Geocoding........................................................................................7

4.1 MAF Structure Point Geocoding...................................................................................................7

4.2 Address Range Geocoding...........................................................................................................8

Part 5: Updating the Census Bureau Shapefiles..................................................................9

5.1 General File Setup Guidelines......................................................................................................9

5.2 Changing the Map Projection .......................................................................................................9

5.3 Boundary Changes .......................................................................................................................9

5.4 Annexations and Deannexations................................................................................................10

5.5 Boundary Corrections .................................................................................................................10

5.6 New Incorporations.....................................................................................................................11

5.7 Disincorporations ........................................................................................................................11

5.8 Geographic Corridors .................................................................................................................12

5.9 Geographic Offsets.....................................................................................................................13

5.10 Linear Feature Updates ..............................................................................................................14

5.11 Area Landmarks, Hydro Areas, and Point Landmarks ...............................................................15

5.12 Reviewing Changes to the Census Bureau Shapefiles..............................................................19

5.13 Additional Review Information ....................................................................................................23

Appendices................................................................................................................................34

Appendix A. Data Dictionary ............................................................................................................. A-1

Appendix B. 2018 Digital BAS Example Process 1......................................................................... B-1

B.1 Required Census Bureau Shapefiles........................................................................................ B-1

B.2 Local Data................................................................................................................................. B-1

B.3 Symbolizing Layers in ArcGIS .................................................................................................. B-1

B.4 Extracting Incorporated Place or MCD Data from Census Shapefiles ..................................... B-2

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

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

B.7 Reviewing and Attributing Change Polygons ........................................................................... B-8

B.8 Renaming and Finalizing Change Polygons........................................................................... B-10
Boundary and Annexation Survey Respondent Guide: Digital Page ii

Appendix C. 2018 Digital Example Process 2.................................................................................. C-1

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

C.2 Local Data................................................................................................................................. C-1

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

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

C.4 Creating and Splitting Linear Features ..................................................................................... C-2

C.4.1 Creating New Linear features ................................................................................................... C-2

C.4.2 Adding Attribute Data To New Linear Features........................................................................ C-4

C.4.3 Splitting Linear Features........................................................................................................... C-4

C.4.4 Selecting Lines and Creating Change Polygons ...................................................................... C-6

C.4.5 Attributing Change Polygons .................................................................................................... C-7

C.4.6 Exporting Change Polygons ..................................................................................................... C-9

Appendix D. MTFCC Descriptions — Complete List....................................................................... D-1
Boundary and Annexation Survey Respondent Guide: Digital Page iii

LIST OF TABLES

Table 1: BAS Naming Conventions. .............................................................................................................6

Table 2: Annexations and Deannexations ..................................................................................................10

Table 3: Boundary Corrections ..................................................................................................................10

Table 4: New Incorporations ..................................................................................................................11

Table 5: Disincorporations ..................................................................................................................12

Table 6: Geographic Corridors ..................................................................................................................13

Table 7: Geographic Offsets ..................................................................................................................14

Table 8: Linear Feature Updates ................................................................................................................14

Table 9. Address Ranges ..................................................................................................................15

Table 10: Landmarks and Hydro Areas ......................................................................................................16

Table 11: Area Landmark MTFCC Codes ..................................................................................................16

Table 12: Point Landmarks ..................................................................................................................17

Table 13: Restricted Point Landmark MTFCC Codes ................................................................................18

Table 14: Change Polygons ..................................................................................................................24

Table 15: Whole Entity Polygons ................................................................................................................24

Table 16: Optional Files ..................................................................................................................25

Table 17: County and Equivalent Areas Shapefile ................................................................................... A-1

Table 18: County Subdivisions Shapefile ................................................................................................. A-2

Table 19: Incorporated Place Shapefile.................................................................................................... A-3

Table 20: Consolidated City Shapefile...................................................................................................... A-4

Table 21: Edges Shapefile ................................................................................................................ A-5

Table 22: Area Landmark Shapefile ......................................................................................................... A-6

Table 23: Hydro Area Shapefile................................................................................................................ A-6

Table 24: Point Landmark Shapefile......................................................................................................... A-7

Table 25: Geographic Offset Shapefile..................................................................................................... A-7

Table 26: Suggested MTFCC Symbolization............................................................................................ B-1

Table 27: Suggested MTFCC Symbolization............................................................................................ C-1

Table 28: MTFCC List ................................................................................................................ D-1
Boundary and Annexation Survey Respondent Guide: Digital Page iv

LIST OF FIGURES

Figure 1. Road Representing 3 Types of Boundaries...................................................................................2

Figure 2. Typological Integration of Four Classes ........................................................................................3

Figure 3. Overlay of Four Feature Classes...................................................................................................4

Figure 4. GIS Place Boundary Does Not Follow Road Feature....................................................................4

Figure 5. MSP Method of Geocoding............................................................................................................7

Figure 6. Address Range Method of Geocoding ..........................................................................................8

Figure 7. Geographic Corridor Created ......................................................................................................12

Figure 8. Geographic Corridor Not Created................................................................................................12

Figure 9. Cadastral Data ..................................................................................................................13

Figure 10. Same Data Edited to Census Requirements.............................................................................13

Figure 11. A Boundary Correction to Park A...............................................................................................15

Figure 12. Boundary Corrections Not Snapped to Existing Linear Features..............................................19

Figure 13. Annexation Created without Snapping to Centerlines...............................................................20

Figure 14. Small Saptial Correction Not Incorporated ................................................................................20

Figure 15. Small Spatial Correction Not Accepted .....................................................................................21

Figure 16. Large Boundary Corrections......................................................................................................21

Figure 17. New Road Features, Not Added to Existing Road ....................................................................22

Figure 18. New Road Features, Correctly Added.......................................................................................22

Figure 19. Selecting and Zipping Return Files............................................................................................26

Figure 20. Naming the Zip File ..................................................................................................................26

Figure 21. SWIM Account Registration.......................................................................................................28

Figure 22. SWIM Login Window .................................................................................................................28

Figure 23. Welcome Screen with Upload History .......................................................................................29

Figure 24. Geographic Partnership Program Selection Window ................................................................29

Figure 25. Geographic Level Selection Window.........................................................................................30

Figure 26. Geographic Entity Selection Window.........................................................................................30

Figure 27. File Upload Screen ..................................................................................................................31

Figure 28. File Browser Dialog Box ............................................................................................................31

Figure 29. Entering Comments into the File Upload Window.....................................................................32

Figure 30. Thank You Screen ..................................................................................................................32

Figure 31. Suggested Map Symbolization ................................................................................................ B-2

Figure 32. Filtering Data ................................................................................................................ B-3

Figure 33. Export Data Window ................................................................................................................ B-4

Figure 34. Finalizing the Merge Process .................................................................................................. B-4

Figure 35. Finalizing the Symmetrical Difference Process ....................................................................... B-5

Figure 36. Finalizing the Union Process ................................................................................................... B-6

Figure 37. Locating the Union Shapefile................................................................................................... B-7

Figure 38. Small Slivers That Should Be Deleted..................................................................................... B-8

Figure 39. Polygons That Should Be Snapped to Roads or Rivers.......................................................... B-8

Figure 40. Suggested Map Symbolization ................................................................................................ C-2

Figure 41. Create Features Window......................................................................................................... C-3

Figure 42. Snapping Toolbar ................................................................................................................ C-3

Figure 43. A Newly Created Linear Feature ............................................................................................. C-4

Figure 44. Linear Feature Selection Before Being Split............................................................................ C-5

Figure 45. Linear Feature Selection After Being Split............................................................................... C-5

Figure 46. Selecting the Linear Features of a Change Polygon............................................................... C-6

Figure 47. Newly Created Place Feature.................................................................................................. C-7

Figure 48. Select All Change Types Formula ........................................................................................... C-9

Figure 49. Exporting Data .............................................................................................................. C-10
Boundary and Annexation Survey Respondent Guide: Digital Page v

PAPERWORK REDUCTION ACT STATEMENT

A federal agency may not conduct or sponsor, nor shall a person be subject to a penalty for 

failure to comply with a collection of information subject to the requirements of the Paperwork 

Reduction Act (PRA) unless that collection of information displays a current valid Office of 

Management and Budget (OMB) Control Number. This collection is voluntary. The authority for 

conducting this collection comes from Title 13 Unites States Code (U.S.C.), Section 6

Paperwork Reduction Act.

The OMB Control Number for this information collection is 0607-0151. Public reporting for this 

collection of information is estimated to be approximately 2 hours per response, including the 

time for reviewing instructions, completing and reviewing the collection of information.

Comments concerning the accuracy of this burden and suggestions for reducing the burden 

should be directed to:

Paperwork Reduction 0607-0151

United States Census Bureau

4600 Silver Hill Road, Room 4H177

Washington, DC 20233

The Census Bureau issued a Federal Register Notice to revise its confidentiality pledge 

language to address the new cybersecurity screening requirements:

Per the Federal Cybersecurity Enhancement Act of 2015, your data are protected from 

cybersecurity risks through screening of the systems that transmit your data.
Boundary and Annexation Survey Respondent Guide: Digital Page vi

INTRODUCTION

A. The Boundary and Annexation Survey

The U.S. Census Bureau (Census Bureau) conducts an annual survey called the Boundary and 

Annexation Survey (BAS) 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, Hawaiian Homelands, and Alaska Native Regional Corporations 

(ANRC). BAS also provides an opportunity for participants to review the names and geographic 

relationships for these areas. Title 13, U.S.C., Section 6, authorizes this survey.

The Census Bureau uses the boundary information collected during the BAS to tabulate data for 

the decennial and economic censuses, and to support the Population Estimates Program (PEP) 

and the American Community Survey (ACS). Maintaining correct boundaries and boundary-tofeature relationships through the BAS helps ensure that the Census Bureau assigns the 

appropriate population to each governmental unit (GU).

In compliance with the Office of Management and Budget Circular A-16, the 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 

GUs.

In addition, the 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, ANRC, and federally recognized AIAs, which include reservations and offreservation trust lands used by the U.S. Geological Survey’s (USGS), the National Map, and the 

Geographic Names Information System (GNIS).

Please visit the BAS program Web site at <https://www.census.gov/programssurveys/bas.html>. For more information on the BAS, please view the “Introduction to BAS” 

video series on the Census Bureau’s BAS Web site at <https://www.census.gov/programssurveys/bas/library/videos/bas-intro.html>

B. What’s New for the 2018 BAS?

1. The Geographic Partnership Support Desk (GPSD) is now fully functional and available to assist 

with any questions respondents may have regarding BAS.

2. Redistricting data contacts participating in the Voting District Project (VTD) may submit boundary 

updates for reconciliation with BAS contacts.

C. Key Dates for BAS Respondents

January 1, 2018 — All boundary changes must be legally in effect on or before this date to be 

reported in the 2018 BAS.

March 1, 2018 — BAS submission date deadline for boundary updates to be reflected in the 

ACS and PEP published data. Boundary submissions received by this date are also reflected in 

next year’s BAS materials.

May 31, 2018 — BAS boundary updates submitted by this date will be reflected in next year’s 

BAS materials. 
Boundary and Annexation Survey Respondent Guide: Digital Page vii

D. BAS State Agreements

The Census Bureau has established a number of arrangements with states for reporting 

boundary changes. Please visit the BAS State Agreements webpage within the BAS program 

Web site at <https://www.census.gov/programs-surveys/bas/information/stateagreements.html> or call (800) 972-5651 for information regarding state agreements.

Note: The Census Bureau can only establish BAS state agreements for states that require local 

governments to report boundary changes to a state agency.

E. 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. 

If you have questions concerning this, please contact the Census Bureau Legal Office at 

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.
Boundary and Annexation Survey Respondent Guide: Digital Page 1

PART 1: DIGITAL BAS REQUIREMENTS

1.1 Digital BAS Participation Requirements

1. All participants must have the ability to edit a Census Bureau shapefile. The Census Bureau 

requires that entities update Census Bureau shapefiles with boundary and feature changes, 

rather than submitting a shapefile from a local Geographic Information System (GIS).

2. All participants must provide current information for the BAS point of contact, the person 

updating the shapefiles, and the highest elected official (HEO) for the entity.

3. All participants must provide legal documentation numbers and effective dates for all legal 

boundary changes (annexations and deannexations). 

4. Each non-legal boundary correction must contain proper update documentation according to 

boundary correction guidelines listed below, or the Census Bureau will not make the correction 

for this BAS cycle.

All participants must use the SWIM to submit their changes to the Census Bureau. Due to 

security requirements, we cannot accept submissions via FTP, email or any protocol other than 

the SWIM site (<https://respond.census.gov/swim/>). If you indicated on your Annual Response 

Form that you wished to receive the GUPS application, you will automatically receive the SWIM 

URL and a registration token via email. The email should arrive 5 days after the Annual 

Response is completed online (or 5 business days after the Census Bureau receives the paper 

form). To access the SWIM, enter the following URL in a new browser window:

<https://respond.census.gov/swim/>.

1.2 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 

Web site at: <https://www.census.gov/programs-surveys/bas/library/videos/bas-intro.html>.

If there are any questions or concerns about the participation requirements, contact the Census 

Bureau at 1-800-972-5651 or geo.bas@census.gov.
Boundary and Annexation Survey Respondent Guide: Digital Page 2

PART 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 MAF/TIGER

At the Census Bureau, we describe topology as the relationship between different levels of 

geography. MAF/TIGER 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 entities for which the Census Bureau tabulates 

data.

Instead of having a separate layer for each feature class (roads, boundaries, etc.) all 

MAF/TIGER information is stored in one layer or file. See Figure 1 and Figure 2 for samples of 

topologically integrated files in MAF/TIGER.

Figure 1. Road Representing 3 Types of Boundaries

This example shows how a road in MAF/TIGER can also represent 

a block boundary, place boundary and a school district boundary.
Boundary and Annexation Survey Respondent Guide: Digital Page 3

Figure 2. Typological 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, place 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 you overlay these layers in a GIS, there may be boundary 

misalignments due to the nature of the data. These non-topologically integrated layers could 

cause issues in MAF/TIGER. Figure 3 and Figure 4 show how files that are not topologically 

integrated might appear in a GIS when overlaid.
Boundary and Annexation Survey Respondent Guide: Digital Page 4

Figure 3. Overlay of Four Feature Classes

This example shows an overlay of four different feature classes. 

Notice how the topological relationship is compromised. The block, 

place, and school district boundaries, which are supposed to follow 

the road feature, are no longer aligned with the road in several 

locations.

Figure 4. GIS Place Boundary Does Not Follow Road Feature

This example shows a situation where a local GIS place boundary 

does not follow a road feature. Assuming that the boundary follows 

the road feature, changing the Census Bureau place boundary to 

match the local file exactly and become misaligned (see arrows) 

would dissolve the topological relationship in MAF/TIGER.
Boundary and Annexation Survey Respondent Guide: Digital Page 5

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. Part 5: Updating the Census Bureau Shapefiles, 

Section 5.12 provides instructions on how to review digital submissions for small spatial 

boundary corrections. It also lists some of the potential consequences of making spatial 

boundary corrections that dissolve the topological relationships present in MAF/TIGER. 

You may find examples of suggested methods for correctly making boundary changes in 

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 

the BAS. For more information, please go to 

<https://www.census.gov/library/video/intro_bas_topology.html> where you can watch the video.
Boundary and Annexation Survey Respondent Guide: Digital Page 6

PART 3: CENSUS BUREAU PROVIDED SHAPEFILES

Please download shapefiles from the BAS Web site at: 

<https://www.census.gov/geographies/mapping-files/2018/geo/bas/2018-bas-shapefiles.html> in 

order to review your boundaries and submit changes.

The Census Bureau provides entity layers in ESRI shapefile format for download via the BAS 

Web site. Regardless of the number of geographic entity polygon based shapefiles each 

participant downloads and edits, there is only one shapefile for the linear feature network for 

each county. See Table 1 for the names of the shapefiles.

Table 1: BAS Naming Conventions.

Geographic Entity Type Shapefile Naming Convention

County PVS_17_v2_county_<ssccc>.shp

Minor Civil Division PVS_17_v2_mcd_<ssccc>.shp

Incorporated Place PVS_17_v2_place_<ssccc>.shp

Consolidated City PVS_17_v2_concity_<ssccc>.shp

Edges (Roads, Rail, Hydro, etc.) PVS_17_v2_edges_<ssccc>.shp

Area Landmarks PVS_17_v2_arealm_<ssccc>.shp

Point Landmarks PVS_17_v2_pointlm_<ssccc>.shp

Hydro Area PVS_17_v2_water_<ssccc>.shp

Geographic Offsets / Corridors PVS_17_v2_offset_<ssccc>.shp

Note: <ssccc> represents the two-digit state FIPS code and three-digit county FIPS code.

All shapefiles provided by the Census Bureau are in the following unprojected geographicbased coordinate system:

 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
Boundary and Annexation Survey Respondent Guide: Digital Page 7

PART 4: CENSUS BUREAU GEOCODING

Geocoding is how the Census Bureau codes population to geographic entities. There are two 

primary methods of geocoding used by the Census Bureau. Both of these involve coding an 

address to a spatial polygon, but one uses Global Positioning System (GPS) technology, while 

the other uses address ranges.

4.1 MAF Structure Point Geocoding

A field worker stands in front of a house or living quarters, and records the physical location with 

a GPS device (Figure 5). 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 5. MSP Method of Geocoding

MAF Structure Point (MSP) 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.
Boundary and Annexation Survey Respondent Guide: Digital Page 8

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 6).

Figure 6. 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 front lot 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 

MAF/TIGER. 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.

When completing a BAS submission in which a road or road right-of-way is owned or 

maintained by a place 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. If local 

or state law requires the use of the front lot line boundary, the respondent must explicitly 

designate the polygon(s) between the road centerline and the front-lot boundary as a 

corridor or an offset (see Section 5.4 and Section 5.5 of this document for more 

details).
Boundary and Annexation Survey Respondent Guide: Digital Page 9

PART 5: UPDATING THE CENSUS BUREAU SHAPEFILES

Census Bureau shapefiles can be updated to reflect boundary and/or linear feature changes 

that have occurred since the last BAS update. Please go to Appendix B and Appendix C and 

watch the Digital BAS demonstration video series at <https://www.census.gov/programssurveys/bas/library/videos/digital-bas.html>for more examples.

Note: 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.

5.1 General File Setup Guidelines

After downloading the shapefiles from the PVS download page, follow these procedures before

beginning actual updates:

 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.

5.2 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 ArcView to update files, activate and utilize 

ArcView’s Projection Utility Wizard extension. If using ArcGIS, use its Project tool in 

ArcToolbox. MAF/TIGER shapefile extracts contain defined projection information in the *.prj 

file. ArcView and ArcGIS access 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 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 MAF/TIGER, participants must create a separate change polygon layer for 

each updated entity type (county, MCD, place). Please create change polygons in relation to the 

current MAF/TIGER boundary. 

Appendix B and Appendix C provide two examples for creating annexation, 

deannexation, boundary correction, new incorporation, geographic corridor, and 

geographic offset change polygons. Review any boundary change polygons before 

submitting them (Section 5.8).

If you need additional shapefiles, please contact the Census Bureau at 1-800-972-5651 or 

geo.bas@census.gov.
Boundary and Annexation Survey Respondent Guide: Digital Page 10

5.4 Annexations and Deannexations

The Census Bureau will accept annexations and deannexations from counties, MCDs, and 

incorporated places. Each annexation or deannexation change polygon must have the required 

attributes and corresponding change type populated, as seen in Table 2. The Census Bureau 

will snap any annexation or deannexation to a MAF/TIGER feature when it exists within thirty

feet of that feature.

Note: Enter the name of the jurisdiction annexing or deannexing the area in the NAME field.

Table 2: Annexations and Deannexations

NAME CHNG_TYPE EFF_DATE AUTHTYPE

DOCU

(Not 

Required in 

GA)

AREA

(Required 

in GA)

RELATE

Annexation X X(‘A’) X X X * See Note

Deannexation X X(‘D’) X X X * See Note

(Note: ‘X’ = Required Field).

Note: Area in acres is required for Georgia, and requested for all other areas.

5.5 Boundary Corrections

The Census Bureau will also accept specific boundary corrections from counties, MCDs, and 

incorporated places. As with annexations and deannexations, 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 3, or 

the Census Bureau will reject them. 

Note: Enter the name of the jurisdiction the boundary correction is for in the NAME field.

Table 3: Boundary Corrections

NAME CHNG_TYPE EFF_DATE AUTHTYPE DOCU AREA RELATE

Boundary Correction

(Add Area)

X X(‘B’) X(‘IN’)

Boundary Correction

(Remove Area)

X X(‘B’) X(‘OUT’)

The Census Bureau uses a topologically integrated database. As a result, the Census Bureau 

cannot process all types of boundary corrections for inclusion in MAF/TIGER. The following are 

types of boundary corrections that the Census Bureau will accept, process, and update or reject 

during the current BAS.
Boundary and Annexation Survey Respondent Guide: Digital Page 11

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 (annexation, 

deannexation, 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; and

 Where the overall shape of the geographic entity is maintained and no feature-to-boundary 

relationships are dissolved.

The Census Bureau will reject boundary corrections:

 Along county boundaries unless there is a written agreement between the two counties that 

documents the correct location of the boundary;

 Between adjacent incorporated places or adjacent MCDs unless the county submitting the 

changes is part of a consolidated county agreement or there is a written agreement between the 

two incorporated places or MCDs;

 That dissolves 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 entity boundary. 

These boundary corrections may be part of annexations that were never reported to the Census 

Bureau. If they are previously unreported boundary changes, please include effective dates and 

legal documentation numbers for these changes; and

 That have a width of less than thirty feet over the entire polygon.

Note: Remember that the Census Bureau will snap any entity boundary correction to a MAF/TIGER 

feature when it exists within thirty feet of that feature.

5.6 New Incorporations

County participants may submit new incorporations for incorporated places and MCDs through 

Digital BAS. As with other change types, an individual change polygon must be created for each 

new incorporation and possess the required attributes and the corresponding change type field 

must be populated (see Table 4).

Note: Enter the name of the new jurisdiction in the NAME field. For required documentation for new 

incorporations, contact the Census Bureau at 1-800-972-5651 or geo.bas@census.gov.

Table 4: New Incorporations

NAME CHNG_TYPE EFF_DATE AUTHTYPE DOCU AREA RELATE

New 

Incorporation X X(‘E’) X X X

(Note: ‘X’ = Required Field).

5.7 Disincorporations

County participants may submit disincorporations through Digital BAS. As with other change 

types, an individual change polygon for each disincorporation and must possess the required 

attributes and the corresponding change type must be populated.
Boundary and Annexation Survey Respondent Guide: Digital Page 12

Table 5: Disincorporations

NAME CHNG_TYPE EFF_DATE AUTHTYPE DOCU AREA RELATE

Disincorporation X X(‘X’) X X X

(Note: ‘X’ = Required Field).

5.8 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 entity, 

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 7 shows a corridor created where 

the incorporated place owns the right-of-way but the housing units are not included in the 

incorporated place (shown in color).

Figure 8 shows that the right-of-way belongs in the unincorporated area, while the housing units 

are included in the incorporated place (shown in color). This is important for some cities 

because they are portraying that the city is not responsible for road maintenance. This is not 

relevant for Census Bureau tabulations and is not easy to depict in the MAF/TIGER. This type of 

corridor should not be included in a BAS response.

 

Figure 7. Geographic Corridor Created

Figure 8. Geographic Corridor Not Created

The image on the left (Figure 7) shows that a geographic corridor 

should be created to allow for proper geocoding of homes. The 

image on the right (Figure 8) 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. In the RELATE field, indicate whether the change is adding 

IN or taking OUT (removing) the corridor.
Boundary and Annexation Survey Respondent Guide: Digital Page 13

Table 6: Geographic Corridors

NAME CHNG_TYPE EFF_DATE AUTHTYPE DOCU AREA RELATE

Geographic 

Corridor X X(‘C’) X(’IN’, ‘OUT’)

(Note: ‘X’ = Required Field)

5.9 Geographic Offsets

A geographic offset is an area claimed by a geographic entity 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 an entity boundary to the centerline wherever applicable will help to establish more 

accurate population counts. If a boundary is the front lot line, the 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 9 depicts a cadastral (parcel-based) boundary map and 

Figure 10 shows how the boundary should be reported when sent to the Census Bureau.

 

Figure 9. Cadastral Data

Figure 10. Same Data Edited to Census Requirements

On the left in Figure 9 is an example of cadastral data. Figure 10

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. In the RELATE field, indicate whether the change is adding 

IN or taking OUT (removing) the area represented as an offset.
Boundary and Annexation Survey Respondent Guide: Digital Page 14

Table 7: Geographic Offsets

NAME CHNG_TYPE EFF_DATE AUTHTYPE DOCU AREA RELATE

Geographic 

Offset X X(‘F’) X (’IN’, ‘OUT’)

(Note: ‘X’ = Required Field).

The Census Bureau has included an “offset” shapefile in the BAS materials 

(PVS_yy_v2_offset_<ssccc>.shp), so that your jurisdiction can be checked for any existing 

corridors or offsets. While the Census Bureau prefers that you do not create new offsets, (see 

above), this information can be helpful in determining if current boundaries are correct.

5.10 Linear Feature Updates

5.10.1 Adding, Deleting, Renaming, and Recoding Linear Features

The Census Bureau will accept linear feature modifications when needed. Please submit linear 

feature updates in a separate linear feature update layer. Each linear feature update must have 

the required attributes and corresponding change type populated, as seen in Table 8. In the 

TLID field, preserve the existing TLID for the feature.

Table 8: Linear Feature Updates

CHNG_TYPE TLID FULLNAME MTFCC

Add Feature X(‘AL’) X X

Delete Feature X(‘DL’) X

Rename Feature X(‘CA’) X X

Recode Feature X(‘CA’) X X

(Note: ‘X’ = Required Field).

Note: A list of MTFCC codes can be found in 0.

5.10.2 Linear Feature Update Guidelines

 If a road, subdivision, etc. is missing from the Census Bureau’s feature network, add the 

feature(s) and provide the name and MTFC;

 If a feature that does not exist is in the Census Bureau’s feature network, delete the feature; and

 If a feature is in the incorrect location in the Census Bureau’s feature network, delete the feature 

and re-add it in the correct location. Only do this if the feature is very far off or in the wrong 

position relative to boundaries or other features.
Boundary and Annexation Survey Respondent Guide: Digital Page 15

5.10.3 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 our 

outgoing shapefiles, we recommend that participants generally only add address ranges to new 

features (see Table 9).

Table 9. Address Ranges 

CHNG_TYPE FULLNAME MTFCC LTOADD RTOADD LFROMADD RFROMADD

Address 

Ranges X(‘CA’) X X X X

(Note: ‘X’ = Required Field)

5.11 Area Landmarks, Hydro Areas, and Point Landmarks

5.11.1 Area Landmark/Hydro Area Updates

The Census Bureau accepts updates to area landmarks and hydro areas in a similar manner to 

legal boundary changes. However, area landmarks and hydro areas are not legal entities, so no 

documentation or effective dates are required. 

In order to submit area landmark and hydro area updates, create a separate change polygon 

layer. Updates to area landmarks and hydro areas include: 

 Boundary corrections (adding and removing area);

 Creating a new area landmark or hydro area;

 Removing an area landmark or hydro area; and

 Name changes.

Figure 11. A Boundary Correction to Park A

Each area landmark or hydro area update must have the required attributes and corresponding 

change type populated. In the AREAID field, preserve the existing AREAID for the feature 

(refer to Table 10).
Boundary and Annexation Survey Respondent Guide: Digital Page 16

Table 10: Landmarks and Hydro Areas

FULLNAME CHNG_TYPE RELATE MTFCC AREAID

Boundary Correction

(Add Area) X X(‘B’) X(‘IN’) X

Boundary Correction

(Remove Area) X X(‘B’) X(‘OUT’)

X

Delete Landmark X(‘D’) X

Change Landmark Name X X(‘G’) X

New Landmark X X(‘E’) X

(Note: ‘X’ = Required Field).

The examples inAppendix B and Appendix C provide information on how to create change 

polygons. While the sample processes are written for legal boundary changes, the same 

methods apply for creating change polygons for area landmarks and hydro areas. When adding 

new area landmarks or hydro areas, only add the following types of areas: 

 Water bodies;

 Glaciers;

 Airports;

 Cemeteries;

 Golf courses; and

 Parks.

The Census Bureau cannot add other types of areas at this time (although some may already 

exist in MAF/TIGER). The following are acceptable MTFCC codes for new area landmarks or 

hydro areas:

Table 11: Area Landmark MTFCC Codes

MTFCC Description 

H2030 Lake/Pond

H2040 Reservoir

H2041 Treatment Pond

H2051 Bay/Estuary/Gulf/Sound

H2081 Glacier

C3023 Island

K1231 Hospital/Hospice/Urgent Care Facility

K1235 Juvenile Institution

K1236 Local Jail or Detention Center 

K1237 Federal Penitentiary, State Prison, or Prison Farm

K2110 Military Installation

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

K2185 Regional Park, Forest, or Recreation Area
Boundary and Annexation Survey Respondent Guide: Digital Page 17

MTFCC Description 

K2186 County Park, Forest, or Recreation Area

K2187 County Subdivision Park, Forest, or Recreation Area

K2188 Incorporated Place Park, Forest, or Recreation Area

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

The Census Bureau prioritizes boundary changes to legal areas in order to meet ACS, PEP, 

and BAS deadlines. Therefore, there may be delays in incorporating area landmark and 

hydrographic area changes to MAF/TIGER. Please do not resubmit any changes that were sent 

during the previous year’s BAS. We are working on incorporating those changes, and they will 

be reflected in the next year’s BAS materials. 

5.11.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; and

 Renaming a point landmark.

Each point landmark update must have the required attributes and corresponding change type 

populated. In the POINTID field, preserve the existing POINTID for the feature.

Table 12: Point Landmarks

FULLNAME CHNG_TYPE MTFCC POINTID

New Point Landmark X X(‘E’) X

Delete Point Landmark X(‘D’) X

Change Name X X(‘G’) X

(Note: ‘X’ = Required Field).

The Census Bureau cannot make the following point landmark changes due to Title 13 privacy 

concerns. Do not include any of the following types of landmarks in the point landmark changes 

file.
Boundary and Annexation Survey Respondent Guide: Digital Page 18

Table 13: Restricted Point Landmark MTFCC Codes

MTFCC Description

K1100 Housing Unit Location

K1121 Apartment Building or Complex

K1122 Rooming or Boarding House

K1223 Trailer Court or Mobile Home Park

K1226 Housing Facility/Dormitory for Workers

K1227 Hotel, Motel, Resort, Spa, Hostel, YMCA, or YWCA

K1228 Campground

K1229 Shelter or Mission

K1232 Halfway House/Group Home

K1233 Nursing Home, Retirement Home, or Home for the Aged

K1234 County Home or Poor Farm

K1235 Juvenile Institution

K1241 Sorority, Fraternity, or College Dormitory

K1251 Military Group Quarters

K1299 Other Group Quarters Location

K2100 Governmental

K2197 Mixed Use/Other Non-residential

K2300 Commercial Workplace

K2361 Shopping Center or Major Retail Center

K2362 Industrial Building or Industrial Park

K2363 Office Building or Office Park

K2364 Farm/Vineyard/Winery/Orchard

K2366 Other Employment Center

K2464 Marina

K2500 Other Workplace

K2564 Amusement Center

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); and

 C3061 (Cul-de-sacs).

The Census Bureau prioritizes boundary changes to legal areas in order to meet ACS, PEP, 

and BAS deadlines. Therefore, there may be delays in incorporating point landmark changes to 

MAF/TIGER. Please do not resubmit any changes that were sent during the previous year’s 

BAS. We are working on incorporating those changes, and they will be reflected in the next 

year’s BAS materials.
Boundary and Annexation Survey Respondent Guide: Digital Page 19

5.12 Reviewing Changes to the Census Bureau Shapefiles

Please review all changes to ensure that they are intentional and correct. The video series 

“Introduction to the Digital BAS” can be found on the Web site at: 

<https://www.census.gov/programs-surveys/bas/library/videos/bas-intro.html>. The videos have 

information on many of the topics below.

5.12.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. Therefore, snap boundaries to street 

centerlines (or rivers, railroads, etc.) wherever applicable. This will help establish a more 

accurate population count for entities.

The following examples show situations where boundary changes should be snapped to 

existing linear features. The Census Bureau will snap boundary changes to any linear feature 

within thirty feet.

Figure 12. Boundary Corrections Not Snapped to Existing Linear Features

These boundary corrections are not snapped to existing linear 

features in MAF/TIGER. Both boundary corrections should be 

snapped to centerlines or population may be assigned to incorrect 

entities.
Boundary and Annexation Survey Respondent Guide: Digital Page 20

Figure 13. Annexation Created without Snapping to Centerlines

This is an example of an annexation created without snapping to 

existing centerlines in MAF/TIGER. Unless the boundary is 

snapped to centerlines, some of the population may be assigned to 

an incorrect entity.

The Census Bureau will not accept boundary corrections that dissolve the current relationship 

between an existing boundary and linear feature, without specific instruction 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 MAF/TIGER. 

See below for examples of changes that will not be accepted.

Figure 14. Small Saptial Correction Not Incorporated

Small spatial boundary corrections would dissolve the relationship 

with the river. These boundary corrections will not be incorporated 

into MAF/TIGER.
Boundary and Annexation Survey Respondent Guide: Digital Page 21

Figure 15. Small Spatial Correction Not Accepted

Small spatial boundary corrections would dissolve the boundary-tofeature 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.12.2 Large Boundary Corrections

The Census Bureau will not accept large boundary corrections to an entity without the 

appropriate legal documentation numbers and effective dates. These large boundary 

corrections 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 MAF/TIGER.

Figure 16. Large Boundary Corrections

Without the appropriate documentation, the Census Bureau will not 

accept large boundary corrections.
Boundary and Annexation Survey Respondent Guide: Digital Page 22

Note: 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.

5.12.3 Including 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 MAF/TIGER. See Section 5.3 for the required 

attribute information and corresponding change type codes.

5.12.4 Including Appropriate Metadata (Projection Information)

It is important that the appropriate projection information is included. Each update layer 

submitted should contain a *.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 MAF/TIGER.

5.12.5 Linear Feature Updates

Please review linear feature changes to ensure that they align with the features currently in 

MAF/TIGER. 

If linear feature changes do not align with current MAF/TIGER linear features, the Census 

Bureau may not incorporate the submitted updates.

 

Figure 17. New Road Features, Not Added to Existing Road

Figure 18. New Road Features, Correctly Added

The image on the left (Figure 17) shows new road features added 

to the existing feature network, but not connected to existing road 

features. The image on the right (Figure 18) shows the correction 

connecting the new roads to the existing road features.
Boundary and Annexation Survey Respondent Guide: Digital Page 23

5.13 Additional Review Information

The Census Bureau will not make any boundary change that affects adjacent legal entities 

without the appropriate documentation. Please review any change polygons that affect adjacent 

entities to determine if they are intentional, legal changes.

Note: Census Bureau will snap any annexation, deannexation, or boundary correction to a MAF/TIGER 

feature when it exists within thirty feet of that feature. This helps maintain the boundary-to-feature 

relationships in MAF/TIGER and will ensure correct housing tabulation counts for entities.

5.13.1 Submitting Digital Data

If a participant is reporting changes to the BAS, the Census Bureau requires that each 

participant submit at least one shapefile (change polygons). The total number of layers 

submitted depends on what types of changes are reported. The following is a list of change files

that may need to be submitted:

1. Change Polygon Layers (County, Minor Civil Division, Incorporated Place, and Consolidated 

City)

 These layers consist of the changes that the Census Bureau needs to make to entities; and

 A layer of change polygons should be created for each level of geography (county, MCD, 

place, etc.) that changes are being submitted for.

2. Whole Modified Entity Layer (County, Minor Civil Division, Incorporated Place, and 

Consolidated City)

 These layers should only contain the complete and current boundary for the entity being 

updated; and

 A whole entity layer should be created for each level of geography that change polygons are 

being created for.

3. Local Government Feature Network 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/Hydro Landmark Update Layer 

 An area/hydro landmark update layer should be submitted only if there are area and/or hydro 

landmark updates.

6. Point Landmark Update Layer

 A point area 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:

<http://www.census.gov/geo/partnerships/bas/bas_ar_form.html>; and

 This update should include this information:

o First Name;

o Last Name;
Boundary and Annexation Survey Respondent Guide: Digital Page 24

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 HEO Term Expires: xx/xxxx; and

o HEO Term Length: x years.

5.13.2 Change Polygon Naming Conventions

The following table provides change polygon naming conventions for county submissions,

county subdivisions, incorporated places, and consolidated cities. The change polygon layer 

naming conventions: <basID> represents your BAS entity ID, found on the BAS Annual 

Response email or online from this link: <https://www.census.gov/programssurveys/bas/technical-documentation/code-lists.html>.

Table 14: Change Polygons

Participant Changes Submitted For: Shape file Naming Conventions

County County bas18_<basID>_changes_county

County Minor Civil Division bas18_<basID>_changes_cousub

County Incorporated Place bas18_<basID>_changes_incplace

Minor Civil Division Minor Civil Division bas18_<basID>_changes_cousub

Incorporated Place Incorporated Place bas18_<basID>_changes_incplace

Consolidated City Consolidated City bas18_<basID>_changes_concity

5.13.3 Whole Entity Polygon Naming Conventions

The following table provides the whole entity polygon naming conventions for consolidated 

county submissions, county subdivisions, incorporated places, and consolidated cities. The 

whole entity polygon layer naming conventions: <basID> represents your BAS entity ID, found 

on the BAS Annual Response email or online from this link: <https://www.census.gov/programssurveys/bas/technical-documentation/code-lists.html>.

Table 15: Whole Entity Polygons

Participant: Changes Submitted For: Shapefile Naming Conventions

County County bas18_<basID>_WholeEntity_county

County Minor Civil Division bas18_<basID>_WholeEntity_cousub
Boundary and Annexation Survey Respondent Guide: Digital Page 25

Participant: Changes Submitted For: Shapefile Naming Conventions

County Incorporated Place bas18_<basID>_WholeEntity_incplace

Minor Civil Division Minor Civil Division bas18_<basID>_WholeEntity_cousub

Incorporated Place Incorporated Place bas18_<basID>_WholeEntity_incplace

Consolidated City Consolidated City bas18_<basID>_WholeEntity_concity

5.13.4 Linear Feature, Area Landmark/Hydro 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 naming conventions for the edges, area 

landmark, and point landmark update layers: <basID> represents your BAS entity ID found on 

the BAS Annual Response email or online from this link: <https://www.census.gov/programssurveys/bas/technical-documentation/code-lists.html>.

Table 16: Optional Files

Participant: Changes Submitted For: Shapefile Naming Conventions

All Participants Edges bas18_<basID>_LN_Changes

All Participants Area / Hydro Landmarks bas18_<basID>_Alndk_Changes

All Participants Point Landmarks bas18_<basID>_Plndk_Changes

5.13.5 Compressing the Digital Files

The SWIM requires all BAS returns to be zipped prior to submission. Please compress ALL 

update materials (including change polygon shapefiles, whole entity shapefiles, linear feature 

updates, landmark updates, local government feature network and boundary layers, and the text 

or other file with your updated BAS contact information). 

1. Navigate to the directory with the shapefiles.

Note: Centerline files or any additional information that may be helpful for Census to process your 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.

2. Select all files and right click on the selection.

3. Select WinZip, and then Add to Zip file.
Boundary and Annexation Survey Respondent Guide: Digital Page 26

Figure 19. 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.

In the Add window, in the Add to archive field, type the filename in the proper naming 

convention: bas<yy>_<basID>_return and then click Add.

Note: Look for the basID number on the BAS Annual Response email or online from this link:

<https://www.census.gov/programs-surveys/bas/technical-documentation/code-lists.html>.

Figure 20. Naming the Zip File

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.
Boundary and Annexation Survey Respondent Guide: Digital Page 27

Note: If you require assistance in preparing or zipping the BAS return files, please call the Census 

Bureau at 1-800-972-5651.

5.13.6 Submitting Digital Files via SWIM

The Secure Web Incoming Module (SWIM) is a one-stop location for submitting your 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 your submission as an email attachment, as we cannot accept them due to the 

security policy at the Census Bureau. 

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 

<http://www.census.gov/geo/partnerships/bas/bas_ar_form.html>. 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 you have registered for an 

account in SWIM, you will no longer need the token to login into the system. If you require 

additional individual SWIM accounts within your organization, please contact the Census 

Bureau at 1-800-972-5651 or email geo.bas@census.gov. Moreover, if you are a participant for 

other Census Bureau geographic programs, you only need one SWIM account to submit files for 

all geographic programs. 

At this time, SWIM only accepts ZIP files. Please zip all your update materials (e.g., spatial 

updates and other relevant update documents) into one ZIP file for your entity’s submission, and 

follow the instructions listed below:

1. In a web browser, go to <https://respond.census.gov/swim>.

2. Login:

a) New Users: You must have a registration token to create a new account. (Please see above).

Once you have your token, please 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.

b) Existing Users: If you already have a registered account from a previous BAS year, please 

login with your user credentials.

Current SWIM Users

If you are a participant in another Census Bureau partnership program, or participated in a previous 

BAS year, and already have a SWIM account, you may use your current account to submit files for the 

BAS. You do not need to set up a new account.
Boundary and Annexation Survey Respondent Guide: Digital Page 28

Figure 21. SWIM Account Registration

Figure 22. SWIM Login Window
Boundary and Annexation Survey Respondent Guide: Digital Page 29

3. If you have submitted files before, the SWIM lists them on the startup screen upon login. Click 

'Start New Upload' to continue.

Figure 23. Welcome Screen with Upload History

4. On the next screen, select the “Boundary Annexation Survey (BAS) option as the geographic 

partnership program, and click ‘Next’ to continue.

Figure 24. Geographic Partnership Program Selection Window
Boundary and Annexation Survey Respondent Guide: Digital Page 30

5. On this screen, you will select a geographic level. This is the geography type of your agency 

(e.g., if you are a county government submitting data, select county. If an incorporated place, 

then select place...etc.). Click 'Next' to continue.

Figure 25. Geographic Level Selection Window

6. Use the drop-down selectors to find the name of your geographic entity. These options 

dynamically update based on the geography type selected from the previous screen. Click ‘Next’ 

to continue.

Figure 26. Geographic Entity Selection Window
Boundary and Annexation Survey Respondent Guide: Digital Page 31

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

Figure 27. File Upload Screen

8. In the file browser dialog box, select the ZIP file you would like to upload. Please be aware that 

the SWIM Web site only accepts ZIP files. Click 'Open' to continue.

Figure 28. File Browser Dialog Box
Boundary and Annexation Survey Respondent Guide: Digital Page 32

9. At this time, you may enter any comments that you wish to include with your file. Click 'Next' to 

upload your submission.

Figure 29. Entering Comments into the File Upload Window

10. The final screen will be a ‘Thank You’ screen confirming receipt of your file submission. If you do 

not see this screen, or you encounter any issues during this upload process, please contact the 

Census Bureau.

Figure 30. Thank You Screen
Boundary and Annexation Survey Respondent Guide: Digital Page 33

5.13.7 Additional Information

The Census Bureau recommends using Federal Information Processing Standards (FIPS) 

codes to identify entities such as counties, minor civil divisions, and incorporated places. Using 

a standard coding scheme facilitates the digital exchange of data. 

The Census Bureau includes these codes are in the BAS shapefiles. Online, you can find the 

codes at <http://geonames.usgs.gov/domestic/download_data.htm>. If there are any questions 

or problems, contact the Census Bureau at 1-800-972-5651 or geo.bas@census.gov.

Due to limited staff, the Census Bureau may not be able to make all updates this year. The 

Census Bureau will prioritize updates in the following order: legal changes, boundary 

corrections, linear feature changes, and landmark changes. The earlier the Census Bureau 

receives a submission, the greater the chance that the Census Bureau will be able to make all 

of the updates. Only submit changes that occurred on or before January 1, 2018. The Census 

Bureau will not be able to make any updates effective after this date until next year’s BAS.
Boundary and Annexation Survey Respondent Guide: Digital Page 34

APPENDICES
Boundary and Annexation Survey Respondent Guide: Digital Page A-1

APPENDIX A. DATA DICTIONARY

Table 17: County and Equivalent Areas Shapefile

ATTRIBUTE 

FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

COUNTYNS 8 String ANSI feature code for the county or equivalent feature

NAMELSAD 100 String Name with translated LSAD code

LSAD 2 String Legal/Statistical Area Description code

FUNCSTAT 1 String Functional status

CLASSFP 2 String FIPS 55 class code describing an entity

CHNG_TYPE 2 String Type of area update

EFF_DATE 8 Date Effective date or vintage

AUTHTYPE 1 String Authorization type (O – Ordinance, R – Resolution, L –

Local Law, S – State Level Action, X – Other)

DOCU 120 String Supporting documentation

FORM_ID 4 String Record ID (GUPS only)

AREA 10 Double Area of update

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change

NAME 100 String Entity name

VINTAGE 2 String Vintage of the data
Boundary and Annexation Survey Respondent Guide: Digital Page A-2

Table 18: County Subdivisions Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

COUSUBFP 5 String FIPS 55 county subdivision code

NAMELSAD 100 String Name with translated LSAD

COUSUBNS 8 String ANSI feature code for the county subdivision

LSAD 2 String Legal/Statistical Area Description

FUNCSTAT 1 String Functional status

CLASSFP 2 String FIPS 55 class code describing an entity

CHNG_TYPE 2 String Type of area update

EFF_DATE 8 Date Effective date or vintage

AUTHTYPE 1 String Authorization type (O – Ordinance, R – Resolution, L –

Local Law, S – State Level Action, X – Other)

DOCU 120 String Supporting documentation

FORM_ID 4 String Record ID (GUPS only)

AREA 10 Double Area of update

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change

NAME 100 String Entity name

VINTAGE 2 String Vintage of the data
Boundary and Annexation Survey Respondent Guide: Digital Page A-3

Table 19: Incorporated Place Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

PLACEFP 5 String FIPS 55 place code

NAMELSAD 100 String Name with translated LSAD

PLACENS 8 String ANSI feature code for the place

LSAD 2 String Legal / Statistical Area Description

FUNCSTAT 1 String Functional status

CLASSFP 2 String FIPS 55 class code describing and entity

PARTFLG 1 String Indicates if only part of a feature is represented

CHNG_TYPE 2 String Type of area update

EFF_DATE 8 Date Effective date or vintage

AUTHTYPE 1 String Authorization type (O – Ordinance, R – Resolution, L –

Local Law, S – State Level Action, X – Other)

DOCU 120 String Supporting documentation

FORM_ID 4 String Record ID (GUPS only)

AREA 10 Double Area of update

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change

NAME 100 String Entity name

VINTAGE 2 String Vintage of the data
Boundary and Annexation Survey Respondent Guide: Digital Page A-4

Table 20: Consolidated City Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

CONCITYFP 5 String FIPS 55 place code

NAMELSAD 100 String Name with translated LSAD

PLACENS 8 String ANSI feature code for the place

LSAD 2 String Legal/Statistical Area Description

FUNCSTAT 1 String Functional status

CLASSFP 2 String FIPS 55 class code describing an entity

PARTFLG 1 String Indicates if only part of a feature is represented

CHNG_TYPE 2 String Type of area update

EFF_DATE 8 Date Effective date or vintage

AUTHTYPE 1 String Authorization type (O – Ordinance, R – Resolution, L –

Local Law, S – State Level Action, X – Other)

DOCU 120 String Supporting documentation

FORM_ID 4 String Record ID (GUPS only)

AREA 10 Double Acreage of update

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change

NAME 100 String Entity name

VINTAGE 2 String Vintage of the data
Boundary and Annexation Survey Respondent Guide: Digital Page A-5

Table 21: Edges Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

TLID 10 Double Permanent edge ID

TFIDL 10 Double Permanent face ID (left)

TFIDR 10 Double Permanent face ID (right)

MTFCC 5 String MAF/TIGER Feature Class Code

FIDELITY 1 String Indication to a respondent when their entity boundary 

has changed through spatial enhancement

FULLNAME 40 String Decoded feature name with abbreviated qualifier, 

direction, and feature type

SMID 22 String Spatial Theta ID

SMIDTYPE 1 String SMIDTYPE code

BBSPFLG 1 String Redistricting data project participant’s submitted request 

of an EDGE for selection as a block boundary

CBBFLG 1 String Indicates the status of an EDGE for a selection as a 

block boundary

BBSP_2020 1 String New BBSP flag

CHNG_TYPE 4 String Type of linear feature update

JUSTIFY 150 String Justification of change

LTOADD 10 String Left To address

RTOADD 10 String Right To address

LFROMADD 10 String Left From address

RFROMADD 10 String Right From address

ZIPL 5 String Left zip code

ZIPR 5 String Right zip code

EXTTYP 1 Char Extension type

MTUPDATE 10 Date Date of last update to the edge
Boundary and Annexation Survey Respondent Guide: Digital Page A-6

Table 22: Area Landmark Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS State Code

COUNTYFP 3 String FIPS County Code

MTFCC 5 String MAF/TIGER Feature Class Code

FULLNAME 120 String Area landmark name

PARTFLG 1 String Indicates if only part of a feature is represented

AREAID 22 String Object ID

ANSICODE 8 String ANSI code for area landmarks

CHNG_TYPE 2 String Type of area landmark update

EFF_DATE 8 Date Effective date or vintage

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change

BAG 3 String Block area grouping

Table 23: Hydro Area Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

ANSICODE 8 String ANSI code for hydrography area

MTFCC 5 String MAF/TIGER Feature Class Code

FULLNAME 120 String Hydro landmark name

CHNG_TYPE 2 String Type of hydro area update

HYDROID 22 String Object ID

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change
Boundary and Annexation Survey Respondent Guide: Digital Page A-7

Table 24: Point Landmark Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

STATEFP 2 String FIPS state code

COUNTYFP 3 String FIPS county code

POINTID 22 String Object ID

ANSICODE 8 String ANSI code for point landmarks

MTFCC 5 String MAF/TIGER Feature Class Code

FULLNAME 120 String Point landmark name

CHNG_TYPE 2 String Type of point landmark update

JUSTIFY 150 String Justification of change

Table 25: Geographic Offset Shapefile

ATTRIBUTE FIELD LENGTH TYPE DESCRIPTION

TFID 20 Integer Permanent Face ID

STATEFP 2 String FIPS State Code

COUNTYFP 3 String FIPS County Code

OFFSET 1 String Geographic Offset / Corridor Flag

ADDEXCLUDE 1 String Address Exclusion Indicator

CHNG_TYPE 2 String Type of area update

EFF_DATE 8 Date Effective date or vintage

RELATE 120 String Relationship description

JUSTIFY 150 String Justification of change
Boundary and Annexation Survey Respondent Guide: Digital Page B-1

APPENDIX B. 2018 DIGITAL BAS EXAMPLE PROCESS 1

B.1 Required Census Bureau Shapefiles

When downloading shapefiles for the 2018 BAS, shapefiles will begin with the prefix 

(e.g., PVS_17_v2_edges_<ssccc>.shp). Throughout this guide, Census Bureau uses the 

prefix of bas_2018, 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 incorporated place, these layers are critical:

 PVS_17_v2_place_<ssccc>.shp

 PVS_17_v2_edges_<ssccc>.shp

Note: <ssccc> represents the two-digit state code and three-digit county code.

The shapefiles should include the home county/counties 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.

B.2 Local 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 entity; 

if some of the entities within the jurisdiction are non-contiguous, they may be saved as a multipart polygon or consist of one polygon for each disjointed part. Other local data layers that may 

be helpful if available include centerline data, hydrological, railroad, or other linear feature data, 

and imagery.

B.3 Symbolizing Layers in ArcGIS

The following are suggestions for symbolizing Census data in ArcGIS. For the Edges layer, 

symbolize the linear features by grouping like MTFCC codes (codes sharing the same first

character). See Table 26.

Table 26: Suggested MTFCC Symbolization

MTFCC 1st Character Linear Feature Type Symbol

H Hydrology

P Non-Visible Feature (boundary)

R Railroad

S Road
Boundary and Annexation Survey Respondent Guide: Digital Page B-2

B.3.1 Symbolizing Geographic Areas

Symbolize the place layer using Fill Color of RGB (255, 235, 190) with no outline.

Note: County participants with many adjacent incorporated places may want to use different colors to 

distinguish one place from another.

Figure 31. Suggested Map Symbolization

B.4 Extracting Incorporated Place or MCD Data from Census 

Shapefiles

Note: County participants submitting county boundary changes can skip this step. Use the 

PVS_yy_v2_county_<ssccc> shapefile which only contains the county boundary. Counties 

submitting for multiple incorporated places or MCDs skip ahead to Section B.4.3.

B.4.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_yy_v2_{place|mcd}_<ssccc>. 

 Double click “NAME”

 Left click the = button

 Click the Get Unique Values button

 In the list, locate and double click the name of the entity (It will appear in the formula).

 Click OK
Boundary and Annexation Survey Respondent Guide: Digital Page B-3

Figure 32. Filtering Data

B.4.2. Exporting the Data to a New Shapefile

1. In the Table of Contents, right click the Incorporated Place or MCD layer, select Data, and then 

click Export Data.

2. In the Export Data window:

 From the Export dropdown, choose Selected Features.

 In the Output feature class field, enter a location to save the shapefile. 

 Click OK. 
Boundary and Annexation Survey Respondent Guide: Digital Page B-4

Figure 33. Export Data Window

Note: If the incorporated place spans more than one county, it will need to be exported from each 

county’s place shapefile and merged. Follow the instructions in Section B.4.3 if the incorporated 

place needs to merge, otherwise skip to Section B.6.

B.4.3. 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 34. Finalizing the Merge Process
Boundary and Annexation Survey Respondent Guide: Digital Page B-5

B.5 Creating Change Polygons Using Symmetrical Difference

Note: If you do not have an ArcInfo license, you may have to use the Union operation rather than the 

Symmetrical Difference operation. See Section B.6 if this is the case.

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 

Section 4. 

 In the Update Features field, click the arrow (or browse) and select the local government 

boundary layer (your data). 

 In the Output Feature Class field, browse to and select a location to save the shapefile.

o Name the shapefile Differences_between_BAS_local, Differences1, or anything easy to 

find/remember.

 Click OK.

Figure 35. Finalizing the Symmetrical Difference Process

Note: This process creates a layer that contains all of the differences between Census Bureau and local 

boundaries. However, the Symmetrical Difference tool creates multipart polygons that need to be 

broken up and individually coded.

1. Turn on Editing (using the Editing dropdown in the Editor toolbar). Select all of the records in the 

layer that was created in the Symmetrical Difference step.

2. On the Advanced Editing toolbar, click the Explode tool . The layer will now contain a 

separate record for each change. 
Boundary and Annexation Survey Respondent Guide: Digital Page B-6

The created layer shows individual change polygons representing the differences 

between the Census Bureau and local government entity boundaries. Please review 

these differences and code them appropriately.

Skip to Section B.7, Reviewing and Attributing Change Polygons.

B.6 Creating Change Polygons Using Union

Note: Use this method if you are a county reporting for incorporated places or MCDs. Also, use this 

method if you do not have an ArcInfo license.

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_yy_v2_{place|mcd}_<ssccc>, and the local incorporated place or MCD 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 36. Finalizing the Union Process
Boundary and Annexation Survey Respondent Guide: Digital Page B-7

The union operation will create records that contain differences as well as areas that are 

in common between the Census Bureau and local government boundary layers. 

The next step is selecting and deleting the areas in common between the Census 

Bureau and local government boundary layers.

3. On the Editor toolbar, click Editor, and then click Start Editing.

4. If a Start Editing window opens, in the top pane, click to highlight the union shapefile, and then 

click OK.

Figure 37. Locating the Union Shapefile

5. In ArcMap, in the Tools toolbar, click the Select Features button. 

 Locate features on the map that the Census Bureau and the local government 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.

6. 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.

7. Select all of the remaining records in the layer that was created in the Union step.
Boundary and Annexation Survey Respondent Guide: Digital Page B-8

8. On the Advanced Editing toolbar, click the Explode tool . The layer will now contain a 

separate record for each change. 

The new layer shows individual change polygons representing the differences between the

Census Bureau and the local 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.

B.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 Section 5.3 in the main part 

of this guide to look for polygons that should be deleted from your submission, as well as those 

that should be snapped to nearby visible features to maintain boundary-to-feature relationships.

B.7.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 38. Small Slivers That Should Be Deleted

These examples show polygons that should be snapped to rivers (left) or roads (right)

Figure 39. Polygons That Should Be Snapped to Roads or Rivers
Boundary and Annexation Survey Respondent Guide: Digital Page B-9

B.7.2 Attribute Information

Note: All updates MUST be attributed.

To begin updating attributes

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

Annexations

 On the Editor Toolbar, click the Edit Tool button and select the annexation polygon.

 On the Editor Toolbar, click the Attributes button.

 In the Attributes window, fill out the mandatory fields required for an annexation.

o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.

o The CHNG_TYPE for an annexation is A.

Deannexations

 On the Editor Toolbar, click the Edit Tool button and select the deannexation polygon.

 On the Editor Toolbar, click the Attributes button.

 In the Attributes window, fill out the mandatory fields required for a deannexation.

o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.

o The CHNG_TYPE for an annexation is D.

Corridors

 On the Editor Toolbar, click the Edit Tool button and select the corridor polygon.

 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.

Offsets

 On the Editor Toolbar, click the Edit Tool button and select the offset polygon.

 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.
Boundary and Annexation Survey Respondent Guide: Digital Page B-10

Boundary Corrections

 On the Editor Toolbar, click the Edit Tool button and select the boundary correction 

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.

Note: If a county is reporting for adjacent incorporated places or MCDs, and a boundary correction to 

one entity affects another, use RELATE = IN and NAME = <entity being added to>. 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 entities.

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.)

B.8 Renaming and Finalizing Change Polygons

Renaming the shapefile

After creating and coding all change polygons, please rename the change polygon 

layer prior to its submission to the Census Bureau. You must complete this 

process for each level of geography (county, place, MCD) that has changes.

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: 

bas18_<basID>_changes_<entity_type>.

Note: You can find the basID numbers on the BAS Annual Response Email or online from this link: 

https://www.census.gov/programs-surveys/bas/technical-documentation/code-lists.html

Note: See Section 5.13.5 for instructions on zipping updates.

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 

<https://respond.census.gov/swim>. For instructions on how to use SWIM, you can find 

them in Section 5.13.6 Submitting Digital Files via SWIM of the respondent guide.
Boundary and Annexation Survey Respondent Guide: Digital Page C-1

APPENDIX C. 2018 DIGITAL EXAMPLE PROCESS 2

Note: This example uses an incorporated place. An MCD, county, or county reporting for incorporated 

places and MCDs may use the same process.

C.1 Required Census Bureau Shapefiles

 When downloading shapefiles for the 2018 BAS, shapefiles will begin with the prefix PVS

(e.g., PVS_17_v2_edges_<ssccc>.shp).

Copy the data to a hard drive/server, and unzip the data to ensure that the correct data was 

downloaded. For an incorporated place, these layers are critical:

 PVS_17_v2_place_<ssccc>.shp

 PVS_17_v2_edges_<ssccc>.shp

Note: <ssccc> represents the two-digit state code and three-digit county code.

The shapefiles should include the home county/counties as well as all adjacent counties.

Note: The Census Bureau suggests that participants make an extra copy of the data as an emergency 

backup. Contact the Census Bureau at 1-800-972-5651 or geo.bas@census.gov with any 

questions.

C.2 Local Data

The minimum data necessary is a shapefile showing your jurisdiction boundary or annexations 

and deannexations. Other local data layers that may be helpful (if available) include centerline 

data, hydrological, railroad, or other linear feature data, and imagery.

C.3 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 27.

Table 27: Suggested MTFCC Symbolization

MTFCC 1st Character... Linear Feature Type Symbol

H Hydrology

P Non-Visible Feature (boundary)

R Railroad

S Road
Boundary and Annexation Survey Respondent Guide: Digital Page C-2

C.3.1 Symbolizing Geographic Areas

Symbolize the place layer using Fill Color of RGB (255,235,190) with no outline.

Note: County participants with many adjacent incorporated places may want to use different colors to 

distinguish one place from another.

Figure 40. Suggested Map Symbolization

C.4 Creating and Splitting Linear Features

C.4.1 Creating New Linear features

Some of the linear features needed to create change polygons may not exist in MAF/TIGER. It 

may be necessary to create and split lines when forming changes. The existing and newly 

created linear features will then be selected to define the boundary changes.

1. In ArcMap, right click the edges layer in the Table of Contents, click Selection, and then click 

Make This The Only Selectable Layer, so that the edges layer is the only layer that can be 

selected while editing.

2. In the Editor toolbar, click Editor and then click Start Editing.

3. In the Create Features window, highlight a non-visible boundary symbolization under the edges 

layer: PVS_17_v2_edges_<ssccc>.
Boundary and Annexation Survey Respondent Guide: Digital Page C-3

Figure 41. Create Features Window

4. In the Editor toolbar, click Editor and then click Snapping, then Snapping Toolbar.

5. On the snapping toolbar, ensure that Point, Vertex, Edge, and End Snapping are all enabled. 

Drop down the Snapping menu, and ensure that Use Snapping is checked. Snapping will ensure 

that newly created lines will follow existing MAF/TIGER linear features.

Figure 42. Snapping Toolbar

6. For any new boundary lines that do not follow existing edges, ensure that Line is suggested in 

the Construction Tools pane (see Figure 43), and in the Editor toolbar, click the Straight 

Segment Tool button and draw new features on the map by clicking to create a line. Single 

clicking will add vertexes to the line, and double-clicking will end the line and create the new 

feature. Any new feature(s) will be highlighted.
Boundary and Annexation Survey Respondent Guide: Digital Page C-4

Figure 43. A Newly Created Linear Feature

C.4.2 Adding Attribute Data To New Linear Features

After creating new linear features: 

1. In the Editor toolbar, click the Attributes button.

2. In the Attributes window, in the MTFCC field, add the appropriate MTFCC code (it should default 

to P0001, but can be changed if necessary).

 Use P0001 if the feature is a non-visible political boundary. 

 If the feature is visible, see 0 for the appropriate codes. 

Note: Each new feature must have an MTFCC code. If larger scale linear feature changes are going to 

be submitted, it is best to create those in a separate layer. 

Note: Click on Editor and then click Save Edits often so that work is not lost. 

3. Once all lines are added, in the Editor toolbar, click Editor and then click Stop Editing (In the 

Save window, click Yes.)

C.4.3 Splitting Linear Features

1. In the Editor toolbar, click Editor and then click Start Editing.

2. In the Editor toolbar, click the Edit Tool button and select a linear feature that needs to be 

split. The line will be highlighted when it is selected.

3. In the Editor toolbar, click the Split Tool button. Click the line where it needs to be split. 

The following examples display why it may be necessary to split lines when creating change 

polygons. 

The desired boundary change is indicated below. When selecting the lines to form the boundary 

change, sections of the linear features that are not a part of the boundary update are included 

(highlighted in blue). 
Boundary and Annexation Survey Respondent Guide: Digital Page C-5

Figure 44. Linear Feature Selection Before Being Split

The existing linear features can be split to prevent unwanted line segments from being selected 

as part of the boundary update.

Figure 45. Linear Feature Selection After Being Split

4. Once all necessary splits are made, in the Editor toolbar, click Editor and then click Save Edits.
Boundary and Annexation Survey Respondent Guide: Digital Page C-6

C.4.4 Selecting Lines and Creating Change Polygons

After creating and/or splitting any necessary linear features, select those that will be used to 

form change polygons. Each change polygon must be created and coded separately.

Creating change polygons

1. If the Topology toolbar is not active, click the Customize menu, select Toolbars, and then select 

Topology to activate it. 

2. In the Editor toolbar, click Editor and then click Start Editing.

3. In the Create Features window, switch the highlighted feature to the place layer:

PVS_yy_v2_place_<ssccc>.

4. In the Editor toolbar, click the Edit Tool button and select the linear features that comprise 

the boundary of a change polygon (i.e. an annexation, deannexation, or incorrect area) by holding 

the Shift key while clicking each linear feature segment.

Figure 46. Selecting the Linear Features of a Change Polygon

5. On the Topology toolbar, click the Construct Features button.

 In the Construct Features dialog box, click OK (the default Cluster Tolerance is 

acceptable).

The polygon is now part of the incorporated place layer; however, it will not have any associated 

attribute values (see the next section). 
Boundary and Annexation Survey Respondent Guide: Digital Page C-7

Figure 47. Newly Created Place Feature

C.4.5 Attributing Change Polygons

After creating the change polygons, each must be correctly attributed so that the boundaries 

can be appropriately updated in MAF/TIGER. Another option is to update the attributes for each 

change polygon after creating all boundary changes. The following steps explain which 

attributes are mandated for each type of boundary change.

Note: All updates MUST be attributed.

To begin updating attributes

 In ArcMap, right click the place layer in the Table of Contents, click Selection, and then click 

Make This The Only Selectable Layer, so that the place layer is the only layer that can be 

selected while editing.

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

Annexations

 On the Editor Toolbar, click the Edit Tool button and select the annexation polygon.

 On the Editor Toolbar, click the Attributes button.

 In the Attributes window, fill out the mandatory fields required for an annexation.

o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.

o The CHNG_TYPE for an annexation is A.
Boundary and Annexation Survey Respondent Guide: Digital Page C-8

Deannexations

 On the Editor Toolbar, click the Edit Tool button and select the deannexation polygon.

 On the Editor Toolbar, click the Attributes button.

 In the Attributes window, fill out the mandatory fields required for a deannexation.

o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.

o The CHNG_TYPE for an annexation is D.

Corridors

 On the Editor Toolbar, click the Edit Tool button and select the corridor polygon.

 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.

Offsets

 On the Editor Toolbar, click the Edit Tool button and select the offset polygon.

 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.

Boundary Corrections

 On the Editor Toolbar, click the Edit Tool button and select the boundary correction 

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.
Boundary and Annexation Survey Respondent Guide: Digital Page C-9

Note: If a county is reporting for adjacent incorporated places or MCDs, and a boundary correction to 

one entity affects another, use RELATE = IN and NAME = <entity being added to>. 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 entities.

To finish updating attributes

 Once all of the attribute changes have been made, on the Editor toolbar, click Editor, and then 

click Stop Editing (in the Save window, click Yes).

C.4.6 Exporting Change Polygons

After creating and coding the change polygons, each level of geography (county, place, MCD) 

that has changes must be exported to a separate change polygon layer.

1. In ArcMap, click Selection and then click Select by Attributes.

2. In the Select By Attributes window:

 Set the Layer dropdown to the incorporated place layer: PVS_yy_v2_place_<ssccc>.

 Set the Method dropdown to Create a new selection.

 In the Select * FROM box, type one of the following formulas:

o “CHNG_TYPE” < > ‘ ’ This equation would select all change polygons that have any 

change type which have been created and coded.

o “CHNG_TYPE” = ‘A’ OR “CHNG_TYPE” = ‘B’ OR... (etc.) This equation can be written to 

select each change type for polygons that were created and coded.

 Click OK

Figure 48. Select All Change Types Formula
Boundary and Annexation Survey Respondent Guide: Digital Page C-10

After clicking OK, each change polygon that that has been created and coded should be 

highlighted on the map and in the attribute table. 

Optional: Open the attribute table and sort to verify that all change polygons with a change type code 

were selected.

Exporting the selected change polygons

1. In the ArcMap Table of Contents, right-click on the incorporated place layer 

(PVS_17_v2_place_<ssccc>), 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, browse to and select a location to save the 

shapefile.

o Name the shapefile bas8_<basID>_changes_incplace.shp.

 Click OK. 

Figure 49. Exporting Data

Note: You can find the basID number on the BAS Annual Response email or online from this link: 

<https://www.census.gov/programs-surveys/bas/technical-documentation/code-lists.html>.

Note: See Section 5.13.5 for instruction on zipping updates.

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 

<https://respond.census.gov/swim>. For instructions on how to use SWIM, you can find 

them in Section 5.13.6, Submitting Digital Files via SWIM.
Boundary and Annexation Survey Respondent Guide: Digital Page D-1

APPENDIX D. MTFCC DESCRIPTIONS — COMPLETE LIST

The MAF/TIGER Feature Classification Code (MTFCC) is a 5-digit code assigned by the 

Census Bureau to classify and describe geographic objects or features in Census Bureau 

MAF/TIGER products.

Table 28: MTFCC List

MTFCC Feature Class Feature Class Description

C3022 Mountain Peak or 

Summit

A prominent elevation rising above the surrounding level of the 

Earth’s surface.

C3023 Island An area of dry or relatively dry land surrounded by water or low 

wetland [including archipelago, atoll, cay, hammock, hummock, 

isla, isle, key, moku and rock].

C3024 Levee An embankment flanking a stream or other flowing water 

feature to prevent overflow.

C3026 Quarry (not water-filled), 

Open Pit Mine or Mine

An area from which commercial minerals are or were removed 

from the Earth; not including an oilfield or gas field.

C3027 Dam A barrier built across the course of a stream to impound water 

and/or control water flow.

C3061 Cul-de-sac An expanded paved area at the end of a street used by 

vehicles for turning around. For mapping purposes, the Census 

Bureau maps it only as a point feature.

C3062 Traffic Circle A circular intersection allowing for continuous movement of 

traffic at the meeting of roadways.

C3066 Gate A movable barrier across a road.

C3067 Toll Booth A structure or barrier where a fee is collected for using a road.

C3071 Lookout Tower A manmade structure, higher than its diameter, used for 

observation.

C3074 Lighthouse Beacon A manmade structure, higher than its diameter, used for 

transmission of light and possibly sound generally to aid in 

navigation.

C3075 Tank/Tank Farm One or more manmade structures, each higher than its 

diameter, used for liquid (other than water) or gas storage or for 

distribution activities.

C3076 Windmill Farm One or more manmade structures used to generate power from 

the wind.

C3077 Solar Farm One or more manmade structures used to generate power from 

the sun.

C3078 Monument or Memorial A manmade structure to educate, commemorate, or 

memorialize an event, person, or feature.

C3079 Boundary Monument 

Point

A material object placed on or near a boundary line to preserve 

and identify the location of the boundary line on the ground.

C3080 Survey Control Point A point on the ground whose position (horizontal or vertical) is 

known and can be used as a base for additional survey work.

C3081 Locality Point A point that identifies the location and name of an unbounded 

locality (e.g., crossroad, community, populated place or locale).

C3085 Alaska Native Village 

Official Point

A point that serves as the core of an Alaska Native village and 

is used in defining Alaska Native village statistical areas.
Boundary and Annexation Survey Respondent Guide: Digital Page D-2

MTFCC Feature Class Feature Class Description

G2100 American Indian Area A legally defined state- or federally recognized reservation 

and/or off-reservation trust land (excludes statistical American 

Indian areas).

G2120 Hawaiian Home Land A legal area held in trust for the benefit of Native Hawaiians.

G2130 Alaska Native Village 

Statistical Area

A statistical geographic entity that represents the residences, 

permanent and/or seasonal, for Alaska Natives who are 

members of or receiving governmental services from the 

defining legal Alaska Native Village corporation.

G2140 Oklahoma Tribal 

Statistical Area

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.

G2150 State-designated Tribal 

Statistical Area

A statistical geographic entity identified and delineated for the 

Census Bureau by a state-appointed liaison for a staterecognized American Indian tribe that does not currently have a 

reservation and/or lands in trust.

G2160 Tribal Designated 

Statistical Area

A statistical geographic entity identified and delineated for the 

Census Bureau by a federally recognized American Indian tribe 

that does not currently have a reservation and/or off-reservation 

trust land.

G2170 American Indian Joint 

Use Area

An area administered jointly and/or claimed by two or more 

American Indian tribes.

G2200 Alaska Native Regional 

Corporation

Corporate entities established to conduct both business and 

nonprofit affairs of Alaska Natives pursuant to the Alaska 

Native Claims Settlement Act of 1972 (Public Law 92-203). 

There are twelve geographically defined ANRCs and they are 

all within and cover most of the State of Alaska (the Annette 

Island Reserve-an American Indian reservation-is excluded 

from any ANRC). The boundaries of ANRCs have been legally 

established.

G2300 Tribal Subdivision Administrative subdivisions of federally recognized American 

Indian reservations, off-reservation trust lands, or Oklahoma 

tribal statistical areas (OTSAs). These entities are internal units 

of self-government or administration that serve social, cultural, 

and/or economic purposes for the American Indians on the 

reservations, off-reservation trust lands, or OTSAs.

G2400 Tribal Census Tract A relatively small and permanent statistical subdivision of a 

federally recognized American Indian reservation and/or offreservation trust land, delineated by American Indian tribal 

participants or the Census Bureau for the purpose of presenting 

demographic data.

G2410 Tribal Block Group A cluster of census blocks within a single tribal census tract 

delineated by American Indian tribal participants or the Census 

Bureau for the purpose of presenting demographic data.

G3100 Combined Statistical 

Area

A grouping of adjacent metropolitan and/or micropolitan 

statistical areas that have a degree of economic and social 

integration, as measured by commuting.

G3110 Metropolitan and 

Micropolitan Statistical 

Area

An area containing a substantial population nucleus together 

with adjacent communities having a high degree of economic 

and social integration with that core, as measured by 

commuting. Defined using whole counties and equivalents.
Boundary and Annexation Survey Respondent Guide: Digital Page D-3

MTFCC Feature Class Feature Class Description

G3120 Metropolitan Division A county or grouping of counties that is a subdivision of a 

Metropolitan Statistical Area containing an urbanized area with 

a population of 2.5 million or more.

G3200 Combined New England 

City and Town Area

A grouping of adjacent New England city and town areas that 

have a degree of economic and social integration, as measured 

by commuting.

G3210 New England City and 

Town Metropolitan and 

Micropolitan Statistical 

Area

An area containing a substantial population nucleus together 

with adjacent communities having a high degree of economic 

and social integration with that core, as measured by 

commuting. Defined using Minor Civil Divisions (MCDs) in New 

England.

G3220 New England City and 

Town Division

A grouping of cities and towns in New England that is a 

subdivision of a New England City and Town Area containing 

an urbanized area with a population of 2.5 million or more.

G3500 Urban Area Densely settled territory that contains at least 2,500 people. 

The subtypes of this feature are Urbanized Area (UA), which 

consists of 50,000 + people and Urban Cluster, which ranges 

between 2,500 and 49,999 people.

G4000 State or Equivalent 

Feature

The primary governmental divisions of the United States. The 

District of Columbia is treated as a statistical equivalent of a 

state for census purposes, as is Puerto Rico.

G4020 County or Equivalent 

Feature

The primary division of a state or state equivalent area. The 

primary divisions of 48 states are termed County, but other 

terms are used such as Borough in Alaska, Parish in Louisiana, 

and Municipio in Puerto Rico. This feature includes 

independent cities, which are incorporated places that are not 

part of any county.

G4040 County Subdivision The primary divisions of counties and equivalent features for 

the reporting of Census Bureau data. The subtypes of this 

feature are Minor Civil Division, Census County 

Division/Census Subarea, and Unorganized Territory. This 

feature includes independent places, which are incorporated 

places that are not part of any county subdivision.

G4050 Estate Estates are subdivisions of the three major islands in the United 

States Virgin Islands (USVI).

G4060 Subbarrio (Subminor 

Civil Division)

Legally defined divisions (subbarrios) of minor civil divisions 

(barrios-pueblo and barrios) in Puerto Rico.

G4110 Incorporated Place A legal entity incorporated under state law to provide generalpurpose governmental services to a concentration of 

population. Incorporated places are generally designated as a 

city, borough, municipality, town, village, or, in a few instances, 

have no legal description.

G4120 Consolidated City 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.

G4210 Census Designated 

Place

A statistical area defined for a named concentration of 

population and the statistical counterpart of an incorporated 

place.
Boundary and Annexation Survey Respondent Guide: Digital Page D-4

MTFCC Feature Class Feature Class Description

G4300 Economic Census Place The lowest level of geographic area for presentation of some 

types of Economic Census data. It includes incorporated 

places, consolidated cities, census designated places (CDPs), 

minor civil divisions (MCDs) in selected states, and balances of 

MCDs or counties. An incorporated place, CDP, MCD, or 

balance of MCD qualifies as an economic census place if it 

contains 5,000 or more residents, or 5,000 or more jobs, 

according to the most current data available.

G5020 Census Tract Relatively permanent statistical subdivisions of a County or 

equivalent feature delineated by local participants as part of the 

Census Bureau’s Participant Statistical Areas Program.

G5030 Block Group A cluster of census blocks having the same first digit of their 

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.

G5035 Block Area Grouping A user-defined group of islands forming a single census 

tabulation block. A BAG must: (1) consist of two or more 

islands, (2) have a perimeter entirely over water, (3) not 

overlap, and (4) not cross the boundary of other tabulation 

geographies, such as county or incorporated place boundaries.

G5040 Tabulation Block The lowest-order census defined statistical area. It is an area, 

such as a city block, bounded primarily by physical features but 

sometimes by invisible city or property boundaries. A tabulation 

block boundary does not cross the boundary of any other 

geographic area for which the Census Bureau tabulates data. 

The subtypes of this feature are Count Question Resolution 

(CQR), current, and census.

G5200 Congressional District The 435 areas from which people are elected to the U.S. 

House of Representatives. Additional equivalent features exist 

for state equivalents with nonvoting delegates or no 

representative. The subtypes of this feature are 106th, 107th, 

108th, 109th, and 111th Congressional Districts, plus 

subsequent Congresses.

G5210 State Legislative District 

(Upper Chamber

Areas established by a state or equivalent government from 

which members are elected to the upper or unicameral 

chamber of a state governing body. The upper chamber is the 

senate in a bicameral legislature, and the unicameral case is a 

single house legislature (Nebraska).

G5220 State Legislative District 

(Lower Chamber)

Areas established by a state or equivalent government from 

which members are elected to the lower chamber of a state 

governing body. The lower chamber is the House of 

Representatives in a bicameral legislature.

G5240 Voting District The generic name for the geographic features, such as 

precincts, wards, and election districts, established by state, 

local, and tribal governments for the purpose of conducting 

elections.

G5400 Elementary School 

District

A geographic area within which officials provide public 

elementary grade-level educational services for residents.

G5410 Secondary School 

District

A geographic area within which officials provide public 

secondary grade-level educational services for residents.
Boundary and Annexation Survey Respondent Guide: Digital Page D-5

MTFCC Feature Class Feature Class Description

G5420 Unified School District A geographic area within which officials provide public 

educational services for all grade levels for residents.

G6120 Public-Use Microdata 

Area

A decennial census area with a population of at least 100,000 

or more persons for which the Census Bureau provides 

selected extracts of household-level data that are screened to 

protect confidentiality.

G6300 Traffic Analysis District 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).

G6320 Traffic Analysis Zone An area delineated by Metropolitan Planning Organizations 

(MPOs) and state Departments of Transportation (DOTs) for 

tabulating journey-to-work and place-of-work data.

G6330 Urban Growth Area An area defined under state authority to manage urbanization 

that the Census Bureau includes in the MAF/TIGER® System in 

agreement with the state.

G6350 ZIP Code Tabulation 

Area (Five-Digit)

An approximate statistical-area representation of a U.S. Postal 

Service (USPS) 5-digit ZIP Code service area.

G6400 Commercial Region For the purpose of presenting economic statistical data, 

municipios in Puerto Rico are grouped into commercial regions.

H1100 Connector A known, but nonspecific, hydrographic connection between 

two nonadjacent water features.

H2025 Swamp/Marsh A poorly drained wetland, fresh or saltwater, wooded or grassy, 

possibly covered with open water [includes bog, cienega, 

marais and pocosin].

H2030 Lake/Pond A standing body of water that is surrounded by land.

H2040 Reservoir An artificially impounded body of water.

H2041 Treatment Pond An artificial body of water built to treat fouled water.

H2051 Bay/Estuary/Gulf/Sound A body of water partly surrounded by land [includes arm, bight, 

cove and inlet].

H2053 Ocean/Sea The great body of salt water that covers much of the earth.

H2060 Gravel Pit/Quarry filled 

with water

A body of water in a place or area from which commercial 

minerals were removed from the Earth.

H2081 Glacier A body of ice moving outward and down slope from an area of 

accumulation; an area of relatively permanent snow or ice on 

the top or side of a mountain or mountainous area [includes ice 

field and ice patch].

H3010 Stream/River A natural flowing waterway [includes anabranch, awawa, 

branch, brook, creek, distributary, fork, kill, pup, rio, and run].

H3013 Braided Stream A natural flowing waterway with an intricate network of 

interlacing channels.

H3020 Canal, Ditch or 

Aqueduct

An artificial waterway constructed to transport water, to irrigate 

or drain land, to connect two or more bodies of water, or to 

serve as a waterway for watercraft [includes lateral].

K1225 Crew-of-Vessel Location A point or area in which the population of military or merchant 

marine vessels at sea are assigned, usually being at or near 

the home port pier.
Boundary and Annexation Survey Respondent Guide: Digital Page D-6

MTFCC Feature Class Feature Class Description

K1231 Hospital/Hospice/Urgent 

Care Facility

One or more structures where the sick or injured may receive 

medical or surgical attention [including infirmary].

K1235 Juvenile Institution A facility (correctional and non-correctional) where groups of 

juveniles reside; this includes training schools, detention 

centers, residential treatment centers and orphanages.

K1236 Local Jail or Detention 

Center

One or more structures that serve as a place for the 

confinement of adult persons in lawful detention, administered 

by a local (county, municipal, etc.) government.

K1237 Federal Penitentiary, 

State Prison, or Prison 

Farm

An institution that serves as a place for the confinement of adult 

persons in lawful detention, administered by the federal 

government or a state government.

K1238 Other Correctional 

Institution

One or more structures that serve as a place for the 

confinement of adult persons in lawful detention, not elsewhere 

classified or administered by a government of unknown 

jurisdiction.

K1239 Convent, Monastery, 

Rectory, Other Religious 

Group Quarters

One or more structures intended for use as a residence for 

those having a religious vocation.

K1246 Community Center Community Center.

K2110 Military Installation An area owned and/or occupied by the Department of Defense 

for use by a branch of the armed forces (such as the Army, 

Navy, Air Force, Marines, or Coast Guard), or a state owned 

area for the use of the National Guard.

K2165 Government Center A place used by members of government (either federal, state, 

local, or tribal) for administration and public business.

K2167 Convention Center An exhibition hall or conference center with enough open space 

to host public and private business and social events.

K2180 Park Parkland defined and administered by federal, state, and local 

governments.

K2181 National Park Service 

Land

Area—National parks, National Monuments, and so forth—

under the jurisdiction of the National Park Service.

K2182 National Forest or Other 

Federal Land

Land under the management and jurisdiction of the federal 

government, specifically including areas designated as National 

Forest, and excluding areas under the jurisdiction of the 

National Park Service.

K2183 Tribal Park, Forest, or 

Recreation Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of an 

American Indian tribe.

K2184 State Park, Forest, or 

Recreation Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of a 

state government.

K2185 Regional Park, Forest, 

or Recreation Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of a 

regional government.

K2186 County Park, Forest, or 

Recreation Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of a 

county government.

K2187 County Subdivision 

Park, Forest, or 

Recreation Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of a 

minor civil division (town/township) government.
Boundary and Annexation Survey Respondent Guide: Digital Page D-7

MTFCC Feature Class Feature Class Description

K2188 Incorporated Place Park, 

Forest, or Recreation 

Area

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of a 

municipal government.

K2189 Private Park, Forest, or 

Recreation Area

A privately owned place or area set aside for recreation or 

preservation of a cultural or natural resource.

K2190 Other Park, Forest, or 

Recreation Area (quasipublic, independent 

park, commission, etc.)

A place or area set aside for recreation or preservation of a 

cultural or natural resource and under the administration of 

some other type of government or agency such as an 

independent park authority or commission.

K2191 Post Office An official facility of the U.S. Postal Service used for processing 

and distributing mail and other postal material.

K2193 Fire Department Fire Department.

K2194 Police Station Police Station.

K2195 Library Library.

K2196 City/Town Hall City/Town Hall.

K2400 Transportation Terminal A facility where one or more modes of transportation can be 

accessed by people or for the shipment of goods; examples of 

such a facility include marine terminal, bus station, train station, 

airport and truck warehouse.

K2424 Marina A place where privately owned, light-craft are moored.

K2432 Pier/Dock A platform built out from the shore into the water and supported 

by piles. This platform may provide access to ships and boats, 

or it may be used for recreational purposes.

K2451 Airport or Airfield A manmade facility maintained for the use of aircraft [including 

airstrip, landing field and landing strip].

K2452 Train Station, Trolley or 

Mass Transit Rail 

Station

A place where travelers can board and exit rail transit lines, 

including associated ticketing, freight, and other commercial 

offices.

K2453 Bus Terminal A place where travelers can board and exit mass motor vehicle 

transit, including associated ticketing, freight, and other 

commercial offices.

K2454 Marine Terminal A place where travelers can board and exit water transit or 

where cargo is handled, including associated ticketing, freight, 

and other commercial offices.

K2455 Seaplane Anchorage A place where an airplane equipped with floats for landing on or 

taking off from a body of water can debark and load.

K2456 Airport—Intermodal 

Transportation 

Hub/Terminal

A major air transportation facility where travelers can board and 

exit airplanes and connect with other (i.e. non-air) modes of 

transportation.

K2457 Airport—Statistical 

Representation

The area of an airport adjusted to include whole 2000 census 

blocks used for the delineation of urban areas

K2458 Park and Ride 

Facility/Parking Lot

A place where motorists can park their cars and transfer to 

other modes of transportation.

K2459 Runway/Taxiway A fairly level and usually paved expanse used by airplanes for 

taking off and landing at an airport.

K2460 Helicopter Landing Pad A fairly level and usually paved expanse used by helicopters for 

taking off and landing.
Boundary and Annexation Survey Respondent Guide: Digital Page D-8

MTFCC Feature Class Feature Class Description

K2540 University or College A building or group of buildings used as an institution for postsecondary study, teaching, and learning [including seminary].

K2543 School or Academy 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].

K2545 Museum, Visitor Center, 

Cultural Center, or 

Tourist Attraction

An attraction of historical, cultural, educational or other interest 

that provides information or displays artifacts.

K2561 Golf Course A place designed for playing golf.

K2582 Cemetery A place or area for burying the dead [including burying ground 

and memorial garden].

K2586 Zoo A facility in which terrestrial and/or marine animals are confined 

within enclosures and displayed to the public for educational, 

preservation, and research purposes.

K3544 Place of Worship A sanctified place or structure where people gather for religious 

worship; examples include church, synagogue, temple, and 

mosque.

L4010 Pipeline A long tubular conduit or series of pipes, often underground, 

with pumps and valves for flow control, used to transport fluid 

(e.g., crude oil, natural gas), especially over great distances.

L4020 Powerline One or more wires, often on elevated towers, used for 

conducting high-voltage electric power.

L4031 Aerial Tramway/Ski Lift A conveyance that transports passengers or freight in carriers 

suspended from cables and supported by a series of towers.

L4110 Fence Line A man-made barrier enclosing or bordering a field, yard, etc., 

usually made of posts and wire or wood, used to prevent 

entrance, to confine, or to mark a boundary.

L4121 Ridge Line The line of highest elevation along a ridge.

L4125 Cliff/Escarpment A very steep or vertical slope [including bluff, crag, head, 

headland, nose, palisades, precipice, promontory, rim and 

rimrock].

L4130 Point-to-Point Line A line defined as beginning at one location point and ending at 

another, both of which are in sight.

L4140 Property/Parcel Line 

(Including PLSS)

This feature class may denote a nonvisible boundary of either 

public or private lands (e.g., a park boundary) or it may denote 

a Public Land Survey System or equivalent survey line.

L4150 Coastline The line that separates either land or Inland water from 

Coastal, Territorial or Great Lakes water. Where land directly 

borders Coastal, Territorial or Great Lakes water, the shoreline 

represents the Coastline. Where Inland water (such as a river) 

flows into Coastal, Territorial or Great Lakes water, the closure 

line separating the Inland water from the other class of water

represents the Coastline.

L4165 Ferry Crossing The route used to carry or convey people or cargo back and 

forth over a waterbody in a boat.

P0001 Nonvisible Linear 

Legal/Statistical 

Boundary

A legal/statistical boundary line that does not correspond to a 

shoreline or other visible feature on the ground.

P0002 Perennial Shoreline The more-or-less permanent boundary between land and water 

for a water feature that exists year-round.
Boundary and Annexation Survey Respondent Guide: Digital Page D-9

MTFCC Feature Class Feature Class Description

P0003 Intermittent Shoreline The boundary between land and water (when water is present) 

for a water feature that does not exist year-round.

P0004 Other non-visible 

bounding Edge (e.g., 

Census water boundary, 

boundary of an areal 

feature)

A bounding Edge that does not represent a legal/statistical 

boundary, and does not correspond to a shoreline or other 

visible feature on the ground. Many such Edges bound area 

landmarks, while many others separate water features from 

each other (e.g., where a bay meets the ocean).

R1011 Railroad Feature (Main, 

Spur, or Yard)

A line of fixed rails or tracks that carries mainstream railroad 

traffic. Such a rail line can be a main line or spur line, or part of 

a rail yard.

R1051 Carline, Streetcar Track, 

Monorail, Other Mass 

Transit

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.

R1052 Cog Rail Line, Incline 

Rail Line, Tram

A special purpose rail line for climbing steep grades that is 

typically inaccessible to mainstream railroad traffic. Note that 

aerial tramways and streetcars (which may also be called 

“trams”) are accounted for by other MTFCCs and do not belong 

in R1052.

S1100 Primary Road Primary roads are generally divided, limited-access highways 

within the interstate highway system or under state 

management, and are distinguished by the presence of 

interchanges. These highways are accessible by ramps and 

may include some toll highways.

S1200 Secondary Road Secondary roads are main arteries, usually in the U.S. 

Highway, State Highway or County Highway system. These 

roads have one or more lanes of traffic in each direction, may 

or may not be divided, and usually have at-grade intersections 

with many other roads and driveways. They often have both a 

local name and a route number.

S1400 Local Neighborhood 

Road, Rural Road, City 

Street

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.

S1500 Vehicular Trail (4WD) An unpaved dirt trail where a four-wheel drive vehicle is 

required. These vehicular trails are found almost exclusively in 

very rural areas. Minor, unpaved roads usable by ordinary cars 

and trucks belong in the S1400 category.

S1630 Ramp A road that allows controlled access from adjacent roads onto a 

limited access highway, often in the form of a cloverleaf 

interchange. These roads are unaddressable and do not carry 

a name in the MAF/TIGER System.

S1640 Service Drive usually 

along a limited access 

highway

A road, usually paralleling a limited access highway, that 

provides access to structures along the highway. These roads 

can be named and may intersect with other roads.

S1710 Walkway/Pedestrian 

Trail

A path that is used for walking, being either too narrow for or 

legally restricted from vehicular traffic.

S1720 Stairway A pedestrian passageway from one level to another by a series 

of steps.
Boundary and Annexation Survey Respondent Guide: Digital Page D-10

MTFCC Feature Class Feature Class Description

S1730 Alley A service road that does not generally have associated 

addressed structures and is usually unnamed. It is located at 

the rear of buildings and properties and is used for deliveries.

S1740 Private Road for service 

vehicles (logging, oil 

fields, ranches, etc.)

A road within private property that is privately maintained for 

service, extractive, or other purposes. These roads are often 

unnamed.

S1750 Internal U.S. Census 

Bureau use

Internal U.S. Census Bureau use.

S1780 Parking Lot Road The main travel route for vehicles through a paved parking 

area.

S1820 Bike Path or Trail A path that is used for manual or small, motorized bicycles, 

being either too narrow for or legally restricted from vehicular 

traffic.

S1830 Bridle Path A path that is used for horses, being either too narrow for or 

legally restricted from vehicular traffic.

S2000 Road Median The unpaved area or barrier between the carriageways of a 

divided road.

Note: The information in this table was last updated in November 2017.