Download:
pdf |
pdfBoundary and Annexation Survey Tribal
Respondent Guide: Digital
Revised as of December 15, 2015
Silver Hill Reservation
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: Tribal
Table of Contents
Paperwork Reduction Act (PRA) State ment .................................................................. iii
Introduction to Digital Boundary and Annexation Survey .......................................... iv
CHAPTER 1.
Digital BAS Requirements ...................................................................... 1
CHAPTER 2.
Topological Relationships and Spatial Accuracy ............................... 3
CHAPTER 3.
Census Bureau Provided Shapefiles .................................................... 7
CHAPTER 4.
Census Bureau Geocoding..................................................................... 8
CHAPTER 5.
Updating the Census Bureau Shapefiles............................................ 10
5.1
Additions and Deletions ....................................................................................... 11
5.2
Boundary Corrections .......................................................................................... 11
5.3
New Tribal Subdivisions ...................................................................................... 12
5.4
Geographic Corridors .......................................................................................... 13
5.5
Geographic Offsets .............................................................................................. 14
5.6
Criteria for Defining Tribal Subdivisions ............................................................. 15
5.7
Updating Tribal Subdivisions............................................................................... 16
5.8
Adding, Deleting, Renaming, and Recoding Linear Features ........................... 16
5.9
Linear Feature Update Guidelines ...................................................................... 17
5.10
Address Range Updates ..................................................................................... 17
5.11
Area Landmarks, Hydro Areas, and Point Landmarks ...................................... 17
5.12
Boundary-to-Feature Relationships .................................................................... 22
5.13
Large Boundary Corrections ............................................................................... 25
5.14
Including Required Attribute Information ............................................................ 25
5.15
Including Appropriate Metadata (Projection Information) .................................. 26
5.16
Linear Feature Updates ....................................................................................... 26
5.17
Submitting Acceptable Documentation............................................................... 27
5.18
Submitting Digital Data ........................................................................................ 28
5.19
Compressing the Digital Files ............................................................................. 30
5.20
Submitting Digital Files via SWIM ....................................................................... 32
5.21
Additional Information .......................................................................................... 38
APPENDICES..................................................................................................................... 39
APPENDIX A Data Dictionary……………………………………………………………A-1
Boundary and Annexation Survey Respondent Guide: Tribal
Page i
APPENDIX B 2016 Digital BAS – Example Process 1………………………………B-1
B1.
Required Census Bureau Shapefiles ............................................................... B-1
B2.
Symbolizing Layers in ArcGIS........................................................................... B-1
B.2.1
B3.
Symbolizing Geographic Areas ..................................................................... B-2
Extracting AIA Data from Census Bureau Shapefiles ..................................... B-2
B.3.1
Filtering the Data ............................................................................................ B-2
B.3.2
Exporting the Data to a New Shapefile ......................................................... B-3
B.3.3
Merging Multipart AIA Data ........................................................................... B-4
B4.
Creating Change Polygons Using Symmetrical Difference ............................. B-5
B5.
Creating Change Polygons Using Union .......................................................... B-6
B6.
Reviewing and Attributing Change Polygons ................................................... B-9
B.6.1
Examples ........................................................................................................ B-9
B.6.2
Attribute Information..................................................................................... B-10
B7.
Renaming and Finalizing Change Polygons .................................................. B-12
APPENDIX C 2016 Digital BAS – Example Process 2……………………………..C-13
C.1
Required Census Bureau Shapefiles ............................................................. C-13
C.2
Symbolizing Layers in ArcGIS......................................................................... C-13
C.2.1
C.3
Symbolizing Geographic Areas ................................................................... C-14
Creating and Splitting Linear Features ........................................................... C-14
C.3.1
Creating New Linear Features .................................................................... C-14
C.3.2
Adding Attribute Data to New Linear Features ........................................... C-16
C.3.3
Splitting Linear Features .............................................................................. C-16
C.3.4
Selecting Lines and Creating Change Polygons ........................................ C-17
C.3.5
Attributing Change Polygons ....................................................................... C-19
C.3.6
Exporting Change Polygons ........................................................................ C-21
APPENDIX D MTFCC Codes……………………………………………………………..D-1
Boundary and Annexation Survey Respondent Guide: Tribal
Page ii
PAPERWORK REDUCTION ACT (PRA) 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 unless that collection of information displays a current valid
OMB Control Number. This collection is voluntary. The authority for conducting this
collection comes from Title 13 U.S.C, Section 6.
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 collec tion 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 3K138, Washington, DC 20233. You may email
comments to [email protected]; use “Paperwork Project 0607-0151” as the
subject.
Boundary and Annexation Survey Respondent Guide: Tribal
Page iii
INTRODUCTION TO DIGITAL BOUNDARY AND ANNEXATION SURVEY
A.
Overview of the Boundary and Annexation Survey
The 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 reservations (including off-reservation
trust lands and tribal subdivisions), Hawaiian Homelands, and Alaska Native Regional
Corporations (ANRC). The 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 BAS information to provide a record for reporting the results
of the decennial and economic censuses, and to support the Population Estimates
Program (PEP) and the American Community Survey (ACS). Maintaining correct
boundaries and boundary-to-feature 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, Alaska Native Regional Corporations (ANRC), and
federally recognized American Indian areas (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).
For more information on the BAS, please view the “Introduction to BAS” video series on
the Census Bureau’s website at
http://www.census.gov/geo/partnerships/bas/videos/introbas.html.
B.
What’s New in the 2016 BAS?
With the suspension of the 2014 BAS and the resumption of the BAS in 2015, it is
important to note some key changes in the 2016 BAS cycle.
All BAS submissions must be submitted via the Secure Web Incoming Module (SWIM).
No other methods or protocols (e.g. email or file transfer protocol (FTP)) are allowed
because of Census IT security policy. To get a SWIM token, you must fill out the annual
response form located at the following address:
http://www.census.gov/geo/partnerships/bas/bas_ar_form.html
Please note that if you received a SWIM token last year, it will not change for 2016.
1. Tribal BAS participants can use either their own Geographic Information System
(GIS) or Census Bureau provided paper maps. The Census Bureau’s free
MAF/TIGER Partnership Software (MTPS) is no longer available. In BAS 2017,
Boundary and Annexation Survey Respondent Guide: Tribal
Page iv
a new free software, Geographic Update Partnership Software (GUPS) will be an
option for Tribal BAS participants. Federally recognized tribes can obtain free
ArcMap GIS from the Bureau of Indian Affairs (BIA). Please see the BIA webpage
for details: http://www.bia.gov/WhatWeDo/ServiceOverview/Geospatial/.
2. In 2016, BAS paper maps will be available. Maps can be downloaded at the
following link: http://www.census.gov/geo/www/bas/bashome.html.
You can also request the Census Bureau mail paper maps to you.
3. All shapefiles are available for download from the BAS website:
http://www.census.gov/geo/www/bas/bashome.html.
If you have any questions or need assistance, please contact the Census Bureau at
1-800-796-3748 or email [email protected].
C.
Legal Disputes
If it comes to the Census Bureau’s attention that an area of tribal land is in dispute, the
Census Bureau will not make either additions or boundary corrections until supporting
documents are provided or the U.S. Department of the Interior issues a comment. If
necessary, the Census Bureau will request clarification regarding current boundaries,
particularly if supporting documents pre-date 1990, from the U.S. Department of the
Interior, Office of the Solicitor. 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.
D.
Key Dates for BAS Participants
January 1: Legal boundary changes (new reservation lands and/or off-reservation trust
lands) reported to the current BAS must be in effect on or before this date.
March 1: All legal changes received by March 1 will be reflected in the next American
Community Survey (ACS) shapefiles and population estimates.
May 31: All legal changes received by May 31 will be reflected in your BAS materials
for the next year.
Boundary and Annexation Survey Respondent Guide: Tribal
Page v
CHAPTER 1.
A.
DIGITAL BAS REQUIREMENTS
To Participate, Entities Must Meet the Following Requirements:
1. All participants must have the ability to edit a Census Bureau shapefile1. 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 contact information for the tribal BAS
point of contact, the person updating the shapefiles, and the tribal chair.
3. All participants must provide legal documentation (such as trust deeds and
Federal Register Notice) and effective dates for all legal boundary changes
(new reservation land and/or off-reservation trust lands).
4. Each non-legal boundary correction must contain proper update
documentation.
5. All participants must use 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.
B.
Tribal Areas that can be Submitted through BAS
The following can be updated through Tribal BAS:
1. Federal American Indian Reservations are areas that have been set aside by
the United States for the use of tribes, the exterior boundaries of which are more
particularly defined in the final tribal treaties, agreements, executive orders,
federal statutes, secretarial orders, or judicial determinations.
Trust lands may be located on or off a reservation; however, the Census Bureau
tabulates data only for off-reservation trust lands. Please do not submit on-reservation
trust land because the Census Bureau can only show the exterior reservation boundary.
2. Federal Off-Reservation Trust Lands are areas for which the United States
holds title in trust for the benefit of a tribe (tribal trust land) or for an individual
American Indian (individual trust land).
The Census Bureau does not identify fee land (or land in fee simple status) or restricted
fee lands as specific geographic areas.
3. Tribal Subdivisions are legal administrative subdivisions of federally recognized
American Indian reservations and off-reservation trust lands and are described
1
The use of brand names does not represent an endorsement of a company or its products by the U.S.
government. Due to the wide use of ESRI products by our partners in the GIS community, and the
ubiquitous use of the shapefile format as a medium for GIS data exchange, the Census Bureau is
providing this data in shapefile format. There should be no problem when importing these shapefiles into
local GIS software. However, if the GIS software does not contain a shapefile translator, contact the
Census Bureau for further instructions 1-800-796-3748 or [email protected].
Boundary and Annexation Survey Respondent Guide: Tribal
Page 1
as additions, administrative areas, areas, chapters, county districts, communities,
districts, or segments. 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 and off-reservation trust lands.
4. Hawaiian Homelands are areas held in trust for Native Hawaiians by the state of
Hawaii, pursuant to the Hawaiian Homes Commission Act of 1920, as amended.
5. Alaska Native Regional Corporation (ANRCs) were created pursuant to the
Alaska Native Claims Settlement Act (ANCSA) enacted in 1971 as a "Regional
Corporation" and organized under the laws of the state of Alaska to conduct both
the for-profit and non-profit affairs of Alaska Natives within a defined region of
Alaska.
C.
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-line.
Please go to http://www.census.gov/geo/partnerships/bas/bas_videos.html for more
information.
D.
Important Information About BAS 2016 Boundary Corrections:
Due to current resource and other budgetary constraints within the Census Bureau, the
Census Bureau cannot guarantee that all boundary corrections will be processed in the
same year’s BAS cycle, especially in the case of very large submissions with many
boundary corrections. We will continue to process all legal boundary changes (i.e. new
reservation lands and off-reservation trust lands), regardless of the number submitted.
The Census Bureau appreciates your understanding and support in this matter.
If there are any questions or concerns about the participation requirements, contact the
Census Bureau at 1-800-796-3748 or [email protected].
Boundary and Annexation Survey Respondent Guide: Tribal
Page 2
CHAPTER 2.
TOPOLOGICAL RELATIONSHIPS AND SPATIAL
ACCURACY
The Geography Division of the Census Bureau is responsible for developing geographic
applications and executing related activities needed to support the Census Bureau in
collecting and disseminating census data. For more than twenty years, the Census
Bureau’s Master Address File/Topologically Integrated Geographic Encoding and
Referencing (MAF/TIGER) System have become critical resources for supporting the
Census Bureau in its geographic activities.
The following section will describe how the Census Bureau uses a topologically
integrated system and how this differs from traditional GIS systems, which use separate
layers of data.
A.
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 Examples 1 and 2 for
samples of topologically integrated files in MAF/TIGER.
Example 1: This example shows how a road in MAF/TIGER can also represent a block boundary,
American Indian Area boundary and a school district boundary.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 3
Example 2: This example shows how four different feature classes are topologically integrated
into one layer. One road feature represents not only a road, but also a block boundary, American
Indian Area boundary, and a school district boundary.
B.
GIS and Spatial Accuracy
In a GIS, feature classes are usually not topologically integrated: they are separated
into 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. Examples 3 and 4 show how files that are not
topologically integrated might appear in a GIS when overlaid.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 4
Example 3: This example shows an overlay of four different feature classes. Notice how the
topological relationship is compromised. The block, AIA, and school district boundaries,
which are supposed to follow the road feature, no longer align with the road in several
locations.
Example 4: This example shows a situation where a local GIS AIA boundary does not follow a
road feature. Assuming that the boundary follows the road feature, changing the AIA boundary to
match the local file exactly, and become misaligned (see arrows) would dissolve the topological
relationship in MAF/TIGER.
Boundary and Annexation Survey Respondent Guide: Tribal
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-tofeature relationship issues for the Census Bureau. Chapter 5, Section C 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 Appendices
B and C.
C.
Census Bureau Topology Training Video
The Census Bureau created a video on topology and why topology is important to the
BAS. For more information, please go to
http://www.census.gov/geo/partnerships/bas/videos/digitalproctopo.html where you can
watch the video.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 6
CHAPTER 3.
CENSUS BUREAU PROVIDED SHAPEFILES
Please download shapefiles from the website
http://www.census.gov/geo/partnerships/bas.html in order to review your boundaries
and submit changes.
Please review and edit all applicable shapefiles. For example, if your tribe has new offreservation trust land to report, you would use the “aial” shapefile. If your tribe also had
tribal subdivision updates, you would use the “aial” shapefile and the “aitsl” shapefile.
See Table 1 for the names of the shapefiles. The Census Bureau provides entity layers
in ESRI shapefile format for download via the website.
BAS Shapefile Naming Conventions
Geographic Entity Type
Shapefile Naming Convention
Federal Reservations and OffReservation Trust Lands
PVS_15_v2_aial_.shp
Tribal Subdivision
PVS_15_v2_aitsl_.shp
ANRC
PVS_15_v2_anrc_.shp
Hawaiian Homeland
PVS_15_v2_hhl_.shp
Edges (Roads, Rail, Hydro, etc.)
PVS_15_v2_edges_.shp
Area Landmarks
PVS_15_v2_arealm_.shp
Point Landmarks
PVS_15_v2_pointlm_.shp
Hydro Area
PVS_15_v2_water_.shp
Geographic Offsets / Corridors
PVS_15_v2_offset_.shp
Table 1: Shapefile Naming Conventions.
NOTE: represents the two-digit state code and three-digit county code.)
All shapefiles provided by the Census Bureau are in the following unprojected
geographic-based coordinate system:
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: Tribal
Page 7
CHAPTER 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 GPS technology, while the
other uses address ranges.
MAF structure point (MSP) geocoding: a field worker stands in front of a house or living
quarters, and records the physical location with a GPS device (Example 5). Usually, the
GPS point should fall very close to the front door of the house. However, since this is a
field operation, 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.
Example 5: 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.
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 (Example 6).
Boundary and Annexation Survey Respondent Guide: Tribal
Page 8
Example 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 is being related to 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.
Using the road centerline as a boundary is much safer.
When completing a BAS submission in which a road or road right-of-way is owned or
maintained by a place or AIA but the adjacent housing is not, the respondent should use
the centerline of the road (not the front lot-line) as the boundary whenever possible. 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.5 of this document for more details).
Boundary and Annexation Survey Respondent Guide: Tribal
Page 9
CHAPTER 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 Tribal BAS survey. Examples of these
procedures can be found in Appendices B and C and in the Digital BAS demonstration
video series at http://www.census.gov/geo/partnerships/bas/videos/digitalbasdemo.html.
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.
A.
General File Setup Guidelines
After downloading the shapefiles from the PVS download page, follow these procedures
before beginning actual updates:
B.
Open the downloaded .ZIP file to verify its contents.
Copy the shapefiles into a directory on a server/hard drive.
Open the shapefiles with GIS software.
Changing the Map Projection
Census Bureau files are in GCS NAD83 format and can be projected into any local
coordinate system/projection. Most GIS software packages will allow users to transform
file coordinate systems and projections. For example, if using ArcView to update files,
activate and utilize ArcView’s Projection Utility Wizard extension. If using ArcGIS, use
its Projection Utilities 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.
C.
Boundary Changes
In order to update MAF/TIGER, participants must create a separate change polygon
layer for each updated entity type (AIA, ANRC, tribal subdivision, or Hawaiian
Homeland). Please create change polygons in relation to the current MAF/TIGER
boundary.
Appendices B and C provide two examples for creating adding, deleting, boundary
correction, new entity, geographic corridor, and geographic offset change polygons .
Review any boundary change polygons before submitting them (Section 5.7).
If you need additional shapefiles, please contact the Census Bureau at 1-800-796-3748
or [email protected].
Boundary and Annexation Survey Respondent Guide: Tribal
Page 10
5.1
Additions and Deletions
The Census Bureau will accept additions and deletions from AIAs, ANRCs, and
Hawaiian Homelands, such as new reservation lands and off-reservation trust lands.
Each addition or deletion change polygon must have the required attributes and
corresponding change type populated, as seen in Table 2. The Census Bureau will
snap any addition or deletion to a MAF/TIGER feature when it exists within thirty feet of
that feature.
NOTE: Enter the name of the jurisdiction (AIA, ANRC or Hawaiian Homeland) adding or
deleting the area in the NAME field.
Additions and Deletions
NAME
CHNG_TYPE
EFF_DATE
AUTHTYPE
DOCU
Addition
X
X(‘A’)
X
X
X
Deletion
X
X(‘D’)
X
X
X
RELATE
Table 2: Additions and Deletions (Note: ‘X’ = Required Field).
5.2
Boundary Corrections
The Census Bureau will also accept specific boundary corrections from AIAs, ANRCs,
and Hawaiian Homelands. As with new reservation lands and off-reservation trust
lands, 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 that the boundary correction is for in the NAME field.
Boundary Corrections
Boundary
Correction
NAME
CHNG_TYPE
EFF_DATE
AUTHTYPE
DOCU
RELATE
X
X(‘B’)
X(‘IN’)
X
X(‘B’)
X(‘OUT’)
(Add Area)
Boundary
Correction
(Remove Area)
Table 3: Boundary Corrections (Note: ‘X’ = Required Field).
The Census Bureau uses a topologically integrated database. As a result, the Census
Bureau cannot process all types of boundary corrections for inclusion into 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: Tribal
Page 11
The Census Bureau will accept and process properly documented boundary
corrections during the current BAS that spatially interact with (abut) other BAS legal
changes (annexation, de-annexation, corridor, offset) and meet both of the following two
conditions:
in situations where the existing boundary has been digitized incorrectly or
appears in the incorrect location due to Census Bureau activities.
where the overall shape of the geographic entity is maintained and no feature-toboundary relationships are dissolved.
The Census Bureau will reject boundary corrections:
that dissolve boundary-to-feature relationships (roads, rivers, railroads, etc.) if the
difference is less than thirty feet.
which are greater than one square mile, or not contiguous with the rest of the
entity boundary. These boundary corrections may be part of additions which
were never reported to the Census Bureau. If so, legal documentation should be
provided.
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.3
New Tribal Subdivisions
AIA participants may submit new entities (tribal subdivisions) through Tribal Digital BAS.
As with other change types, an individual change polygon must be created for each new
entity and possess the required attributes and the corresponding change type field must
be populated (see Table 4). Please see Chapter 5, Section D for more information
about tribal subdivisions.
NOTE: Enter the name of the new jurisdiction in the NAME field. For required documentation
for new entities, contact your Regional Census Center (see Appendices B and C).
New Entities
NAME
CHNG_TYPE
X
New Entity
(subdivision
name)
EFF_DATE
X
X(‘E’)
AUTHTYPE
DOC
X (‘R’)
X
(date of tribal
resolution)
RELATE
(tribal
resolution
number)
Table 4: New Entities (Note: ‘X’ = Required Field).
Boundary and Annexation Survey Respondent Guide: Tribal
Page 12
5.4
Geographic Corridors
The Census Bureau geocodes addresses based on the street centerline. If the
geocoding of these addresses would result in the assignment of population to the
incorrect geographic 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. Example 7 shows a
corridor created where the AIA owns the right-of-way but the housing units are not
included within the AIA (shown in color). Without a corridor, the housing units along this
road would be included in the AIA.
Example 8 shows that the right-of-way belongs in the unincorporated area, while the
housing units are included in the AIA (shown in color). This is important for some
entities because they are portraying that the entity is not responsible for road
maintenance. This is not relevant for Census Bureau tabulations and is not easy to
depict in the Census Bureau’s nationwide database. This type of corridor should not be
included in a BAS response.
Example 7
Example 8
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 5.
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.
Geographic Corridors
Geographic
Corridor
NAME
CHNG_TYPE
X
X(‘C’)
EFF_DATE
AUTHTYPE
DOC
AREA
RELATE
X(‘IN’, ‘OUT’)
Table 5: Geographic Corridors (Note: ‘X’ = Required Field).
Boundary and Annexation Survey Respondent Guide: Tribal
Page 13
5.5
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, 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. Example 9 depicts a
cadastral (parcel-based) boundary map and Example 10 shows how the boundary
should be reported when sent to the Census Bureau.
Example 9
Example 10
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 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 area represented as an
offset.
Geographic Offsets
Geographic
Offset
NAME
CHNG_TYPE
X
X(‘F’)
EFF_DATE
AUTHTYPE
DOCU
AREA
RELATE
X(‘IN’, ‘OUT’)
Table 6: Geographic Offsets (Note: ‘X’ = Required Field).
Census Bureau has included an “offset” shapefile in the BAS materials
(PVS_15_v2_offset_.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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 14
D.
Tribal Subdivisions
Tribes may submit the boundaries for one type of administrative area within their
reservation(s) and/or off-reservation trust lands (land base) for inclusion in MAF/TIGER.
The Census Bureau will consider any type of unit of self-government or administration
as a “tribal subdivision.” Tribal subdivisions should cover all, or most, of the tribe’s land
base. If a tribe has more than one type of distinct administrative area that could qualify
as a tribal subdivision (such as tribal election districts, tribal water districts, or health
service areas with different boundaries), the tribe may submit only one type of
subdivision. Tribal subdivisions can be considered either active (A) or inactive (I).
Active subdivisions are defined as having a functioning government with elected officials
that provide programs and services. Inactive subdivisions have no functioning
government or elected officials and receive services solely from the tribe.
Some examples of areas submitted as tribal subdivisions are:
Areas used by a tribe for the election of tribal government officials (such as
districts or precincts used for the election of tribal council members).
Areas used by a tribal government for tax purposes.
Areas used by a tribal government for the provision of general services or
specified services, such as:
o Water districts
o Health service areas
o Emergency service delivery areas (such as 911, fire, and/or police), or
o Grazing districts or range units
Historical or traditional areas recognized by a tribal government.
Local tribal community governments.
Criteria for Defining Tribal Subdivisions
5.6
The delineation of tribal subdivisions is restricted to the area contained within
reservation(s) and/or associated off-reservation trust lands (land base).
There is no minimum population threshold for a tribal subdivision.
Tribal subdivisions should cover all, or most, of the tribe’s land base.
A tribal subdivision may be discontinuous.
A tribe may designate only ONE type of tribal subdivision. If a tribe has more
than one level of tribal subdivisions within its land base, the Census Bureau
recommends delineating subdivisions corresponding to the lowest geographic
level (those geographic areas containing the smallest area) of the tribe’s
administrative hierarchy.
Tribal subdivisions should not be based solely on land ownership or other
cadastral areas, nor should they consist of divisions based on the U.S. Public
Boundary and Annexation Survey Respondent Guide: Tribal
Page 15
Land Survey System (PLSS) of townships, ranges, and sections, if these areas
have no governmental or administrative function for your tribe.
Some examples of descriptors for tribal subdivisions are:
o District
o Community
o Area
o Chapter
o Segment
o Administrative Area
o Addition
o County District
5.7
Updating Tribal Subdivisions
Tribal Subdivisions are updated in a similar manner to boundary changes (such as
additions or deletions). In order to submit tribal subdivision updates, please create a
separate tribal subdivision change polygon layer. Updates that can be made to tribal
subdivisions include additions, deletions, boundary corrections (adding and removing
area), and creating new tribal subdivisions. Please note that all tribal subdivision
updates (additions, deletions, name changes, and new entities), with the exception of
boundary corrections, require a tribal resolution. Tables 7, 8, and 9 displays the
required attributes for each of the change types. Review the example processes in
Appendices B and C for information on how to create change polygons. Change
polygons for tribal subdivisions may be created in the same manner as for reservations
and off-reservation trust lands.
E.
Linear Feature Updates
5.8
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 7. In the TLID field, preserve the existing TLID for the
feature.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 16
Linear Feature Updates
CHNG_TYPE
TLID
Add Feature
X(‘AL’)
Delete Feature
X(‘DL’)
X
Rename Feature
X(‘CA’)
X
Recode Feature
X(‘CA’)
X
FULLNAME
MTFCC
X
X
X
X
Table 7: Linear Feature Updates (Note: ‘X’ = Required Field).
NOTE: A list of MTFCC codes can be found in Appendix D.
Linear Feature Update Guidelines
5.9
If a road, subdivision, etc. is missing from the Census Bureau’s feature network,
add the feature(s) and provide the name and MTFCC.
If a feature does not exist and is in the Census Bureau’s feature network, delete
the feature.
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.
5.10
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.
Address Range Updates
CHNG_TYPE
Address
Ranges
X(‘CA’)
FULLNAME
MTFCC
LTOADD
RTOADD
X
X
LFROMADD RFROMADD
X
X
Table 8: Address Range Updates (Note: ‘X’ = Required Field).
5.11 Area Landmarks, Hydro Areas, and Point Landmarks
1. Area Landmark / Hydro Area Updates
The Census Bureau accepts updates to area landmarks and hydrographic areas
in a similar manner to legal boundary changes. However, area landmarks and
hydro areas are not legal entities, so no documentation or effective dates are
required.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 17
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
changing the name
Example 11: This Example Shows a Boundary Correction to Park A. See Appendices B and C for
more information on creating change polygons for area landmark and hydro area s.
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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 18
Landmark/Hydro Area Updates
FULLNAME
CHNG_TYPE
RELATE
X
X(‘B’)
X(‘IN’)
X
X
X(‘B’)
X(‘OUT’)
X
Boundary Correction
(Add Area)
Boundary Correction
(Remove Area)
Delete Landmark
MTFCC
AREAID
X(‘D’)
X
X
Change Landmark
Name
X
X(‘G’)
New Landmark
X
X(‘E’)
X
Table 9: Landmark/Hydro Area Updates (Note: ‘X’ = Required Field).
The examples in Appendices B and 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
parks
Census Bureau cannot add other types of areas at this time (although some may
already exist in the database). The following are acceptable MTFCC codes for new
area landmarks or hydro areas:
New Landmark/Hydro Area 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
Boundary and Annexation Survey Respondent Guide: Tribal
Page 19
MTFCC
Description
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
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
Table 10: Landmark Area MTFCC Codes.
Due to heavy workloads for boundary changes to legal areas, changes to area
landmarks and hydrographic areas may not be added to the database until after the
next year’s BAS materials are created. It may take two BAS cycles in order to see
these changes reflected in the materials.
2. Point Landmark Updates
The Census Bureau accepts updates to point landmarks. Please submit point landmark
updates as a separate point landmark update layer. Updates to point landmarks
include:
adding a new point landmark
deleting an existing point landmark
renaming a point landmark
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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 20
Point Landmark Updates
FULLNAME
CHNG_TYPE
MTFCC
X
X(‘E’)
X
New Point Landmark
Delete Point Landmark
Change Name
X
POINTID
X(‘D’)
X
X(‘G’)
X
Table 11: Point Landmark Updates (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.
Restricted Point Landmark MTFCC Codes
MTFCC Description
K1100
K1121
K1122
K1223
K1226
K1227
K1228
K1229
K1232
K1233
K1234
K1235
K1241
K1251
K1299
K2100
K2197
K2300
K2361
K2362
K2363
K2364
K2366
K2464
K2500
K2564
Housing Unit Location
Apartment Building or Complex
Rooming or Boarding House
Trailer Court or Mobile Home Park
Housing Facility/Dormitory for Workers
Hotel, Motel, Resort, Spa, Hostel, YMCA, or YWCA
Campground
Shelter or Mission
Halfway House/Group Home
Nursing Home, Retirement Home, or Home for the Aged
County Home or Poor Farm
Juvenile Institution
Sorority, Fraternity, or College Dormitory
Military Group Quarters
Other Group Quarters Location
Governmental
Mixed Use/Other Non-residential
Commercial Workplace
Shopping Center or Major Retail Center
Industrial Building or Industrial Park
Office Building or Office Park
Farm/Vineyard/Winery/Orchard
Other Employment Center
Marina
Other Workplace
Amusement Center
Table 12: Restricted MTFCCs.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 21
Census Bureau also cannot delete or modify any point landmarks imported from the
USGS GNIS database. Changes submitted for the following types of landmarks may be
left unchanged:
K2451 (Airport)
K2582 (Cemetery)
C3022 (Summit or Pillar)
C3081 (Locale or Populated Place)
C3061 (Cul-de-sacs)
Due to heavy workloads for boundary changes to legal areas, changes to point
landmarks may not be added to the database until after the next year’s BAS materials
are created. It may take two BAS cycles in order to see these changes reflected in local
materials.
F.
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 at:
http://www.census.gov/geo/partnerships/bas/videos/introdigitalbas.html. The videos
have information on many of the topics below.
5.12
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 tribal 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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 22
Example 12: 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.
Example 13: This is an example of an addition that has been 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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 23
The Census Bureau will not accept boundary corrections that dissolve the current
relationship between an existing boundary and linear feature. Any boundary corrections
that create thirty feet or less of gap or overlap between the existing linear feature and
boundary will not be incorporated into MAF/TIGER. See below for examples of
changes that will not be accepted.
Example 14: Small spatial boundary corrections would dissolve the relationship with the river.
These boundary corrections will not be incorporated into MAF/TIGER.
Example 15: Small spatial boundary corrections that dissolve the boundary-to-feature relationship
with multiple streets have been created. Incorporating these changes would affect the population
counts for the area. Therefore, the Census Bureau will not accept these small boundary
corrections.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 24
5.13 Large Boundary Corrections
The Census Bureau will not accept large boundary corrections to an AIA without the
appropriate legal documentation(such as Trust Deed, Executive Order, new legal
opinion, act of Congress, or Federal Register Notice). 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 and
effective date so that changes may be incorporated into MAF/TIGER.
Example 16: Without the appropriate documentation, Census Bureau will not accept large
boundary corrections.
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.14
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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 25
5.15 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.16
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.
Example 17: The image on the top shows new road features added to the existing feature network,
but do not connect to existing road features. The image on the bottom shows the correction;
connecting the new roads to the existing road features.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 26
G.
Additional Review Information
The Census Bureau will not make any boundary change that affects adjacent legal
entities without the appropriate documentation. Review any change polygons that affect
adjacent entities to determine if they are intentional, legal changes.
NOTE: The Census Bureau will snap any addition, deletion, or boundary correction to a
MAF/TIGER feature when it exists within thirty feet of that feature. This helps maintain the
boundary-to-feature relationships in MAF/TIGER and will ensure correct housing tabulation
counts for entities.
5.17
Submitting Acceptable Documentation
The Census Bureau is responsible for depicting reservation and off-reservation trust
land boundaries but because the Census Bureau is not the authority on the boundaries,
we require documentation to update reservation and off-reservation trust land
boundaries.
The following changes require documentation:
New off-reservation trust land
New reservation land
Changes from off-reservation trust land to reservation land and changes from
reservation land to off-reservation trust land
Large changes to existing off-reservation trust land
Large changes to existing reservation land
Boundary corrections to off-reservation trust land or reservation land that do not
follow the general shape of the boundary
For off-reservation trust land, the most common documentation is a trust deed or a letter
from the BIA. Documents should state that the land is “in trust” for your tribe.
For reservation land, documentation examples include (but are not limited to) federal
register notice, Act of Congress, Executive Order, or a new legal opinion issued by the
BIA. When submitting large boundary corrections to an existing reservation, please
submit your reservation document.
If you cannot locate your documentation, you can contact your regional BIA office to
obtain documentation. The Census Bureau will treat legal opinions issued in writing
from the BIA as documentation since the BIA is the authority on reservation and offreservation trust land boundaries. If the Census Bureau cannot interpret a document,
such as a treaty, the Census Bureau will contact the BIA for assistance.
If you have questions about documentation, please call the Census Bureau at
1-800-796-3748 or email [email protected]. If you need to contact the BIA,
please see http://www.bia.gov/WhoWeAre/RegionalOffices/index.htm for contact
information for your regional office.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 27
5.18 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 layers that may need to be submitted:
1. Change Polygon Layers (ANRC, AIA, Tribal Subdivisions, Hawaiian Homelands)
These layers consist of the changes that the Census Bureau needs to make to
entities.
A layer of change polygons should be created for each level of geography
(ANRC, AIA, Tribal Subdivisions, etc.) that changes are being submitted for.
2. Whole Modified Entity Layer (ANRC, AIA, Tribal Subdivisions, and Hawaiian
Homelands)
These layers should only contain the complete and current boundary for the
entity being updated.
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 that need to
be corrected.
5. Area / Hydro Landmark Layer
Only if there are area and/or hydro landmark updates.
6. Point Landmark Layer
Only if there are point landmark updates.
o BAS Contact Text File (if the BAS point of contact (the person that
receives the BAS Annual Response Email) has changed)
o This can be updated online at:
http://www.census.gov/geo/partnerships/bas/bas_ar_form.html
o This BAS Contact update should include this information:
First Name:
Last Name:
Department:
Position:
Boundary and Annexation Survey Respondent Guide: Tribal
Page 28
Shipping Address:
City:
State:
ZIP Code:
Phone: xxx-xxx-xxxx
FAX: xxx-xxx-xxxx
Email:
Tribal Chair Term Expires: xx/xxxx
Tribal Chair Term Length: x years
7. AIA, ANRC, Tribal Subdivision, and Hawaiian Homeland Submissions (Change
Polygons).
The following table provides change polygon naming conventions for ANRCs,
AIAs and Hawaiian Homelands.
Change Polygon Naming Conventions
Participant
Changes Submitted For
Shapefile Naming Conventions
AIA
AIA
bas16__changes_aiannh
AIA
Tribal Subdivisions
bas16__changes_tribalsub
ANRC
ANRC
bas16__changes_anrc
Hawaiian
Homelands
Hawaiian Homelands
bas16__changes_hhl
Table 13: The change polygon layer naming conventions: represents your BAS entity ID,
found
in
the
BAS
Annual
Response
Email
or
online
from this link:
http://www.census.gov/geo/partnerships/bas/bas_codes.html.
8. ANRC, AIA, Tribal Subdivision, and Hawaiian Homeland Submissions (Whole
Entity Polygons).
The following table provides the whole entity polygon naming conventions for
ANRCs, AIAs and Hawaiian Homelands.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 29
Whole Entity Polygon Naming Conventions
Participant:
Changes Submitted For:
Shapefile Naming Conventions
AIA
AIA
bas16__WholeEntity_aiannh
AIA
Tribal Subdivision
bas16__WholeEntity_trialsub
ANRC
ANRC
bas16__WholeEntity_anrc
Hawaiian
Homelands
Hawaiian Homelands
bas16__WholeEntity_hhl
Table 14: The whole entity polygon layer naming conventions: represents your BAS
entity ID, found on the BAS Annual Response Email or online from this link:
http://www.census.gov/geo/partnerships/bas/bas_codes.html.
9. Linear Feature, Area Landmark / Hydro Area, and Point Landmark Updates
(Not Required).
The following table provides the update layer naming conventions for the
edges, area landmark, and point landmark update layers.
Edges/Area Landmarks/Point Landmarks Naming Conventions
Participant:
Changes Submitted For:
Shapefile Naming Conventions
All Participants
Edges
bas16__LN_Changes
All Participants
Area / Hydro Landmarks
bas16__Alndk_Changes
All Participants
Point Landmarks
bas16__Plndk_Changes
Table 15: The naming conventions for the edges, area landmark, and point landmark update
layers: represents your BAS entity ID, found on the BAS Annual Response Email or
online from this link: http://www.census.gov/geo/partnerships/bas/bas_codes.html.
5.19
Compressing the Digital Files
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 the Census Bureau
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: Tribal
Page 30
Example 18: Selecting and Zipping Return Files.
NOTE: Versions of WinZip may vary so the interface may be slightly different. Software other
than WinZip may be used to zip the return files.
a)
In the Add window, in the Add to archive field, type the filename in the
proper naming convention: bas__return and then click
Add.
NOTE: Look for the basID numbers on the BAS Annual Response Email or online from this link:
http://www.census.gov/geo/partnerships/bas/bas_codes.html.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 31
Example 19: Naming the Zip File.
b)
Check the folder where the zip file was saved to verify that it was
created properly. If so, the return file is ready for submission.
NOTE: If assistance is needed with preparing or zipping the BAS return files, call the Census
Bureau at 1-800-796-3748.
5.20 Submitting Digital Files via SWIM
The SWIM is a new 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.
The old BAS FTP site is no longer in operation, so please do not use it. 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
Boundary and Annexation Survey Respondent Guide: Tribal
Page 32
system. If you require additional individual SWIM accounts within your organization,
please contact the Census Bureau at 1-800-796-3748 or email [email protected].
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, the 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. If you already have a registered account, please login with your user
credentials.
Example 20: SWIM Account Registration.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 33
Example 21: SWIM Login Window.
3. If you have submitted files before, the SWIM lists them on the startup screen
upon login. Click 'Start New Upload' to continue.
Example 22: Welcome Screen with Upload History.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 34
4. On the next screen, select the Boundary and Annexation Survey (BAS) option as
the geographic partnership program, and click ‘Next’ to continue.
Example 23: Geographic Partnership Program Selection Window .
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.
Example 24: Geographic Level Selection Window .
Boundary and Annexation Survey Respondent Guide: Tribal
Page 35
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.
Example 25: Geographic Entity Selection Window .
7. On the file upload screen, please click on the ‘+ Add file', and a file browser
dialog will appear.
Example 26: File Upload Screen.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 36
8. In the file browser dialog box, select the ZIP file you would like to upload. Please
be aware that the SWIM website only accepts ZIP files. Click 'Open' to continue.
Example 27: File Browser Dialog Box .
9. At this time, you may enter any comments that you wish to include with your file.
Click 'Next' to upload your submission.
Example 28: Entering Comments into the File Upload Window.
Boundary and Annexation Survey Respondent Guide: Tribal
Page 37
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.
Example 29: Thank You Screen.
5.21
Additional Information
The Census Bureau recommends using FIPS codes to identify entities such as
counties, AIAs, etc. Using a standard coding scheme facilitates the digital exchange of
data. The Census Bureau includes these codes in the BAS shapefiles. 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-796-3748 or
[email protected].
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
Jan. 1, 2016. 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: Tribal
Page 38
APPENDICES
Boundary and Annexation Survey Respondent Guide: Tribal
Page 39
APPENDIX A Data Dictionary
Alaska Native Regional Corporation (ANRC) Shapefile
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
ANRCFP
5
String
FIPS ANRC Code
ANRCCE
2
String
Current Census ANRC Code
NAMELSAD
100
String
Name with Translated LSAD
LSAD
2
String
Legal / Statistical Area Description
AIANNHNS
8
String
ANSI Numeric Identifier for AIANNH Areas
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code Describing an Entity
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of Area Update
EFF_DATE
8
Date
Effective Date
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
(Web BAS Only)
AREA
10
Double
Acreage of Area Update
RELATE
120
String
Relationship Description
NAME
100
String
ANRC name
Table A-1: Alaska Native Regional Corporation (ANRC) Shapefile.
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-1
American Indian Areas (AIA) Shapefile
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
AIANNHCE
4
String
Census AIANNH Code
COMPTYP
1
String
Indicates if Reservation, Trust Land, or both are
Present
AIANNHFSR
1
String
Flag Indicating Level of Recognition of an AIA
NAMELSAD
100
String
Name with Translated LSAD
AIANNHNS
8
String
ANSI numeric identifier for AIA areas
LSAD
2
String
Legal / Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code Describing an Entity
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of Area Update
AUTHTYPE
1
String
Authorization Type (O – Ordinance, R – Resolution,
L – Local Law, S – State Level Action, X – Other)
EFF_DATE
8
Date
Effective Date
DOCU
120
String
Supporting Documentation
FORM_ID
4
String
(Web BAS Only)
AREA
10
Double
Acreage of Area Update
RELATE
120
String
Relationship Description
NAME
100
String
AIA name
VINTAGE
2
String
Vintage of the Data
Table A-2: American Indian Areas (AIA) Shapefile .
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-2
American Indian Tribal Subdivisions (AITS) Shapefile
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
AIANNHCE
4
String
Census AIANNH Code
TRIBALSUBCE
3
String
Census Tribal Subdivision Code
NAMELSAD
100
String
Name with translated LSAD
AIANNHNS
8
String
ANSI Numeric Identifier for AIANNH Areas
LSAD
2
String
Legal / Statistical Area Description
FUNCSTAT
1
String
Functional Status
CLASSFP
2
String
FIPS 55 Class Code Describing an Entity
PARTFLG
1
String
Part Flag Indicator
CHNG_TYPE
2
String
Type of Area Update
EFF_DATE
8
Date
Effective Date
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
(Web BAS Only)
AREA
10
Double
Acreage of Area Update
RELATE
120
String
Relationship Description
NAME
100
String
Tribal subdivision name
VINTAGE
2
String
Vintage of the Data
AIANNHFSR
1
String
Flag Indicating Level of Recognition of an AIA
Table A-3: American Indian Tribal Subdivisions (AITS) Shapefile .
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-3
Edges Shapefile
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
State FIPS Code
COUNTYFP
3
String
County FIPS 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
Prefix qualifier code, prefix direction code, prefix type
code, base name, suffix type code, suffix qualifier
code
SMID
22
String
Spatial Metadata ID
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
2020_BBSP
1
String
New BBSP flag
CHNG_TYPE
4
String
Type of linear update
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
Table A-4: Edges Shapefile.
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-4
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
Prefix direction code, prefix type code, base name,
suffix type code, suffix direction code
AREAID
22
String
Landmark identification number
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
BAG
3
String
Block Area Grouping
Table A-5: Area Landmark Shapefile.
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
Prefix direction code, prefix type code, base name,
suffix type, suffix type code, suffix direction code
CHNG_TYPE
2
String
Type of Area Update
HYDROID
22
String
Hydrography Identification Number
RELATE
120
String
Relationship description
Table A-6: Hydro Area Shapefile.
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-5
Point Landmarks Shapefile
ATTRIBUTE FIELD
LENGTH
TYPE
DESCRIPTION
STATEFP
2
String
FIPS State Code
COUNTYFP
3
String
FIPS County Code
POINTID
22
String
Point Landmark Identification Number
MTFCC
5
String
MAF/TIGER Feature Class Code
FULLNAME
120
String
Prefix type code, base name, suffix type code
CHNG_TYPE
2
String
Type of Area Update
Table A-7: Point Landmarks Shapefile.
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
Table A-8: Geographic Offset Shapefile.
Boundary and Annexation Survey Respondent Guide: Tribal
Page A-6
APPENDIX B 2016 Digital BAS – Example Process 1
B1.
Required Census Bureau Shapefiles
When downloading shapefiles for the 2016 BAS, shapefiles will begin with
the prefix PVS (e.g., PVS_15_v2_edges_.shp).
Throughout this guide, Census Bureau uses the prefix of bas_2016, but
the PVS files are exactly the same.
NOTE: Contact the Census Bureau at 1-800-796-3748 or [email protected] with any
questions.
Copy the data to a hard drive/server, and unzip the data to ensure that the
correct data was downloaded. For an AIA, these layers are critical:
PVS_15_v2_aial_.shp
PVS_15_v2_edges_.shp
NOTE: represents the two-digit state code and three-digit county code.
The shapefiles should include the home county/counties for all reservations and
off-reservation trust lands as well as all adjacent counties.
NOTE: Census Bureau suggests that participants make an extra copy of the data as an
emergency backup.
B2.
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 B-1:
Edges MTFCC Suggested Symbolization
MTFCC 1st Character
Linear Feature Type
H
Hydrology
P
Non-Visible Feature
(boundary)
R
Railroad
S
Road
Symbol
Table B-1: MTFCC Types and Suggested Symbolization.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-1
B.2.1
Symbolizing Geographic Areas
Symbolize the AIAL layer by “COMPTYP” field to show reservation and offreservation trust land.
NOTE: AIA participants working on changes for tribal subdivisions may want to use different
colors to distinguish one from another.
Example B-1: Suggested Map Symbolization.
B3.
Extracting AIA Data from Census Bureau Shapefiles
NOTE: If you do not have an ArcInfo license, skip ahead to Section B5.
B.3.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 bas_2016_aial_.
Double click “NAME”
Left click the = button,
Click the Get Unique Values button
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-2
In the list, locate and double click the name of the entity. (It will appear in the
formula).
Click OK
Example B-2: Filtering Data.
B.3.2 Exporting the Data to a New Shapefile
1. In the Table of Contents, Right click the AIA layer, select Data, and then click
Export Data.
2. In the Export Data window:
From the Export dropdown, choose Selected Features.
In the Output shapefile or feature class field, enter a location to save the
shapefile.
Click OK.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-3
Example B-3: Export Data Window.
NOTE: If the AIA spans more than one county, it will need to be exported from each county’s
AIA shapefile and merged. Follow the instructions in Section B4 if the AIA needs to be merged,
otherwise skip to Section B5.
B.3.3 Merging Multipart AIA 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 Input 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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-4
Example B-4: Finalizing the Merge Process.
B4.
Creating Change Polygons Using Symmetrical Difference
NOTE: If you do not have an ArcInfo license, you will have to use the Union operation rather
than the Symmetrical Difference operation. See Section B5 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 that was created in Section 3.
In the Update Features field, click the arrow (or browse) and select the
tribal 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_tribal,
Differences1, or anything easy to find/remember.
Click OK.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-5
Example B-5: 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.
3. 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.
4. On the Advanced Editing toolbar, click the Explode tool
contain a separate record for each change.
. The layer will now
The created layer shows individual change polygons representing the differences
between the Census Bureau and tribal entity boundaries. These differences need to be
reviewed and coded appropriately.
Skip to Section B6, Reviewing and Attributing Change Polygons.
B5.
Creating Change Polygons Using Union
NOTE: 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_15_v2_aial_, and the tribe’s own layer.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-6
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.
Example B-6: Finalizing the Union Process.
The union operation will create records that contain differences as well as areas that are
in common between the Census Bureau and local tribal boundary layers.
The next step is selecting and deleting the areas in common between the Census
Bureau and local tribal boundary layers.
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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-7
Example B-7: 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 tribal layers
have in common.
Select each feature individually, or click and hold the left mouse button and
drag a box to highlight the common features.
Press Delete.
Repeat these steps until only the features that have changed are left in the
map.
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.
8. On the Advanced Editing toolbar, click the Explode tool
contain a separate record for each change.
Boundary and Annexation Survey Respondent Guide: Tribal
. The layer will now
Page B-8
The new layer shows individual change polygons representing the differences between
the Census Bureau and the tribal government’s representation of the boundaries.
Please review these differences and make sure they are coded appropriately. Continue
to the next section for instructions on reviewing and coding change polygons.
B6.
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.7 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.6.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.
Example B-8: Small Slivers That Should Be Deleted.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-9
These examples show polygons that should be snapped to roads (left) or
rivers (right).
Example B-9: Polygons That Should Be Snapped to Roads or Rivers.
B.6.2
Attribute Information
NOTE: All updates MUST be attributed.
To begin updating attributes
On the Editor Toolbar, click Editor, and then click Start Editing.
Additions
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for an addition.
button and select the addition
button.
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
o The CHNG_TYPE for an addition is A.
Deletions
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a deletion.
button and select the deletion
button.
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
o The CHNG_TYPE for a deletion is D.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-10
Corridors
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a corridor.
button and select the corridor
button.
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
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for an offset.
button and select the offset
button.
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
correction polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a boundary
correction:
o
button and select the boundary
button.
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 boundary correction to one tribal subdivision affects another, use RELATE = IN and
NAME = . This is due to the fact that RELATE = OUT leaves a question
as to whether or not there should be a gap between the two entities.
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-11
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.)
B7. 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 (AIA, tribal subdivision) 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:
bas16__changes_aiannh.
NOTE: You can find the basID numbers in the BAS Annual Response Email or online from this
link: http://www.census.gov/geo/partnerships/bas/bas_codes.html.
NOTE: See Section 5.19 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.20 Submitting Digital Files via the Secure Web Incoming
Module (SWIM).
Boundary and Annexation Survey Respondent Guide: Tribal
Page B-12
APPENDIX C 2016 Digital BAS – Example Process 2
C.1
Required Census Bureau Shapefiles
When downloading shapefiles for the 2016 BAS, shapefiles will begin with
the prefix PVS (e.g., PVS_15_v2_edges_.shp).
Throughout this guide, Census Bureau uses the prefix of bas_2016, but
the PVS files are exactly the same.
NOTE: Contact the Census Bureau at 1-800-796-3748 or [email protected] with any
questions.
Copy the data to a hard drive/server, and unzip the data to ensure that the
correct data was downloaded. For an AIA, these layers are critical:
PVS_15_v2_aial_.shp
PVS_15_v2_edges_.shp
NOTE: represents the two-digit state code and three-digit county code.
The shapefiles should include the home county/counties for all of your
reservation and off-reservation trust lands as well as all adjacent counties.
NOTE: Census Bureau suggests that participants make an extra copy of the data as an
emergency backup.
C.2
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 A2B.2.1:
Edges MTFCC Suggested Symbolization
MTFCC 1st
Character…
Linear Feature Type
H
Hydrology
P
Non-Visible Feature
(boundary)
R
Railroad
S
Road
Symbol
Table C-1: MTFCC Types and Suggested Symbolization.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-13
C.2.1 Symbolizing Geographic Areas
Symbolize the AIAL layer by “COMPTYP” field to show reservation and off-reservation
trust land.
NOTE: AIA participants reporting tribal subdivisions may want to use different colors to
distinguish one from another.
Example C-1: Suggested Map Symbolization.
C.3
Creating and Splitting Linear Features
C.3.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 one which 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_15_v2_edges_.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-14
Example C-2: 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.
Example C-3: 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 Example A2B.3.1.1), and in the
Editor toolbar, click the Straight Segment Tool
button and draw new
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-15
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.
Example C-4: A Newly Created Linear Feature .
C.3.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 Appendix D 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. It is not necessary to
submit linear feature changes for non-visible boundaries.
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.3.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: Tribal
Page C-16
Example C-5: 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.
Example C-6: Linear Feature Selection After Being Split.
4. Once all necessary splits are made, in the Editor toolbar, click Editor and then
click Save Edits.
C.3.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.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-17
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 aia layer:
PVS_15_v2_aial_.
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 addition, deletion, or
incorrect area) by holding the Shift key while clicking each linear feature
segment.
Example C-7: 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 AIA layer; however, it will not have any associated
attribute values (see the next section).
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-18
Example C-8: Newly Created AIA Feature.
C.3.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 will 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 AIA layer in the Table of Contents, click Selection,
and then click Make This The Only Selectable Layer, so that the AIA layer is
the only one which can be selected while editing
On the Editor Toolbar, click Editor, and then click Start Editing.
Additions
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for an addition.
button and select the addition
button.
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
The CHNG_TYPE for an addition is A.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-19
Deletions
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a deletion.
button and select the deletion
button.
o NAME, CHNG_TYPE, AUTHTYPE, DOCU and EFF_DATE.
o The CHNG_TYPE for an addition is D.
Corridors
On the Editor Toolbar, click the Edit Tool
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a corridor.
button and select the corridor
button.
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
polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for an offset.
button and select the offset
button.
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
correction polygon.
On the Editor Toolbar, click the Attributes
In the Attributes window, fill out the mandatory fields required for a boundary
correction:
button and select the boundary
button.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-20
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 boundary correction to one tribal subdivision affects another, use RELATE = IN and
NAME = . This is due to the fact that RELATE = OUT leaves a question
as to whether or not there should be a gap between the two 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.3.6 Exporting Change Polygons
After creating and coding the change polygons, each level of geography (AIA, tribal
subdivision) 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 AIA layer: bas_2016_aial_.
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 a specific change type for polygons
that were created and coded.
Click OK
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-21
Example C-9: Select All Change Types Formula.
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
4. In the ArcMap Table of Contents, right-click on the AIA layer
(PVS_15_v2_aial_), select Data, and then click Export Data.
5. 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 bas16__changes_aiannh.shp.
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-22
Click OK.
Example C-10: Exporting Data.
NOTE: The basID numbers can be found on the BAS Annual Response Email or online from
this link: http://www.census.gov/geo/partnerships/bas/bas_codes.html.
NOTE: See Section 5.9.4 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.19 and Section 5.20 Submitting Digital
Files via the Secure Web Incoming Module (SWIM).
Boundary and Annexation Survey Respondent Guide: Tribal
Page C-23
APPENDIX D MTFCC Codes
MTFCC FEATURE CLASS
C3022
MOUNTAIN PEAK OR
SUMMIT
C3023
ISLAND
C3024
LEVEE
C3026
C3027
QUARRY (NOT WATERFILLED), OPEN PIT MINE OR
MINE
DAM
C3061
CUL-DE-SAC
C3062
TRAFFIC CIRCLE
C3066
C3067
GATE
TOLL BOOTH
C3071
LOOKOUT TOWER
C3074
LIGHTHOUSE BEACON
C3075
TANK/TANK FARM
C3076
WINDMILL FARM
C3077
SOLAR FARM
C3078
MONUMENT OR MEMORIAL
C3079
BOUNDARY MONUMENT
POINT
C3080
SURVEY CONTROL POINT
C3081
LOCALITY POINT
FEATURE CLASS DESCRIPTION
A PROMINENT ELEVATION RISING ABOVE THE
SURROUNDING LEVEL OF THE EARTH'S SURFACE.
AN AREA OF DRY OR RELATIVELY DRY LAND
SURROUNDED BY WATER OR LOW WETLAND.
[INCLUDING ARCHIPELAGO, ATOLL, CAY, HAMMOCK,
HUMMOCK, ISLA, ISLE, KEY, MOKU AND ROCK]
AN EMBANKMENT FLANKING A STREAM OR OTHER
FLOWING WATER FEATURE TO PREVENT OVERFLOW.
AN AREA FROM WHICH COMMERCIAL MINERALS ARE
OR WERE REMOVED FROM THE EARTH; NOT
INCLUDING AN OILFIELD OR GAS FIELD.
A BARRIER BUILT ACROSS THE COURSE OF A STREAM
TO IMPOUND WATER AND/OR CONTROL WATER
FLOW.
AN EXPANDED PAVED AREA AT THE END OF A STREET
USED BY VEHICLES FOR TURNING AROUND. FOR
MAPPING PURPOSES, THE U.S. CENSUS BUREAU
MAPS IT ONLY AS A POINT FEATURE.
A CIRCULAR INTERSECTION ALLOWING FOR
CONTINUOUS MOVEMENT OF TRAFFIC AT THE
MEETING OF ROADWAYS.
A MOVABLE BARRIER ACROSS A ROAD.
STRUCTURE OR BARRIER WHERE A FEE IS
COLLECTED FOR USING ROAD.
A MANMADE STRUCTURE, HIGHER THAN ITS
DIAMETER, USED FOR OBSERVATION.
A MANMADE STRUCTURE, HIGHER THAN ITS
DIAMETER, USED FOR TRANSMISSION OF LIGHT AND
POSSIBLY SOUND GENERALLY TO AID IN NAVIGATION.
ONE OR MORE MANMADE STRUCTURES, EACH
HIGHER THAN ITS DIAMETER, USED FOR LIQUID
(OTHER THAN WATER) OR GAS STORAGE OR FOR
DISTRIBUTION ACTIVITIES.
ONE OR MORE MANMADE STRUCTURES USED TO
GENERATE POWER FROM THE WIND.
ONE OR MORE MANMADE STRUCTURES USED TO
GENERATE POWER FROM THE SUN.
A MANMADE STRUCTURE TO EDUCATE,
COMMEMORATE, OR MEMORIALIZE AN EVENT,
PERSON, OR FEATURE.
A MATERIAL OBJECT PLACED ON OR NEAR A
BOUNDARY LINE TO PRESERVE AND IDENTIFY THE
LOCATION OF THE BOUNDARY LINE ON THE GROUND.
A POINT ON THE GROUND WHOSE POSITION
(HORIZONTAL OR VERTICAL) IS KNOWN AND CAN BE
USED AS A BASE FOR ADDITIONAL SURVEY WORK.
A POINT THAT IDENTIFIES THE LOCATION AND NAME
OF AN UNBOUNDED LOCALITY (E.G., CROSSROAD,
COMMUNITY, POPULATED PLACE OR LOCALE).
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-1
MTFCC FEATURE CLASS
C3085
ALASKA NATIVE VILLAGE
OFFICIAL POINT
G2100
AMERICAN INDIAN AREA
G2120
HAWAIIAN HOME LAND
G2130
ALASKA NATIVE VILLAGE
STATISTICAL AREA
G2140
OKLAHOMA TRIBAL
STATISTICAL AREA
G2150
STATE-DESIGNATED TRIBAL
STATISTICAL AREA
G2160
TRIBAL DESIGNATED
STATISTICAL AREA
G2170
AMERICAN INDIAN JOINT
USE AREA
ALASKA NATIVE REGIONAL
CORPORATION
G2200
G2300
TRIBAL SUBDIVISION
G2400
TRIBAL CENSUS TRACT
FEATURE CLASS DESCRIPTION
A POINT THAT SERVES AS THE CORE OF AN ALASKA
NATIVE VILLAGE AND IS USED IN DEFINING ALASKA
NATIVE VILLAGE STATISTICAL AREAS.
A LEGALLY DEFINED STATE- OR FEDERALLY
RECOGNIZED RESERVATION AND/OR OFFRESERVATION TRUST LAND (EXCLUDES STATISTICAL
AMERICAN INDIAN AREAS).
LEGAL AREA HELD IN TRUST FOR THE BENEFIT OF
NATIVE HAWAIIANS.
A STATISTICAL GEOGRAPHIC ENTITY THAT
REPRESENTS THE RESIDENCES, PERMANENT AND/OR
SEASONAL, FOR ALASKA NATIVES WHO ARE
MEMBERS OF OR RECEIVING GOVERNMENTAL
SERVICES FROM THE DEFINING LEGAL ALASKA
NATIVE VILLAGE CORPORATION.
A STATISTICAL ENTITY IDENTIFIED AND DELINEATED
BY THE CENSUS BUREAU IN CONSULTATION WITH
FEDERALLY RECOGNIZED AMERICAN INDIAN TRIBES
THAT HAVE NO CURRENT RESERVATION, BUT HAD A
FORMER RESERVATION IN OKLAHOMA.
A STATISTICAL GEOGRAPHIC ENTITY IDENTIFIED AND
DELINEATED FOR THE CENSUS BUREAU BY A STATEAPPOINTED LIAISON FOR A STATE-RECOGNIZED
AMERICAN INDIAN TRIBE THAT DOES NOT
CURRENTLY HAVE A RESERVATION AND/OR LANDS IN
TRUST.
A STATISTICAL GEOGRAPHIC ENTITY IDENTIFIED AND
DELINEATED FOR THE CENSUS BUREAU BY A
FEDERALLY RECOGNIZED AMERICAN INDIAN TRIBE
THAT DOES NOT CURRENTLY HAVE A RESERVATION
AND/OR OFF-RESERVATION TRUST LAND.
AREA ADMINISTERED JOINTLY/CLAIMED BY TWO OR
MORE AMERICAN INDIAN TRIBES.
CORPORATE ENTITIES ESTABLISHED TO CONDUCT
BOTH BUSINESS AND NONPROFIT AFFAIRS OF
ALASKA NATIVES PURSUANT TO THE ALASKA NATIVE
CLAIMS SETTLEMENT ACT OF 1972 (PUBLIC LAW 92203). THERE ARE TWELVE GEOGRAPHICALLY DEFINED
ANRCS AND THEY ARE ALL WITHIN AND COVER MOST
OF THE STATE OF ALASKA (THE ANNETTE ISLAND
RESERVE-AN AMERICAN INDIAN RESERVATION-IS
EXCLUDED FROM ANY ANRC). THE BOUNDARIES OF
ANRCS HAVE BEEN LEGALLY ESTABLISHED.
ADMINISTRATIVE SUBDIVISIONS OF FEDERALLY
RECOGNIZED AMERICAN INDIAN RESERVATIONS, OFFRESERVATION TRUST LANDS, OKLAHOMA TRIBAL
STATISTICAL AREAS (OTSAS). ENTITIES ARE
INTERNAL UNITS OF SELFGOVERNMENT/ADMINISTRATION THAT SERVE SOCIAL,
CULTURAL, AND/OR ECONOMIC PURPOSES FOR THE
AMERICAN INDIANS ON THE RESERVATIONS, OFFRESERVATION TRUST LANDS, OR OTSAS.
RELATIVELY SMALL, PERMANENT STATISTICAL
SUBDIVISION OF FEDERALLY RECOGNIZED AMERICAN
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-2
MTFCC FEATURE CLASS
G2410
TRIBAL BLOCK GROUP
G3100
COMBINED STATISTICAL
AREA
G3110
METROPOLITAN AND
MICROPOLITAN STATISTICAL
AREA
G3120
METROPOLITAN DIVISION
G3200
COMBINED NEW ENGLAND
CITY AND TOWN AREA
G3210
NEW ENGLAND CITY AND
TOWN METROPOLITAN AND
MICROPOLITAN STATISTICAL
AREA
G3220
NEW ENGLAND CITY AND
TOWN DIVISION
G3500
URBAN AREA
G4000
STATE OR EQUIVALENT
FEATURE
G4020
COUNTY OR EQUIVALENT
FEATURE
FEATURE CLASS DESCRIPTION
INDIAN RESERVATION/ OFF-RESERVATION TRUST
LAND, DELINEATED BY AMERICAN INDIAN TRIBAL
PARTICIPANTS OR THE BUREAU FOR THE PURPOSE
OF PRESENTING DEMOGRAPHIC DATA.
CLUSTER OF CENSUS BLOCKS WITHIN A SINGLE
TRIBAL CENSUS TRACT DELINEATED BY AMERICAN
INDIAN TRIBAL PARTICIPANTS OR THE BUREAU FOR
PURPOSE OF PRESENTING DEMOGRAPHIC DATA
A GROUPING OF ADJACENT METROPOLITAN AND/OR
MICROPOLITAN STATISTICAL AREAS THAT HAVE A
DEGREE OF ECONOMIC AND SOCIAL INTEGRATION,
AS MEASURED BY COMMUTING.
AN AREA CONTAINING A SUBSTANTIAL POPULATION
NUCLEUS TOGETHER WITH ADJACENT COMMUNITIES
HAVING A HIGH DEGREE OF ECONOMIC AND SOCIAL
INTEGRATION WITH THAT CORE, AS MEASURED BY
COMMUTING. DEFINED USING WHOLE COUNTIES AND
EQUIVALENTS.
A COUNTY OR GROUPING OF COUNTIES THAT IS A
SUBDIVISION OF A METROPOLITAN STATISTICAL AREA
CONTAINING AN URBANIZED AREA WITH A
POPULATION OF 2.5 MILLION OR MORE.
A GROUPING OF ADJACENT NEW ENGLAND CITY AND
TOWN AREAS THAT HAVE A DEGREE OF ECONOMIC
AND SOCIAL INTEGRATION, AS MEASURED BY
COMMUTING.
AN AREA CONTAINING A SUBSTANTIAL POPULATION
NUCLEUS TOGETHER WITH ADJACENT COMMUNITIES
HAVING A HIGH DEGREE OF ECONOMIC AND SOCIAL
INTEGRATION WITH THAT CORE, AS MEASURED BY
COMMUTING. DEFINED USING MINOR CIVIL DIVISIONS
(MCDS) IN NEW ENGLAND.
A GROUPING OF CITIES AND TOWNS IN NEW
ENGLAND THAT IS A SUBDIVISION OF A NEW
ENGLAND CITY AND TOWN AREA CONTAINING AN
URBANIZED AREA WITH A POPULATION OF 2.5 MILLION
OR MORE.
DENSELY SETTLED TERRITORY THAT CONTAINS AT
LEAST 2,500 PEOPLE. THE SUBTYPES OF THIS
FEATURE ARE URBANIZED AREA (UA), WHICH
CONSISTS OF 50,000 + PEOPLE AND URBAN CLUSTER,
WHICH RANGES BETWEEN 2,500 AND 49,999 PEOPLE.
THE PRIMARY GOVERNMENTAL DIVISIONS OF THE
UNITED STATES. THE DISTRICT OF COLUMBIA IS
TREATED AS A STATISTICAL EQUIVALENT OF A STATE
FOR CENSUS PURPOSES, AS IS PUERTO RICO.
THE PRIMARY DIVISION OF A STATE OR STATE
EQUIVALENT AREA. THE PRIMARY DIVISIONS OF 48
STATES ARE TERMED COUNTY, BUT OTHER TERMS
ARE USED SUCH AS BOROUGH IN ALASKA, PARISH IN
LOUISIANA, AND MUNICIPIO IN PUERTO RICO. THIS
FEATURE INCLUDES INDEPENDENT CITIES, WHICH
ARE INCORPORATED PLACES THAT ARE NOT PART OF
ANY COUNTY.
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-3
MTFCC FEATURE CLASS
G4040 COUNTY SUBDIVISION
G4050
ESTATE
G4060
SUBBARRIO (SUBMINOR
CIVIL DIVISION)
G4110
INCORPORATED PLACE
G4120
CONSOLIDATED CITY
G4210
CENSUS DESIGNATED
PLACE
G4300
ECONOMIC CENSUS PLACE
G5020
CENSUS TRACT
G5030
BLOCK GROUP
FEATURE CLASS DESCRIPTION
THE PRIMARY DIVISIONS OF COUNTIES AND
EQUIVALENT FEATURES FOR THE REPORTING OF
CENSUS BUREAU DATA. THE SUBTYPES OF THIS
FEATURE ARE MINOR CIVIL DIVISION, CENSUS
COUNTY DIVISION/CENSUS SUBAREA, AND
UNORGANIZED TERRITORY. THIS FEATURE INCLUDES
INDEPENDENT PLACES, WHICH ARE INCORPORATED
PLACES THAT ARE NOT PART OF ANY COUNTY
SUBDIVISION.
ESTATES ARE SUBDIVISIONS OF THE THREE MAJOR
ISLANDS IN THE UNITED STATES VIRGIN ISLANDS
(USVI).
LEGALLY DEFINED DIVISIONS (SUBBARRIOS) OF
MINOR CIVIL DIVISIONS (BARRIOS-PUEBLO AND
BARRIOS) IN PUERTO RICO.
A LEGAL ENTITY INCORPORATED UNDER STATE LAW
TO PROVIDE GENERAL-PURPOSE GOVERNMENTAL
SERVICES TO A CONCENTRATION OF POPULATION.
INCORPORATED PLACES ARE GENERALLY
DESIGNATED AS A CITY, BOROUGH, MUNICIPALITY,
TOWN, VILLAGE, OR, IN A FEW INSTANCES, HAVE NO
LEGAL DESCRIPTION.
AN INCORPORATED PLACE THAT HAS MERGED
GOVERNMENTALLY WITH A COUNTY OR MINOR CIVIL
DIVISION, BUT ONE OR MORE OF THE INCORPORATED
PLACES CONTINUES TO FUNCTION WITHIN THE
CONSOLIDATION. IT IS A PLACE THAT CONTAINS
ADDITIONAL SEPARATELY INCORPORATED PLACES.
A STATISTICAL AREA DEFINED FOR A NAMED
CONCENTRATION OF POPULATION AND THE
STATISTICAL COUNTERPART OF AN INCORPORATED
PLACE.
THE LOWEST LEVEL OF GEOGRAPHIC AREA FOR
PRESENTATION OF SOME TYPES OF ECONOMIC
CENSUS DATA. IT INCLUDES INCORPORATED PLACES,
CONSOLIDATED CITIES, CENSUS DESIGNATED
PLACES (CDPS), MINOR CIVIL DIVISIONS (MCDS) IN
SELECTED STATES, AND BALANCES OF MCDS OR
COUNTIES. AN INCORPORATED PLACE, CDP, MCD, OR
BALANCE OF MCD QUALIFIES AS AN ECONOMIC
CENSUS PLACE IF IT CONTAINS 5,000 OR MORE
RESIDENTS, OR 5,000 OR MORE JOBS, ACCORDING TO
THE MOST CURRENT DATA AVAILABLE.
RELATIVELY PERMANENT STATISTICAL SUBDIVISIONS
OF A COUNTY OR EQUIVALENT FEATURE DELINEATED
BY LOCAL PARTICIPANTS AS PART OF THE CENSUS
BUREAU'S PARTICIPANT STATISTICAL AREAS
PROGRAM.
A CLUSTER OF CENSUS BLOCKS HAVING THE SAME
FIRST DIGIT OF THEIR FOUR-DIGIT IDENTIFYING
NUMBERS WITHIN A CENSUS TRACT. FOR EXAMPLE,
BLOCK GROUP 3 (BG 3) WITHIN A CENSUS TRACT
INCLUDES ALL BLOCKS NUMBERED FROM 3000 TO
3999.
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-4
MTFCC FEATURE CLASS
G5035 BLOCK AREA GROUPING
G5040
TABULATION BLOCK
G5200
CONGRESSIONAL DISTRICT
G5210
STATE LEGISLATIVE
DISTRICT (UPPER CHAMBER
G5220
STATE LEGISLATIVE
DISTRICT (LOWER
CHAMBER)
G5240
VOTING DISTRICT
G5400
ELEMENTARY SCHOOL
DISTRICT
G5410
SECONDARY SCHOOL
DISTRICT
G5420
UNIFIED SCHOOL DISTRICT
G6120
PUBLIC-USE MICRODATA
AREA
FEATURE CLASS DESCRIPTION
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, 4) NOT CROSS THE BOUNDARY OF OTHER
TABULATION GEOGRAPHIES (I.E.,COUNTY OR
INCORPORATED PLACE BOUNDARIES).
THE LOWEST-ORDER CENSUS DEFINED STATISTICAL
AREA. IT IS AN AREA, SUCH AS A CITY BLOCK,
BOUNDED PRIMARILY BY PHYSICAL FEATURES BUT
SOMETIMES BY INVISIBLE CITY OR PROPERTY
BOUNDARIES. A TABULATION BLOCK BOUNDARY
DOES NOT CROSS THE BOUNDARY OF ANY OTHER
GEOGRAPHIC AREA FOR WHICH THE CENSUS
BUREAU TABULATES DATA. THE SUBTYPES OF THIS
FEATURE ARE COUNT QUESTION RESOLUTION (CQR),
CURRENT, AND CENSUS.
THE 435 AREAS FROM WHICH PEOPLE ARE ELECTED
TO THE U.S. HOUSE OF REPRESENTATIVES.
ADDITIONAL T FEATURES EXIST FOR STATE
EQUIVALENTS WITH NONVOTING DELEGATES OR NO
REPRESENTATIVE. SUBTYPES OF THIS FEATURE ARE
106TH, 107TH, 108TH, 109TH, 111TH CONGRESSIONAL
DISTRICTS, PLUS SUBSEQUENT CONGRESSES.
AREAS ESTABLISHED BY A STATE OR EQUIVALENT
GOVERNMENT FROM WHICH MEMBERS ARE ELECTED
TO THE UPPER OR UNICAMERAL CHAMBER OF A
STATE GOVERNING BODY. THE UPPER CHAMBER IS
THE SENATE IN A BICAMERAL LEGISLATURE, AND THE
UNICAMERAL CASE IS A SINGLE HOUSE LEGISLATURE
(NEBRASKA).
AREAS ESTABLISHED BY A STATE OR EQUIVALENT
GOVERNMENT FROM WHICH MEMBERS ARE ELECTED
TO THE LOWER CHAMBER OF A STATE GOVERNING
BODY. THE LOWER CHAMBER IS THE HOUSE OF
REPRESENTATIVES IN A BICAMERAL LEGISLATURE.
GENERIC NAME FOR GEOGRAPHIC FEATURES, SUCH
AS PRECINCTS, WARDS, ELECTION DISTRICTS,
ESTABLISHED BY STATE, LOCAL, AND TRIBAL
GOVERNMENTS FOR THE PURPOSE OF CONDUCTING
ELECTIONS.
A GEOGRAPHIC AREA WITHIN WHICH OFFICIALS
PROVIDE PUBLIC ELEMENTARY GRADE-LEVEL
EDUCATIONAL SERVICES FOR RESIDENTS.
A GEOGRAPHIC AREA WITHIN WHICH OFFICIALS
PROVIDE PUBLIC SECONDARY GRADE-LEVEL
EDUCATIONAL SERVICES FOR RESIDENTS.
A GEOGRAPHIC AREA WITHIN WHICH OFFICIALS
PROVIDE PUBLIC EDUCATIONAL SERVICES FOR ALL
GRADE LEVELS FOR RESIDENTS.
A DECENNIAL CENSUS AREA WITH A POPULATION OF
AT LEAST 100,000 OR MORE PERSONS FOR WHICH
THE CENSUS BUREAU PROVIDES SELECTED
EXTRACTS OF HOUSEHOLD-LEVEL DATA THAT ARE
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-5
MTFCC FEATURE CLASS
G6300
TRAFFIC ANALYSIS
DISTRICT
G6320
TRAFFIC ANALYSIS ZONE
G6330
URBAN GROWTH AREA
G6350
ZIP CODE TABULATION
AREA (FIVE-DIGIT)
G6400
COMMERCIAL REGION
H1100
CONNECTOR
H2025
SWAMP/MARSH
H2030
LAKE/POND
H2040
H2041
RESERVOIR
TREATMENT POND
H2051
BAY/ESTUARY/GULF/SOUND
H2053
OCEAN/SEA
H2060
GRAVEL PIT/QUARRY FILLED
WITH WATER
H2081
GLACIER
H3010
STREAM/RIVER
H3013
BRAIDED STREAM
H3020
CANAL, DITCH OR
AQUEDUCT
FEATURE CLASS DESCRIPTION
SCREENED TO PROTECT CONFIDENTIALITY
AN AREA DELINEATED BY METROPOLITAN PLANNING
ORGANIZATIONS (MPOS) AND STATE DEPARTMENTS
OF TRANSPORTATION (DOTS) FOR TABULATING
JOURNEY-TO-WORK AND PLACE-OF-WORK DATA. A
TRAFFIC ANALYSIS DISTRICT (TAD) CONSISTS OF ONE
OR MORE TRAFFIC ANALYSIS ZONES (TAZS).
AN AREA DELINEATED BY METROPOLITAN PLANNING
ORGANIZATIONS (MPOS) AND STATE DEPARTMENTS
OF TRANSPORTATION (DOTS) FOR TABULATING
JOURNEY-TO-WORK AND PLACE-OF-WORK DATA.
AN AREA DEFINED UNDER STATE AUTHORITY TO
MANAGE URBANIZATION THAT THE U.S. CENSUS
BUREAU INCLUDES IN THE MAF/TIGER® DATABASE IN
AGREEMENT WITH THE STATE.
AN APPROXIMATE STATISTICAL-AREA
REPRESENTATION OF A U.S. POSTAL SERVICE (USPS)
5-DIGIT ZIP CODE SERVICE AREA.
FOR THE PURPOSE OF PRESENTING ECONOMIC
STATISTICAL DATA, MUNICIPIOS IN PUERTO RICO ARE
GROUPED INTO COMMERCIAL REGIONS.
A KNOWN, BUT NONSPECIFIC, HYDROGRAPHIC
CONNECTION BETWEEN TWO NONADJACENT WATER
FEATURES.
A POORLY DRAINED WETLAND, FRESH OR
SALTWATER, WOODED OR GRASSY, POSSIBLY
COVERED WITH OPEN WATER. [INCLUDES BOG,
CIENEGA, MARAIS AND POCOSIN]
A STANDING BODY OF WATER THAT IS SURROUNDED
BY LAND.
AN ARTIFICIALLY IMPOUNDED BODY OF WATER.
AN ARTIFICIAL BODY OF WATER BUILT TO TREAT
FOULED WATER.
A BODY OF WATER PARTLY SURROUNDED BY LAND.
[INCLUDES ARM, BIGHT, COVE AND INLET]
THE GREAT BODY OF SALT WATER THAT COVERS
MUCH OF THE EARTH.
A BODY OF WATER IN A PLACE OR AREA FROM WHICH
COMMERCIAL MINERALS WERE REMOVED FROM THE
EARTH.
A BODY OF ICE MOVING OUTWARD AND DOWN SLOPE
FROM AN AREA OF ACCUMULATION; AN AREA OF
RELATIVELY PERMANENT SNOW OR ICE ON THE TOP
OR SIDE OF A MOUNTAIN OR MOUNTAINOUS AREA.
[INCLUDES ICE FIELD AND ICE PATCH]
A NATURAL FLOWING WATERWAY. [INCLUDES
ANABRANCH, AWAWA, BRANCH, BROOK, CREEK,
DISTRIBUTARY, FORK, KILL, PUP, RIO, AND RUN]
A NATURAL FLOWING WATERWAY WITH AN INTRICATE
NETWORK OF INTERLACING CHANNELS.
AN ARTIFICIAL WATERWAY CONSTRUCTED TO
TRANSPORT WATER, TO IRRIGATE OR DRAIN LAND,
TO CONNECT TWO OR MORE BODIES OF WATER, OR
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-6
MTFCC FEATURE CLASS
K1225
CREW-OF-VESSEL
LOCATION
K1231
HOSPITAL/HOSPICE/URGENT
CARE FACILITY
K1235
JUVENILE INSTITUTION
K1236
LOCAL JAIL OR DETENTION
CENTER
K1237
FEDERAL PENITENTIARY,
STATE PRISON, OR PRISON
FARM
K1238
OTHER CORRECTIONAL
INSTITUTION
K1239
K1246
K2110
CONVENT, MONASTERY,
RECTORY, OTHER
RELIGIOUS GROUP
QUARTERS
COMMUNITY CENTER
MILITARY INSTALLATION
K2165
GOVERNMENT CENTER
K2167
CONVENTION CENTER
K2180
PARK
K2181
NATIONAL PARK SERVICE
LAND
K2182
NATIONAL FOREST OR
OTHER FEDERAL LAND
FEATURE CLASS DESCRIPTION
TO SERVE AS A WATERWAY FOR WATERCRAFT.
[INCLUDES LATERAL]
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.
ONE OR MORE STRUCTURES WHERE THE SICK OR
INJURED MAY RECEIVE MEDICAL OR SURGICAL
ATTENTION. [INCLUDING INFIRMARY]
A FACILITY (CORRECTIONAL AND NONCORRECTIONAL) WHERE GROUPS OF JUVENILES
RESIDE; THIS INCLUDES TRAINING SCHOOLS,
DETENTION CENTERS, RESIDENTIAL TREATMENT
CENTERS AND ORPHANAGES.
ONE OR MORE STRUCTURES THAT SERVE AS A
PLACE FOR THE CONFINEMENT OF ADULT PERSONS
IN LAWFUL DETENTION, ADMINISTERED BY A LOCAL
(COUNTY, MUNICIPAL, ETC.) GOVERNMENT.
AN INSTITUTION THAT SERVES AS A PLACE FOR THE
CONFINEMENT OF ADULT PERSONS IN LAWFUL
DETENTION, ADMINISTERED BY THE FEDERAL
GOVERNMENT OR A STATE GOVERNMENT.
ONE OR MORE STRUCTURES THAT SERVE AS A
PLACE FOR THE CONFINEMENT OF ADULT PERSONS
IN LAWFUL DETENTION, NOT ELSEWHERE CLASSIFIED
OR ADMINISTERED BY A GOVERNMENT OF UNKNOWN
JURISDICTION.
ONE OR MORE STRUCTURES INTENDED FOR USE AS
A RESIDENCE FOR THOSE HAVING A RELIGIOUS
VOCATION.
COMMUNITY CENTER.
AN AREA OWNED AND/OR OCCUPIED BY THE
DEPARTMENT OF DEFENSE FOR USE BY A BRANCH
OF THE ARMED FORCES (SUCH AS THE ARMY, NAVY,
AIR FORCE, MARINES, OR COAST GUARD), OR A
STATE OWNED AREA FOR THE USE OF THE NATIONAL
GUARD.
A PLACE USED BY MEMBERS OF GOVERNMENT
(EITHER FEDERAL, STATE, LOCAL, OR TRIBAL) FOR
ADMINISTRATION AND PUBLIC BUSINESS.
AN EXHIBITION HALL OR CONFERENCE CENTER WITH
ENOUGH OPEN SPACE TO HOST PUBLIC AND PRIVATE
BUSINESS AND SOCIAL EVENTS.
PARKLAND DEFINED AND ADMINISTERED BY
FEDERAL, STATE, AND LOCAL GOVERNMENTS.
AREA—NATIONAL PARKS, NATIONAL MONUMENTS,
AND SO FORTH—UNDER THE JURISDICTION OF THE
NATIONAL PARK SERVICE.
LAND UNDER THE MANAGEMENT AND JURISDICTION
OF THE FEDERAL GOVERNMENT, SPECIFICALLY
INCLUDING AREAS DESIGNATED AS NATIONAL
FOREST, AND EXCLUDING AREAS UNDER THE
JURISDICTION OF THE NATIONAL PARK SERVICE.
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-7
MTFCC FEATURE CLASS
K2183
TRIBAL PARK, FOREST, OR
RECREATION AREA
K2184
STATE PARK, FOREST, OR
RECREATION AREA
K2185
REGIONAL PARK, FOREST,
OR RECREATION AREA
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 (QUASIPUBLIC, INDEPENDENT
PARK, COMMISSION, ETC.)
K2191
POST OFFICE
K2193
K2194
K2195
K2196
K2400
FIRE DEPARTMENT
POLICE STATION
LIBRARY
CITY/TOWN HALL
TRANSPORTATION
TERMINAL
K2424
MARINA
K2432
PIER/DOCK
FEATURE CLASS DESCRIPTION
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF AN
AMERICAN INDIAN TRIBE.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF A
STATE GOVERNMENT.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF A
REGIONAL GOVERNMENT.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF A
COUNTY GOVERNMENT.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF A
MINOR CIVIL DIVISION (TOWN/TOWNSHIP)
GOVERNMENT.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF A
MUNICIPAL GOVERNMENT.
A PRIVATELY OWNED PLACE OR AREA SET ASIDE FOR
RECREATION OR PRESERVATION OF A CULTURAL OR
NATURAL RESOURCE.
A PLACE OR AREA SET ASIDE FOR RECREATION OR
PRESERVATION OF A CULTURAL OR NATURAL
RESOURCE AND UNDER THE ADMINISTRATION OF
SOME OTHER TYPE OF GOVERNMENT OR AGENCY
SUCH AS AN INDEPENDENT PARK AUTHORITY OR
COMMISSION.
AN OFFICIAL FACILITY OF THE U.S. POSTAL SERVICE
USED FOR PROCESSING AND DISTRIBUTING MAIL AND
OTHER POSTAL MATERIAL.
FIRE DEPARTMENT.
POLICE STATION.
LIBRARY.
CITY/TOWN HALL.
A FACILITY WHERE ONE OR MORE MODES OF
TRANSPORTATION CAN BE ACCESSED BY PEOPLE OR
FOR THE SHIPMENT OF GOODS; EXAMPLES OF SUCH
A FACILITY INCLUDE MARINE TERMINAL, BUS
STATION, TRAIN STATION, AIRPORT AND TRUCK
WAREHOUSE.
A PLACE WHERE PRIVATELY OWNED, LIGHT-CRAFT
ARE MOORED.
A PLATFORM BUILT OUT FROM THE SHORE INTO THE
WATER AND SUPPORTED BY PILES. THIS PLATFORM
MAY PROVIDE ACCESS TO SHIPS AND BOATS, OR IT
MAY BE USED FOR RECREATIONAL PURPOSES.
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-8
MTFCC FEATURE CLASS
K2451
AIRPORT OR AIRFIELD
K2452
TRAIN STATION, TROLLEY
OR MASS TRANSIT RAIL
STATION
K2453
BUS TERMINAL
K2454
MARINE TERMINAL
K2455
SEAPLANE ANCHORAGE
K2456
AIRPORT—INTERMODAL
TRANSPORTATION
HUB/TERMINAL
K2457
AIRPORT—STATISTICAL
REPRESENTATION
K2458
PARK AND RIDE
FACILITY/PARKING LOT
K2459
RUNWAY/TAXIWAY
K2460
HELICOPTER LANDING PAD
K2540
UNIVERSITY OR COLLEGE
K2543
SCHOOL OR ACADEMY
K2545
K2561
K2582
MUSEUM, VISITOR CENTER,
CULTURAL CENTER, OR
TOURIST ATTRACTION
GOLF COURSE
CEMETERY
K2586
ZOO
K3544
PLACE OF WORSHIP
FEATURE CLASS DESCRIPTION
A MANMADE FACILITY MAINTAINED FOR THE USE OF
AIRCRAFT. [INCLUDING AIRSTRIP, LANDING FIELD AND
LANDING STRIP]
A PLACE WHERE TRAVELERS CAN BOARD AND EXIT
RAIL TRANSIT LINES, INCLUDING ASSOCIATED
TICKETING, FREIGHT, AND OTHER COMMERCIAL
OFFICES.
A PLACE WHERE TRAVELERS CAN BOARD AND EXIT
MASS MOTOR VEHICLE TRANSIT, INCLUDING
ASSOCIATED TICKETING, FREIGHT, AND OTHER
COMMERCIAL OFFICES.
A PLACE WHERE TRAVELERS CAN BOARD AND EXIT
WATER TRANSIT OR WHERE CARGO IS HANDLED,
INCLUDING ASSOCIATED TICKETING, FREIGHT, AND
OTHER COMMERCIAL OFFICES.
A PLACE WHERE AN AIRPLANE EQUIPPED WITH
FLOATS FOR LANDING ON OR TAKING OFF FROM A
BODY OF WATER CAN DEBARK AND LOAD.
A MAJOR AIR TRANSPORTATION FACILITY WHERE
TRAVELERS CAN BOARD AND EXIT AIRPLANES AND
CONNECT WITH OTHER (I.E. NON-AIR) MODES OF
TRANSPORTATION.
THE AREA OF AN AIRPORT ADJUSTED TO INCLUDE
WHOLE 2000 CENSUS BLOCKS USED FOR THE
DELINEATION OF URBAN AREAS
A PLACE WHERE MOTORISTS CAN PARK THEIR CARS
AND TRANSFER TO OTHER MODES OF
TRANSPORTATION.
A FAIRLY LEVEL AND USUALLY PAVED EXPANSE USED
BY AIRPLANES FOR TAKING OFF AND LANDING AT AN
AIRPORT.
A FAIRLY LEVEL AND USUALLY PAVED EXPANSE USED
BY HELICOPTERS FOR TAKING OFF AND LANDING.
A BUILDING OR GROUP OF BUILDINGS USED AS AN
INSTITUTION FOR POST-SECONDARY STUDY,
TEACHING, AND LEARNING. [INCLUDING SEMINARY]
A BUILDING OR GROUP OF BUILDINGS USED AS AN
INSTITUTION FOR PRESCHOOL, ELEMENTARY OR
SECONDARY STUDY, TEACHING, AND LEARNING.
[INCLUDING ELEMENTARY SCHOOL AND HIGH
SCHOOL]
AN ATTRACTION OF HISTORICAL, CULTURAL,
EDUCATIONAL OR OTHER INTEREST THAT PROVIDES
INFORMATION OR DISPLAYS ARTIFACTS.
A PLACE DESIGNED FOR PLAYING GOLF.
A PLACE OR AREA FOR BURYING THE DEAD.
[INCLUDING BURYING GROUND AND MEMORIAL
GARDEN]
A FACILITY IN WHICH TERRESTRIAL AND/OR MARINE
ANIMALS ARE CONFINED WITHIN ENCLOSURES AND
DISPLAYED TO THE PUBLIC FOR EDUCATIONAL,
PRESERVATION, AND RESEARCH PURPOSES.
A SANCTIFIED PLACE OR STRUCTURE WHERE
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-9
MTFCC FEATURE CLASS
L4010
PIPELINE
L4020
POWERLINE
L4031
AERIAL TRAMWAY/SKI LIFT
L4110
FENCE LINE
L4121
L4125
RIDGE LINE
CLIFF/ESCARPMENT
L4130
POINT-TO-POINT LINE
L4140
PROPERTY/PARCEL LINE
(INCLUDING PLSS)
L4150
COASTLINE
L4165
FERRY CROSSING
P0001
P0002
NONVISIBLE LINEAR
LEGAL/STATISTICAL
BOUNDARY
PERENNIAL SHORELINE
P0003
INTERMITTENT SHORELINE
P0004
OTHER NON-VISIBLE
BOUNDING EDGE (E.G.,
FEATURE CLASS DESCRIPTION
PEOPLE GATHER FOR RELIGIOUS WORSHIP;
EXAMPLES INCLUDE CHURCH, SYNAGOGUE, TEMPLE,
AND MOSQUE.
A LONG TUBULAR CONDUIT OR SERIES OF PIPES,
OFTEN UNDERGROUND, WITH PUMPS AND VALVES
FOR FLOW CONTROL, USED TO TRANSPORT FLUID
(E.G., CRUDE OIL, NATURAL GAS), ESPECIALLY OVER
GREAT DISTANCES.
ONE OR MORE WIRES, OFTEN ON ELEVATED
TOWERS, USED FOR CONDUCTING HIGH-VOLTAGE
ELECTRIC POWER.
A CONVEYANCE THAT TRANSPORTS PASSENGERS OR
FREIGHT IN CARRIERS SUSPENDED FROM CABLES
AND SUPPORTED BY A SERIES OF TOWERS.
A MAN-MADE BARRIER ENCLOSING OR BORDERING A
FIELD, YARD, ETC., USUALLY MADE OF POSTS AND
WIRE OR WOOD, USED TO PREVENT ENTRANCE, TO
CONFINE, OR TO MARK A BOUNDARY.
THE LINE OF HIGHEST ELEVATION ALONG A RIDGE.
VERY STEEP/VERTICAL SLOPE. [INCLUDING BLUFF,
CRAG, HEAD, HEADLAND, NOSE, PALISADES,
PRECIPICE, PROMONTORY, RIM AND RIMROCK]
A LINE DEFINED AS BEGINNING AT ONE LOCATION
POINT AND ENDING AT ANOTHER, BOTH OF WHICH
ARE IN SIGHT.
THIS FEATURE CLASS MAY DENOTE A NONVISIBLE
BOUNDARY OF EITHER PUBLIC OR PRIVATE LANDS
(E.G., A PARK BOUNDARY) OR IT MAY DENOTE A
PUBLIC LAND SURVEY SYSTEM OR EQUIVALENT
SURVEY LINE.
THE LINE THAT SEPARATES EITHER LAND OR INLAND
WATER FROM COASTAL, TERRITORIAL OR GREAT
LAKES WATER. WHERE LAND DIRECTLY BORDERS
COASTAL, TERRITORIAL OR GREAT LAKES WATER,
THE SHORELINE REPRESENTS THE COASTLINE.
WHERE INLAND WATER (SUCH AS A RIVER) FLOWS
INTO COASTAL, TERRITORIAL OR GREAT LAKES
WATER, THE CLOSURE LINE SEPARATING THE INLAND
WATER FROM THE OTHER CLASS OF WATER
REPRESENTS THE COASTLINE.
THE ROUTE USED TO CARRY OR CONVEY PEOPLE OR
CARGO BACK AND FORTH OVER A WATERBODY IN A
BOAT.
A LEGAL/STATISTICAL BOUNDARY LINE THAT DOES
NOT CORRESPOND TO A SHORELINE OR OTHER
VISIBLE FEATURE ON THE GROUND.
THE MORE-OR-LESS PERMANENT BOUNDARY
BETWEEN LAND AND WATER FOR A WATER FEATURE
THAT EXISTS YEAR-ROUND.
THE BOUNDARY BETWEEN LAND AND WATER (WHEN
WATER IS PRESENT) FOR A WATER FEATURE THAT
DOES NOT EXIST YEAR-ROUND.
A BOUNDING EDGE THAT DOES NOT REPRESENT A
LEGAL/STATISTICAL BOUNDARY, AND DOES NOT
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-10
MTFCC FEATURE CLASS
CENSUS WATER
BOUNDARY, BOUNDARY OF
AN AREA FEATURE)
R1011
RAILROAD FEATURE (MAIN,
SPUR, OR YARD)
R1051
CARLINE, STREETCAR
TRACK, MONORAIL, OTHER
MASS TRANSIT
R1052
R1052
S1100
PRIMARY ROAD
S1200
SECONDARY ROAD
S1400
LOCAL NEIGHBORHOOD
ROAD, RURAL ROAD, CITY
STREET
S1500
VEHICULAR TRAIL (4WD)
S1630
RAMP
S1640
SERVICE DRIVE USUALLY
FEATURE CLASS DESCRIPTION
CORRESPOND TO A SHORELINE OR OTHER VISIBLE
FEATURE ON THE GROUND. MANY SUCH EDGES
BOUND AREA LANDMARKS, WHILE MANY OTHERS
SEPARATE WATER FEATURES FROM EACH OTHER
(E.G., WHERE A BAY MEETS THE OCEAN).
A LINE OF FIXED RAILS OR TRACKS THAT CARRIES
MAINSTREAM RAILROAD TRAFFIC. SUCH A RAIL LINE
CAN BE A MAIN LINE OR SPUR LINE, OR PART OF A
RAIL YARD.
MASS TRANSIT RAIL LINES (INCLUDING LINES FOR
RAPID TRANSIT, MONORAILS, STREETCARS, LIGHT
RAIL, ETC.) THAT ARE TYPICALLY INACCESSIBLE TO
MAINSTREAM RAILROAD TRAFFIC AND WHOSE
TRACKS ARE NOT PART OF A ROAD RIGHT-OF-WAY.
SPECIAL PURPOSE RAIL LINE FOR CLIMBING STEEP
GRADES TYPICALLY INACCESSIBLE TO MAINSTREAM
RAILROAD TRAFFIC. NOTE THAT AERIAL TRAMWAYS
AND STREETCARS (WHICH MAY ALSO BE CALLED
“TRAMS”) ARE ACCOUNTED FOR BY OTHER MTFCCS
AND DO NOT BELONG IN R1052
PRIMARY ROADS ARE GENERALLY DIVIDED, LIMITEDACCESS HIGHWAYS WITHIN THE INTERSTATE
HIGHWAY SYSTEM OR UNDER STATE MANAGEMENT,
AND ARE DISTINGUISHED BY THE PRESENCE OF
INTERCHANGES. THESE HIGHWAYS ARE ACCESSIBLE
BY RAMPS AND MAY INCLUDE SOME TOLL HIGHWAYS.
SECONDARY ROADS ARE MAIN ARTERIES, USUALLY
IN THE U.S. HIGHWAY, STATE HIGHWAY OR COUNTY
HIGHWAY SYSTEM. THESE ROADS HAVE ONE OR
MORE LANES OF TRAFFIC IN EACH DIRECTION, MAY
OR MAY NOT BE DIVIDED, AND USUALLY HAVE ATGRADE INTERSECTIONS WITH MANY OTHER ROADS
AND DRIVEWAYS. THEY OFTEN HAVE BOTH A LOCAL
NAME AND A ROUTE NUMBER.
GENERALLY A PAVED NON-ARTERIAL STREET, ROAD,
OR BYWAY THAT USUALLY HAS A SINGLE LANE OF
TRAFFIC IN EACH DIRECTION. ROADS IN THIS
FEATURE CLASS MAY BE PRIVATELY OR PUBLICLY
MAINTAINED. SCENIC PARK ROADS WOULD BE
INCLUDED IN THIS FEATURE CLASS, AS WOULD
(DEPENDING ON THE REGION OF THE COUNTRY)
SOME UNPAVED ROADS.
UNPAVED DIRT TRAIL WHERE FOUR-WHEEL DRIVE
VEHICLES REQUIRED. THESE VEHICULAR TRAILS ARE
FOUND ALMOST EXCLUSIVELY IN VERY RURAL
AREAS. MINOR, UNPAVED ROADS USABLE BY
ORDINARY CARS AND TRUCKS BELONG IN THE S1400
CATEGORY.
A ROAD THAT ALLOWS CONTROLLED ACCESS FROM
ADJACENT ROADS ONTO A LIMITED ACCESS
HIGHWAY, OFTEN IN THE FORM OF A CLOVERLEAF
INTERCHANGE. THESE ROADS ARE UNADDRESSABLE
AND DO NOT CARRY A NAME IN MAF/TIGER.
A ROAD, USUALLY PARALLELING A LIMITED ACCESS
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-11
MTFCC FEATURE CLASS
ALONG A LIMITED ACCESS
HIGHWAY
S1710
WALKWAY/PEDESTRIAN
TRAIL
S1720
STAIRWAY
S1730
ALLEY
S1740
PRIVATE ROAD FOR
SERVICE VEHICLES
(LOGGING, OIL FIELDS,
RANCHES, ETC.)
INTERNAL U.S. CENSUS
BUREAU USE
PARKING LOT ROAD
S1750
S1780
S1820
S1830
S2000
FEATURE CLASS DESCRIPTION
HIGHWAY, THAT PROVIDES ACCESS TO STRUCTURES
ALONG THE HIGHWAY. THESE ROADS CAN BE NAMED
AND MAY INTERSECT WITH OTHER ROADS.
A PATH THAT IS USED FOR WALKING, BEING EITHER
TOO NARROW FOR OR LEGALLY RESTRICTED FROM
VEHICULAR TRAFFIC.
A PEDESTRIAN PASSAGEWAY FROM ONE LEVEL TO
ANOTHER BY A SERIES OF STEPS.
SERVICE ROAD THAT DOES NOT GENERALLY HAVE
ASSOCIATED ADDRESSED STRUCTURES, USUALLY
UNNAMED. IT IS LOCATED AT THE REAR OF
BUILDINGS AND PROPERTIES AND IS USED FOR
DELIVERIES.
A ROAD WITHIN PRIVATE PROPERTY, PRIVATELY
MAINTAINED FOR SERVICE, EXTRACTIVE, OTHER
PURPOSES. OFTEN UNNAMED.
INTERNAL U.S. CENSUS BUREAU USE.
MAIN TRAVEL ROUTE FOR VEHICLES THROUGH A
PAVED PARKING AREA.
BIKE PATH OR TRAIL
A PATH USED FOR MANUAL OR SMALL, MOTORIZED
BICYCLES, BEING EITHER TOO NARROW FOR OR
LEGALLY RESTRICTED FROM VEHICULAR TRAFFIC.
BRIDLE PATH
A PATH THAT IS USED FOR HORSES, BEING EITHER
TOO NARROW FOR OR LEGALLY RESTRICTED FROM
VEHICULAR TRAFFIC.
ROAD MEDIAN
THE UNPAVED AREA OR BARRIER BETWEEN THE
CARRIAGEWAYS OF A DIVIDED ROAD.
Table D-1: Select MTFCC Codes
Note: The information in this table was last updated in December 2015.
Boundary and Annexation Survey Respondent Guide: Tribal
Page D-12
| File Type | application/pdf |
| File Title | Boundary and Annexation Survey Tribal Respondent Guide: Digital |
| Author | U.S. Census Bureau |
| File Modified | 2015-12-16 |
| File Created | 2015-12-16 |