2010 Tribal Statistical Areas Program (TSAP)

TSAP MATERIALS

1. Sample 2010 TSAP Invitation Letter to Tribe
2. Sample 2010 TSAP Invitation Letter to State Liaison
3. TSAP ANVSA Participant Information Sheet
4. TSAP Participant Information Sheet
5. 2010 Census State Geographic Programs Participant Information Sheet
6. 2010 TSAP Cover Sheet
7. TSAP Guidelines for Digital Participants
8. Statistical Areas on Federal American Indian Reservations Paper Map Guidelines
9. Tribal Designated Statistical Areas Paper Map Guidelines
10. Oklahoma Tribal Statistical Areas Paper Map Guidelines
11. Alaska Native Village Statistical Areas Paper Map Guidelines
12. State Designated Statistical Area Paper Map Guidelines
13. State American Indian Reservation Paper Map Guidelines

Sample 2010 TSAP Invitation Letter
Sample Invitation Letter to Tribe:
FROM THE DIRECTOR
U.S. CENSUS BUREAU
REGIONAL CENSUS CENTER
Dear Tribal Chair:
On behalf of the U.S. Census Bureau, I invite your tribal government to work with us to
identify and delineate tribal census tracts, tribal block groups, and census designated
places (CDPs) for your American Indian Reservation (AIR) and/or off-reservation trust
lands (ORTLs) as part of our Tribal Statistical Areas Program (TSAP). The Census
Bureau will tabulate data from the 2010 Census for your statistical areas, and post-2010
we will tabulate data for the same areas from the American Community Survey (ACS).
In addition, you are also invited to suggest census block boundaries as part of our Block
Definition Program (BDP). Statistical data from the 2010 Census and the ACS can
provide your tribe with a meaningful tool to help make informed decisions and plan for
services such as education, health, and housing.
Your tribe is eligible to delineate tribal census tracts, tribal block groups, and CDPs, and
to suggest census block boundaries through the BDP. Your eligibility to delineate these
statistical areas is based upon population data from Census 2000 for people living on
your AIR and/or ORTL. In accordance with TSAP criteria, an AIR and/or ORTL must
have population equal to or greater than 2,400 to delineate more than one tribal census
tract and equal to or greater than 1,200 to delineate more than one tribal block group.
These population thresholds apply to all people on the AIR and/or ORTL – not just tribal
members – and do not include tribal members that live off the AIR and/or ORTL.
Statistical data for your tribe can be found on the Census Bureau’s American Factfinder
website (http://factfinder.census.gov). Proposed delineation criteria for these statistical
areas were published in the April 1, 2008 Federal Register Notice (http://www.census.
gov/geo/www/tsap2010/e8-6665.pdf).
While participation in the TSAP is voluntary, this program provides your tribe the
opportunity to use local knowledge to update and/or delineate your statistical areas (in
accordance with Census Bureau guidelines) for the 2010 Census. In late 2008, the
Census Bureau will send materials to participants and you will have the option of
updating and/or delineating your tribal statistical areas using either paper maps or Census
Bureau provided Geographic Information System tools and shapefiles. (ESRI ArcGIS
version 9.2 or higher is required for this application.) We will also provide you with
detailed guidelines and criteria regarding how to delineate these statistical areas, and
Census Bureau staff will be available to answer questions and lend assistance. You will
have 120 calendar days from the date you receive your TSAP materials to complete your
review and submit your tribal census tract, tribal block group, and CDP delineations, and
block boundary suggestions to the Census Bureau for processing. A final copy of your

updated boundaries will be made available to you in late calendar year 2009 and you will
then have the opportunity to verify boundaries and to discuss any changes made by the
Census Bureau with our Geography staff.
We request that you review and complete the attached TSAP participant information
sheet within two weeks. You may return the information sheet by mail using the postage
paid envelope provided, or by fax at the number below. You may also provide the
information by calling or e-mailing Census Bureau Geography staff at the telephone
number and e-mail address provided below. If you decline participation in the TSAP, the
update of your tribal statistical areas will default to Census Bureau staff who will conduct
the review and delineation for the 2010 Census.
Additional information about the 2010 TSAP is available at:
http://www.census.gov/geo/www/tsap2010/tsap2010.html
If you have any questions regarding the 2010 TSAP, please contact the Regional Census
Center by telephone at XXX-XXX-XXXX, by fax at XXX-XXX-XXXX, or via e-mail at
yourRCC_tsap@census.gov.
We look forward to working with you.
Sincerely,

###### ######
Regional Director
U.S. Census Bureau
Regional Census Center

Sample Invitation Letter to State Liaison:
Mr. Benjamin Moreira,
Planning and Economic Development Specialist
771 South Lawrence Street, Suite 106
Montgomery, Alabama 36130
Dear Mr. Moreira:
The Governor’s Office of Alabama has informed the U.S. Census Bureau that you will be our
liaison for the 2010 Census geographic programs for state-recognized American Indian tribes.
This letter serves both to invite you to participate in these important programs and to confirm that
the inventory of state and federal tribes in our database is correct.
Geographic programs for state-recognized tribes include the State Reservation Program (SRP)
and the Tribal Statistical Areas Program (TSAP). The SRP seeks to determine the current
inventory and legally defined boundaries of state American Indian Reservations. As part of
TSAP, you will have the opportunity to work with state-recognized tribes in Alabama that do not
have a reservation or trust lands in order to update or to define State Designated Tribal Statistical
Areas (SDTSAs). SDTSAs generally encompass a compact and contiguous area in which there is
structured or organized tribal activity and a concentration of individuals who identify with a
specific state-recognized American Indian tribe. (SDTSAs were called State Designated
American Indian Statistical Areas [SDAISAs] during Census 2000.) Proposed criteria for the
update or delineation of State Reservations and SDTSAs for the 2010 Census were published in
the April 1, 2008 Federal Register Notice (http://www.census.gov/geo/www/tsap2010/e86665.pdf). Your participation provides an opportunity to use local knowledge in the
update/delineation process.
The Census Bureau will tabulate statistical data from the 2010 Census for State Reservations and
SDTSAs, and post-2010 we will be tabulating data for the same areas from the American
Community Survey (ACS). Meaningful statistical data from the 2010 Census and the ACS can
provide both states and state-recognized tribes with a tool to help make informed decisions and
plan for services such as education, health, and housing.
Our records show that the state of Alabama has granted recognition to the tribes listed below.
State- recognized tribes that have reservations or that had SDTSAs delineated during Census
2000 are listed with the names of their reservations or statistical areas. Please review the list for
accuracy and return any updates or corrections on the 2010 Census State Geographic Programs
Participant Information Sheet attached.
State Recognized Tribes
MOWA Band of Choctaw Indians - MOWA Choctaw (state) Reservation
Cherokees of Southeast Alabama - Cherokees of Southeast Alabama SDAISA
Cherokee Tribe of Northeast Alabama - Cherokee Tribe of Northeast Alabama SDAISA
Echota Cherokee Tribe - Echota Cherokee SDAISA
MaChis Lower Creek Tribe - Machis Lower Creek SDAISA
Star Clan of Muscogee Creeks - Star Musckogee Creek SDAISA
Piqua Shawnee Tribe
United Cherokee Ani-Yun-Wiya Nation

Additionally, we are including below a list of tribes in Alabama that have been recognized by the
federal government. While the Census Bureau works directly with federally recognized tribes,
we ask that you review the list for accuracy and note any corrections in the appropriate space on
the Participant Information Sheet.
Federal Tribes
Poarch Band of Creek Indians - Poarch Creek Reservation
In late 2008, the Census Bureau will send you all of the materials needed for updating and/or
delineating state-recognized tribal boundaries using either paper maps or Census Bureau provided
Geographic Information System tools and shapefiles. (ESRI ArcGIS version 9.2 or higher is
required for this ESRI ArcGIS extension.) You will also be provided with detailed guidelines and
criteria regarding how to report state reservation boundaries and update or delineate SDTSAs.
Census Bureau staff will be available to answer questions and lend assistance as needed. We
encourage you to work with the tribes in your state to optimize the results for all stakeholders and
data users.
You will have 120 calendar days from the date you receive the materials to complete your review
and submit your delineations and/or updates to the Census Bureau for processing. A final copy of
your updated boundaries will be made available to you in late 2009. You will have the
opportunity to verify the boundaries and discuss any changes that may have been made by the
Census Bureau with our Geography Staff.
We request that you complete the 2010 Census State Geographic Programs Participant
Information Sheet within two weeks of receipt. You may return the Information Sheet by mail
using the postage paid envelope provided, or by fax at the number below. You may also provide
the required information by calling or e-mailing the Census Bureau Geography staff at the
telephone number and e-mail address provided below.
Additional information regarding the 2010 TSAP program is available at:
http://www.census.gov/geo/www/tsap2010/tsap2010.html
If you have any questions regarding the 2010 State Reservation or SDTSA Programs, please
contact the Atlanta Regional Census Center by telephone at 404-332-2721, by fax at , or via email at donna.bullock@census.gov.
We look forward to working with you.
Sincerely,

George Grandy Jr.
Regional Director
U.S. Census Bureau
Atlanta Regional Census Center

OMB No. 0607-0795: Approval Expires 3/31/09

TSAP ANVSA Participant Information Sheet
1. Village Name: _________________________________________________
2. Person Completing this Form:______________________________________
3. Do you want to participate in the 2010 ANVSA program? Y______
N ______ (If you do not plan to participate,
please sign the bottom line of this form and return it so that we may be notified of your intention.)
4. In the table below please provide contact information for any known technical participants. If you will perform the actual
review and update, indicate “Same” under Technical Participant #1.
ANVSA Primary Participant

Technical Participant #1

Technical Participant #2

Title
First Name
Middle Initial
Last Name
Name Suffix
Professional Suffix
Position
Department Name
Address (Street)
City
State
ZIP+4
Phone
FAX
Email

5. Are you interested in 2010 TSAP specific training provided by the Census Bureau?

Y______

N ______

6. Do you intend to use paper maps and/or the ESRI ArcGIS extension tool to conduct your review and update? Both paper
maps and the extension tool will be provided to you regardless of your choice.
Paper Maps______

ESRI ArcGIS extension (requires version 9.2)______

7. Do you have high-speed internet access? Y______

N ______

8. Signature: _________________________________________________ Date: _______________
Return this information sheet by mail, using the enclosed self-addressed postage paid envelope, or by fax to the Regional
Census Center, within two weeks of receipt. This will be your official confirmation of participation in the 2010 TSAP. You
may contact the Regional Census Center by telephone at 425-908-3010, by fax at 425-318-1424, or via e-mail to
yourRCC_tsap@census.gov.

OMB No. 0607-0795: Approval Expires 3/31/09

TSAP Participant Information Sheet
1. Tribe Name: _________________________________________________
2. Person Completing this Form:______________________________________
3. Do you want to participate in the 2010 TSAP?
Y______
N ______ (If you do not plan to participate, please
sign the bottom line of this form and return it so that we may be notified of your intention.)
4. In the table below please provide contact information for any known technical participants. If you will perform the actual
review and update, indicate “Same” under Technical Participant #1.
TSAP Primary Participant

Technical Participant #1

Technical Participant #2

Title
First Name
Middle Initial
Last Name
Name Suffix
Professional Suffix
Position
Department Name
Address (Street)
City
State
ZIP+4
Phone
FAX
Email

5. Are you interested in 2010 TSAP specific training provided by the Census Bureau?

Y______

N ______

6. Do you intend to use paper maps or the ESRI ArcGIS extension tool to conduct your review and update?
Paper Maps______

ESRI ArcGIS extension (requires version 9.2)______

7. Do you have high-speed internet access? Y______

N ______

8. Signature: _________________________________________________ Date: _______________
Return this information sheet by mail, using the enclosed self-addressed postage paid envelope, or by fax to the Regional
Census Center, within two weeks of receipt. This will be your official confirmation of participation in the 2010 TSAP. You
may contact the Regional Census Center by telephone at XXX-XXX-XXXX, by fax at XXX-XXX-XXXX, or via e-mail to
yourRCC_tsap@census.gov.

OMB No. 0607-0795: Approval Expires 3/31/09

Attachment
2010 Census State Geographic Programs
Participant Information Sheet
Please provide contact information for the State Liaison for Geographic Programs in the table below. In
addition, provide the contact information for any known technical persons that will be assisting with the
review and delineation of State Reservations and SDTSAs. If you will perform the actual review and
update, indicate “Same” in the TSAP Technical Participant column. Please make copies of this sheet to list
any additional technical participants.

SDTSA/SRP Liaison
Title
First Name
Middle Initial
Last Name

«Title»
«First_Name»
«MI»
«Last_Name»

Name Suffix

«N_suffix»

Professional Suffix

«P_Suffix»

Position
Department Name
Address (Street)

«Position»
«Dept»
«Address»

City

«City»

State

«State1»

ZIP+4

«Zip»

Phone

«liaison_phone»

FAX
Email

«liaison_fax»
«liaison_email»

SDTSA/SRP Technical Participant

OMB No. 0607-0795: Approval Expires 3/31/09

1. Corrections or Updates to State Recognized Tribes:
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________

____________________________________
____________________________________
____________________________________
____________________________________
____________________________________

2. Corrections or Updates to Federally Recognized Tribes:
____________________________________
____________________________________
____________________________________
____________________________________
____________________________________

____________________________________
____________________________________
____________________________________
____________________________________
____________________________________

3. Are you interested in 2010 TSAP specific training provided by the Census Bureau?
Y______

N ______

4. Do you intend to use paper maps or the ESRI ArcGIS extension tool to conduct your review and
update?
Paper Maps______

ESRI ArcGIS extension (requires version 9.2)______

5. Do you have high-speed internet access?

Y______

N ______

6. Person Completing this Form (print name):
_______________________________________________
Return this information sheet by mail, using the enclosed self-addressed postage paid envelope, or by fax to
the Regional Census Center, within two weeks of receipt. You may contact the Regional Census Center by
telephone at «phone», by fax «fax», or via e-mail to «email».

OMB No. 0607-0795: Approval Expires 03/31/09

Introduction to the Tribal Statistical Area Program materials
The U.S. Census Bureau would like to thank your tribal government for considering participation
in the Tribal Statistical Areas Program (TSAP), a geographic program conducted prior to the
2010 Census. As noted in the invitation letter you should have received earlier this fall, through
the TSAP your tribe is eligible to delineate and/or update tribal census tracts, tribal block groups,
and census designated places, and to suggest census block boundaries through the block
definition project. Because you indicated an interest in the program or we did not receive a
response, we have enclosed the materials to accomplish your statistical area delineations. If you
do not wish to participate or if you have no changes to your tribal statistical areas, please fill out
and return the form below to the Census Bureau’s Regional Census Center (RCC) by mail with
the enclosed self addressed stamped envelope or by fax (XXX-XXX-XXXX).
You have the option of using paper maps or an ESRI® ArcMap™ GIS (version 9.2 or 9.3)
software extension to accomplish your delineation work and the materials and guidelines for each
option are enclosed with this letter. Participants using paper maps may return their submission
with the attached Business Reply Mail label that will cover the return mailing costs. The ESRI
ArcMap GIS software extension, in the form of an executable installation file and geospatial data
(in shapefile format) are found on an enclosed CD. Also on the CD are the Guidelines for Digital
Submission (a pdf document) which includes software installation instructions, descriptions of the
tools included with the extension, and guidance in the delineation of your eligible statistical areas.
Participants choosing digital submission will use the internet to upload their digital delineations.
From the date you receive this package, you will have 120 calendar days to complete either a
paper map or digital GIS submission for your tribal statistical areas. At any point in the process
please do not hesitate to contact ###staff name contact### at the RCC for additional guidance,
help, or any questions regarding your delineation project work. The U.S. Census Bureau looks
forward to working with you to delineate your 2010 Census tribal statistical areas.
--------------------------------------------------------------------------------------------------------------------PLEASE CUT ALONG THE DOTTED LINE ABOVE AND RETURN TO YOUR REGIONAL CENSUS CENTER

PLEASE INFORM THE U.S. CENSUS BUREAU IF THERE ARE NO CHANGES NECESSARY
TO YOUR STATISTICAL AREA(S) OR YOUR TRIBAL GOVERNMENT DOES NOT INTEND TO
PARTICIPATE IN THE 2010 CENSUS TSAP.
Check the appropriate box:
[]

No changes to our tribal statistical area(s).

[]

Our tribe does not intend to participate in the 2010 Census TSAP.

Tribe Name: _____________________________________________________________
Date: ___________________________________________________________________
Signature: _______________________________________________________________

2010 Census Tribal Statistical Areas Program

Guidelines for Digital Participants

Version 1
January 2009

Table of Contents
1.0

Introduction
1.1 About the TSAP ESRI® ArcGIS® ArcMap™ (version 9.2) Extension
1.2 Schedule
1.3 The Boundary and Annexation Survey
1.4 Important Information on Features
1.5 Boundary Feature Updates
1.6 Criteria

2.0

Delineation Eligibility of American Indian and Alaska Native Areas

3.0

Installation
3.1 Enabling the Extension in ArcMap

4.0

Starting a project
4.1 Overview of the Extension’s Tools and Commands

5.0

Delineating your statistical area
5.1 Tribal census tracts
5.2 Tribal block groups
5.3 Census designated places (CDPs)
5.4 Alaska Native village statistical areas (ANVSAs)
5.5 Oklahoma Tribal Statistical Area (OTSA) tribal subdivisions
5.6 Tribal designated statistical areas (TDSAs)
5.7 State designated tribal statistical areas (SDTSAs)
5.8 State American Indian reservations

6.0

Using the Extension
6.1 TSAP Geography Manager
6.2 Workflow manager
6.3 Working with Census blocks
6.4 Assigning and unassigning geography to and from your area
6.5 Splitting tracts and block groups by block selections
6.6 Splitting blocks with existing line features
6.7 Splitting blocks with new line features
6.8 Line attributes tool
6.9 Merging tracts and block groups
6.10 Updating type attributes for tracts and block groups

7.0

Block boundary definition

8.0

Quality Control and Name Changes

9.0

Submitting your data
9.1 Compressing files for submittal
9.2 Transferring files to Census Bureau

10.0

Verification

Appendices
1. American Indian and Alaska Native Tribe and Eligibility Listings
2. Justifications for Unmet Criteria and Thresholds
3. Glossary of Terms
4. List of Shapefiles Included on the TSAP CD
5. Regional Census Centers Contact List

3

OMB No. 0607-0795: Approval Expires 03/31/09

1.0 Introduction
The U.S. Census Bureau is the premier source of information about the American people and the
economy. The U.S. Constitution mandates that a census be taken every 10 years in order to reapportion
the House of Representatives. The data gathered by the decennial census and other Census Bureau
programs are used for several other purposes, including the allocation and distribution of funds to state,
local and tribal governments. Census information shapes important policy decisions that in turn shape
the nation’s social and economic conditions. While best known for the decennial census, the Census
Bureau conducts numerous surveys and censuses that measure changing individual and household
demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need. Many tribal
communities use census information to attract new business and plan for growth. In fact, many tribes
and tribal organizations use census data to plan new facilities and programs for the communities they
serve.
The Tribal Statistical Areas Program (TSAP) is part of an ongoing effort to enhance the reporting of
meaningful statistical data for American Indian and Alaska Native areas. Through this program tribes
have the opportunity to identify and delineate the statistical areas and block boundaries from which the
Census Bureau will tabulate data for the 2010 Census and the subsequently occurring American
Community Survey (ACS). Meaningful statistical data from the 2010 Census and the ACS can provide
tribes and other data users with tools to help make informed decisions, and plan for services such as
education, transportation, health, and housing.
Tribes and states should strongly consider participating in the TSAP for the 2010 Census. The program
offers federally recognized tribes and designated state officials for state-recognized tribes greater control
and improved flexibility to identify and propose changes to the boundaries of American Indian and
Alaska Native statistical areas. Nonetheless, participation in the TSAP is voluntary. If your tribe or
state chooses not to participate, the Census Bureau may revise the boundary of an existing area or
delineate a new area in accordance with published criteria and guidelines. TSAP includes the following
statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts and tribal block groups – on American Indian reservations (AIRs) and/or offreservation trust lands (ORTLs)
census designated places (CDPs)

In preparation for Census 2010, the Census Bureau also has developed the State Reservation Program
(SRP). The SRP occurs once before each decennial census, and is a survey of state AIRs for those states
with state-recognized tribes that are not also federally recognized. Its purpose is to determine, solely for
data collection and tabulation by the Census Bureau, the complete and current inventory and the correct
attributes (names, legal descriptions, official status) and official, legal boundaries of the state AIRs in
each state. Through the State Reservation Program, the Census Bureau also accepts additions and

updates to features such as roads or rivers that serve as a boundary for the state AIR, as well as address
range break information at the boundaries.
More information about the background and components of these geographic areas as well as the
delineation update criteria and guidelines can be found in the Federal Register notices for American
Indian Areas (Vol. 73, No. 221, Friday, November 14, 2008, p. 67470) and Alaska Native Areas (Vol.
73, No. 214, Tuesday, November 4, 2008, p. 65572). These notices may be accessed from our TSAP
webpage at http://www.census.gov/geo/www/tsap2010/tsap2010.html. Copies are also included on the
enclosed CD.
The instructions provided in this document will guide participants through the computer based
Geographic Information Systems (GIS) mapping process using ESRI® ArcGIS® ArcMap™ software
(version 9.2 or 9.3) and the Census Bureau’s TSAP Extension for ArcMap. Following this background
and information section, an explanation of delineation eligibility and the installation instructions are
presented. Directions for starting a TSAP project and delineating tribal statistical areas are then
described offering specific criteria and guidelines for each particular area type. This is followed with a
detailed presentation using the TSAP Extension’s Tools. The guidelines conclude with a review of the
quality control and submission processes.
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries, addresses, and
geographic entities in the Master Address File / Topologically Integrated Geographic Encoding and
Referencing System (MAF/TIGER) database (MTdb) that is used to support programs and to conduct
the census and surveys. The TSAP program was developed to give tribes the opportunity to review and
update, if necessary, statistical tribal entities for use in tabulating and publishing data from the 2010
Census, the American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours per
respondent, including time for reviewing instructions, assembling materials, organizing and reviewing
the information, and reporting any needed changes. We anticipate that an estimated 650 participants will
respond. Remaining entities may be worked by Census Bureau regional staff. For larger areas or areas
with many changes, however, the respondent burden may be 180 hours or longer to complete. Please
send comments regarding this burden estimate or any other aspect of this collection of information,
including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 0607-0795” as the
subject.
Responses to this survey are voluntary. The authority for conducting these activities is covered under the
legal authority of Title 13 U.S.C. Sections 141 and 193.

5

No agency may conduct and no person may be required to respond to a collection of information unless
it displays a valid Office of Management and Budget (OMB) approval number. The OMB approval
number for this information collection is 0607-0795.

1.1 About the TSAP ESRI® ArcGIS® ArcMap™ (version 9.2 or 9.3) Extension
The Census Bureau has developed a TSAP Extension for ESRI’s ArcMap version 9.2 or 9.3 that
provides a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data submission, and
workflow administration are all included in the data management features of the extension. In addition
to the inherent functionality of the ArcGIS software, the extension’s unique editing tools consist of
geographic area assignment, block boundary definition, tribal tract/tribal block group type attribution, as
well as line editing and polygon split/merge functions.
Essential Census geographic datasets, used in the review and delineation of your areas, are provided
with the extension on CD. These geographic datasets will be used to create the workspace for your
delineation and review tasks (as explained in the Starting a Project section). Additional GIS data such
as imagery, can be added to your project using ArcMap’s standard Add Data command button and other
tools.
In addition to digital submission, the TSAP offers participants the option of using paper maps to
delineate their tribal statistical areas. Paper map participants draw their delineations by hand directly
upon maps and return their paper map submission by postal mail to the Regional Census Center (RCC)
using a prepaid Business Reply Mail label. If you would prefer to accomplish your delineations with the
paper map option and did not receive paper map materials and guidelines please contact the RCC.
1.2 Schedule
In October 2008, the Census Bureau mailed formal invitation letters to tribal officials eligible to
delineate tribal statistical areas. These guidelines accompany the delineation materials required to
complete the work are scheduled to arrive in January 2009. Tribes have 120 days from the date they
receive these materials to review and submit their tribal statistical area delineations or updates to the
Census Bureau’s RCCs. In late 2009/early 2010, after the Census Bureau has reviewed and
incorporated your statistical areas into our geographic database, you will receive new maps or digital
files so that you can verify that we have inserted your boundaries correctly. If you have questions
regarding your delineation or submission, assistance will be available from geographers at your RCC
(see Appendix 5 for contact information).
1.3 The Boundary and Annexation Survey
The Boundary and Annexation Survey (BAS) is an annual Census Bureau survey of legal geographic
entities that includes federal AIRs, ORTLs, and any associated tribal subdivisions. Whereas the TSAP
provides the process for reviewing and updating those AIAs that are statistical geographic entities (tribal
census tracts, tribal block groups, and census designated places), the BAS provides the process for

6

reviewing and updating AIAs that are legal federal geographic entities, such as the reservation itself,
tribal subdivisions and ORTLs. Its purpose is to determine, solely for data collection and tabulation by
the Census Bureau, the complete and current inventory and the correct names, legal descriptions, official
status, and official, legal boundaries of the legal geographic entities with governmental authority over
certain areas within the United States, as of January 1 of the survey year. The BAS also collects specific
information to document the legal actions that established a boundary or imposed a boundary change. In
support of the government-to-government relationship with federally recognized American Indian tribes,
the Census Bureau works directly with tribal officials on the BAS. Through the BAS, the Census
Bureau also accepts updates to features such as roads or rivers, and address range break information at
the boundaries. If you wish to update boundaries for you reservation, off-reservation trust lands or legal
tribal subdivisions, you should do so through the BAS.
For more information about the BAS, contact your RCC or see the Census Bureau's Web
site at http://www.census.gov/geo/www/bas/bashome.html. The BAS Respondent
Guide for federally recognized tribes is available at:
http://www.census.gov/geo/www/bas/bas09/bas09_mat_aia.html
1.4 Important Information on Features
Feature boundaries of statistical areas should follow specified legal or administrative boundaries that do
not change greatly over time, or permanent, visible features, such as roads, perennial streams, railroads,
and high-tension power lines. Permanent visible features should be easily locatable in the field by
Census Bureau staff without ambiguity. The acceptable visible boundary features are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (Main)
carline, streetcar track, monorail, other mass transit rail
interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county highway, secondary
and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
fencelines

7

Data user and Census Bureau experience has shown that some features make better boundaries than
others, and the same type of feature can make an excellent boundary in one place and a poor one in
another. Rivers, major canals, lakes, and other bodies of water often make good statistical area
boundaries because they generally limit access from one area to another and rarely change relative
location. Other features that limit access between areas, such as interstate and other major highways,
railroad tracks, and the ridges of mountain ranges, also make good statistical area boundaries. In some
instances, however, such a feature unifies a community, for example, a lake forming the core of a
recreational housing development or a through street forming the spine of a subdivision. In these
circumstances, the statistical area boundary should include the entire area of the lake or both sides of a
unifying street to better encompass similar community patterns.
In general, when delineating boundaries in bodies of water represented as polygons and having area
(lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow a line bisecting the water
body rather than following a shoreline. Wherever possible, use an existing line in water (for example, a
county line in the middle of a river) rather than adding a new line.
Tribal officials delineating tribal statistical areas may only add nonvisible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and ridgelines, are not
available and they aid in a tribal statistical area meeting other specific delineations criteria and/or
guidelines. The Census Bureau staff will contact you if they require more information or have questions
about feature updates submitted as part of the 2010 TSAP.
1.5 Boundary Feature Updates
The Census Bureau has spent the last six years enhancing the spatial accuracy of the roads in our
database system. The local files used during this project were required to have an overall average
accuracy of 7.6 meters while some files had better accuracy.
Although much of the street network is vastly improved, as you work with our shapefiles you may
notice that in some counties the street and boundary features look distorted. A line that should be
straight may have a noticeable kink or pointed shape. The Census Bureau is working to correct these
problems, and if you need to use a feature that is distorted in our shapefiles follow the guidelines below.
The Census Bureau is also now moving forward with our 2010 Census field canvassing and collection
activities. This means that we are no longer processing realignments to our street network. What is
critical for the success of the 2010 Census data tabulation is the location of roads relative to the
tabulation entity boundary. As long as the road is within the correct entity, the population and housing
will be properly reported. The guidelines below explain what updates are acceptable as part of the
TSAP.
It is critical that participants understand that the TSAP is not intended for street feature updates except
where a boundary follows a road (or other visible feature such as a stream) and the road is not reflected
in our file. For this reason the Census Bureau can not accept street (or other) feature updates that do not
follow the guidelines below:
Guidelines for Updating Features

8

1. If a road is missing and it forms the boundary for the area you are defining, add the road and
provide the name.
2. If you can not correctly delineate the boundary for an entity you are updating because the feature
you need to follow is incorrectly located, mislabeled or distorted in the Census Bureau’s file, we
request that you use the problematic boundary and report the existence of the identified
problematic boundary feature(s). The problematic boundary may be reported to the Census
Bureau through the RCC (contact information is contained in Appendix 5). The Census Bureau
will then correct the feature and adjust your delineation accordingly.
3. Do not add streets that are missing for an entire housing development (add only streets that are
needed to form a boundary). We will be adding new or missing streets during our address
canvassing operation which will occur in the spring and early summer of 2009. The Census
Bureau will provide verification materials to each participant that returns their submission in the
correct format and within the allotted 120 days that will show the results of address canvassing.
If these streets are still missing at that time, we will accept these as adds.
4. When adding a boundary that is within 30 feet (10 meters) of an existing line in the Census
Bureau’s shapefile do not add an additional line. Instead use the existing line features wherever
possible.
1.6 Criteria
All American Indian Areas (AIAs) must follow a standard set of criteria that support a shared purpose of
providing a meaningful and relevant geographic framework for tabulating data for the Census. It is the
responsibility of the Census Bureau to ensure that geographic entity criteria can achieve the goal of
providing meaningful, relevant, and reliable statistical data, and that the final criteria for geographic
entities are met. While aware that there are secondary uses of geographic entities and the data tabulated
for them, the Census Bureau will not modify their boundaries or attributes specifically to meet these
secondary uses, including those of other government agencies. If a change is made to a geographic
entity to meet one specific purpose, it may be detrimental for other programs that also use these entities.
The Census Bureau will use the criteria and guidelines to help ensure that tribal statistical areas
delineated for the 2010 Census, support the intended purpose of the program, provide useful and
meaningful data for the tribe they represent, and enhance the ability for data users to make more
meaningful comparisons between data.
Criteria are rules that must be followed by all officials delineating statistical AIAs for the 2010 Census,
while guidelines are suggestions for improving the relevance and utility of statistical AIAs. Criteria and
guidelines for specific tribal statistical area entities are explained in section 5.0 Delineating your
statistical area.

2.0 Delineation Eligibility of American Indian and Alaska Native Areas
American Indian tribes and Alaska Native villages reside in a diverse landscape of legal, cultural, social,
and historical contexts. This diversity has resulted in an equally varied identification of geographic
boundaries and statistical areas for American Indian and Alaska Native areas (AIANAs). For the 2010
Census, the TSAP offers the opportunity to delineate the following AIANAs: tribal census tracts, tribal
block groups, census designated places (CDPs), Oklahoma tribal statistical areas (OTSAs), OTSA tribal
subdivisions, tribal designated statistical areas (TDSAs), state designated tribal statistical areas

9

(SDTSAs), State recognized American Indian Reservations (SAIRs), and Alaska Native village
statistical areas (ANVSAs). Federally recognized tribes with American Indian reservations (AIRs)
and/or off-reservation trust lands (ORTLs) are eligible to suggest 2010 Census tabulation block
boundaries through the Block Definition Project (BDP). The eligibility of a tribe to delineate a
particular AIANA is expressed in Table 1. In addition, a list of all TSAP eligible tribes and the AIANA
types that they are eligible to delineate is presented in Tables A-D of Appendix 1 (Table A. Federally
Recognized Tribes, Table B. Alaska Native villages, Table C. Federally Recognized Tribes in Oklahoma
with a former American Indian reservation in Oklahoma, Table D. State Recognized Tribes).
Table 1. AIANAs Delineation Eligibility
Tribal Participant

Geographic Areas Eligible for Delineation

Federally recognized tribe¹ (AIA population >= 2,400 or HU >= 960)

Tribal Census Tract, Tribal Block Group, CDP, BDP

Federally recognized tribe¹ (AIA population >= 1,200 and < 2,400 or
HU >=480 and <960)
Federally recognized tribe¹ (AIA population < 1,200 or HU < 480)

Tribal Census Tract², Tribal Block Group, CDP, BDP

Federally recognized tribe in Oklahoma with former AIR in Oklahoma

CDP, OTSA, OTSA Tribal Subdivision³

Federally recognized tribe without AIR or ORTL

TDSA

Alaska Native village (federally or ANCSA recognized)

ANVSA

State recognized tribe with an AIR or ORTL

State recognized American Indian Reservation

State recognized tribe without an AIR or ORTL

SDTSA

Tribal Census Tract², Tribal Block Group², CDP, BDP

¹ with an American Indian reservation (AIR) and/or off reservation trust lands (ORTL).
² only one entity coinciding to the same area as the AIR and/or ORTL will be delineated.
³ The boundaries for tribal subdivisions on AIRs and ORTLs, and well as the outer boundaries for AIRs and ORTLs, are collected via the Census
Bureau’s annual Boundary and Annexation Survey (BAS).
Acronyms AIR: American Indian Reservation; ANCSA: Alaska Native Claims Settlement Act; ANVSA: Alaska Native village statistical area;
BDP: Block Definition Project; CDP: Census designated place; HU: housing units; ORTL: Off-reservation trust land; OTSA: Oklahoma Tribal
Statistical Area; SDTSA: State Designated Tribal Statistical Area; TDSA: Tribal Designated Statistical Area

If you believe the population or housing unit (HU) count for your AIR and/or ORTL now meet
population or housing unit thresholds changing your eligibility status, despite the 2000 Census counts,
please contact your Regional Census Center (RCC). Appendix 5 includes RCC contact information.
Appendix 1 provides the 2000 Census housing unit counts and population as well as the RCC name.

10

3.0 Installation of TSAP ArcGIS Extension
Installation Requirements
Operating System: Windows XP (preferred) or Windows Vista
Hardware: CD disk drive
GIS Software: ESRI ArcGIS ArcMap (version 9.2 or 9.3)
Local disk space: The extension itself will require 230 MB of local disk space. Additional space is
required for the area data files.
Installation Directions
Insert the enclosed CD into your computer’s CD drive. If the setup process does not automatically
initiate, navigate to the CD, locate the Setup.exe file and double click it to begin the installation. When
prompted, select a location on your local hard drive where you will want to store the extension (the
default location is C:\Program Files\U.S. Department of Commerce\TSAP Extension).
After the TSAP Extension installation is complete you will be prompted to copy the spatial data for your
area to a local directory on your computer. A list of the spatial data files included with the TSAP
Extension is included in Appendix 4.
3.1 Enabling the Extension in ArcMap
1. Open ArcMap
2. Enable the TSAP Extensions by selecting the Tools drop down menu and navigating to Extensions…

11

After the Extensions window pops-up check on the TSAP Extension.

3. Add the TSAP toolbars to the ArcMap interface by selecting the View drop down menu, navigating to
Toolbars, scrolling down the Toolbar fly-out window and then checking on the following three toolbars:
TSAP Management, TSAP Tools, and Census Editing Tools (you will need to check each one separately).

12

As each new toolbar is selected, it will appear in your ArcMap interface. When all three toolbars have
been added, your ArcMap window should appear similar to the image below.

13

4.0 Starting a Project
1. New TSAP projects are started and existing projects opened by clicking on the Show Project
found on the TSAP Management toolbar. This begins the process of
Manager command button
establishing a workspace that will contain the files necessary for the review and delineation of your
statistical areas. TSAP projects can only be started and reopened with the Show Project Manager
command button. ArcMap’s standard Open Project command should not be used when working with a
TSAP project.
2. After clicking the Show Project Manager command button, the TSAP Workspace Creation window
appears. Select New Project and click the Next button. The following window will prompt you to enter
the location of your Data Folder. This is the folder where the data from the TSAP CD was placed during
the installation and setup process. Click the Browse button to navigate to the Data Folder. (The Data
Folder must be stored on a local directory with write access).

3. Once your Data Folder is located, the directory path will be displayed in the window similar to the
example below. To continue and create your workspace, click the New button.

14

As the workspace is being created and essential files are assembled a message window will be displayed.
This process could take several minutes or longer depending upon the size of the files for your project’s
geographic area.

After the workspace has been created, you will be prompted with a message box as shown below. We
suggest that you always start with existing boundaries, therefore always answer yes.

Your new project workspace will appear similar to the example image below.

15

4.1 Overview of the TSAP Extension’s tools and commands
These tools will be explained in greater detail throughout the guidelines.

TSAP Management Toolbar

The TSAP Management toolbar includes all of the administrative functionality
needed from project inception to the submittal of your final output shapefiles.
Show Project Manager (opens new and existing projects)
Quality control of your edited statistical areas
Submits your final output shapefiles to a local directory
Show/Hide TSAP Geography Manager
Show/Hide Workflow Manager
Toggle block symbology (toggle to/from AIAN percent population by block)
Show TSAP Extension guidelines
Zoom to entity

TSAP Tools

The TSAP Tools toolbar includes commands and tools necessary for updating
polygon area features (e.g. tribal tracts, tribal block groups, CDPs, etc.).
Assign geography (e.g. add area to your tract)
Unassign geography (e.g. remove area from your tract)
Block Boundary Definition Tool
Tract/Block Group type tool
Merge tool (used to merge tracts and block groups)
Split tool (used to split tracts and block groups by a block selection)
Find Noncontiguous Areas
Find block groups split by tribal tracts
Find unassigned areas

16

Census Editing Tools

The Census Editing Tools toolbar is specifically used for line editing tasks. Line
editing will be used when drawing new boundary lines as well as selecting
existing line features to split census blocks, and statistical areas.
Pull down menu to start and end line editing tasks.
Sketch tool
Edit feature selection tool
Select target layer pull down (this will only be
visible in the Census Editing Tools if the standard Editor toolbar is not already
added)
Line attributes tool
Feature selection tool
Split block tool

17

5.0 Delineating your statistical area
General Guidance
The TSAP extension is designed to assist participants with the review and delineation of the American
Indian and Alaska Native areas (AIANAs) included in the 2010 Census TSAP. The eligibility to
delineate specific AIANAs was presented in section 2 of this document and may also be found for your
tribe in Tables A-D of Appendix 1 (Table A. Federally Recognized Tribes, Table B. Alaska Native
villages, Table C. Federally Recognized Tribes in Oklahoma with a former American Indian reservation
in Oklahoma, Table D. State Recognized Tribes). This section is intended to offer guidance in the
delineation process for each type of AIANA through an introduction, example delineation scenario, and
the listing of specific criteria and guidelines. In the AIANA list below please refer to the italicized
section listings and page forward for guidance in the delineation of your tribal statistical area.
AIANAs to be reviewed and updated include:
•
•
•
•
•
•
•
•

Tribal census tracts Section 5.1
Tribal block groups Section 5.2
Census designated places (CDPs) Section 5.3
Alaska Native village statistical areas (ANVSAs) Section 5.4
Oklahoma tribal statistical areas (OTSAs) and OTSA tribal subdivisions Section 5.5
Tribal designated statistical areas (TDSAs) Section 5.6
State designated tribal statistical areas (SDTSAs) Section 5.7
State American Indian Reservations Section 5.8

As noted the TSAP extension has been developed for ESRI’s ArcGIS software. Therefore as with any
ArcMap project, additional spatial datasets that may be useful in your delineation work for reference,
such as land use, zoning, aerial imagery, etc. may be added at anytime to supplement your TSAP
projects. The TSAP extension does not offer any custom tools for adding supplemental datasets to the
data frame, rather you must utilize the existing Add Data
toolbar.

command found on ArcGIS’s Standard

All data supplied by the Census Bureau for use with the TSAP extension is delivered in geographic
projection, North American Datum 1983 (NAD83). The TSAP data is supplied in shapefile format and
is thus not topologically integrated. The Census Bureau requests that tribal participants maintain the
shapefile format and projection throughout all use of the TSAP extension from review and delineation
to final submittal. It is necessary to maintain the delivered shapefile and projection format because all
submitted delineations will be incorporated by the Census Bureau into a seamless topologically
integrated spatial database. As well, Census Bureau provided shapefiles must be used for the actual
delineation work. All delineations submitted in other file formats and/or projections will cause a delay
in processing and acceptance.
If you believe the boundary for your reservation or off-reservation trust land is not correct, please
contact the Census Bureau RCC (see Appendix 5 for your RCC’s contact information).

18

Things to consider when delineating CDPs, ANVSAs, TDSAs and SDTSAs
Since CDPs, ANVSAs, TDSAs and SDTSAs also will be used to tabulate and present period estimates
from the American Community Survey, defining officials should consider that, as a general rule, period
estimates of demographic characteristics for geographic entities with small populations will be subject to
higher variances than comparable estimates for geographic entities with larger populations. In addition,
the Census Bureau’s disclosure rules may have the effect of restricting the availability and amount of
data for geographic entities with small populations. The more closely a CDP, ANVSA, TDSA, and
SDTSA boundary relates to the distribution of tribal members and American Indians receiving
governmental services from the tribe, and does not include large numbers of people and households not
affiliated with the tribe, the more likely that data presented for the CDP, ANVSA, TDSA, and SDTSA
will accurately reflect the characteristics of the intended tribal population.
Although eligible, in a few cases a tribe may elect not to delineate a CDP, ANVSA, TDSA, and SDTSA
if it will not provide meaningful, relevant, or reliable statistical data because the member population
now resides in numerous other locations or has been completely subsumed by non-member and/or nonAmerican Indian populations. In such instances, defining a CDP, ANVSA, TDSA, and SDTSA will not
improve the presentation of statistical data relating to tribal members. These tribes may still be able to
receive meaningful, relevant, and reliable statistical data for their tribal membership at higher levels of
census geography through the characteristic of tribal affiliation.

19

5.1 About tribal census tracts and tribal block groups
Tribal census tracts are delineated within federally recognized AIRs/ORTLs, and may contain one or
more tribal block groups. Tribal block groups in turn represent a collection of adjacent census blocks.
Together these statistical areas make up a nested geographic hierarchy.
Table 2. Tribal census tract and tribal block group thresholds
Area Type
Tribal census tract
Tribal block group

Threshold Type
Population
Housing Unit
Population
Housing Unit

Minimum
1,200
480
600
240

Optimal
4,000
1,600
N/A
N/A

Maximum
8,000
3,200
3,000
1,200

The Census Bureau recommends minimum/maximum and optimal population and housing unit
thresholds for tribal census tracts and tribal block groups (see Table 2 above). In accordance with TSAP
criteria, an AIR/ORTL must have population equal to or greater than 2,400 or a housing unit count equal
to or greater than 960 to delineate more than one tribal census tract. To delineate more than one tribal
block group an AIR/ORTL must have population equal to or greater than 1,200 or a housing unit count
equal to or greater than 440. If an AIR/ORTL lacks the population/housing unit count to delineate more
than one tribal census tract/tribal block group the Census Bureau will delineate one tribal census tract
and tribal block group coextensive with the entire AIR/ORTL. These thresholds apply to the entire
population living on, and housing units existing within the AIR/ORTL – not only American Indians or
Alaska Natives, and not only tribal members. These thresholds do not take into account and do not
include Tribal members that live outside the boundaries of the AIR/ORTL. These thresholds are in
keeping with those established for the Participant Statistical Areas Program (PSAP) and were
determined based on comprehensive consultations with statisticians and demographers regarding data
accuracy and privacy concerns. Areas delineated with population or housing counts below these
thresholds may not have data released due to data disclosure prevention. Areas above these maximum
thresholds may lose the data richness and usability that may be attained with the optimal thresholds.
Tribal census tracts and tribal block groups vs. standard census tracts and standard block groups
Census tracts are the oldest and one of the most utilized statistical geographic entities for which the
Census Bureau tabulates data. The primary purpose of census tracts is to provide a set of nationally
consistent small, statistical geographic units, with stable boundaries, that facilitate analysis of data
across time. Standard census tracts always nest hierarchically within states and counties. Standard
block groups are subdivisions of standard census tracts and always nest hierarchically within standard
census tracts. Standard block groups provide the geographic framework within which the Census
Bureau defines and numbers census blocks, with the block group number serving as the first digit for
each census block in the block group.
Tribal census tracts and tribal block groups are conceptually similar and equivalent to standard census
tracts and block groups. They recognize the unique statistical data needs of federally recognized
American Indian tribes by providing meaningful, relevant, and reliable data for small geographic areas
within the boundaries of federally recognized AIRs and/or ORTLs. The delineation of tribal census
tracts and tribal block groups allows for an unambiguous presentation of census tract and block group
level data specific to an AIR and/or ORTL, without the imposition of state or county boundaries, which

20

might artificially separate American Indian populations located within a single AIR and/or ORTL. To
this end, tribal census tracts and tribal block groups may cross county or state boundaries, or both.
For the 2010 Census, tribal census tracts and tribal block groups will be for the first time identified as a
geographic framework completely separate from standard census tracts and standard block groups. With
the development of an entirely separate tribal geographic framework, tribal participants have greater
freedom to begin their delineations from scratch without need to consider compatibility with Census
2000 tracts and block groups. Aside from the intent presented in the previous paragraph the
identification of tribal census tracts and tribal block groups for the 2010 Census also seeks to eliminate
data issues associated with previous censuses, so that for the 2010 Census more census tracts and block
groups, both tribal and standard, will meet the population and housing unit thresholds. The separation of
tribal and standard geographic frameworks will apply to data tabulation products, as well as to
geographic information products.
While there will be a separate hierarchy for standard and tribal census tracts and block groups in 2010,
there will only be one set of 2010 tabulation blocks. Tabulation blocks are the smallest geographic unit
for which the Census Bureau tabulates decennial census data. Tabulation blocks will be numbered with
a 4-digit code, the first digit being the number of the standard block group in which it nests. For
example, tabulation block 1001 is in standard block group 1 and block 2001 is in standard block group 2.
Because census blocks will be numbered within standard block groups and tribal block groups will be
identified uniquely from standard block groups, there will not be a relationship between tribal block
group identifiers and census block numbers. Thus, tribal block group A might contain census blocks
numbered in different ‘‘thousand’’ ranges (e.g., blocks 1001, 2001, and 3001).
An explanation of the tribal census tract and tribal block group code labels
When working with new or existing tribal census tracts and tribal block groups you will respectively
notice their ten and eleven digit identification code labels. For raw data work processes such as the
delineation tasks you are accomplishing with the TSAP Extension, the entire code for both tribal census
tracts and tribal block groups are used when labeling features. The entire code may not be present on
other Census Bureau data products including the American Fact Finder website.
Tribal census tract example
4625T00400
The first four characters identify the American Indian Area (AIA). The middle four characters
beginning with “T” identify the tribal census tract. The last two characters are a tract suffix that will
identify split tracts.
Tribal block group example
Tribal block groups add to the tribal census tract code one additional character. The example below is a
code for tribal block group “A” which is within the tribal census tract “T004” of AIA 4625.
4625T00400A

21

Delineating tribal census tracts
Delineations should begin with a reading of the criteria and guidelines for tribal census tracts found
below:
Tribal Census Tract Criteria and Guidelines
The criteria for tribal census tracts are:
1. Tribal census tracts may not cross AIR/ORTL boundaries.
2. The entire land and water area of an AIR/ORTL must be covered by one or more tribal census tract.
3. Tribal census tracts will be labeled by a “T” followed by three digits, beginning with “T001, T002,
etc.”
Guidelines for delineating tribal census tracts are:
1. Optimally, census tracts should have 4,000 people or 1,600 housing units. Meeting or exceeding the
optimum thresholds will help improve the reliability of sample data for tribal census tracts.
2. Each tribal census tract must encompass at least 1,200 people or at least 480 housing units unless it
is flagged as a special land use tract (see section 6.10).
3. A tribal census tract must comprise a reasonably compact and contiguous land area.
4. Tribal census tract boundaries should follow visible and identifiable features.
Next, review the 2000 Census tract boundaries and inspect the location and spatial extent of all existing
statistical areas as well as the corresponding demographic data reported from the 2000 Census.
Demographic data can easily be found using the TSAP Geography Manager
tool. Select Tribal
Census Tracts as your work layer and All as your update type. In the Current Work District pull-down
menu scroll through the available tracts. Notice that as each is selected, demographic attributes are
displayed beneath the Current Work District within the TSAP Geography Manager. Tracts falling
within or outside the population and/or housing unit thresholds are symbolized accordingly (red outline:
outside thresholds, green outline: within thresholds). It should again be noted that if your tribe is
eligible for only one tribal census tract, the Census Bureau will delineate a single tribal census tract
coextensive to your AIR/ORTL boundary. In the example below, an AIR with three census tracts is
depicted. The demographic attributes for each tract are present in the three following screenshots of the
TSAP Geography Manager on the next page.

22

In the scenario presented on the previous page, two tracts (outlined in red) fall outside the population
and housing unit thresholds required for tribal census tracts. The delineation of the tracts appears to be
based on standard geographic area governmental unit boundaries (e.g. counties and states) rather than
demographic rationale, and may not aid in the accurate reporting of the tribe’s statistical data. An
appropriate solution would be the merging of the three tracts into one contiguous entity. This is
accomplished by using the Merge Tool
found on the TSAP Tools toolbar (see Section 5.9). A new
tribal census tract, 4625T00600, with correspondingly summarized demographic data is formed from the
merging process (see image below).

23

Creating New Tribal Census Tracts
Continuing from the preceding scenario, the subject AIR/ORTL is eligible for two new tribal census
tracts. When creating new tribal census tracts, it is recommended that the Assign
Geography tool is
used to maintain the nesting relationships between the tracts and the AIR/ORTL. Not using this method
of delineation may result in blocks that are unassigned to a tribal census tract, which will slow the final
quality control process.
Begin the delineation by selecting Tribal Census Tracts as your work layer and All as your update type.
In the Current Work District pull-down menu select New District, then select the appropriate New
District Parameters and click OK (see images below).

The new tribal census tract, assigned with a new tribal tract number, is then created and displayed in the
Geography tool, select and
Current Work District, and you may begin adding area. Using the Assign
add census blocks until a tribal census tract is delineated (see image below).

The example above presents two tribal census tracts that both meet all necessary criteria. If a tract falls
below the population or housing unit thresholds (tracts below thresholds will be shown in red), select the
tract in the Current Work District and again use the Assign
Geography tool add area until all tracts
meet threshold criteria.

24

5.2 Delineating Tribal block groups
Tribal block groups are aggregations of census blocks within a tribal census tract. Block groups provide
a geographic summary unit for census block data, and represent the smallest geographic area that data
will be reported for the American Community Survey. Therefore the delineation of tribal census block
groups should be recognized as the most flexible opportunity for the collection of demographic data for
population centers, unique land uses, group quarters, and transitional/temporary communities within a
single census tract.
Tribal Block Group Criteria and Guidelines
The criteria for tribal block groups are:
1. Tribal block groups must not cross tribal census tract boundaries.
2. Because tribal census tracts must cover the entire area of each AIR/ORTL, by definition, tribal block
groups also must cover the entire area of each AIR/ORTL.
3. Tribal block groups will be designated with a single capital letter from “A” through “IC” (except for
the letter “I”). Tribal block group identifiers must be unique within tribal census tracts.
Guidelines for delineating tribal block groups are:
1. Each block group must encompass at least 600 people or at least 240 housing units unless it is
coextensive with a flagged special land use tract.
2. A block group must comprise a reasonably compact, contiguous land area.
3. Noncontiguous block groups are permitted only where a contiguous area or inaccessible area would
not meet population or housing unit count requirements for a separate tribal block group, in which
case the non contiguous or inaccessible area must be combined with a proximate block group.
4. Block group boundaries should follow visible and identifiable features.

As with tribal census tracts, your review should begin with an
inspection of the 2000 Census block groups and the corresponding
demographic data reported for the 2000 Census. Using the TSAP
Geography Manager
tool, select Tribal Block Groups as the
current work layer, and All as the update type. In the Current Work
District pull-down menu, scroll through and select any block group to
see its demographic data. An example block group selection using the
TSAP Geography Manager is shown in the image to the right.

25

In the following example, all of the reservation’s block groups are displayed. Block groups outlined in
red are outside the established population and/or housing unit thresholds while block groups outlined in
green are within. The reservation is displayed by a transparent green shade.

With so many block groups falling outside the thresholds it is apparent that some will need to be merged.
After choosing a current work district (in this example tract 4625T00400C), the tribal block group
to merge block groups. Two block groups are selected
delineation is begun by using the Merge Tool
(in blue outline) for merging in the image below.

After merging block groups until thresholds are met, as shown by block groups outlined in green, it may
tool.
be necessary to continue the delineations using the Assign Geography

26

A potential delineation of tribal block groups is pictured below. Notice the heavy green outlines
symbolizing that all tribal block groups have met the established population and housing unit thresholds.

27

5.3 Delineating Census designated places (CDPs)
Census designated places (CDP) are statistical geographic entities that generally represent closely settled,
unincorporated communities that are locally recognized and identified by a single name. A CDP should
be composed of a mix of residential and commercial structures, and have at least some housing or
population, ideally both. The purpose of delineating a CDP is the creation of a statistical area equivalent
to its counterpart – an incorporated governmental unit such as a city, town, or village. CDPs may not be
partially or entirely within another incorporated place or CDP, and should not be coextensive with any
other Census geographic entity (i.e. tract, AIR/ORTL, etc.). The boundaries should follow visible
features such as streams, roads, railroad tracks, or ridgelines whenever possible.
CDP Criteria and Guidelines
The criteria for CDPs are:
1. CDPs cannot be coextensive with an entire AIR, ORTL, OTSA, or any other AIA.
2. CDPs may extend off AIRs, ORTLs, or OTSAs.
3. A CDP may not have the same name as an adjacent or nearby incorporated place. If the community
does not have a name that distinguishes it from other nearby communities, then the community is not
a distinct place and should not be submitted as a CDP.
4. A CDP may not be located, either partially or entirely, within an incorporated place or another CDP.
5. A CDP may be located in more than one county.
6. A CDP must not cross state boundaries.
Guidelines for delineating CDPs are:
1. A CDP constitutes a single, closely settled center of population that is named. To the extent possible,
individual unincorporated communities should be identified as separate CDPs.
2. A CDP is defined to provide data for a single named locality, therefore the Census Bureau does not
encourage delineating CDPs that comprise a combination of places or are identified by hyphenated
names. For example, CDPs such as Poplar-Cotton Center and Downieville-Lawson-Dumont are no
longer acceptable. Prior to Census 2000 communities were sometimes combined as a single CDP in
order to comply with the Census Bureau minimum population requirements. The Census Bureau’s
elimination of population threshold criteria has made such combinations unnecessary.
3. Multiple communities may only be combined to form a single CDP when the identities of these
communities have become so intertwined that the communities are commonly perceived and
referenced as a single place.
4. Multiple communities also may be defined as a single CDP when there is no distinguishable or
suitable feature in the landscape that can be used as a boundary between the communities, even if the
two communities still have separate identities.
5. There is no minimum population or housing unit thresholds for defining CDPs; however, a CDP
must contain some population or housing units or both. Participants submitting boundaries for
places with less than ten housing units may be asked to provide additional information attesting to
the existence of the CDP.
6. CDP boundaries should follow visible features, except in those circumstances when a CDP’s
boundary is coincident with the nonvisible boundary of a state, county, MCD, or incorporated place.

28

CDP boundaries may follow other nonvisible features in instances where reliance upon visible
features will result in over bounding of the CDP in order to include housing units on both sides of a
road or street feature. Such boundaries might include parcel boundaries and public land survey
system lines; fence lines; national, state, or local park boundaries; ridgelines; or drainage ditches.
7. The CDP name should be one that is recognized and used in daily communication by the residents of
the community.
8. A CDP should have population during at least one entire season of the year, and have a higher
housing unit and population density than surrounding areas.

In the following scenario a new CDP is created for the unincorporated community of Forks. The
unincorporated community of Forks on an AIR is labeled in the image below.

A new CDP is added to the shapefile with the TSAP Geography
tool (left image). Census Designated Places and All are
Manager
selected respectively as the work layer and update type. After
choosing New District for the current work district, the New District
Parameters window pops-up (see first image next page).

29

In the New District Parameters window, Forks is typed as the CDP name.

To begin a new CDP, area must be added to the project with the Assign Geography
tool. A new
CDP is initially an empty record and requires the addition of census blocks before it will be visible in
the view. A potential delineation for the Forks CDP is symbolized by a heavy green outline and green
stipple fill pattern in the image below.

Many tribes have population living in a community with a locally recognizable name outside the
boundary of their reservation. To define CDPs off your AIR/ORTL, please contact your RCC who will
help you coordinate with the appropriate Participant Statistical Area Program (PSAP) participant.

30

Working with existing CDPs
For CDPs delineated in prior decades, you may modify the name or revise the boundary. Name changes
are processed through the CDP component of the QC Tool (please refer to section 8.0), so even if no
geographic area changes are made, the QC Tool provides a function to review and modify CDP names.
The boundaries of CDPs are modified using the Assign
and Unassign
Geography tools, as
covered in the earlier “Using the Extension” section. However, if you select a block to assign to a CDP
that is already part of another CDP or incorporated place a message box will appear to notify you (see
image below).

If you do in fact intend to include a portion of an existing CDP into your new CDP delineation, select
Yes. Please report to your RCC if this situation occurs (see Appendix 5 to find your RCC’s contact
information).

31

5.4 Delineating Alaska Native village statistical areas (ANVSAs)
An ANVSA is a statistical area that represents the relatively densely settled portion of an Alaska Native
village (ANV). These are areas where residents of the defining ANV reside during at least one season
of the year, and include housing, cultural, and commercial structures. Members of the defining ANV
should also represent a significant proportion of the population of the ANVSA. ANVSAs are not meant
to portray large unpopulated areas or the full extent of traditional lands, and their delineation is not
intended to convey any rights to land ownership, governmental authority, or jurisdictional status.
ANVSA Criteria and Guidelines
The criteria for ANVSAs are:
1.
2.
3.
4.

ANVSAs delineated for the 2010 Census shall not overlap.
An ANVSA shall not completely surround the location of another ANV.
All portions of an ANVSA must be located within fifty miles of the ANV’s point location.
An ANVSA shall not include more water area than land area. Large expanses of water area should
be included only to maintain contiguity, to provide a generalized version of the shoreline, or if the
water area is completely surrounded by land area included in the ANVSA.
5. The name for an ANV must match the name corresponding to the ANV point location. Name
changes will only be considered if submitted in writing and signed by the highest elected official of
the ANV.
Guidelines for delineating ANVSAs are:
1. Housing units occupied by Alaska Natives, even if seasonal, should constitute the majority of
housing units within an ANVSA.
2. The population within an ANVSA should be majority Alaska Native and of that population, the
majority should be members of our population served by the delineating ANV.
3. ANVSAs should be located in areas of historical and traditional significance and include land that is
locally recognized as being associated with the village or group. In addition each ANVSA should
include land area that contains structures such as tribal headquarters, meeting areas, cultural or
spiritual landmarks, service centers and/or tribally owned stores.
4. An ANVSA should not extend beyond the regional boundary of the ANRC in which the ANV is
located (ANRC boundary shapefiles are included on the CD).
5. An ANVSA should not exceed 325 square miles in area. Based on review of ANVSA boundaries
from previous censuses as well as other information about ANVs and ANVSAs, the Census Bureau
suggests this size as sufficient to encompass the Alaska Native population and housing associated
with each respective ANVSA, but not so extensive that large amounts of non-Native population and
housing are included.
6. An ANVSA should not contain large areas without housing or population. Specifically, an ANVSA
should have a housing unit density of at least three housing units per square mile.
7. An ANVSA should be contiguous; that is, an ANVSA should form a single area with all territory
located within a continuous boundary. This makes identification of the extent of the ANVSA easier
for residents and data users, and also provides for a clearer representation of the ANVSA’s

32

boundaries on maps. An ANVSA, however, may be defined with multiple noncontiguous pieces if
doing so helps avoid inclusion of population and housing not associated with the ANV.
8. An ANVSA’s boundary shall follow visible, physical features, such as rivers, streams, shorelines,
roads, trails, and ridgelines.
9. Officials delineating ANVSAs may use nonvisible lines as an ANVSA boundary only if acceptable
boundary features are not available. For example, an ANVSA boundary may follow the nonvisible,
legally defined boundaries of ANRCs, boroughs, or cities.
10. If the ANVSA boundary follows a governmental unit boundary, the Census Bureau will adjust the
ANVSA boundary to continue to follow that boundary should it change due to correction,
annexation or detachment.
The process for delineating your ANVSA should begin with a review and inspection of the 2000 Census
ANVSA boundary (if an ANVSA was delineated in 2000) and the point location of your Alaska Native
village as well as the AIAN percent of total population of your ANVSA reported for the 2000 Census.
After opening the TSAP Geography Manager
tool, ANVSA and All are respectively selected as the
work layer and update type. In the example below, the fictional Alaska ANVSA has been chosen as the
current work district and its demographic data is listed beneath. Notice the extent and size of the census
blocks (light orange boundary lines) in relation to the 2000 Census ANVSA (transparent green fill). The
point location of the ANV is symbolized with a flag.

33

Utilizing the Toggle Block Symbology
tool, an additional perspective of the American Indian and
Alaska Native (AIAN) population per census block is displayed (see below image). Most noticeably the
2000 Census ANVSA boundary contains several large uninhabited census blocks covering both land
(areas in white) and adjacent water features. (The 2000 Census ANVSA boundary is symbolized with a
heavy green line.) An ANVSA with a total AIAN population percentage of 30% or greater is
recommended for statistical purposes.

An improved ANVSA boundary eliminates the large uninhabited census blocks and results in a more
spatially concise and accurate representation of the ANVSA’s population (see image below). The new
tool.
ANVSA boundary was achieved by removing census blocks with the Unassign Geography
Compare the new ANVSA boundary (visible by the green shaded area) with the 2000 Census ANVSA
boundary found on the previous page.

34

5.5 Delineating Oklahoma tribal statistical area (OTSA) tribal subdivisions
OTSA boundaries represent statistical entities identified and delineated by the Census Bureau in
consultation with federally recognized American Indian tribes that have no current AIR, but that had a
former AIR in Oklahoma. The boundary of an OTSA is that of the former AIR. Therefore, the Ceusns
Bureau does not expect any changes to OTSA boundaries. Upon review of your OTSA boundary if you
identify an error please contact the Kansas City RCC (see Appendix 5 for contact information).
OTSA and OTSA tribal subdivision Criteria and Standards
The criteria for OTSAs are:
1) An OTSA must contain some American Indian population and housing.
2) An OTSA may not overlap with any other AIA, at the same level of the geographic hierarchy.
3) An OTSA may not include more water area than land area.
4) OTSAs should be bounded by visible features such as roads, rivers, streams, shorelines, trails and
ridgelines.
5) The Census Bureau will evaluate the submitted name of each OTSA to ensure that the name is
clearly distinguishable from the name of any other OTSA.
6) OTSAs must be located completely within the current boundaries of the state of Oklahoma.
7) An OTSA may not completely surround another legal or statistical area at the same level of the
geographic hierarchy.
8) The name for each OTSA is determined by the tribe or tribes (in conjunction with the Census
Bureau) that are responsible for delineating each OTSA. The Census Bureau will revise any name
submitted for a geographic entity if it is determined that the criteria listed below were not applied
properly. The name of an OTSA must reflect one or more of the following conditions
a) The tribe or tribes associated with the former AIR represented by the OTSA;
b) Tribes that have historically resided within the area of the OTSA;
c) Tribes that have significant population currently residing within the OTSA; and/or
d) The name(s) of the tribe(s) commonly associated with the area encompassed by the OTSA.
Guidelines for delineating OTSAs are:
1. To the extent possible, OTSA boundaries identified for the 2010 Census should be the same as those
delineated for Census 2000.
2. OTSAs should follow the last legal boundaries established for their former AIR.
3. Tribes should strive to eliminate overlapping OTSA boundaries that resulted in the Census 2000
joint use area OTSAs.
4. Tribes may delineate tribal subdivisions within their own OTSAs.
5. Tribes may delineate CDPs representing unincorporated communities located within their own
OTSAs.
Guidelines for delineating OTSA Tribal Subdivisions are:
1. A Tribal subdivisions should represent units of self-government or administration within an AIR or
ORTL for a federally recognized tribe.

35

2. OTSA Tribal subdivisions are intended to completely cover all of an AIR and/or ORTL, or OTSA,
or at least the major contiguous portion of an AIR, ORTL, or OTSA.
3. The name of each tribal subdivision must reflect its name, as cited in recent tribal legal
documentation and/or used by the tribal government for administrative purposes.
4. If an OTSA consists of multiple, noncontiguous parts, the tribal subdivisions within them will be
noncontiguous.
OTSA tribal subdivisions are statistical entities that represent internal units of self government or
administration. Internal units may include areas that serve social, cultural, and/or legal purposes for a
tribal government. Please report the lowest level of administrative units that are available. For example,
if the tribe uses several levels of nesting geography, such as tribal council management districts that
wholly contain grazing districts, the grazing districts should be reported to the Census Bureau as the
tribal subdivision boundaries, as they are the smallest and lowest level of units used in that hierarchy. If
a similar hierarchical structure exists within the governmental units being reported as tribal subdivisions,
please delineate the lowest level unit in the steps below.
Working with existing OTSA tribal subdivisions
Existing OTSA tribal subdivisions should be reviewed and adjusted as needed. The Assign geography
tool , Unassign geography tool , and Merge tool
,all found on the TSAP Tools toolbar and
explained in section 6.0 Using the Extension, will be useful in census block based adjustments to your
OTSA tribal subdivision delineations.
Creating new OTSA tribal subdivisions
In the following example new OTSA tribal subdivisions are developed upon existing county boundaries
tool. The image below contains the spatial
and 2000 Census blocks with the Assign geography
extent of the two counties which will serve as building units for delineating new OTSA tribal
subdivisions.

36

Using the TSAP Geography Manager
tool select OTSA Tribal Subdivision as the current work layer
to begin the delineation process. You will immediately be prompted with the New District Parameters
window to identify your new OTSA tribal subdivision (see image below). A Tribal Subdivision Name is
typed in the text box provided.

The name of the new district will then be displayed as the current work district in the TSAP Geography
(see below left image). The Assign Geography
tool may be used to assign area by
Manager
county boundary or 2000 Census block. By default the Assign Geography
tool is set to use 2000
Census blocks for assignment. If you prefer to use county boundaries be certain to check the Use
Counties to Assign OTSA Subdivisions option box in the the TSAP Geography Manager .
In the example below the area from OK County 1 has been assigned to District 1 using the Assign
tool. Notice that the Use Counties to Assign OTSA Subdivisions option box has been
Geography
checked so that the area of OK County 1 was assigned to District 1 with a single click.

37

A second OTSA Tribal Subdivision is created by selecting New District as the current work district (see
below left image). Again, the New District Parameters window will appear prompting you to enter a
name for the new district (see below right image). Please enter the full administrative name of the
subdivision. For example, if the Tribal Subdivision is referred to as District 2 in official tribal
documentation, please type in District 2.

When switching to another work district be certain the current work district in the TSAP Geography
Manager
is correctly selected (see below left image). The area of OK County 2 is added to District 2
with the Assign Geography
tool (see below right image).

38

A third district, not based upon county boundaries, but upon 2000 Census blocks is added to finish this
OTSA tribal subdivision example. Following the directions for creating a new work district explained
above, District 3 is created. After checking off the Use Counties to Assign OTSA Subdivisions option
box - so that area will be assigned by 2000 Census blocks - the Assign Geography
tool is used with a
marquee selection (see below right image).

39

5.6 Delineating Tribal Designated Statistical Areas (TDSAs)
A TDSA is a statistical geographic entity identified and delineated by a federally recognized American
Indian tribe that does not currently have a reservation and/or off-reservation trust land. A TDSA is
intended to be comparable to the AIRs within the same state or region, especially those for tribes that are
of similar size. Your TDSA should encompass a compact and contiguous area that contains a
concentration of individuals who identify with your American Indian tribe and within which there is
structured, organized tribal activity. Criteria and guidelines for TDSAs are listed below:
TDSA Criteria and Guidelines
The criteria for TDSAs are:
1. A TDSA must contain some American Indian population and housing.
2. A TDSA may not overlap with any other AIA, at the same level of the geographic hierarchy.
3. A TDSA may not completely surround another legal or statistical AIA at the same level of the
geographic hierarchy.
4. A TDSA may not include more water area than land area.
5. Officials delineating TDSAs may only add nonvisible lines as a boundary if other acceptable
boundary features such as roads, rivers, streams, shorelines, trails and ridgelines, are not available
and they aid in a TDSA meeting other specific, delineation criteria and/or guidelines.
6. TDSAs may not include military areas.
7. TDSAs may not be delineated in Hawaii, Oklahoma or Alaska, nor will those existing in Alaska
continue to be recognized.
8. The name of a TDSA will be determined by the tribe or tribes, in conjunction with the Census
Bureau. The Census Bureau will evaluate the submitted name to ensure that each TDSA name is
clearly distinguishable from the name of any other legal or statistical AIA. The name must also
reflect one of two conditions: the tribe that has the largest population currently residing within the
TDSA, or the name of the tribe most commonly associated with the area that the TDSA
encompasses.
Guidelines for delineating TDSAs are:
1. TDSAs should be comparable in area to the AIRs and/or ORTLs of other tribes with similar numbers
of members in the same state and/or region.
2. American Indians should constitute a large proportion of the population within a TDSA, and of the
American Indian population, the majority should be members of the delineating tribe.
3. As a minimum, TDSAs should have a population of 1,200 individuals or 480 housing units.
4. A TDSA should include an area where there is structured and organized tribal activity, including
tribal headquarters, tribal service centers, meeting areas and buildings, ceremonial grounds, tribally
owned commercial locations, etc.
5. TDSAs should not contain large areas without housing or population. A housing unit density of at
least three housing units per square mile is suggested.
6. TDSAs should be contiguous.
7. Water area should be included only to maintain contiguity, to provide a generalized version of the
shoreline, or if the water area is completely surrounded by land area included in the TDSA.

40

8. TDSA boundaries should follow visible, physical features, such as rivers, streams, shorelines, roads,
and ridgelines.
9. TDSA boundaries may follow the nonvisible, legally defined boundaries of AIRs, ORTLs, states,
counties, or incorporated places.

The delineation process begins with the selection of TDSA as the
current work layer in the TSAP Geography Manager . After the
update type of All is selected the current work district will
automatically display the four digit census code for your area (see
right image).

After locating the general area for which you are considering your TDSA delineation, it is recommended
that you review the existing census block data. Using the Toggle Block Symbology
tool, activate the
AIAN percent of total population symbology. This will allow you to identify the blocks with a 30% or
greater AIAN percent of the total population. In the example pictured below a distinct pattern of census
blocks with a 30% or higher AIAN population is visible. A TDSA with a total AIAN population
percentage of 30% or greater is recommended.

41

In this scenario a new TDSA is delineated with the Assign Geography tool by clicking once on each
block that will comprise the TDSA. The finalized TDSA delineation is displayed in the image below
(census blocks are shown with default symbology).

42

5.7 Delineating State Designated Tribal Statistical Areas (SDTSAs)
Called SDAISAs in Census 2000, SDTSAs are created to provide state-recognized American Indian
tribes without an AIR, statistical data similar to that provided to tribes with AIRs. The entity
terminology changed to adhere more closely to the similar federal tribe naming convention, tribal
designated statistical area. SDTSAs are identified and delineated for the Census Bureau by a governorappointed state liaison, working in conjunction with tribal officials through the TSAP. SDTSAs
generally encompass a compact and contiguous area in which there is structured or organized tribal
activity and a concentration of individuals who identify with a state-recognized American Indian tribe.
As part of the 2010 Census, TSAP state liaisons representing state recognized tribe officials will again
have the opportunity to review and update the boundaries of existing SDTSAs (SDAISAs) or delineate
new SDTSAs.
The definition of a SDTSA may not necessarily include all tribal members; nor is it intended to depict
land ownership, represent an area over which a tribe has any form of governmental authority or
jurisdiction, or represent all of the traditional or historical areas associated with the tribe, including areas
used for subsistence activities. Representation of statistical American Indian Area (AIA) boundaries in
Census Bureau products is solely for the purpose of data tabulation and presentation. Likewise,
representation of SDTSA boundaries in Census Bureau products does not convey or confer any rights to
land ownership, government authority, or jurisdictional status.
SDTSA Criteria and Guidelines
The criteria for SDTSAs are:
1. A SDTSA must contain some American Indian population and housing.
2. A SDTSA may not overlap with any other AIA, at the same level of the geographic hierarchy.
3. A SDTSA may not completely surround another legal or statistical AIA at the same level of the
geographic hierarchy.
4. A SDTSA may not include more water area than land area.
5. Officials delineating SDTSAs may only add nonvisible lines such as corporate limits as a boundary
if other acceptable boundary features such as roads, rivers, streams, shorelines, trails and ridgelines,
are not available and they aid in a SDTSA meeting other specific, delineation criteria and/or
guidelines.
6. SDTSAs may not include military areas.
7. An SDTSA for a specific tribe may be delineated in a state only if the tribe is officially recognized
by the state.
8. The name for each SDTSA is determined by the tribe or tribes (in conjunction with the Census
Bureau, and the state liaison for SDTSAs) that are responsible for its delineation. The Census
Bureau will evaluate the submitted name to ensure that each SDTSAs name is clearly distinguishable
from the name of any other legal or statistical AIA. The name of a SDTSA must reflect one or more
of the following conditions: The tribe that has the largest population currently residing within the
SDTSA; and/or the name of the tribe most commonly associated with the area encompassed by the
SDTSA.

43

Guidelines for delineating SDTSAs are:
1. SDTSAs should be comparable in area to the AIRs and/or ORTLs of other tribes with similar
numbers of members in the same state and/or region.
2. American Indians should constitute a large proportion of the population within a SDTSA, and of the
American Indian population, the majority should be members of the delineating tribe.
3. A minimum population of at least 1,200 individuals or 480 housing units is suggested to help
enhance reliability and availability of sample-based data.
4. SDTSAs should include area where there is structured and organized tribal activity, including tribal
headquarters, tribal service centers, meeting areas and buildings, ceremonial grounds, tribally owned
commercial locations, etc.
5. SDTSAs should not contain large areas without housing or population. A housing unit density of at
least three housing units per square mile is suggested.
6. SDTSAs should be contiguous.
7. Water area should be included only to maintain contiguity, to provide a generalized version of the
shoreline, or if the water area is completely surrounded by land area included in the SDTSA.
8. SDTSA boundaries should follow visible, physical features, such as rivers, streams, shorelines, roads,
and ridgelines.
9. SDTSA boundaries may follow the non visible, legally defined boundaries of AIRs, ORTLs, states,
counties, or incorporated places.

The delineation process begins by selecting the SDTSA as the current
work layer in the TSAP Geography Manager . After the update
type of All is selected the current work district will automatically
display the four digit census code for your area (see right image). As
in the example image, population and housing unit data will be blank
when delineating a completely new SDTSA.

After locating the general area for which you are considering your SDTSA delineation, it is
recommended that you review the existing census block geography. Using the Toggle Block Symbology
tool, activate the AIAN percent of total population symbology. This will allow you to identify the
blocks with a 30% or greater AIAN percent of the total population.

44

In the example image below a distinct pattern of census blocks with a 30% or higher AIAN population is
visible. An SDTSA with a total AIAN population percentage of 30% or greater is recommended.

In this scenario a new SDTSA is delineated with the Assign
Geography tool by clicking once on each
block that will comprise the SDTSA. The finalized SDTSA delineation is displayed in the image below
(census blocks are shown with default symbology).

45

5.8 Delineating State American Indian Reservations
State American Indian reservations (state AIRs) are reviewed and updated as needed once before each
decennial census to ensure a complete inventory of state AIRs for those states with state-recognized
tribes that are not also federally recognized. The review should determine, solely for data collection and
tabulation by the Census Bureau, the complete and current inventory and the correct attributes (names,
legal descriptions, official status) and official, legal boundaries of the state AIRs in each state. The
Census Bureau also accepts additions and updates to features such as roads or rivers that serve as the
boundary of the state AIR, as well as address range break information at the boundaries.
For affected states, a governor appointed state liaison provides the name, boundary, and any associated
updates for each state recognized AIR to the Census Bureau. If the state AIR official declines or defers
participation, the Census Bureau will use the Census 2000 state AIR boundaries, to tabulate 2010
Census data.
State Reservation Criteria and Guidelines
State AIR boundaries and names should be reported to the Census Bureau as they exist in the legislation
or treaty under which they were established. By definition, state AIR boundaries cannot cross state lines
unless the AIR and tribe is separately recognized in each state. State AIRs may not include territory
within federally recognized AIRs or ORTLs. Acceptance of boundary changes to state AIRs requires
clear legal documentation supporting any, and all, changes involving these boundaries. The Census
Bureau will identify each state AIR with the name submitted by the state liaison providing the boundary
for the area. For this reason, the state AIR name should reflect the specific tribal name cited in the legal
records establishing the state AIR.

In the following example delineation scenario an existing state AIR
boundary is updated to include additional legally defined land. The
delineation process begins with the selection of STRES as the current
work layer in the TSAP Geography Manager . After the update
type of All is selected the current work district will automatically
display the name of the state AIR to be delineated (see right image).

46

Next the spatial extent of the state AIR and existing census block geography are reviewed. The existing
state AIR (light green fill) and census blocks (heavy orange lines) are pictured below.

Upon comparing the Census Bureau’s depiction of the state reservation boundary to a reliable state
document a difference is noted. In some cases the area that needs to be added may be a whole block and
you can use the Assign geography tool to accomplish the task. In this example, it is apparent that a
new line must be added to correctly depict the state AIR boundary. This is accomplished by starting a
line edit session with the Census Editing Tools toolbar (see below image).

Once the edit session is active, use the Sketch tool
page).

to add your new line feature (see first image next

47

After completing the new line feature with a double click, the Update Line Attributes message box will
pop-up (see below image). The default Classification is the Nonvisible Legal/Statistical Boundary type;
other types may be found in the pull down menu. OK is clicked once to continue.

After choosing a Classification type, the Split Block Attributes window appears offering an opportunity
to utilize local knowledge while assigning population to the new blocks (see below image).

48

The new area is pictured in the below image.

After ending the line edit session, the new area must be assigned to the state AIR boundary with the
Assign geography
tool. The completed state AIR boundary update is pictured below.

When adding a boundary that is within 30 feet (10 meters) of an existing line in the Census Bureau’s
shapefile do not add an additional line. Instead use the existing line features wherever possible.

49

6.0 Using the Extension
The TSAP Extension features tools and commands useful in the identification, delineation, and review
of your statistical areas. This section presents details on how these tools/commands can be used to
accomplish the core tasks of the mapping process. The administrative Geography Manager and
Workflow Manager are presented first, followed by editing tools, and the quality control tools.
6.1 TSAP Geography Manager
The TSAP Geography Manager tool allows you to identify and select with pull-down menus a work
layer, update type, and work district. A work layer specifies the entity type you will be delineating, for
example: tribal census tracts, Alaska Native village statistical areas, census designated places, etc. A
work district further specifies a particular feature of the work layer such as an individual tribal census
tract. The update type menu allows you to narrow your work districts to those features above or below
population and/or housing unit thresholds (applicable only when working with tribal census tracts, tribal
block groups, and census designated places). The TSAP Geography Manager is activated by clicking
once on the Show/Hide TSAP Geography Manager
button in the TSAP Management toolbar. In the
series of example images below a work layer, update type, and work district is selected. In the final
image notice the demographic data visible once a work district is selected.

TOOL TIP
Hold down the Ctrl key and
click on an area to change the
Current Work District
selection

50

6.2 Workflow Manager
The Workflow Manager presents an outline of the major tasks associated with delineating your statistical
areas and offers a tool for you to monitor the progress of your project work. It is activated by clicking
once on the Show/Hide Workflow Manager
button on the TSAP Management Toolbar. Before your
project is started the manager will appear blank as shown in the below left image. As you work through
your project, review and delineation tasks will automatically become checked as they are completed.
For example, after you start a project and the necessary datasets are assembled, the Data Setup task will
become checked (see below right image).
Once your project is setup the Workflow Manager will display the area types eligible for delineation as
determined by your tribe’s delineation eligibility (see Table 1, section 2 or Appendix 1). In the example
shown in the below right image, the tribal participant is eligible to delineate tribal tracts, tribal block
groups, and CDPs. Therefore all other area types are grayed out and disabled.

51

6.3 Working with Census blocks
The census block is the smallest unit of census geography. The TSAP extension makes use of existing
census block geography generated from the 2000 Census. Census 2000 block geography is provided for
reference in your delineations because it is the most recent area representation of population and housing
unit counts available. Following the completion of the TSAP statistical area delineations for the 2010
Census, the Census Bureau will generate an entirely new set of block boundaries that will nest within the
statistical areas you delineate. It is the newly generated block boundaries that will be the most accurate
representation of your area’s 2010 Census population.
Several of the tools described later in this section present methods used to assign and unassign blocks to
an entity, as well as methods of splitting blocks. However, it is important to understand which blocks
you may want to include or exclude from your area or to modify for your delineations, as based upon the
Census 2000 American Indian Alaska Native (AIAN) percent of total population. The Toggle Block
Symbology
tool, found in the TSAP Management toolbar, is intended to aid you in this process. The
default block symbology is a heavy orange outline (see below left image). Click once on the Toggle
button and the block symbology will switch to a graduated color fill corresponding
Block Symbology
to the AIAN percent of total Census 2000 population for each block (see lower right image). In the
Table of Contents, you will also notice that the legend switches as shown in the below images. Blocks
without population will appear without a fill color or boundary when in the AIAN percent of total
population symbology. Click the Toggle Block Symbology
button again to return to the default block
symbology.

Default block symbology

AIAN percent of total population symbology

52

6.4 Assigning and unassigning geography to and from your area
The Assign
and Unassign
Geography tools in the TSAP Tools toolbar allow you to spatially add
and subtract Census 2000 blocks to/from your statistical areas. In the following example many blocks
are assigned to tract 1490T00100 using a marquee selection. First the Assign Geography
button is
clicked once, making the tool active (you will notice a modified cursor when the tool is active). The
cursor is then clicked and dragged over the blocks to be assigned. Blocks may also be selected
individually by clicking once directly on the block you wish to assign. It is highly encouraged to assign
blocks rather than unassign blocks when delineating your statistical areas however the Unassign
Geography
tool may be used when necessary. Using the Unassign Geography
tool does not
reassign blocks to another feature but rather removes the blocks entirely from any feature. This process
could result in unassigned areas that will be caught and corrected in the QC process.

TOOL TIP
More than one block can be assigned or unassigned at one time. Use a standard rectangular marquee selection or
while holding down the Shift key freehand sketch a polygon that contains the blocks you wish to assign or
unassign.

53

6.5 Splitting tribal census tracts and tribal block groups by block selection (applies only to Federally
recognized tribes with AIRs/ORTLs)
Splitting tribal census tracts and tribal block groups is a convenient method for creating new tribal
census tracts and tribal block groups. The TSAP Tools toolbar offers a unique solution with the Split by
block selection tool . This tool is activated by clicking once on the Split by block selection tool
button. Once the tool is active, click and drag the crosshair cursor over the Census 2000 blocks of
interest to make a block selection. In the left image below a rectangular marquee selection has been
made to split a block group. The right image displays the selected blocks (highlighted in blue).

If your block selection is complete, double
click anywhere to continue the split
process. A message window (shown
below) will prompt you to confirm your
block selection. After clicking Yes, the
existing block group is split yielding a new
tract (see right image).

54

6.6 Splitting blocks with existing line features
Blocks are most often defined by visible linear features such as roads, shorelines, rivers, power lines, et
cetera, as well as by governmental unit boundaries that are frequently not visible features. When
working with the Census 2000 blocks you may find the need to split blocks to accommodate your
statistical area delineations. Splitting Census 2000 blocks is also considered an opportunity to suggest
Census 2010 block boundaries that upon review may be utilized by the Census Bureau when generating
the new 2010 block boundaries.
The Census Editing Tools toolbar offers unique line editing tools to accomplish the process of splitting
Census 2000 blocks with existing line features (as found in the Line Features Group Layer in your
ArcMap project). If a linear feature is not represented in the dataset you may also sketch in that feature
using the line editing tools. You may also need to add a feature extension or a new line if an existing
line feature does not entirely split a block. This will be covered in the next section, Splitting blocks with
new line features.

Begin the block splitting process by clicking on the Line Edit Menu pull down of the Census Editing
Tools toolbar and selecting the Start Line Editing command (see image above). If ArcMap’s Editor
toolbar is already in use, the Target layer pull-down menu may be found there rather than the Census
Editing Tools toolbar. If your project contains more than one county, be certain that your Target Layer
is the edge shapefile for the correct county.

55

Line features that will be used to split the block are selected with the Select Features tool
example, Mifflin Ditch has been selected to split block 1002 (see image below).

. In this

With the line features selected, click once on the Split Block Tool
button. A Split Block Attributes
window (see image below) will pop-up containing the tabulated total population, housing units, and
American Indian Alaska Native (AIAN) population for the two blocks generated by the split block
operation. The tabulated statistical data contained within the window is based upon 2000 Census data
and automatically calculated by area. Use the Highlight Part 1 and Highlight Part 2 buttons to spatially
identify the two new blocks. Local knowledge may be used to adjust the new blocks’ population,
housing units, and AIAN population by clicking inside the cell of interest and typing. Notice the data
cells of the other block will adjust automatically as you change the population values in the Split Block
Attributes window.

After the data cells have been adjusted as needed, OK is clicked to proceed and finalize the block
splitting process.

56

The two new blocks and the block boundary are now visible and symbolized appropriately. Because
you are not actually changing Census 2000 blocks but rather beginning to define Census 2010 blocks,
the block labels will remain the same (i.e. the two resulting blocks have the same label).

When finished splitting blocks, deactivate the line edit session and save your work by selecting Stop
Line Editing in the Line Edit Menu (see image below). A message window will then appear prompting
you to save or cancel your changes.

57

6.7 Splitting blocks with new line features
In the following example, block 1002 will be split using the Mifflin Ditch because there is a desire to
make the ditch a block group boundary. However unlike the previous section, in this example the
Mifflin Ditch line feature does not completely cross the entire block. While it is recommended that
existing features be used to split blocks, small “feature extensions” may be added to complete the
splitting line feature. Such feature extensions may follow lines of sight or convenience when no other
feature is available to better enclose an area. The feature extension added in this example connects
Mifflin Ditch to Conrail Railroad. If possible, “feature extensions” should be no longer than 300 feet in
length. The Census Bureau also wishes to stress that line feature additions will be accepted through the
TSAP only if they serve as boundaries. Feature extensions are not permitted to connect to non visible
boundaries.
When adding a boundary that is within 30 feet (10 meters) of an existing line in the Census Bureau’s
shapefile do not add an additional line. Instead use the existing line features wherever possible.
The block splitting process is begun by clicking on the Line Edit Menu pull down of the Census Editing
Tools toolbar and selecting the Start Line Editing command (see image below).

After the line editing toolbar is activated make certain the correct line features shapefile is the Target
layer. If ArcMap’s Editor toolbar is already in use, the Target layer pull-down menu may be found
there rather than the Census Editing Tools toolbar.

58

Because in this example, Mifflin Ditch does not entirely cross block 1002, it is necessary to add a
feature extension from the end of Mifflin Ditch to Conrail Railroad, a visible feature. A feature
extension is added by first clicking on the Sketch Tool
button. Once activated, the Sketch Tool cursor
is located over the end of the Mifflin Ditch and clicked once to begin the line. Be sure to zoom in very
close to make sure the new feature snaps properly to the existing feature both at the start and end of the
line. All subsequent vertices are added by single clicks. The feature extension is ended with a double
click. Again, zoom in to make sure the end properly snaps to the existing features.
TOOL TIP 
The snap tolerance when 
adding a line feature is 
10 feet.  When starting 
or beginning a line be 
sure to zoom in close 
enough that you sense 
the snap tolerance. 

Hold down the z key to 
zoom in and hold down 
the x key to zoom out 
while the sketching tool 
is active. 

After the feature extension is ended, a line attributes window will pop-up (see image below). In the
Classification pull-down the type is selected. The default class for new line features is P0001 –
Nonvisible Legal/Statistical Boundary. If a line feature is being added that represents an actual visible
physical feature, please select the appropriate class code. A full name is required for road features only,
but is recommended for all new features. Address ranges may be optionally included by State
Reservation Program participants when adding new street features that intersect the boundary of their
reservation.

59

Next, all line features that will be used to split the block are selected with the Select Features tool .
In this example, Mifflin Ditch and the new feature extension line have been selected (see image below).

button. A Split Block Attributes
With the line features selected, click once on the Split Block Tool
window (see image below) will pop-up containing the tabulated total population, housing units, and
AIAN population for the two blocks generated by the split block operation. The tabulated statistical
data contained within the window is based upon 2000 Census data and automatically calculated by area.
Use the Highlight Part 1 and Highlight Part 2 buttons to spatially identify the two new blocks. Local
knowledge may be used to adjust the split blocks population, housing units, and AIAN population by
clicking inside the cell of interest and typing. Notice the data cells of the other block will adjust
automatically.

After the data cells have been adjusted as needed, OK is clicked to proceed and finalize the block split
process.

60

The two new blocks and the block boundary are now visible and symbolized appropriately. Because
you are not actually changing Census 2000 blocks but rather beginning to define Census 2010 blocks,
the block labels will remain the same (i.e. the two resulting blocks have the same label).

When finished splitting blocks deactivate the line edit session and save your work by selecting Stop Line
Editing in the Line Edit Menu. A message window will then appear prompting you to save or cancel
your changes.

61

6.8 Line attributes tool
The attributes of individual line segments may be updated with the Line attributes tool , including the
name, type of feature (i.e. classification), address range and ZIP code range (optional for State
Reservation Program participants adding street features). The tool is activated by clicking once on the
Line attributes tool
button included in the Census Editing Tools toolbar. The tool’s selection cursor
is then located over the line feature to be updated and clicked once. In the example below, Ash Street is
being selected.

Once a line feature has been selected the Update Line Attributes window will pop-up displaying the
existing attributes for Ash Street (image below).

62

The classification is changed by selecting a type from the pull-down menu. A name for the feature is
added in the Full Name text box. In the example below, Ash Street has been updated to an alley named
Old Ash Alley (see image below).

After clicking OK, to confirm the line attribute update, your changes will take effect immediately.
Notice the new label for Old Ash Alley in the example image below.

63

6.9 Merging tracts and block groups
The Merge Tool
included in the TSAP Tools toolbar is used to combine two tribal census tract or
tribal block group features. In the example below two tribal census tracts, 4760T00201 and
4760T00202, that were originally split from the same tract (as identified by the T002 tract code and their
two character suffixes) will be merged to reform one new tribal census tract. The merge function is
activated by clicking once on the Merge Tool
button. The crosshair cursor is then positioned over
one of the two tracts and clicked once selecting the first feature (see below right image).

The selection process is then repeated for the second feature to be merged. After the second selection a
message window will pop-up to confirm or cancel the merge process.

64

With the merge process complete a new tribal census tract with a new unique code is displayed (see
below image).

6.10 Updating type attributes for tribal tracts and tribal block groups
Tribal tracts and tribal block groups may contain features such as parks, schools, group quarters, water
features, etc. that influence or change the usefulness of statistical data being reported for your area. In
some cases it is useful to isolate these areas as special use tracts and block groups. In the event that
separate special use tracts or block groups are created to enhance your delineations, the Tract/BG type
found on the TSAP Tools Toolbar may be used to assign attribute types to those areas. The tool
tool
is activated by clicking once on the Tract/BG type tool
button. The cursor is then positioned over the
area of interest and clicked once. In the example below the cursor has been placed over block group
4160T00100B.

65

The Select Type pop-up window will appear following your selection (see below image). The ID field
will remain disabled and you will need to only select a type from the pull-down menu. In the example
below the P-Park type has been selected. Click OK to proceed and finish the process.

Special land use tribal census tracts and tribal block groups
To recognize and distinguish the special uses of some parcels of land, the Census Bureau allows for the
definition of special land use tribal census tracts or block groups. Specific areas such as ceremonial
grounds, historic sites, and parks can be identified as special land use tribal census tracts or tribal block
groups. These areas must have an official name, generally have little or no residential population or
housing units (or meet the non special land use tribal census tract or tribal block group population and
housing unit thresholds) and must be contiguous. If located in a densely populated urban area, a special
land use tribal census tract or tribal block group must have an area measurement of approximately 1
square mile or more. If delineated completely outside an urban area, a special land use tribal census
tract or tribal block group must have an area of approximately 10 square miles or more. Participants are
not required to delineate special land use tribal census tracts or tribal block groups.
The Census Bureau recognizes that some special land use areas not intended for residential population,
such as parks, may contain some population, such as caretakers or the homeless. Our intent is to allow
for the delineation of parks and other special land use areas as separate tribal census tracts and therefore
we will accept such areas as special land use tribal census tracts even if some, but very little, residential
population is present.

66

7.0 Block boundary definition
Each of the legal and statistical boundaries delineated as part of TSAP will be held as 2010 census block
boundaries. Many other features, such as roads, that form closed polygons with other features are also
planned to be held as 2010 block boundaries by the Census Bureau. Other line features are either
ineligible to be 2010 block boundaries (most likely because they do not form a closed polygon with
other features) or are neither planned nor eligible to be held (unassigned). The block boundary
definition tool provides an opportunity for TSAP participants to identify features that are currently
unassigned or planned that they want the Census Bureau to recognize or hold as block boundaries for the
2010 Census. TSAP participants may also identify features they do not want held as block boundaries.
Below is a list of all the feature and boundary types that are currently already planned to be held as 2010
Census tabulation block boundaries and therefore do not need to be noted as suggested holds on the
paper maps. In some instances you may not want a feature to become a 2010 Census tabulation block
boundary such as where there are roads identified in our files as double lined roads. Due to recent
updates to our data, there are now many more roads identified as double line roads that, in the past, were
classified as single line roads. This causes the area in the middle (a median strip for example) to become
a long narrow block. If you do not want the polygon formed by the two road edges to be a separate
2010 Census tabulation block, you may want to consistently flag one of the edges with a “Do Not Hold.”
Note: If any other program sponsored by the Census Bureau uses that line as a boundary, the Census
Bureau will override the “Do Not Hold” status of the line.
Entities: The boundaries, as of January 1, 2010, for each of the entities listed below, are planned 2010
Census tabulation block boundaries and therefore do not have to be flagged as a 2010 block boundary.
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Hawaiian home land
Alaska Native village statistical area
Oklahoma tribal statistical area
state-designated tribal statistical area
Tribal Designated Statistical Area
American Indian joint use area
Alaska Native Regional Corporation
tribal subdivision
tribal census tract
tribal block group
state or state equivalent
county or county equivalent
county subdivision
incorporated place
consolidated city
census designated place
census tract
block group
congressional district
state legislative district (upper chamber)

67

ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

state legislative district (lower chamber)
voting district
elementary school district
secondary school district
unified school district
special school administrative area
urban growth area
military installation
national park service land

Features: The features listed below will qualify as 2010 Census tabulation block boundaries based on
criteria.
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

primary road
secondary road
local neighborhood road, rural road, city street
vehicular trail (road passable only by a 4-wheel drive)
main line railroad feature
perennial water

The TSAP extension provides functionality to make block boundary definitions through the Block
Boundary Definition Tool
found on the TSAP Tools toolbar. In the following example, Lincoln
Street between 3rd and 4th streets is updated from a ‘planned hold boundary’ to a ‘do not hold boundary’
(see below image).

68

After activating the Block Boundary Definition Tool
the line features will turn to a block boundary
definition symbology. Lincoln Street is currently attributed as a Planned hold boundary (see right
image and legend below).

The update is accomplished by positioning the Block Boundary Definition Tool
cursor over the line
segments of interest and clicking once on each segment while holding down the Shift Key. The
symbology for the targeted line segments will immediately change to display Lincoln Street as a ‘do not
hold boundary’.

A single click on an eligible line feature will assign it as a Planned hold boundary. A single click while
pressing the Shift Key will identify a line feature as a Do not hold boundary. Double clicking anywhere
within the data frame will return the line features to their default symbology.

69

8.0 Quality Control and Name Changes
Participants should review their delineations before submitting them to the Census Bureau. The Census
Bureau will review each plan before it is accepted for use in the 2010 Census. Submissions will be
compared against published criteria and standards, and accepted on a case-by-case basis. Criteria checks,
such as population and housing unit thresholds, and minimizing geographically noncontiguous areas, are
included in the QC Tool
for participants to use before submittal. The QC Tool
also offers an
opportunity for participants to justify or explain delineations not meeting population and housing unit
thresholds as well as those areas that are noncontiguous. Justifications for not meeting criteria are found
in Appendix 2
Participants will be prompted to operate the QC Tool
after delineating each entity type. For example,
a participant trying to delineate a tribal block group before having run the QC Tool
on tribal census
tracts will be encouraged with a message box to complete the QC process for tribal census tracts before
continuing (see below image).

After clicking once on the QC Tool
button to activate the tool, the QC window will appear (see
below image). Although the following example scenario is for the QC of Tribal Tracts, the process
described and the accompanying screenshots are similar and applicable to the QC process for all TSAP
entities. When you need to make corrections to your delineations close the QC window and adjust
your shapefiles as necessary with the tools included in the TSAP Extension as presented in the
previous sections of this guidelines document.

70

As seen in the previous image, the queue of the QC window will be empty on first opening. Features
available for QC are identified by clicking the Show All button (see below image).

Features not meeting particular criteria will appear in the queue and may be sorted by clicking one of the
criteria buttons on the left side of the QC window. In the example image below, only the tracts falling
under the population threshold are identified by clicking the Below Population button.

71

To continue the QC process, individual tracts are selected from the queue with a single click. After
selection, unmet thresholds associated with the selected tract will become active in the right pane of the
QC window. Tract 4610T00600 is selected in the below image.

Unmet thresholds should be corrected or explained by either typing directly in or choosing a justification
from the combination text box/pull-down menu (justifications are listed in Appendix 2). After entering a
justification, the corresponding threshold button (e.g. in the above image the Below 1,200 Pop, Below
480 HUs buttons) must be pressed to accept the update and populate the attributes of the shapefile. (See
below image.)

TOOL TIP
Use the Zoom and scroll buttons to navigate through the features. The Zoom button will change the data frame to
the extent of the selected feature.

72

After a feature has been justified it will no longer be available from the queue for that particular
threshold (e.g. after accepting a Below 1,200 Pop justification, tract 4610T00600 will no longer appear
in the Below Population queue). Justifications may be reviewed by clicking the Show All button,
selecting the feature of interest, and clicking the View Justification button at the bottom of the QC
window. In the example below tract 4610T00600 is selected and the justification is visible.

Once the population and housing unit thresholds have undergone the QC checks, and have either been
corrected or justified, participants are encouraged to check their delineations for noncontiguous areas.
Noncontiguous areas are those entities which are comprised of several disconnected polygons (i.e.
multipart features in shapefiles). The noncontiguous area QC is activated by clicking on the
Noncontiguous button on the lower left of the QC window (as shown in the previous screenshots). After
activation, a Noncontiguous Parts pane appears on the left side of the QC window. Only one part per
feature needs justification.

73

A convenient tool for reviewing noncontiguous areas is the Zoom
tool. When reviewing
noncontiguous areas you will often find that some noncontiguous parts are not immediately visible on
screen. This is due to small census blocks that often occur at the intersection of line features such as non
visible boundaries, water features, and urban/developed areas. Clicking on the zoom button will allow
you to quickly locate those hard-to-see noncontiguous parts. Most noncontiguous parts should be
corrected by assigning them to the immediately adjacent statistical area.
After completing the noncontiguous areas portion of the QC process clicking the Show All button will
return the default QC window. The final component of the QC process involves identifying empty
shapefile records that may have resulted from the merging, splitting, and geographic assignment tasks
associated with delineating. Click the Show Empty Shapes button to identify these records and click the
Remove Empty Shapes button to delete these records from your shapefiles (the buttons are found in the
lower left corner of the QC window).
Upon completing the entire QC process the red Review button is clicked. Provided all QC is completed
correctly, the red Review button will become a green Complete button (see below image).

If the review is incomplete or incorrect a message box will pop-up identifying the threshold or criteria
still needing review (see example in bottom image).

TOOL TIP
and the Find Unassigned Areas Tool
both available on the TSAP
The Find Noncontiguous Areas Tool
Tools toolbar may be used outside of a formal QC Tool session to identify potential geography errors.

74

Name Changes
Aside from tribal census tracts and tribal block groups, all TSAP entities may submit name changes or
corrections. Name changes are accomplished during the QC process. The option to change an entity’s
name will be the first item in the QC Tool window for ANVSAs, OTSAs, CDPs, TDSAs, SDTSAs, and
State reservations. After typing in an updated name in the left justified text box click the Change Name
button to update your delineations. Examples of the QC Tool window for ANVSAs and CDPs with the
Change Name option visible are pictured below.
If you do choose to change the name of your tribal statistical area, the Census Bureau additionally
requests that you report your name change to the RCC (RCC contact information is found in
Appendix 5).

75

9.0 Submitting your data
Delineations are finalized and prepared for submission with the Submit Data Tool
on the TSAP
Management toolbar. This tool assembles and exports the necessary shapefiles into an Output directory
in your local workspace. The finalized delineations exported to the Output directory are the shapefiles
of your delineations that the Census Bureau will review before the verification phase of the 2010 Census.
Upon activating the Submit Data Tool
with a single click a
message box will immediately appear to confirm your submission
(see right image). After clicking Yes, the necessary shapefiles will
be assembled and exported to the Output directory that will reside
within the original workspace of your project. A second message
box will appear listing the local path name to your Output directory
(see below image). Please make note of the Workspace directory, as you need to navigate to it in the
next step in the submittal process.

At this point the TSAP Workflow Manager will appear similar to the below image.

76

An example Output directory is pictured below in Windows Explorer. It is recommended the Output
directory be compressed, or “zipped”, with a file compression utility before electronic submission to the
Census Bureau (see section 9.1).

77

9.1 Compressing the files for submittal
To prepare your files for submittal, please locate your work output folder, in this example:
C:\TSAPExtension\Data\Output folder and compress it into a single “zip” file, using the provided utility,
Freebyte Zip. The compression utility is located on the TSAP Data CD, and named “fbzpack.exe”.
Please do not use WinZip to compress the files, as some older versions of the program may corrupt
shapefiles.
To install fbzpack.exe, copy the file “fbzpack.exe” to the TSAPExtensionData directory, and doubleclick on the file to run the installation. You may get a pop up warning; please click “Run” (see image
below) to continue the installation.

At the next prompt, make sure all three files are highlighted and click “Start” to continue (see image
below).

78

Click OK to complete the installation.

To begin using the program and compress your output files for submittal, navigate to the FBZip.exe
program (below) and double-click.

After the Starting Freebyte ZIP program window appears, select Create a new ZIP archive (see image
below).

Select

79

You are then presented with a prompt to “Save new ZIP archive as” (below).

Navigate to the Workspace directory, noted previously and using your project’s entity code, name the
zip file TSAP and select Save (The entity code is the same as the Census Area Code
found in Tables A-D of Appendix 1: Table A. Federally Recognized Tribes, Table B. Alaska Native
Villages, Table C. Federally Recognized Tribes in Oklahoma with former American Indian reservation
in Oklahoma, Table D. State Recognized Tribes). You will then be prompted to “Add files or folders to
zip archive” (see image below).

Please make sure that your selections match the above image, then select Add folder.

80

You will then be prompted to add a directory to your archive (image below). Select the directory named
TSAP_Complete then click OK.

You should now transfer the resulting zip file to the Census Bureau using the instructions in the next
section.

9.2 Transferring your data to the Census Bureau
Submissions will be accepted via the Census Bureau’s Public File Send Utility (pictured on the next
page) found online at:
http://www2.census.gov/cgi-bin/sendfile
Use the following steps to send your files to us via the Public File Send Utility (see the following page
for a screenshot of the website):
1. Under Source Information (Local), click on the Browse button to navigate to your zip folder created
in the previous section containing your delineations (named TSAP_Complete).
2. In the Target Information (Remote) section, enter /geo/2010_PSAP_TSAP/ in the Directory to
Receive File.
3. Under the Notify by E-mail, type your e-mail address in the Sender’s E-mail Address. In the Census
Bureau Employee’s E-mail Address field enter geo.tsap.list@census.gov.
4. Type in the Verification Code that you see in the box at the screen and click Upload to send your file.
Additional contact information for the Regional Census Center that will process your submission is
found in Appendix 5 of this document.

81

82

10.0 Verification
As long as a submission for TSAP is received by the Census Bureau within the 120 day schedule, each
participating tribe will be eligible for a verification phase. During verification, the Census Bureau
provides new materials to reflect how we inserted the submitted tribal statistical area delineations into
our database. The verification materials will be provided in late 2009. At that time, tribes may review
the new areas and as needed make minor boundary corrections. Digital participants will be provided
with shapefiles for their verification review process.

83

Appendix 1. American Indian and Alaska Native Tribe and Eligibility Listings
Table A. Federally Recognized American Indian Tribes
Tribe Name

Area Name

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Jamul Indian Village
Jamul Indian Village 1670
Washoe Tribe (Woodfords Woodfords
4665
Community)
Community

1
219

1 CDP, BDP
61 CDP, BDP

Yavapai-Apache Nation of
the Camp Verde Indian
Reservation
Yavapai-Prescott Tribe of
the Yavapai Reservation
Yerington Paiute Tribe of
the Yerington Colony &
Campbell Ranch
Hannahville Indian
Community
Pueblo of Zia

Inaja Band of Diegueno
Mission Indians of the
Inaja and Cosmit
Reservation
Bay Mills Indian
Community
Grand Traverse Band of
Ottawa & Chippewa
Indians
Yomba Shoshone Tribe of
the Yomba Reservation
Te-Moak Tribe of Western
Shoshone Indians (Wells
Band)
Fort Independence Indian
Community of Paiute
Indians of the Fort
Independence Reservation
Washoe Tribe
La Jolla Band of Luiseno
Mission Indians of the La
Jolla Reservation
Walker River Paiute Tribe
of the Walker River
Reservation
Skull Valley Band of
Goshute Indians

Regional
Census
Center
Los Angeles
Denver

Yavapai-Apache
Nation Reservation

4708

743

197 CDP, BDP

Denver

Yavapai-Prescott
Reservation
Yerington Colony

4710

182

60 CDP, BDP

Denver

4725

139

54 CDP, BDP

Denver

1410

395

109 CDP, BDP

Detroit

4770

646

189 CDP, BDP

Denver

1560

0

0 CDP, BDP

Bay Mills Reservation 0170

812

333 CDP, BDP

Detroit

Grand Traverse
Reservation

1370

545

166 CDP, BDP

Detroit

Yomba Reservation

4740

96

36 CDP, BDP

Denver

Wells Colony

4580

54

24 CDP, BDP

Denver

Fort Independence
Reservation

1195

86

42 CDP, BDP

Los Angeles

Washoe Ranches
La Jolla Reservation

4560
1850

0
390

0 CDP, BDP
143 CDP, BDP

Denver
Los Angeles

Walker River
Reservation

4515

853

339 CDP, BDP

Denver

Skull Valley
Reservation

3840

31

11 CDP, BDP

Denver

Hannahville
Community
Zia Pueblo and OffReservation Trust
Land
Inaja and Cosmit
Reservation

Los Angeles

84

Tribe Name

Area Name

Tonto Apache Tribe

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Tonto Apache
Reservation
Pueblo of Tesuque
Tesuque Pueblo
Seminole Tribe
Tampa Reservation
Summit Lake Paiute Tribe Summit Lake
Reservation
La Posta Band of Diegueno La Posta Reservation
Mission Indians of the La
Posta Indian Reservation
Washoe Tribe (Stewart
Stewart Community
Community)
Paiute-Shoshone Indians of Lone Pine
the Lone Pine Community Reservation
of the Lone Pine
Reservation
Te-Moak Tribe of Western South Fork
Shoshone Indians (South Reservation
Fork Band)
Winnemucca Indian
Winnemucca Colony
Colony
Minnesota Chippewa Tribe Minnesota Chippewa
Trust Land
Big Sandy Rancheria of
Big Sandy Rancheria
Mono Indians
Big Pine Band of Owens Big Pine Reservation
Valley Paiute Shoshone
Indians of the Big Pine
Reservation

4235

132

38 CDP, BDP

Denver

4170
4130
4045

806
0
15

327 CDP, BDP
0 CDP, BDP
15 CDP, BDP

Denver
Atlanta
Denver

1895

18

6 CDP, BDP

3980

196

62 CDP, BDP

1970

212

100 CDP, BDP

3930

123

62 CDP, BDP

Denver

4635

62

21 CDP, BDP

Denver

2285

78

43 CDP, BDP

Kansas City

0265

98

34 CDP, BDP

Los Angeles

0250

462

181 CDP, BDP

Los Angeles

Capitan Grande Band of
Barona Reservation
Diegueno Mission Indians:
Barona Group of Capitan
Grande Band of Mission
Indians of the Barona
Reservation

0155

536

162 CDP, BDP

Los Angeles

Augustine Band of
Cahuilla Indians
Upper Sioux Community

Augustine
Reservation
Upper Sioux
Reservation
Shakopee
Mdewakanton Sioux
Community
Cabazon Reservation

0125

0

0 CDP, BDP

Los Angeles

4445

57

31 CDP, BDP

Kansas City

3680

338

120 CDP, BDP

Kansas City

0415

806

192 CDP, BDP

Los Angeles

Sandy Lake
Reservation
Sac and Fox
Reservation

3385

70

22 CDP, BDP

Kansas City

3285

217

79 CDP, BDP

Kansas City

Shakopee Mdewakanton
Sioux Community
Cabazon Band of Mission
Indians
Minnesota Chippewa Tribe
(Mille Lacs Band)
Sac & Fox Nation of
Missouri in Kansas and
Nebraska

Los Angeles

Denver
Los Angeles

85

Tribe Name

Area Name

Sac & Fox Tribe of the
Mississippi in Iowa

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Sac and
Fox/Meskwaki
Reservation
Prairie Island Indian
Prairie Island Indian
Community
Community
Nottawaseppi Huron Band Huron Potawatomi
of the Potawatomi
Reservation
Campo Band of Diegueno Campo Reservation
Mission Indians of the
Campo Indian Reservation
Cold Springs Rancheria of Cold Springs
Mono Indians
Rancheria
Lower Sioux Indian
Lower Sioux
Community of Minnesota Reservation
Mdewakanton Sioux
Indians of the Lower Sioux
Reservation

3280

761

267 CDP, BDP

Kansas City

2985

199

65 CDP, BDP

Kansas City

1550

11

7 CDP, BDP

0450

351

111 CDP, BDP

Los Angeles

0720

193

46 CDP, BDP

Los Angeles

2055

335

116 CDP, BDP

Kansas City

Iowa Tribe of Kansas and
Nebraska
Capitan Grande Band of
Diegueno Mission Indians:
Barona Group of Capitan
Grande Band of Mission
Indians of the Barona
Reservation

Iowa (KS-NE)
Reservation
Capitan Grande
Reservation

1590

168

67 CDP, BDP

Kansas City

0495

0

0 CDP, BDP

Los Angeles

Minnesota Chippewa Tribe
(Grand Portage Band)
Minnesota Chippewa Tribe
(Bois Forte Band (Nett
Lake))
Capitan Grande Band of
Diegueno Mission Indians:
Viejas (Baron Long) Group
of Capitan Grande Band of
Mission Indians of the
Viejas Reservation

Grand Portage
Reservation
Bois Forte
Reservation

1355

557

286 CDP, BDP

Kansas City

0335

657

398 CDP, BDP

Kansas City

Capitan Grande
Reservation

0495

0

0 CDP, BDP

Los Angeles

Pokagon Band of
Potawatomi Indians
Keweenaw Bay Indian
Community of L'Anse and
Ontonagon Bands
Little Traverse Bay Bands
of Odawa Indians
Ewiiaapaayp Band of
Kumeyaay Indians
Little River Band of
Ottawa Indians

Pokagon Reservation 2890

0

0 CDP, BDP

Detroit

Ontonagon
Reservation

2580

0

0 CDP, BDP

Detroit

Little Traverse Bay
Reservation
Ewiiaapaayp
Reservation
Little River
Reservation

1963

0

0 CDP, BDP

Detroit

1065

0

0 CDP, BDP

Los Angeles

1960

2

2 CDP, BDP

Detroit

Detroit

86

Tribe Name

Lac Vieux Desert Band of
Lake Superior Chippewa
Indians
Cahuilla Band of Mission
Indians of the Cahuilla
Reservation
Narragansett Indian Tribe
Passamaquoddy Tribe Indian Township
Reservation
Sokaogon Chippewa
Community of Chippewa
Indians
St. Croix Chippewa Indians
Red Cliff Band of Lake
Superior Chippewa Indians
Ho-Chunk Nation
Forest County Potawatomi
Community
Wampanoag Tribe of Gay
Head
Tuscarora Nation
Tonawanda Band of
Seneca Indians
Passamaquoddy Tribe Pleasant Point Reservation
Penobscot Tribe

Area Name

Lac Vieux Desert
Reservation

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

1830

135

50 CDP, BDP

Detroit

Cahuilla Reservation 0435

154

56 CDP, BDP

Los Angeles

2415

60

20 CDP, BDP

Boston

1575

676

261 CDP, BDP

Boston

Sokaogon Chippewa 3885
Community

392

167 CDP, BDP

Chicago

St. Croix Reservation 3305
Red Cliff Reservation 3085

641
1,078

208 CDP, BDP
429 CDP, BDP

Chicago
Chicago

1450

960

349 CDP, BDP

Chicago

1135

531

174 CDP, BDP

Chicago

4530

91

34 CDP, BDP

Boston

4360

1,138

398 CDP, BDP

Boston

4225

543

197 CDP, BDP

Boston

2850

640

256 CDP, BDP

Boston

2760

584

364 CDP, BDP

Boston

2695

0

88 CDP, BDP

Boston

2695

0

88 CDP, BDP

Boston

0050

480

203 CDP, BDP

Dallas

2240

0

0 CDP, BDP

Atlanta

0575

691

214 CDP, BDP

Seattle

1995

70

23 CDP, BDP

0360

566

216 CDP, BDP

Narragansett
Reservation
Indian Township
Reservation

Ho-Chunk Nation
Reservation
Forest County
Potawatomi
Community
WampanoagAquinnah
Tuscarora
Reservation
Tonawanda
Reservation
Pleasant Point
Reservation
Penobscot
Reservation
Passamaquoddy Trust
Land
Passamaquoddy Trust
Land

Passamaquoddy Tribe Pleasant Point Reservation
Passamaquoddy Tribe Indian Township
Reservation
Alabama-Coushatta Tribes Alabama-Coushatta
Reservation
Miccosukee Tribe of
Miccosukee
Indians
Reservation
Confederated Tribes of the Chehalis Reservation
Chehalis Reservation
Los Coyotes Band of
Los Coyotes
Cahuilla and Cupeno
Reservation
Indians
Seminole Tribe
Brighton Reservation

Los Angeles

Atlanta

87

Tribe Name

Seminole Tribe

Area Name

Big Cypress
Reservation
Seminole Tribe
Coconut Creek Trust
Land
Oneida Nation
Oneida (NY)
Reservation
Seminole Tribe
Immokalee
Reservation
Seneca Nation
Oil Springs
Reservation
Poarch Band of Creek
Poarch Creek
Indians
Reservation
Seminole Tribe
Seminole Trust Land
Houlton Band of Maliseet Houlton Maliseet
Indians
Reservation
Mashantucket Pequot Tribe Mashantucket Pequot
Reservation
Mohegan Indian Tribe
Mohegan Reservation
Chitimacha Tribe
Chitimacha
Reservation
Seminole Tribe
Fort Pierce
Reservation
Flandreau Santee Sioux
Flandreau
Tribe
Reservation
Pueblo of Santa Ana
Santa Ana Pueblo
Reno-Sparks Indian
Reno-Sparks Colony
Colony
Ponca Tribe of Nebraska Ponca (NE) Trust
Land
Paiute Indian Tribe
Paiute (UT)
Reservation
Northwestern Band of
Northwestern
Shoshone Nation
Shoshone Reservation
(Washakie)
Moapa Band of Paiute
Moapa River
Indians of the Moapa River Reservation
Indian Reservation
Ak Chin Indian
Maricopa (Ak Chin)
Community of the
Reservation
Maricopa (Ak Chin) Indian
Reservation
Lovelock Paiute Tribe of Lovelock Colony
the Lovelock Indian
Colony
Las Vegas Tribe of Paiute Las Vegas Colony
Indians of the Las Vegas
Indian Colony

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

0225

142

55 CDP, BDP

Atlanta

0690

0

0 CDP, BDP

Atlanta

2555

26

20 CDP, BDP

Boston

1555

175

62 CDP, BDP

Atlanta

2535

11

20 CDP, BDP

Boston

2865

211

101 CDP, BDP

Atlanta

3665
1530

0
136

0 CDP, BDP
54 CDP, BDP

Atlanta
Boston

2145

325

114 CDP, BDP

Boston

2320
0635

2
409

1 CDP, BDP
168 CDP, BDP

Boston
Dallas

1260

2

1 CDP, BDP

Atlanta

1100

408

137 CDP, BDP

Denver

3480
3130

487
881

197 CDP, BDP
282 CDP, BDP

Denver
Denver

2900

0

0 CDP, BDP

Denver

2625

270

84 CDP, BDP

Denver

2505

0

0 CDP, BDP

Denver

2315

206

90 CDP, BDP

Denver

2130

742

234 CDP, BDP

Denver

2015

103

38 CDP, BDP

Denver

1915

108

37 CDP, BDP

Denver

88

Tribe Name

Kaibab Band of Paiute
Indians of the Kaibab
Indian Reservation
Havasupai Tribe of the
Havasupai Reservation
Confederated Tribes of the
Goshute Reservation
Fort Mojave Indian Tribe
Catawba Indian Nation
Washoe Tribe
(Dresslerville Colony)
Coushatta Tribe

Area Name

Kaibab Reservation

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

1720

196

88 CDP, BDP

Denver

Havasupai
1440
Reservation
Goshute Reservation 1340

503

161 CDP, BDP

Denver

105

45 CDP, BDP

Denver

1,043

416 CDP, BDP

Denver

494
315

174 CDP, BDP
116 CDP, BDP

Charlotte
Denver

Fort Mojave
1235
Reservation
Catawba Reservation 0525
Dresslerville Colony 0940

Coushatta
Reservation
Kickapoo Traditional Tribe Kickapoo (TX)
Reservation
Tunica-Biloxi Indian Tribe Tunica-Biloxi
Reservation
Ysleta Del Sur Pueblo
Ysleta Del Sur Pueblo
Te-Moak Tribe of Western Battle Mountain
Shoshone Indians (Battle Reservation
Mountain Band)
Fort McDowell Yavapai
Fort McDowell
Nation
Reservation
Washoe Tribe (Carson
Carson Colony
Colony)
Fort McDermitt Paiute and Fort McDermitt
Shoshone Tribes of the
Reservation
Fort McDermitt Indian
Reservation

0795

25

14 CDP, BDP

Dallas

1775

420

104 CDP, BDP

Dallas

4315

89

34 CDP, BDP

Dallas

4755
0165

421
124

116 CDP, BDP
63 CDP, BDP

Dallas
Denver

1220

824

275 CDP, BDP

Denver

0510

286

105 CDP, BDP

Denver

1210

309

119 CDP, BDP

Denver

Duckwater Shoshone Tribe
of the Duckwater
Reservation
Te-Moak Tribe of Western
Shoshone Indians (Elko
Band)
Ely Shoshone Tribe
Paiute-Shoshone Tribe of
the Fallon Reservation and
Colony
Paiute-Shoshone Tribe of
the Fallon Reservation and
Colony
Santee Sioux Nation
Yerington Paiute Tribe of
the Yerington Colony &
Campbell Ranch

Duckwater
Reservation

0975

149

65 CDP, BDP

Denver

Elko Colony

1005

729

257 CDP, BDP

Denver

Ely Reservation
Fallon PaiuteShoshone Colony

1040
1070

133
123

67 CDP, BDP
51 CDP, BDP

Denver
Denver

Fallon Paiute1075
Shoshone Reservation

620

256 CDP, BDP

Denver

Santee Reservation
Campbell Ranch

878
446

368 CDP, BDP
80 CDP, BDP

Denver
Denver

3565
0440

89

Tribe Name

Area Name

Census Census 2000
Area Population
Code

Confederated Tribes of the
Coos, Lower Umpqua and
Siuslaw Indians
Lytton Rancheria
Quileute Tribe of the
Quileute Reservation
Chicken Ranch Rancheria
of Me-Wuk Indians
Cachil DeHe Band of
Wintun Indians of the
Colusa Indian Community
of the Colusa Rancheria

Coos, Lower
0770
Umpqua, and Siuslaw
Reservation
Lytton Rancheria
2075
Quileute Reservation 3030

Pit River Tribe
Guidiville Rancheria
Nisqually Indian Tribe of
the Nisqually Reservation
Bear River Band of the
Rohnerville Rancheria
Middletown Rancheria of
Pomo Indians
Cher-Ae Heights Indian
Community of the Trinidad
Rancheria
Coquille Tribe
Cortina Indian Rancheria
of Wintun Indians
Wiyot Tribe
Lower Elwha Tribal
Community of the Lower
Elwha Reservation
Cow Creek Band of
Umpqua Indians
Robinson Rancheria of
Pomo Indians
Mooretown Rancheria of
Maidu Indians
Klamath Tribes
United Auburn Indian
Community
Tuolumne Band of MeWuk Indians of the
Tuolumne Rancheria
Utu Utu Gwaitu Paiute
Tribe of the Benton Paiute
Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

25

9 CDP, BDP

Seattle

0
371

0 CDP, BDP
128 CDP, BDP

Seattle
Seattle

0620

11

4 CDP, BDP

Seattle

0750

77

25 CDP, BDP

Seattle

Roaring Creek
3185
Rancheria
Guidiville Rancheria 1400
Nisqually Reservation 2460

9

5 CDP, BDP

Seattle

2
588

1 CDP, BDP
178 CDP, BDP

Seattle
Seattle

3220

98

29 CDP, BDP

Seattle

2255

73

20 CDP, BDP

Seattle

4275

73

37 CDP, BDP

Seattle

Coquille Reservation 0775
Cortina Rancheria
0780

258
19

98 CDP, BDP
9 CDP, BDP

Seattle
Seattle

Chicken Ranch
Rancheria
Colusa Rancheria

Rohnerville
Rancheria
Middletown
Rancheria
Trinidad Rancheria

Table Bluff
Reservation
Lower Elwha
Reservation

4095

97

35 CDP, BDP

Seattle

2040

315

99 CDP, BDP

Seattle

Cow Creek
Reservation
Robinson Rancheria

0815

22

8 CDP, BDP

Seattle

3195

153

43 CDP, BDP

Seattle

Mooretown Rancheria 2340

166

52 CDP, BDP

Seattle

Klamath Reservation 1785
Auburn Rancheria
0120

9
0

6 CDP, BDP
0 CDP, BDP

Seattle
Seattle

Tuolumne Rancheria 4330

168

68 CDP, BDP

Seattle

50

30 CDP, BDP

Seattle

Benton Paiute
Reservation

0185

90

Tribe Name

Berry Creek Rancheria of
Maidu Indians
Pit River Tribe
Manchester Band of Pomo
Indians of the ManchesterPoint Arena Rancheria
Big Valley Band of Pomo
Indians of the Big Valley
Rancheria
Confederated Tribes of the
Warm Springs Reservation
Blue Lake Rancheria
Bridgeport Paiute Indian
Colony
Burns Paiute Tribe of the
Burns Paiute Indian
Colony
Cedarville Rancheria
Confederated Tribes and
Bands of the Yakama
Nation
Pit River Tribe
Elem Indian Colony of
Pomo Indians of the
Sulphur Bank Rancheria
Big Lagoon Rancheria

Area Name

Berry Creek
Rancheria
Big Bend Rancheria
Manchester-Point
Arena Rancheria

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

0200

138

40 CDP, BDP

Seattle

0215
2100

0
197

0 CDP, BDP
65 CDP, BDP

Seattle
Seattle

Big Valley Rancheria 0275

225

64 CDP, BDP

Seattle

0560

44

22 CDP, BDP

Seattle

Blue Lake Rancheria 0325
Bridgeport
0350
Reservation
Burns Paiute Colony 0400

78
43

41 CDP, BDP
21 CDP, BDP

Seattle
Seattle

171

57 CDP, BDP

Seattle

Cedarville Rancheria 0555
Celilo Village
0560

26
44

9 CDP, BDP
22 CDP, BDP

Seattle
Seattle

Celilo Village

Montgomery Creek
Rancheria
Sulphur Bank
Rancheria

2330

5

2 CDP, BDP

Seattle

4030

69

15 CDP, BDP

Seattle

Big Lagoon
Rancheria
Hopland Rancheria

0240

24

9 CDP, BDP

Seattle

1515

45

18 CDP, BDP

Seattle

4060

298

95 CDP, BDP

Seattle

3115

263

87 CDP, BDP

Seattle

1955
2115

0
69

0 CDP, BDP
29 CDP, BDP

Seattle
Los Angeles

1925

188

61 CDP, BDP

Seattle

0560

44

22 CDP, BDP

Seattle

3250

300

108 CDP, BDP

Seattle

Hopland Band of Pomo
Indians of the Hopland
Rancheria
Susanville Indian
Susanville Rancheria
Rancheria
Redwood Valley Rancheria Redwood Valley
of Pomo Indians
Rancheria
Reservation
Pit River Tribe
Likely Rancheria
Manzanita Band of
Manzanita
Diegueno Mission Indians Reservation
of the Manzanita
Reservation
Cahto Indian Tribe of the Laytonville Rancheria
Laytonville Rancheria
Confederated Tribes of the Celilo Village
Umatilla Reservation
Round Valley Indian
Round Valley
Tribes of the Round Valley Reservation
Reservation

91

Tribe Name

Sherwood Valley
Rancheria of Pomo Indians
Greenville Rancheria of
Maidu Indians
Jackson Rancheria of MeWuk Indians
Jamestown S'Klallam Tribe

Area Name

Census Census 2000
Area Population
Code

Sherwood Valley
3735
Rancheria
Greenville Rancheria 1380

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

179

49 CDP, BDP

Seattle

22

9 CDP, BDP

Seattle

1640

2

1 CDP, BDP

Seattle

Jamestown S'Klallam 1655
Reservation
Kalispel Reservation 1735

16

8 CDP, BDP

Seattle

206

63 CDP, BDP

Seattle

3625

45

16 CDP, BDP

Seattle

3265

36

11 CDP, BDP

Seattle

1750
1800
1460

333
75
102

124 CDP, BDP
24 CDP, BDP
33 CDP, BDP

Seattle
Seattle
Seattle

3855

62

21 CDP, BDP

Seattle

2475

547

142 CDP, BDP

Seattle

0955

53

15 CDP, BDP

Seattle

4000

102

31 CDP, BDP

Seattle

1010
1055

77
1

36 CDP, BDP
1 CDP, BDP

Seattle
Seattle

3985

57

17 CDP, BDP

Seattle

1395

162

49 CDP, BDP

Seattle

3860

0

0 CDP, BDP

Seattle

0825

104

31 CDP, BDP

Seattle

3825

730

279 CDP, BDP

Seattle

1980
1170

7
108

5 CDP, BDP
47 CDP, BDP

Seattle
Seattle

Jackson Rancheria

Kalispel Indian
Community of the Kalispel
Reservation
Sauk-Suiattle Indian Tribe Sauk-Suiattle
Reservation
Rumsey Indian Rancheria Rumsey Rancheria
of Wintun Indians
Karuk Tribe
Karuk Reservation
Kootenai Tribe
Kootenai Reservation
Hoh Indian Tribe of the
Hoh Reservation
Hoh Indian Reservation
Smith River Rancheria
Smith River
Rancheria
Nooksack Indian Tribe
Nooksack
Reservation
Dry Creek Rancheria of
Dry Creek Rancheria
Pomo Indians
Stillaguamish Tribe
Stillaguamish
Reservation
Elk Valley Rancheria
Elk Valley Rancheria
Enterprise Rancheria of
Enterprise Rancheria
Maidu Indians
Kashia Band of Pomo
Stewarts Point
Indians of the Stewarts
Rancheria
Point Rancheria
Grindstone Indian
Grindstone Rancheria
Rancheria of WintunWailaki Indians
Snoqualmie Tribe
Snoqualmie
Reservation
Coyote Valley Band of
Coyote Valley
Pomo Indians
Reservation
Skokomish Indian Tribe of Skokomish
the Skokomish Reservation Reservation
Pit River Tribe
Lookout Rancheria
Fort Bidwell Indian
Fort Bidwell
Community of the Fort
Reservation
Bidwell Reservation

92

Tribe Name

Confederated Tribes of the
Siletz Reservation
Shoalwater Bay Tribe of
the Shoalwater Bay Indian
Reservation
Confederated Tribes of the
Grand Ronde Community
Shingle Springs Band of
Miwok Indians, Shingle
Springs Rancheria (Verona
Tract)

Area Name

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Siletz Reservation

3795

308

104 CDP, BDP

Seattle

Shoalwater Bay
Reservation

3780

70

35 CDP, BDP

Seattle

Grand Ronde
Community
Shingle Springs
Rancheria

1365

55

19 CDP, BDP

Seattle

3750

57

16 CDP, BDP

Seattle

Squaxin Island Tribe of the Squaxin Island
Squaxin Island Reservation Reservation
Capitan Grande Band of
Viejas Reservation
Diegueno Mission Indians:
Viejas (Baron Long) Group
of Capitan Grande Band of
Mission Indians of the
Viejas Reservation

3955

405

127 CDP, BDP

Seattle

4500

394

148 CDP, BDP

Los Angeles

Alturas Indian Rancheria
Resighini Rancheria
Twenty-Nine Palms Band
of Mission Indians
Tule River Indian Tribe of
the Tule River Reservation
Redding Rancheria
Death Valley Timbi-Sha
Shoshone Band
Table Mountain Rancheria

Alturas Rancheria
Resighini Rancheria
Twenty-Nine Palms
Reservation
Tule River
Reservation
Redding Rancheria
Timbi-Sha Shoshone
Reservation
Table Mountain
Rancheria
Sycuan Reservation

0095
3145
4375

2
36
0

2 CDP, BDP
6 CDP, BDP
0 CDP, BDP

Seattle
Seattle
Los Angeles

4300

566

179 CDP, BDP

Los Angeles

3095
4180

45
0

17 CDP, BDP
0 CDP, BDP

Seattle
Los Angeles

4110

11

4 CDP, BDP

Los Angeles

4090

33

14 CDP, BDP

Los Angeles

Santa Ysabel
Reservation

3550

250

102 CDP, BDP

Los Angeles

Santa Ynez
Reservation

3540

122

42 CDP, BDP

Los Angeles

Santa Rosa
3525
Reservation
Santa Rosa Rancheria 3520

65

25 CDP, BDP

Los Angeles

517

125 CDP, BDP

Los Angeles

752

228 CDP, BDP

Los Angeles

Sycuan Band of the
Kumeyaay Nation
Santa Ysabel Band of
Diegueno Mission Indians
of the Santa Ysabel
Reservation
Santa Ynez Band of
Chumash Mission Indians
of the Santa Ynez
Reservation
Santa Rosa Band of
Cahuilla Indians
Santa Rosa Indian
Community of the Santa
Rosa Rancheria
San Pasqual Band of
Diegueno Mission Indians

San Pasqual
Reservation

3460

93

Tribe Name

Pit River Tribe
Paskenta Band of Nomlaki
Indians
Mesa Grande Band of
Diegueno Mission Indians
of the Mesa Grande
Reservation
Soboba Band of Luiseno
Indians of the Soboba
Reservation
Northfork Rancheria of
Mono Indians
San Manuel Band of
Serrano Mission Indians of
the San Manuel
Reservation
Pauma Band of Luiseno
Mission Indians of the
Pauma & Yuima
Reservation
Habematolel Pomo of
Upper Lake
Upper Skagit Indian Tribe

Area Name

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

XL Ranch Rancheria 4680
Paskenta Rancheria 2685

14
0

13 CDP, BDP
0 CDP, BDP

Seattle
Seattle

Mesa Grande
Reservation

2190

75

19 CDP, BDP

Los Angeles

Soboba Reservation

3870

522

173 CDP, BDP

Los Angeles

North Fork Rancheria 2495

9

2 CDP, BDP

Los Angeles

San Manuel
Reservation

3445

74

27 CDP, BDP

Los Angeles

Pauma and Yuima
Reservation

2715

186

53 CDP, BDP

Los Angeles

4430

82

34 CDP, BDP

Seattle

4455

238

76 CDP, BDP

Seattle

2820
2745

136
467

42 CDP, BDP
163 CDP, BDP

Seattle
Los Angeles

2835
2775

9
20

4 CDP, BDP
16 CDP, BDP

Seattle
Los Angeles

2910

699

226 CDP, BDP

Seattle

3020

126

58 CDP, BDP

Seattle

3070

0

0 CDP, BDP

Los Angeles

2360

954

345 CDP, BDP

Los Angeles

8300

8

4 TDSA

Seattle

0000

0

0 TDSA

Seattle

8450

3,198

1,162 TDSA

Seattle

Upper Lake
Rancheria
Upper Skagit
Reservation
Pinoleville Pomo Nation
Pinoleville Rancheria
Pechanga Band of Luiseno Pechanga Reservation
Mission Indians of the
Pechanga Reservation
Pit River Tribe
Pit River Trust Land
Picayune Rancheria of
Picayune Rancheria
Chukchansi Indians
Port Gamble Indian
Port Gamble
Community of the Port
Reservation
Gamble Reservation
Quartz Valley Indian
Quartz Valley
Community of the Quartz Reservation
Valley Reservation
Ramona Band or Village of Ramona Village
Cahuilla Mission Indians
Morongo Band of Cahuilla Morongo Reservation
Mission Indians of the
Morongo Reservation
Ione Band of Miwok
Ione Band of Miwok
Indians
TDSA
Scotts Valley Band of
Tribal Area
Pomo Indians
Placeholder
Mechoopda Indian Tribe of Mechoopda TDSA
Chico Rancheria

94

Tribe Name

Area Name

Buena Vista Rancheria of
Me-Wuk Indians
California Valley Miwok
Tribe
Cloverdale Rancheria of
Pomo Indians
Cowlitz Indian Tribe

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Federated Indians of
Tribal Area
Graton Rancheria
Placeholder
Samish Indian Tribe
Samish TDSA
Potter Valley Tribe
Tribal Area
Placeholder
Match-e-be-nash-she-wish Tribal Area
Band of Pottawatomi
Placeholder
Indians
Mashpee Wampanoag
Tribal Area
Tribe
Placeholder
Cayuga Nation of New
Cayuga Nation TDSA
York
Lower Lake Rancheria
Tribal Area
Placeholder
Seneca Nation
Allegany Reservation

0000

0

0 TDSA

Seattle

0000

0

0 TDSA

Seattle

0000

0

0 TDSA

Seattle

0000

0

0 TDSA

Seattle

0000

0

0 TDSA

Seattle

8750
0000

33,265
0

18,901 TDSA
0 TDSA

Seattle
Seattle

0000

0

0 TDSA

Detroit

0000

0

0 TDSA

Boston

8100

10,707

4,906 TDSA

Boston

0000

0

0 TDSA

Seattle

0080

6,804

Eastern Band of Cherokee Eastern Cherokee
Indians
Reservation

0990

8,092

Oneida Tribe of Indians

Oneida (WI)
Reservation

2560

21,321

Menominee Indian Tribe

Menominee
Reservation

2175

3,225

Lac du Flambeau Band of
Lake Superior Chippewa
Indians of the Lac du
Flambeau Reservation

Lac du Flambeau
Reservation

1825

2,995

Lac Courte Oreilles Band Lac Courte Oreilles
of Lake Superior Chippewa Reservation
Indians
Saint Regis Mohawk Tribe St. Regis Mohawk
Reservation

1815

2,900

3320

2,699

Swinomish Indians of the
Swinomish Reservation

4075

2,664

Swinomish
Reservation

3,035 Tribal Tracts,
Tribal BG,
CDP, BDP
3,194 Tribal Tracts,
Tribal BG,
CDP, BDP
7,559 Tribal Tracts,
Tribal BG,
CDP, BDP
932 Tribal Tracts,
Tribal BG,
CDP, BDP
2,907 Tribal Tracts,
Tribal BG,
CDP, BDP

Boston

Charlotte

Chicago

Chicago

Chicago

1,990 Tribal Tracts, Chicago
Tribal BG,
CDP, BDP
977 Tribal Tracts, Boston
Tribal BG,
CDP, BDP
1,302 Tribal Tracts, Seattle
Tribal BG,
CDP, BDP

95

Tribe Name

Seneca Nation

Area Name

Cattaraugus
Reservation

Census Census 2000
Area Population
Code
0540

2,412

Confederated Tribes of the Umatilla Reservation 4405
Umatilla Reservation

2,927

Confederated Tribes of the Warm Springs
Warm Springs Reservation Reservation

4545

3,314

Seminole Tribe

Hollywood
Reservation

1475

2,051

Confederated Tribes and
Bands of the Yakama
Nation
Tulalip Tribes of the
Tulalip Reservation

Yakama Reservation 4690

31,799

Tulalip Reservation

4290

9,246

Spirit Lake Tribe

Spirit Lake
Reservation

3935

4,435

Coeur D'Alene Tribe of the Coeur d'Alene
Coeur D'Alene Reservation Reservation

0705

6,551

Ute Indian Tribe of the
Uintah & Ouray
Reservation
Turtle Mountain Band of
Chippewa Indians

Uintah and Ouray
Reservation

4390

19,182

Turtle Mountain
Reservation

4345

8,331

Confederated Tribes of the Colville Reservation
Colville Reservation

0760

7,587

Tohono O'odham Nation

Tohono O'odham
Reservation

4200

10,787

Navajo Nation

Navajo Nation
Reservation

2430

180,462

Standing Rock Sioux Tribe Standing Rock
of North & South Dakota Reservation

3970

8,250

Winnebago Tribe

4625

2,588

3925

11,159

Winnebago
Reservation

Southern Ute Indian Tribe Southern Ute
of the Southern Ute
Reservation
Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

901 Tribal Tracts,
Tribal BG,
CDP, BDP
1,065 Tribal Tracts,
Tribal BG,
CDP, BDP
884 Tribal Tracts,
Tribal BG,
CDP, BDP
1,498 Tribal Tracts,
Tribal BG,
CDP, BDP
9,128 Tribal Tracts,
Tribal BG,
CDP, BDP
3,638 Tribal Tracts,
Tribal BG,
CDP, BDP
1,534 Tribal Tracts,
Tribal BG,
CDP, BDP
4,015 Tribal Tracts,
Tribal BG,
CDP, BDP
8,700 Tribal Tracts,
Tribal BG,
CDP, BDP
2,656 Tribal Tracts,
Tribal BG,
CDP, BDP
3,309 Tribal Tracts,
Tribal BG,
CDP, BDP
3,572 Tribal Tracts,
Tribal BG,
CDP, BDP
68,744 Tribal Tracts,
Tribal BG,
CDP, BDP
2,762 Tribal Tracts,
Tribal BG,
CDP, BDP
875 Tribal Tracts,
Tribal BG,
CDP, BDP
4,796 Tribal Tracts,
Tribal BG,
CDP, BDP

Regional
Census
Center
Boston

Seattle

Seattle

Atlanta

Seattle

Seattle

Denver

Seattle

Denver

Denver

Seattle

Denver

Denver

Denver

Denver

Denver

96

Tribe Name

Area Name

Census Census 2000
Area Population
Code

Pueblo of Santo Domingo

Santo Domingo
Pueblo

3585

3,166

Pueblo of Santa Clara

Santa Clara Pueblo

3495

10,658

Pueblo of San Felipe

San Felipe Pueblo

3400

3,185

Pueblo of Sandia

Sandia Pueblo

3370

4,414

San Carlos Apache Tribe
of the San Carlos
Reservation
Pueblo of Taos

San Carlos
Reservation

3355

9,385

Taos Pueblo

4140

4,492

Kickapoo Tribe of Indians
of the Kickapoo
Reservation
Quechan Tribe of the Fort
Yuma Indian Reservation

Kickapoo (KS)
Reservation

1770

4,419

Fort Yuma
Reservation

1280

2,376

Torres Martinez Desert
Cahuilla Indians

Torres-Martinez
Reservation

4255

4,146

Agua Caliente Band of
Cahuilla Indians

Agua Caliente
Reservation

0020

21,358

4595

9,192

Red Lake Band of
Chippewa Indians of the
Red Lake Reservation
Osage Nation

Red Lake Reservation 3100

5,162

Osage Reservation

2595

44,437

Arapahoe Tribe of the
Wind River Reservation

Wind River
Reservation

4610

23,250

Minnesota Chippewa Tribe Leech Lake
(Leech Lake Band)
Reservation

1940

10,205

Shoshone Tribe of the
Wind River Reservation

4610

23,250

Minnesota Chippewa Tribe White Earth
(White Earth Band)
Reservation

Wind River
Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

601 Tribal Tracts,
Tribal BG,
CDP, BDP
4,435 Tribal Tracts,
Tribal BG,
CDP, BDP
738 Tribal Tracts,
Tribal BG,
CDP, BDP
1,622 Tribal Tracts,
Tribal BG,
CDP, BDP
2,497 Tribal Tracts,
Tribal BG,
CDP, BDP
2,491 Tribal Tracts,
Tribal BG,
CDP, BDP
1,902 Tribal Tracts,
Tribal BG,
CDP, BDP
962 Tribal Tracts,
Tribal BG,
CDP, BDP
933 Tribal Tracts,
Tribal BG,
CDP, BDP
20,926 Tribal Tracts,
Tribal BG,
CDP, BDP
4,992 Tribal Tracts,
Tribal BG,
CDP, BDP
1,419 Tribal Tracts,
Tribal BG,
CDP, BDP
18,826 Tribal Tracts,
Tribal BG,
CDP, BDP
9,375 Tribal Tracts,
Tribal BG,
CDP, BDP
6,828 Tribal Tracts,
Tribal BG,
CDP, BDP
9,375 Tribal Tracts,
Tribal BG,
CDP, BDP

Regional
Census
Center
Denver

Denver

Denver

Denver

Denver

Denver

Kansas City

Los Angeles

Los Angeles

Los Angeles

Kansas City

Kansas City

Kansas City

Denver

Kansas City

Denver

97

Tribe Name

Area Name

Census Census 2000
Area Population
Code

Minnesota Chippewa Tribe Fond du Lac
(Fond du Lac Band)
Reservation

1125

3,728

Keweenaw Bay Indian
L'Anse Reservation
Community of L'Anse and
Ontonagon Bands
Saginaw Chippewa Indian Isabella Reservation
Tribe

1880

3,672

1610

25,838

Zuni Tribe of the Zuni
Reservation

Zuni Reservation

4785

7,758

Yankton Sioux Tribe

Yankton Reservation 4700

6,500

Chippewa-Cree Indians of
the Rocky Boy's
Reservation
Minnesota Chippewa Tribe
(Mille Lacs Band)

Rocky Boy's
Reservation

3205

2,676

Mille Lacs
Reservation

2270

4,704

Colorado River Indian
Tribes of the Colorado
River Indian Reservation
Salt River Pima-Maricopa
Indian Community of the
Salt River Reservation
Three Affiliated Tribes of
the Fort Berthold
Reservation
Fort Belknap Indian
Community of the Fort
Belknap Reservation of
Montana

Colorado River
Reservation

0735

9,201

Salt River
Reservation

3340

6,405

Fort Berthold
Reservation

1160

5,915

Fort Belknap
Reservation

1150

2,959

White Mountain Apache
Tribe of the Fort Apache
Reservation
Confederated Salish &
Kootenai Tribes of the
Flathead Reservation
Muckleshoot Indian Tribe
of the Muckleshoot
Reservation
Assiniboine and Sioux
Tribes of the Fort Peck
Indian Reservation
Crow Tribe

Fort Apache
Reservation

1140

12,429

Flathead Reservation 1110

26,172

Muckleshoot
Reservation

2375

3,606

Fort Peck Reservation 1250

10,321

Crow Reservation

0845

6,894

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

1,513 Tribal Tracts,
Tribal BG,
CDP, BDP
1,664 Tribal Tracts,
Tribal BG,
CDP, BDP
10,584 Tribal Tracts,
Tribal BG,
CDP, BDP
2,107 Tribal Tracts,
Tribal BG,
CDP, BDP
2,581 Tribal Tracts,
Tribal BG,
CDP, BDP
698 Tribal Tracts,
Tribal BG,
CDP, BDP
2,869 Tribal Tracts,
Tribal BG,
CDP, BDP
5,894 Tribal Tracts,
Tribal BG,
CDP, BDP
2,526 Tribal Tracts,
Tribal BG,
CDP, BDP
2,881 Tribal Tracts,
Tribal BG,
CDP, BDP
967 Tribal Tracts,
Tribal BG,
CDP, BDP
3,532 Tribal Tracts,
Tribal BG,
CDP, BDP
12,679 Tribal Tracts,
Tribal BG,
CDP, BDP
1,333 Tribal Tracts,
Tribal BG,
CDP, BDP
3,755 Tribal Tracts,
Tribal BG,
CDP, BDP
2,280 Tribal Tracts,
Tribal BG,
CDP, BDP

Regional
Census
Center
Kansas City

Detroit

Detroit

Denver

Denver

Denver

Kansas City

Denver

Denver

Denver

Denver

Denver

Denver

Seattle

Denver

Denver

98

Tribe Name

Area Name

Gila River Indian
Community of the Gila
River Indian Reservation
Cocopah Tribe

Gila River
Reservation

Cheyenne River Sioux
Tribe of the Cheyenne
River Reservation
Blackfeet Tribe of the
Blackfeet Indian
Reservation
Pueblo of Acoma

Census Census 2000
Area Population
Code
1310

11,257

Cocopah Reservation 0695

1,025

Cheyenne River
Reservation

0605

8,470

Blackfeet Reservation 0305

10,100

Acoma Pueblo

0010

2,802

Suquamish Indian Tribe of Port Madison
2925
the Port Madison
Reservation
Reservation
Puyallup Tribe of the
Puyallup Reservation 3000
Puyallup Reservation

6,536

41,341

Nez Perce Tribe

Nez Perce
Reservation

2445

17,959

Hoopa Valley Tribe

Hoopa Valley
Reservation

1490

2,633

Mississippi Band of
Choctaw Indians

Mississippi Choctaw 2300
Reservation

5,190

Shoshone-Bannock Tribes Fort Hall Reservation 1185
of the Fort Hall
Reservation
Pueblo of Pojoaque
Pueblo of Pojoaque 2990

5,762

2,712

Oglala Sioux Tribe of the
Pine Ridge Reservation

Pine Ridge
Reservation

2810

15,521

Pascua Yaqui Tribe

Pascua Yaqui
Reservation

2680

3,315

Omaha Tribe

Omaha Reservation

2550

5,194

Lummi Tribe of the Lummi Lummi Reservation
Reservation

2070

4,193

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

2,901 Tribal Tracts,
Tribal BG,
CDP, BDP
970 Tribal Tracts,
Tribal BG,
CDP, BDP
3,004 Tribal Tracts,
Tribal BG,
CDP, BDP
3,583 Tribal Tracts,
Tribal BG,
CDP, BDP
1,004 Tribal Tracts,
Tribal BG,
CDP, BDP
2,884 Tribal Tracts,
Tribal BG,
CDP, BDP
16,388 Tribal Tracts,
Tribal BG,
CDP, BDP
7,940 Tribal Tracts,
Tribal BG,
CDP, BDP
1,001 Tribal Tracts,
Tribal BG,
CDP, BDP
1,411 Tribal Tracts,
Tribal BG,
CDP, BDP
2,011 Tribal Tracts,
Tribal BG,
CDP, BDP
1,179 Tribal Tracts,
Tribal BG,
CDP, BDP
3,931 Tribal Tracts,
Tribal BG,
CDP, BDP
785 Tribal Tracts,
Tribal BG,
CDP, BDP
1,837 Tribal Tracts,
Tribal BG,
CDP, BDP
1,749 Tribal Tracts,
Tribal BG,
CDP, BDP

Regional
Census
Center
Denver

Denver

Denver

Denver

Denver

Seattle

Seattle

Seattle

Seattle

Dallas

Seattle

Denver

Denver

Denver

Denver

Seattle

99

Tribe Name

Area Name

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Northern Cheyenne Tribe
of the Northern Cheyenne
Indian Reservation
Rosebud Sioux Tribe of the
Rosebud Indian
Reservation
Mescalero Apache Tribe of
the Mescalero Reservation

Northern Cheyenne
Reservation

Mescalero
Reservation

2205

3,156

Sisseton-Wahpeton Oyate
of the Lake Traverse
Reservation
Pueblo of Laguna

Lake Traverse
Reservation

1860

10,408

Laguna Pueblo

1840

3,815

Jicarilla Apache Nation

Jicarilla Apache
Reservation

1700

2,755

Pueblo of Isleta

Isleta Pueblo

1625

3,166

Hopi Tribe

Hopi Reservation

1505

6,946

Ohkay Owingeh

Ohkay Owingeh

2510

6,748

Stockbridge-Munsee
Community of Mohican
Indians
Bad River Band of the
Lake Superior Tribe of
Chippewa Indians of the
Bad River Reservation

Stockbridge Munsee
Community

4015

1,527

Bad River
Reservation

0140

1,411

595 Tribal BG,
CDP, BDP

Chicago

Quinault Tribe of the
Quinault Reservation
Prairie Band of
Potawatomi Nation

Quinault Reservation 3040

1,370

Seattle

Prairie Band
Potawatomi
Reservation
Pueblo de Cochiti

2980

1,238

487 Tribal BG,
CDP, BDP
428 Tribal BG,
CDP, BDP

0680

1,502

Denver

Sault Ste. Marie
Reservation
Annette Island
Reserve

3635

1,676

0110

1,447

625 Tribal BG,
CDP, BDP
673 Tribal BG,
CDP, BDP
562 Tribal BG,
CDP, BDP

Crow Creek
Reservation

0855

2,225

Pueblo of Cochiti
Sault Ste. Marie Tribe of
Chippewa Indians
Metlakatla Indian
Community, Annette
Island Reserve
Crow Creek Sioux Tribe of
the Crow Creek
Reservation

2490

4,470

Rosebud Reservation 3235

10,469

1,328 Tribal Tracts,
Tribal BG,
CDP, BDP
3,166 Tribal Tracts,
Tribal BG,
CDP, BDP
916 Tribal Tracts,
Tribal BG,
CDP, BDP
5,184 Tribal Tracts,
Tribal BG,
CDP, BDP
1,238 Tribal Tracts,
Tribal BG,
CDP, BDP
972 Tribal Tracts,
Tribal BG,
CDP, BDP
1,204 Tribal Tracts,
Tribal BG,
CDP, BDP
2,512 Tribal Tracts,
Tribal BG,
CDP, BDP
2,554 Tribal Tracts,
Tribal BG,
CDP, BDP
676 Tribal BG,
CDP, BDP

617 Tribal BG,
CDP, BDP

Denver

Denver

Denver

Denver

Denver

Denver

Denver

Denver

Denver

Chicago

Kansas City

Detroit
Seattle

Denver

100

Tribe Name

Area Name

Census Census 2000
Area Population
Code

Census
2000
Housing
Units

2010 Census
Areas Eligible
for
Delineation

Regional
Census
Center

Shoshone-Paiute Tribes of
the Duck Valley
Reservation
Makah Indian Tribe of the
Makah Indian Reservation
Hualapai Indian Tribe of
the Hualapai Indian
Reservation
Pueblo of Jemez

Duck Valley
Reservation

0965

1,265

457 Tribal BG,
CDP, BDP

Denver

Makah Reservation

2085

1,356

Seattle

Hualapai Reservation 1545

1,353

533 Tribal BG,
CDP, BDP
475 Tribal BG,
CDP, BDP

Jemez Pueblo

1685

1,958

Denver

Lower Brule Sioux Tribe
of the Lower Brule
Reservation
Ute Mountain Tribe of the
Ute Mountain Reservation
Spokane Tribe of the
Spokane Reservation
Pueblo of Picuris

Lower Brule
Reservation

2030

1,353

504 Tribal BG,
CDP, BDP
392 Tribal BG,
CDP, BDP

Ute Mountain
4470
Reservation
Spokane Reservation 3940

1,687

Denver

Picuris Pueblo

2785

1,801

Pyramid Lake Paiute Tribe Pyramid Lake
3010
of the Pyramid Lake
Reservation
Reservation
Pueblo of San Ildefonso
San Ildefonso Pueblo 3415

1,734

570 Tribal BG,
CDP, BDP
701 Tribal BG,
CDP, BDP
883 Tribal BG,
CDP, BDP
687 Tribal BG,
CDP, BDP

Pueblo of Nambe

Nambe Pueblo

2400

1,764

Chemehuevi Indian Tribe
of the Chemehuevi
Reservation
Onondaga Nation

Chemehuevi
Reservation

0585

345

Onondaga
Reservation
Bishop Reservation

2570

1,473

0290

1,441

Rincon Band of Luiseno
Rincon Reservation
Mission Indians of the
Rincon Reservation
Yurok Tribe of the Yurok Yurok Reservation
Reservation
Pala Band of Luiseno
Pala Reservation
Mission Indians of the Pala
Reservation

3165

1,495

4760

1,103

2635

1,573

Bishop Paiute Tribe

2,004

1,524

626 Tribal BG,
CDP, BDP
735 Tribal BG,
CDP, BDP
699 Tribal BG,
CDP, BDP
311 Tribal BG,
CDP, BDP
530 Tribal BG,
CDP, BDP
385 Tribal BG,
CDP, BDP
604 Tribal BG,
CDP, BDP
408 Tribal BG,
CDP, BDP

Denver

Denver

Seattle
Denver
Denver

Denver
Denver
Los Angeles

Boston
Los Angeles
Los Angeles

Seattle
Los Angeles

101

102

OMB No. 0607-0795: Approval Expires 03/31/09

Table B. Alaska Native villages
Tribe Name

Eklutna Native Village
Chilkoot Indian
Association
Chilkat Indian Village
Chignik Lake Village
Native Village of
Chignik Lagoon
Chignik Bay Tribal
Council
Chickaloon Native
Village
Chevak Native Village
Native Village of
Chanega
Village of Chefornak
Chalkyitsik Village
Caswell Native
Association,
Incorporated
Kian Tree Corporation
Native Village of
Cantwell
Native Village of
Chuathbaluk
Organized Village of
Saxman
Native Village of
Stevens
Stebbins Community
Association

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Eklutna ANVSA

6450

394

141

Chilkoot ANVSA
Chilkat ANVSA
Chignik Lake
ANVSA
Chignik Lagoon
ANVSA

6315
6310

338
139

186
85

6305

145

6300

Chignik ANVSA

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Eklutna
(Anchorage)

61.4606405

-149.3612981

Cook Inlet

Seattle

Chilkoot (Haines)
Chilkat (Klukwan)

59.2239572
59.399702

-135.4459756
-135.8964089

Sealaska
Sealaska

Seattle
Seattle

50

Chignik Lake

56.2496142

-158.7521999

Bristol Bay

Seattle

103

68

Chignik Lagoon

56.3084393

-158.5302391

Bristol Bay

Seattle

6295

79

80

Chignik

56.3037403

-158.4129046

Bristol Bay

Seattle

Chickaloon ANVSA
Chevak ANVSA

6290
6285

16,918
765

6,393
190

61.8001927
61.5285278

-148.4916137
-165.5807499

Cook Inlet
Calista

Seattle
Seattle

Chenega ANVSA
Chefornak ANVSA
Chalkyitsik ANVSA

6280
6275
6265

86
394
83

27
82
62

Chickaloon
Chevak
Chenega (Chenega
Bay)
Chefornak
Chalkyitsik

60.0663707
60.1538056
66.6534092

-148.012387
-164.2723052
-143.7285785

Chugach
Calista
Doyon

Seattle
Seattle
Seattle

Caswell
Canyon Village

6260
6257

0
0

0
0

Caswell
Canyon Village

62.0046861
67.15484

-149.9478739
-142.0878206

Cook Inlet
Doyon

Seattle
Seattle

Cantwell ANVSA
Chuathbaluk
ANVSA

6255

222

177

Cantwell

63.3920921

-148.9104556

Ahtna

Seattle

6335

119

43

Chuathbaluk

61.5774142

-159.2481461

Calista

Seattle

Saxman ANVSA
Stevens Village
ANVSA

7420

431

146

Saxman

55.3220786

-131.6002963

Sealaska

Seattle

7520

87

43

Stevens Village

66.0054606

-149.1038725

Seattle

Stebbins ANVSA

7510

547

134

Stebbins

63.5208272

-162.2819964

Doyon
Bering
Straits

Seattle

Tribe Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

South Naknek
ANVSA

7505

137

137

Village of Solomon
Village of Sleetmute
Skagway Village
Sitka Tribe of Alaska
Native Village of
Shungnak
Native Village of
Shishmaref
Native Village of
Shaktoolik
Shageluk Native Village

Solomon ANVSA
Sleetmute ANVSA
Skagway
Sitka

7500
7495
7485
7475

4
100
0
0

Shungnak ANVSA

7470

Shishmaref ANVSA

Seldovia Village Tribe
Native Village of Port
Graham
Native Village of
Scammon Bay
Native Village of
Tanacross
Native Village of
Savoonga
Qagan Tayagungin
Tribe of Sand Point
Village
Village of Salamatoff

South Naknek Village

Pribilof Islands Aleut
Communities of St. Paul
& St. George (St. Paul)
Native Village of Saint
Michael

Area Name

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

South Naknek

58.7123478

-157.0026423

Seattle

4
51
0
0

Solomon
Sleetmute
Skagway
Sitka

64.5596601
61.6962336
59.4583395
57.0543416

-164.4487838
-157.1689024
-135.3119224
-135.3425771

Bristol Bay
Bering
Straits
Calista
Sealaska
Sealaska

256

64

Shungnak

66.887306

-157.1426196

7465

562

148

Shishmaref

66.2564123

-166.0666291

Shaktoolik ANVSA
Shageluk ANVSA

7450
7440

230
129

66
52

64.3494735
62.6555754

Seldovia ANVSA
Port Graham
ANVSA
Scammon Bay
ANVSA

7435

430

391

Shaktoolik
Shageluk
Seldovia (Seldovia
Village)

7265

171

82

Port Graham

7425

465

114

Tanacross ANVSA

7535

140

53

Savoonga ANVSA

7415

643

Sand Point ANVSA
Salamatof ANVSA

7410
7400

St. Paul ANVSA
St. Michael ANVSA

Seattle
Seattle
Seattle
Seattle

-161.1845472
-159.5226837

NANA
Bering
Straits
Bering
Straits
Doyon

Seattle
Seattle

59.4389826

-151.7122604

Cook Inlet

Seattle

59.3481439

-151.83529

Chugach

Seattle

61.8417

-165.5818139

Calista

Seattle

Tanacross

63.3761711

-143.3565211

Seattle

160

Savoonga

63.6959165

-170.4639566

Doyon
Bering
Straits

Seattle

952
954

282
282

Sand Point (Qagun
Tayagungin Tribe)
Salamatof

55.3458213
60.615375

-160.4905342
-151.3194369

Aleut
Cook Inlet

Seattle
Seattle

7390

532

214

Saint Paul

57.127394

-170.2727324

Seattle

7375

368

93

63.4783536

-162.038351

Aleut
Bering
Straits

Scammon Bay

Saint Michael

Seattle
Seattle

Seattle

104

Tribe Name

Pribilof Islands Aleut
Communities of St. Paul
& St. George (St.
George)
Iqurmuit Traditional
Council
Native Village of Ruby
Chinik Eskimo
Community
Native Village of
Diomede
Village of Iliamna
Igiugig Village
Hydaburg Cooperative
Association
Huslia Village
Hughes Village
Native Village of
Hooper Bay
Hoonah Indian
Association
Holy Cross Village
Healy Lake Village
Native Village of
Hamilton
Gulkana Village
Native Village of
Kwinhagak
Native Village of
Goodnews Bay
Organized Village of
Kake
Gold Creek-Susitna
Association,
Incorporated

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

56.6044126

-169.5519435

Aleut

Seattle

61.7853706
64.7370784

-161.3286859
-155.472947

Seattle
Seattle

St. George ANVSA
Russian Mission
ANVSA
Ruby ANVSA

7340

152

67

7315
7310

296
188

81
107

Saint George
Iqurmuit (Russian
Mission)
Ruby

Golovin ANVSA

6540

144

54

Chinik (Golovin)

64.5443153

-163.0287302

Inalik ANVSA
Iliamna ANVSA
Igiugig ANVSA

6630
6625
6620

146
102
53

47
58
20

Inalik (Diomede)
Iliamna
Igiugig

65.7546776
59.7567965
59.3266025

-168.937034
-154.9110837
-155.8927205

Calista
Doyon
Bering
Straits
Bering
Straits
Bristol Bay
Bristol Bay

Hydaburg ANVSA
Huslia ANVSA
Hughes ANVSA

6615
6610
6605

382
293
78

154
111
39

Hydaburg
Huslia
Hughes

55.2066677
65.7026276
66.0455433

-132.8201169
-156.3892174
-154.2557494

Sealaska
Doyon
Doyon

Seattle
Seattle
Seattle

Hooper Bay ANVSA

6595

1,014

239

Hooper Bay

61.5293908

-166.0977978

Calista

Seattle

Hoonah ANVSA
Holy Cross ANVSA
Healy Lake ANVSA

6590
6585
6575

860
227
37

348
81
21

Hoonah
Holy Cross
Healy Lake

58.1099855
62.1985193
63.9872308

-135.4345509
-159.7737538
-144.6998325

Sealaska
Doyon
Doyon

Seattle
Seattle
Seattle

Hamilton ANVSA
Gulkana ANVSA

6570
6560

0
164

0
74

62.8896468
62.2633915

-163.8597707
-145.3655587

Calista
Ahtna

Seattle
Seattle

Kwinhagak ANVSA
Goodnews Bay
ANVSA

6845

555

153

Hamilton
Gulkana
Kwinhagak
(Quinhagak)

59.7524618

-161.9054612

Calista

Seattle

6545

230

87

Goodnews Bay

59.1233725

-161.5863711

Calista

Seattle

Kake ANVSA

6670

710

288

Kake

56.9774822

-133.9450634

Sealaska

Seattle

Gold Creek

6537

0

0

62.75667

-149.69389

Cook Inlet

Seattle

Gold Creek

Seattle
Seattle
Seattle
Seattle

105

Tribe Name

Point
Location Latitude

Point
Location Longitude

Georgetown

61.8979091

-157.6727421

187
259

Gambell
Galena

63.7621144
64.7426745

84

39

Gakona

6515

595

317

False Pass ANVSA
Eyak ANVSA
Evansville ANVSA
Emmonak ANVSA

6500
6495
6490
6480

64
168
71
767

40
65
66
218

Native Village of Elim
Ekwok Village
Organized Village of
Grayling
Native Village of
Kipnuk
Native Village of
Kwigillingok
Organized Village of
Kwethluk
Koyukuk Native Village

Elim
Ekwok ANVSA

6470
6460

0
130

0
56

Elim
Ekwok

Grayling ANVSA

6550

194

63

Kipnuk ANVSA
Kwigillingok
ANVSA

6750

644

154

6840

338

78

Kwethluk ANVSA
Koyukuk ANVSA

6835
6830

713
101

199
55

Native Village of Koyuk
Native Village of
Kotzebue
Village of Kotlik
Native Village of
Kongiganak
Kokhanok Village

Koyuk ANVSA

6825

297

95

Kotzebue ANVSA
Kotlik ANVSA

6820
6815

3,082
591

1,007
139

Kongiganak ANVSA
Kokhanok ANVSA
Kodiak (Shoonaq'
Tribe)

6810
6800

359
174

90
59

6795

0

0

Native Village of
Georgetown
Native Village of
Gambell
Galena Village
Native Village of
Gakona
Native Village of Fort
Yukon
Native Village of False
Pass
Native Village of Eyak
Evansville Village
Emmonak Village

Sun'aq Tribe of Kodiak

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Georgetown ANVSA

6535

3

4

Gambell ANVSA
Galena ANVSA

6530
6525

649
675

Gakona ANVSA

6520

Fort Yukon ANVSA

Alaska Native
Village Name

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Seattle

-171.702207
-156.8851662

Calista
Bering
Straits
Doyon

Seattle
Seattle

62.3004045

-145.3119166

Ahtna

Seattle

Fort Yukon

66.5626991

-145.2496728

Doyon

Seattle

False Pass
Eyak (Cordova)
Evansville (Bettles)
Emmonak

54.8519613
60.526294
66.927233
62.7786549

-163.412128
-145.6351157
-151.5099561
-164.5453798

Seattle
Seattle
Seattle
Seattle

64.616495
59.351935

-162.2575681
-157.4865969

Aleut
Chugach
Doyon
Calista
Bering
Straits
Bristol Bay

Seattle
Seattle

Grayling

62.9061128

-160.0688723

Doyon

Seattle

Kipnuk

59.9342781

-164.0375868

Calista

Seattle

Kwigillingok

59.8693714

-163.1647332

Calista

Seattle

Kwethluk
Koyukuk

60.8101309
64.8818268

-161.4381234
-157.7031427

Seattle
Seattle

Koyuk

64.9311897

-161.1628455

Calista
Doyon
Bering
Straits

Kotzebue
Kotlik

66.8988065
63.032498

-162.5874263
-163.5499514

NANA
Calista

Seattle
Seattle

Kongiganak
Kokhanok
Kodiak (Shoonaq'
Tribe)

59.9532731
59.4374439

-162.8951327
-154.7681714

Calista
Bristol Bay

Seattle
Seattle

57.8008507

-152.3885025

Koniag

Seattle

Seattle

106

Tribe Name

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Native Village of Kobuk

Kobuk ANVSA
Kanakanak
(Knugank /
Olsonville)
Knik ANVSA
Ivanof Bay ANVSA

6790

109

45

6787
6785
6650

0
31,969
22

0
16,333
12

Kivalina ANVSA
Kaguyak
King Salmon

6755
6660
6740

377
0
0

80
0
0

King Cove ANVSA
Kiana ANVSA

6735
6730

792
388

207
133

Ketchikan

6725

0

0

Kenaitze ANVSA

6720

29,320

14,124

Kasigluk ANVSA

6710

543

110

Kasaan ANVSA
Karluk ANVSA

6705
6700

39
27

39
24

Kanatak
Kaltag ANVSA

6695
6690

10,252
230

3,997
78

Village of Kalskag

Kalskag ANVSA

6685

230

66

Kaktovik Village
Egegik Village
Klawock Cooperative
Association

Kaktovik ANVSA
Egegik ANVSA

6680
6445

293
116

Klawock ANVSA

6765

Yupiit of Andreafski
Native Village of Ekuk

Andreafsky ANVSA
Ekuk ANVSA

6095
6455

Olsonville, Incorporated
Knik Tribe
Ivanoff Bay Village
Native Village of
Kivalina
Kaguyak Village
King Salmon Tribe
Agdaagux Tribe of King
Cove
Native Village of Kiana
Ketchikan Indian
Corporation
Kenaitze Indian Tribe
Kasigluk Traditional
Elders Council
Organized Village of
Kasaan
Native Village of Karluk
Native Village of
Kanatak
Village of Kaltag

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Kobuk
Kanakanak
(Knugank /
Olsonville)
Knik
Ivanof Bay

66.9252171

-156.8887759

NANA

Seattle

59.0046325
61.4946614
55.903292

-158.5372637
-149.6821811
-159.4836055

Bristol Bay
Cook Inlet
Bristol Bay

Seattle
Seattle
Seattle

Kivalina
Kaguyak
King Salmon
King Cove
(Agdaagux Tribe)
Kiana

67.7295203
56.868931
58.7090295

-164.5386059
-153.7955164
-156.7311507

NANA
Koniag
Bristol Bay

Seattle
Seattle
Seattle

55.0629282
66.9716847

-162.3028896
-160.4309426

Aleut
NANA

Seattle
Seattle

55.3420894

-131.6444895

Sealaska

Seattle

60.5521284

-151.2613885

Cook Inlet

Seattle

60.887316

-162.5138906

Calista

Seattle

Kasaan
Karluk

55.5418886
57.5571678

-132.4017381
-154.4393132

Sealaska
Koniag

Seattle
Seattle

Kanatak
Kaltag
Kalskag (Upper
Kalskag)

57.5727792
64.3259494

-156.0431783
-158.7301853

Koniag
Doyon

Seattle
Seattle

61.5400011

-160.3214855

Seattle

95
286

Kaktovik
Egegik

70.1324111
58.2173441

-143.6113046
-157.3535623

Calista
Arctic
Slope
Bristol Bay

Seattle
Seattle

854

368

55.552629

-133.0947795

Sealaska

Seattle

127
2

59
73

Klawock
Andreafsky (St.
Mary's)
Ekuk

62.0476191
58.8035099

-163.1933921
-158.5533853

Calista
Bristol Bay

Seattle
Seattle

Ketchikan
Kenai (Kenaitze
Indian Tribe)
Kasigluk

107

Tribe Name

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Bill Moore's ANVSA

6225

0

0

Village of Bill Moore's
Slough
Orutsararmuit Native
Village
Native Village of
Belkofski
Beaver Village

Bethel ANVSA

6205

5,471

1,990

Belkofski ANVSA
Beaver ANVSA

6195
6190

0
84

Native Village of
Barrow Inupiat
Traditional Government
Ayakulik, Incorporated

Barrow ANVSA
Ayakulik

6175
6170

Atqasuk Village
Village of Atmautluak
Native Village of Atka
Native Village of
Venetie Tribal
Government (Arctic
Village)
Anvik Village
Native Village of Brevig
Mission
Angoon Community
Association
Native Village of
Buckland
Village of Anaktuvuk
Pass
Native Village of
Ambler
Allakaket Village

Atqasuk ANVSA
Atmautluak ANVSA
Atka ANVSA

Algaaciq Native Village
Alexander Creek,
Incorporated

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Bill Moore's
Orutsararmuit
(Bethel)

62.9448676

-163.7766666

Calista

Seattle

60.7968375

-161.7730197

Calista

Seattle

4
54

Belkofski
Beaver

55.0865176
66.3628034

-162.0423148
-147.4025507

Aleut
Doyon

Seattle
Seattle

4,581
0

1,620
0

Barrow
Ayakulik

71.2909063
57.1949295

-156.7811223
-154.5072442

6165
6160
6150

228
294
92

60
64
41

Atqasuk
Atmautluak
Atka

70.4736266
60.8590583
52.2105764

-157.4135247
-162.2794732
-174.2095218

6140
6125

152
104

67
49

Arctic Village
Anvik

68.1242576
62.65154

-145.5283348
-160.1965315

6240

276

76

Brevig Mission

65.3350407

Angoon ANVSA

6100

572

221

Angoon

Buckland ANVSA
Anaktuvuk Pass
ANVSA

6250

406

89

6080

282

101

Ambler ANVSA
Allakaket ANVSA

6075
6070

309
133

98
68

Algaacig ANVSA
Alexander Creek
(Susitna)

6065

373

127

6055

0

0

Arctic Village
ANVSA
Anvik ANVSA
Brevig Mission
ANVSA

Arctic
Slope
Koniag
Arctic
Slope
Calista
Aleut

Seattle
Seattle
Seattle
Seattle
Seattle

-166.4885137

Doyon
Doyon
Bering
Straits

Seattle

57.4975419

-134.5823806

Sealaska

Seattle

65.976712

-161.1246103

Seattle

Anaktuvuk Pass

68.1479512

-151.7285614

NANA
Arctic
Slope

Seattle

Ambler
Allakaket
Algaaciq (St.
Mary's)
Alexander Creek
(Susitna)

67.0873951
66.5596513

-157.8670731
-152.6506408

NANA
Doyon

Seattle
Seattle

62.0534167

-163.1768811

Calista

Seattle

61.4217936

-150.5999329

Cook Inlet

Seattle

Buckland

Seattle
Seattle

108

Tribe Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Aleknagik
Alatna
Alakanuk

59.278885
66.5636177
62.6797024

-158.6188518
-152.756306
-164.6612268

Bristol Bay
Doyon
Calista

Seattle
Seattle
Seattle

38

Akutan

54.1383602

-165.7808952

Aleut

Seattle

309

76

Akiak

60.911928

-161.2222287

Calista

Seattle

6020

585

189

60.9026297

-161.4276407

Calista

Seattle

Akhiok ANVSA

6015

80

34

56.94556

-154.17028

Koniag

Seattle

Afognak
Aniak ANVSA

6005
6105

0
572

0
203

58.0221236
61.5750236

-152.7652264
-159.5486861

Koniag
Calista

Seattle
Seattle

Cheesh-Na Tribe
Craig Community
Association
Native Village of Eek

Chistochina ANVSA

6325

75

39

62.5717828

-144.6541704

Ahtna

Seattle

Craig ANVSA
Eek ANVSA

6385
6440

1,725
280

737
83

55.4870391
60.2170012

-133.1253201
-162.0247336

Sealaska
Calista

Seattle
Seattle

Native Village of Eagle
Douglas Indian
Association

Eagle ANVSA

6430

77

57

64.7807903

-141.1112818

Doyon

Seattle

Douglass ANVSA

6420

5,297

2,372

58.2781154

-134.3992073

Sealaska

Seattle

Village of Dot Lake

Dot Lake ANVSA

6415

38

25

63.6502637

-144.0354243

Doyon

Seattle

Curyung Tribal Council
Native Village of
Deering
Village of Crooked
Creek
Native Village of
Council

Dillingham ANVSA

6405

2,466

1,000

59.0487208

-158.4669939

Bristol Bay

Seattle

Deering ANVSA
Crooked Creek
ANVSA

6400

136

61

Deering

66.078021

-162.7283017

NANA

Seattle

6390

137

46

Crooked Creek

61.8719565

-158.1123526

Seattle

Council ANVSA
Clark's Point
ANVSA

6380

0

40

Council

64.895

-163.67639

Calista
Bering
Straits

Seattle

6360

75

51

Clark's Point

58.8330083

-158.5471213

Bristol Bay

Seattle

Native Village of
Aleknagik
Alatna Village
Village of Alakanuk
Native Village of
Akutan
Akiak Native
Community
Akiachak Native
Community
Native Village of
Akhiok
Native Village of
Afognak
Village of Aniak

Village of Clarks Point

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Aleknagik ANVSA
Alatna ANVSA
Alakanuk ANVSA

6045
6040
6035

221
35
652

107
17
160

Akutan ANVSA

6030

713

Akiak ANVSA

6025

Akiachak ANVSA

Alaska Native
Village Name

Akiachak
Akhiok
Afognak
Aniak
Cheesh-Na
(Chistochina)
Craig
Eek
Eagle (Eagle
Village)
Douglas (Juneau)
Dot Lake (Dot Lake
Village)
Curyung
(Dillingham)

109

Tribe Name

Circle Native
Community
Chuloonawick Native
Village
Birch Creek Tribe
Native Village of
Chitina
Village of Red Devil
Rampart Village
Native Village of Port
Lions
Native Village of Port
Heiden
Native Village of
Selawik
Ugashik Village
Native Village of Kluti
Kaah
Minchumina Natives
Incorporated
Yakutat Tlingit Tribe
Wrangell Cooperative
Association
Native Village of White
Mountain

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Circle ANVSA
Chulloonawick
ANVSA
Birch Creek ANVSA

6350

100

42

Circle

65.8260731

-144.0723417

Doyon

Seattle

6340
6235

0
28

1
22

Chulloonawick
Birch Creek

62.950411
66.2590355

-164.1627576
-145.8190168

Calista
Doyon

Seattle
Seattle

Chitina ANVSA
Red Devil ANVSA
Rampart ANVSA

6330
7305
7300

106
48
45

41
22
46

Chitina
Red Devil
Rampart

61.524029
61.7834473
65.5094443

-144.4412094
-157.3387411
-150.1453142

Ahtna
Calista
Doyon

Seattle
Seattle
Seattle

Port Lions ANVSA

7275

256

106

Port Lions

57.8658671

-152.8893955

Koniag

Seattle

Port Heiden ANVSA

7270

119

56

Port Heiden

56.9325614

-158.6249699

Bristol Bay

Seattle

Selawik ANVSA
Ugashik ANVSA
Copper Center
ANVSA

7430
7665

772
11

188
35

66.5983985
57.5027418

-160.0162004
-157.3887491

NANA
Bristol Bay

Seattle
Seattle

6365

492

218

Selawik
Ugashik
Kluti Kaah (Copper
Center)

61.9769598

-145.3297294

Ahtna

Seattle

Lake Minchumina
Yakutat ANVSA

6850
7765

0
680

0
385

Lake Minchumina
Yakutat

63.8829979
59.5542784

-152.3122074
-139.7435343

Doyon
Sealaska

Seattle
Seattle

Wrangell
White Mountain
ANVSA

7755

0

0

Wrangell

56.4752443

-132.3791325

Seattle

7745

203

75

White Mountain

64.6805456

-163.4042118

Native Village of Wales

Wales ANVSA

7740

152

59

Wales

65.6082056

-168.0960055

Village of Wainwright
Native Village of
Venetie Tribal
Government (Venetie
Village)
Uyak, Incorporated
Unga Corporation

Wainwright ANVSA

7735

546

179

Wainwright

70.6447815

-160.0201934

Sealaska
Bering
Straits
Bering
Straits
Arctic
Slope

Venetie
Uyak
Unga

7725
7715
7705

0
0
0

0
0
0

Venetie
Uyak
Unga

67.0177722
57.6335601
55.1840915

-146.4148666
-154.007795
-160.5050438

Doyon
Koniag
Aleut

Seattle
Seattle
Seattle

Seattle
Seattle
Seattle

110

Tribe Name

Qawalangin Tribe of
Unalaska
Native Village of
Unalakleet
Village of Stony River
King Island Native
Community
Takotna Village
Uganik Natives,
Incorporated
Native Village of
Tyonek
Twin Hills Village
Native Village of
Tununak
Native Village of
Tuntutuliak
Tuluksak Native
Community
Traditional Village of
Togiak
Native Village of Teller
Telida Village
Native Village of
Tazlina
Native Village of
Tatitlek
Native Village of
Tanana
Native Village of Tetlin
Umkumiute Native
Village
Native Village of Minto
Native Village of
Nelson Lagoon

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Unalaska ANVSA

7695

4,283

988

Unalakleet ANVSA
Stony River ANVSA
Ukivok (King
Island)
Takotna ANVSA

7690
7525

747
61

242
25

7675
7530

0
50

0
49

Uganik

7660

0

0

Tyonek ANVSA
Twin Hills ANVSA

7655
7650

193
69

Tununak ANVSA

7645

Tuntutuliak ANVSA

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

53.8745625

-166.5337448

Seattle

-168.0718043
-156.0870195

Aleut
Bering
Straits
Calista
Bering
Straits
Doyon

Unalakleet
Stony River
Ukivok (King
Island)
Takotna

63.8776565
61.7891481

-160.79136
-156.589835

64.9642527
62.972292

Uganik

57.7565056

-153.4046297

Koniag

Seattle

90
33

Tyonek
Twin Hills

61.0716285
59.0773756

-151.1494465
-160.2835707

Cook Inlet
Bristol Bay

Seattle
Seattle

325

93

Tununak

60.5827236

-165.2588303

Calista

Seattle

7640

370

97

Tuntutuliak

60.3423989

-162.6695799

Calista

Seattle

Tuluksak ANVSA

7630

428

93

Tuluksak

61.1019806

-160.9629755

Calista

Seattle

Togiak ANVSA

7605

809

221

Togiak

59.06194

-160.37639

Seattle

Teller ANVSA
Telida ANVSA

7570
7565

268
3

87
8

Teller
Telida

65.261291
63.3839856

-166.3627828
-153.2785017

Bristol Bay
Bering
Straits
Doyon

Tazlina ANVSA

7560

339

173

Tazlina

62.0588695

-145.4284212

Ahtna

Seattle

Tatitlek ANVSA

7555

107

57

Tatitlek

60.8663962

-146.6779418

Chugach

Seattle

Tanana ANVSA
Tetlin ANVSA

7540
7580

308
124

166
66

Tanana
Tetlin

65.1715657
63.1350512

-152.0762703
-142.5238796

Doyon
Doyon

Seattle
Seattle

Umkumiute
Minto ANVSA
Nelson Lagoon
ANVSA

7685
6965

0
258

0
99

Umkumiute
Minto

60.4996523
65.150411

-165.1988597
-149.349708

Calista
Doyon

Seattle
Seattle

7025

83

33

Nelson Lagoon

56.0006152

-161.206974

Aleut

Seattle

Unalaska
(Qawalangin Tribe)

Seattle
Seattle
Seattle
Seattle

Seattle
Seattle

111

Tribe Name

Newtok Village
New Koliganek Village
Council
Newhalen Village
Nenana Native
Association
Lesnoi Village
Native Village of
Napaskiak
Native Village of
Napakiak
Native Village of
Napaimute
Native Village of
Nanwalek
Naknek Native Village
Nagamut, Limited
Nikolai Village
Montana Creek Native
Association,
Incorporated
Native Village of
Nightmute
Mentasta Traditional
Council
Native Village of
Mekoryuk
Native Village of Mary's
Igloo
Native Village of
Marshall
Manokotak Village
Manley Hot Springs
Village
McGrath Native Village

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

7055

321

67

-164.6307421

Calista

Seattle

7040
7035

182
160

77
51

59.72861
59.723835

-157.28444
-154.8923946

Bristol Bay
Bristol Bay

Seattle
Seattle

Nenana ANVSA
Lesnoi (Woody
Island)

7030

402

210

64.5609632

-149.0874579

Doyon

Seattle

6860

0

0

57.7778517

-152.3350845

Koniag

Seattle

Napaskiak ANVSA

7020

390

95

Napaskiak

60.706026

-161.7633667

Calista

Seattle

Napakiak ANVSA

7010

353

101

Napakiak

60.6905612

-161.9789784

Calista

Seattle

Napaimute ANVSA

7005

0

16

Napaimute

61.5414325

-158.6738827

Calista

Seattle

Nanwalek ANVSA
Naknek ANVSA
Nagamut
Nikolai ANVSA

6995
6990
6985
7070

177
678
0
100

54
455
0
47

Nanwalek
Naknek
Nagamut
Nikolai

59.3520867
58.7329799
61.01944
63.0127602

-151.9119024
-156.9868784
-157.67444
-154.3814348

Chugach
Bristol Bay
Calista
Doyon

Seattle
Seattle
Seattle
Seattle

Montana Creek

6970

0

0

Montana Creek

62.0686031

-150.0650363

Cook Inlet

Seattle

Nightmute ANVSA
Mentasta Lake
ANVSA

7065

208

54

Nightmute

60.4788125

-164.7216172

Calista

Seattle

6945

125

68

Mentasta Lake

62.9329779

-143.7700394

Ahtna

Seattle

Mekoryuk ANVSA
Mary's Igloo
ANVSA

6935

210

96

Mekoryuk

60.3891594

-166.1942792

Seattle

6915

0

5

Mary's Igloo

65.1488994

-165.0677585

Calista
Bering
Straits

Seattle

Marshall ANVSA
Manokotak ANVSA
Manley Hot Springs
ANVSA
McGrath ANVSA

6910
6905

349
399

104
106

Marshall
Manokotak

61.8794301
58.9724274

-162.0878085
-158.9981386

Calista
Bristol Bay

Seattle
Seattle

6900
6895

72
401

105
213

Manley Hot Springs
McGrath

65.0088256
62.9488245

-150.6107477
-155.575891

Doyon
Doyon

Seattle
Seattle

Newtok ANVSA
New Koliganek
ANVSA
Newhalen ANVSA

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Newtok
New Koliganek
(Koliganek)
Newhalen

60.9376751

Nenana
Lesnoi (Woody
Island)

112

Tribe Name

Village of Lower
Kalskag
Lime Village
Levelock Village
Native Village of Larsen
Bay
Nunakauyarmiut Tribe
Tanalian, Incorporated
Asa'carsarmiut Tribe
Pilot Station Traditional
Village
Native Village of
Nikolski
Native Village of
Paimiut
New Stuyahok Village
Pedro Bay Village
Native Village of
Perryville
Oscarville Traditional
Village
Native Village of Pilot
Point
Native Village of
Ouzinkie
Native Village of Pitka's
Point
Platinum Traditional
Village
Native Village of Point
Hope

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

6890

267

79

Lower Kalskag

61.5125106

-160.3642285

Calista

Seattle

6875
6865

6
122

24
50

Lime Village
Levelock

61.3539737
59.1116702

-155.4378285
-156.8612549

Calista
Bristol Bay

Seattle
Seattle

Larsen Bay ANVSA
Toksook Bay
ANVSA
Port Alsworth
Mountain Village
ANVSA

6855

115

70

7625
7263

532
0

110
0

6975

755

211

Larsen Bay
Nunakauyarmiut
(Toksook Bay)
Port Alsworth
Asa'carsarmiut
(Mountain Village)

57.5351177

-153.9874373

Koniag

Seattle

60.5337752
60.2016214

-165.1036627
-154.322332

Calista
Cook Inlet

Seattle
Seattle

62.0905945

-163.7278598

Calista

Seattle

Pilot Station ANVSA

7230

550

126

Pilot Station

61.9375015

-162.8824583

Calista

Seattle

Nikolski ANVSA

7075

39

28

Nikolski

52.9400839

-168.8615003

Aleut

Seattle

Paimiut ANVSA
New Stuyahok
ANVSA
Pedro Bay ANVSA

7185

2

1

Paimiut

61.7029942

-165.8200534

Calista

Seattle

7050
7205

471
50

107
44

New Stuyahok
Pedro Bay

59.4518085
59.7768286

-157.3207794
-154.1483802

Bristol Bay
Bristol Bay

Seattle
Seattle

Perryville ANVSA

7215

107

45

Perryville

55.9139846

-159.1632767

Bristol Bay

Seattle

Oscarville ANVSA

7175

61

20

Oscarville

60.7236478

-161.775834

Calista

Seattle

Pilot Point ANVSA

7225

100

60

Pilot Point

57.5545282

-157.575306

Bristol Bay

Seattle

Ouzinkie ANVSA

7180

225

86

Ouzinkie

57.9237326

-152.5002138

Koniag

Seattle

Pitkas Point ANVSA

7235

125

42

Pitkas Point

62.0345494

-163.2826137

Calista

Seattle

Platinum ANVSA

7245

41

26

Platinum

59.0094965

-161.8236582

Seattle

Point Hope ANVSA

7250

757

215

Point Hope

68.3485799

-166.7693181

Calista
Arctic
Slope

Lower Kalskag
ANVSA
Lime Village
ANVSA
Levelock ANVSA

Alaska Native
Village Name

Seattle

113

Tribe Name

Native Village of Point
Lay
Point Possession,
Incorporated
Portage Creek Village
Petersburg Indian
Association
Native Village of
Nuiqsut
Ninilchik Village
Native Village of
Noatak
Nome Eskimo
Community
Nondalton Village
Pauloff Harbor Village
Northway Village
Village of Old Harbor
Nulato Village
Native Village of
Nunam Iqua
Native Village of
Nunapitchuk
Village of Ohogamiut
Noorvik Native
Community

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Point Lay ANVSA

7255

247

67

Point Possession
Portage Creek
ANVSA

7257

0

0

7260

36

22

Petersburg

7220

0

0

Nuiqsut ANVSA
Ninilchik ANVSA

7125
7080

433
13,264

126
7,007

Noatak ANVSA

7085

428

Nome
Nondalton ANVSA
Pauloff Harbor

7095
7100
7195

Northway ANVSA
Old Harbor ANVSA
Nulato ANVSA
Nunam Iqua ANVSA
Nunapitchuk
ANVSA
Ohogamiut ANVSA
Noorvik ANVSA

Alaska Native
Village Name

Point
Location Latitude

Point
Location Longitude

Alaska
Native
Regional
Corporatio
n Name

Regional
Census
Center

Point Lay

69.7426654

-163.0081627

Arctic
Slope

Seattle

Point Possession

61.0307945

-150.4110377

Cook Inlet

Seattle

Portage Creek

58.9072773

-157.7174301

Bristol Bay

Seattle

Petersburg

56.8112667

-132.9512425

Seattle

Nuiqsut
Ninilchik

70.2166008
60.0299672

-150.9999733
-151.6936161

Sealaska
Arctic
Slope
Cook Inlet

106

Noatak

67.5716105

-162.9676294

0
221
0

0
120
0

64.4999264
59.9634006
54.4576992

7115
7150
7130

107
237
336

39
111
119

7133

164

45

Nome
Nondalton
Pauloff Harbor
Northway
(Northway Village)
Old Harbor
Nulato
Nunam Iqua
(Sheldon Point)

7135
7145

466
0

120
4

7110

634

157

Seattle
Seattle

-165.3939641
-154.8564289
-162.7071458

NANA
Bering
Straits
Bristol Bay
Aleut

Seattle
Seattle
Seattle
Seattle

62.98222
57.2104162
64.724638

-141.95167
-153.303112
-158.1066292

Doyon
Koniag
Doyon

Seattle
Seattle
Seattle

62.5298955

-164.8525142

Calista

Seattle

Nunapitchuk
Ohogamiut

60.8967946
61.5703795

-162.4522001
-161.8648259

Calista
Calista

Seattle
Seattle

Noorvik

66.8344824

-161.0439804

NANA

Seattle

114

OMB No. 0607-0795: Approval Expires 03/31/09

Table C. Federally Recognized Tribes in Oklahoma with a former American Indian reservation in
Oklahoma
Tribe Name

Seneca-Cayuga
Tribe
Otoe-Missouria
Tribe of Indians
Ottawa Tribe

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

5835

3,997

2,874

5760

778

323

Ottawa OTSA

5770

6,204

2,764

Pawnee OTSA

5780

16,509

7,407

Peoria OTSA

5795

4,840

2,051

Ponca OTSA

5800

2,284

904

Quapaw OTSA
Seminole
OTSA

5810

7,455

3,119

5830

22,792

10,255

5740

228

79

5860

4,119

1,786

5890

1,678

741

5720

193,260

81,174

5820

55,690

24,684

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

5540

14,638

6,897

OTSA Tribal Sub.,
CDP

Kansas City

5720

193,260

81,174

OTSA Tribal Sub.,
CDP

Kansas City

5540

14,638

6,897

OTSA Tribal Sub.,
CDP

Kansas City

Modoc Tribe
Tonkawa Tribe of
Indians
Wyandotte Nation
Apache Tribe

Sac & Fox Nation,
Oklahoma
Wichita and
Affiliated Tribes
(Wichita, Keechi,
Waco &
Tawakonie)
Fort Sill Apache
Tribe

Delaware Nation

Modoc OTSA
Tonkawa
OTSA
Wyandotte
OTSA
KiowaComancheApache-Fort
Sill Apache
OTSA
Sac and Fox
OTSA
CaddoWichitaDelaware
OTSA
KiowaComancheApache-Fort
Sill Apache
OTSA
CaddoWichitaDelaware
OTSA

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

Regional
Census
Center

Seneca-Cayuga
OTSA
Otoe-Missouria
OTSA

Pawnee Nation
Peoria Tribe of
Indians
Ponca Tribe of
Indians
Quapaw Tribe of
Indians
Seminole Nation

2010 Census Areas
Eligible for
Delineation

Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City
Kansas City

Kansas City
Kansas City

Tribe Name

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

5730

271

103

5550

462,327

204,270

5560

157,869

66,836

5580

277,416

127,634

5590

224,472

101,877

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

5600

106,624

41,192

OTSA Tribal Sub.,
CDP

Kansas City

5720

193,260

81,174

OTSA Tribal Sub.,
CDP

Kansas City

5540

14,638

6,897

OTSA Tribal Sub.,
CDP

Kansas City

5600

106,624

41,192

OTSA Tribal Sub.,
CDP

Kansas City

5720

193,260

81,174

5700

18,544

7,130

Kaw OTSA

5690

6,123

2,759

Iowa OTSA
Eastern
Shawnee
OTSA

5670

6,148

2,536

5640

661

278

Creek OTSA

5620

704,565

306,727

Miami Tribe
Cherokee Nation
Cheyenne and
Arapahoe Tribes
Chickasaw Nation
Choctaw Nation
Absentee-Shawnee
Tribe of Indians

Comanche Nation

Caddo Nation

Citizen
Potawatomi Nation

Kiowa Indian Tribe

Kickapoo Tribe of
Oklahoma
Kaw Nation
Iowa Tribe of
Oklahoma
Eastern Shawnee
Tribe
Muscogee (Creek)
Nation

Miami OTSA
Cherokee
OTSA
CheyenneArapaho
OTSA
Chickasaw
OTSA
Choctaw
OTSA
Citizen
Potawatomi
NationAbsentee
Shawnee
OTSA
KiowaComancheApache-Fort
Sill Apache
OTSA
CaddoWichitaDelaware
OTSA
Citizen
Potawatomi
NationAbsentee
Shawnee
OTSA
KiowaComancheApache-Fort
Sill Apache
OTSA
Kickapoo
OTSA

2010 Census Areas
Eligible for
Delineation
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

Regional
Census
Center

Kansas City
Kansas City

Kansas City
Kansas City
Kansas City

Kansas City
Kansas City
Kansas City
Kansas City

Kansas City
Kansas City

116

Table D. State Recognized Tribes
Tribe Name

Waccamaw Indian
People
Santee Indian
Organization
Choctaw Apache Tribe
Pee Dee Indian Nation
of Upper South Carolina
Nansemond Indian Tribe
Pee Dee Tribe
Rappahannock Tribe
Upper Mattaponi Indian
Tribe
Echota Cherokee Tribe
Little Shell Tribe of
Chippewa Indians
Point-Au-Chen Tribe
United Houma Nation
Clifton Choctaw Tribe
Adai Caddo Tribe
Monacan Indian Nation
Beaver Creek Indians
Occaneechi Band of
Saponi Nation
Four Winds Tribe
Cherokee Tribe of
Northeast Alabama
Ramapough Lenape
Indian Nation
Chickahominy Indians
Eastern Division

Area Name

Tribal Area
Placeholder
Tribal Area
Placeholder
Apache Choctaw
SDAISA
Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Echota Cherokee
SDAISA
Tribal Area
Placeholder
Tribal Area
Placeholder
United Houma
Nation SDAISA
Clifton Choctaw
SDAISA
Adais Caddo
SDAISA
Tribal Area
Placeholder
Tribal Area
Placeholder
Tribal Area
Placeholder
Four Winds
Cherokee SDAISA
Cherokee Tribe of
Northeast Alabama
SDAISA
Ramapough
SDAISA
Eastern
Chickahominy
SDAISA

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units
0

2010
Census
Areas
Eligible for
Delineation
SDTSA

0

0

0

Regional
Census
Center

Charlotte

0

0

SDTSA

Charlotte

9515

23,459

13,671

SDTSA

Dallas

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

9680

65,068

26,997

SDTSA

Atlanta

0000

0

0

SDTSA

Denver

0

0

0

SDTSA

Dallas

9960

839,880

337,007

SDTSA

Dallas

9630

476

205

SDTSA

Dallas

9510

39,080

16,890

SDTSA

Dallas

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

0

0

0

SDTSA

Charlotte

9720

79,657

34,316

SDTSA

Dallas

9560

173

92

SDTSA

Atlanta

9850

892

262

SDTSA

Philadelphia

9675

104

42

SDTSA

Charlotte

117

Tribe Name

Nanticoke Lenni-Lenape
Indians
Nanticoke Indian Tribe
Haliwa-Saponi Tribe
Chickahominy Indian
Tribe
Biloxi-Chitimacha
Confederation/Bayou
LaFourche Band
Coharie Tribe
Piqua Shawnee Tribe
MaChis Lower Creek
Tribe
Star Clan of Muscogee
Creeks
Meherrin Tribe
Waccamaw Siouan
Tribe
Cherokees of Southeast
Alabama
United Cherokee AniYun-Wiya Nation
Lumbee Tribe
Person County Indians
(Sappony)
Pamunkey Indian Tribe
Lower Muscogee Creek
Tribe
MOWA Band of
Choctaw Indians
Mattaponi Indian Tribe
Shinnecock Indian
Nation
Paugussett Indian
Nation
Powhatan-Renape
Hassanamisco Band of
the Nipmuc Nation

Area Name

Nanticoke Lenni
Lenape SDAISA
Nanticoke Indian
Tribe SDAISA
Haliwa-Saponi
SDAISA
Chickahominy
SDAISA
Tribal Area
Placeholder
Coharie SDAISA
Tribal Area
Placeholder
MaChis Lower
Creek SDAISA
Star Musckogee
Creek SDAISA
Meherrin SDAISA
Waccamaw Siouan
SDAISA
Cherokees of
Southeast Alabama
SDAISA
Tribal Area
Placeholder
Lumbee SDAISA
Indians of Person
County SDAISA
Pamunkey (state)
Reservation
Tama (state)
Reservation
MOWA Choctaw
(state) Reservation
Mattaponi (state)
Reservation
Shinnecock (state)
Reservation
Golden Hill (state)
Reservation
Rankokus (state)
Reservation
Hassanamisco
(state) Reservation

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units
2,959

2010
Census
Areas
Eligible for
Delineation
SDTSA

9835

12,316

9830

Regional
Census
Center

Philadelphia

22,683

17,594

SDTSA

Philadelphia

9745

8,272

3,384

SDTSA

Charlotte

9580

3,313

1,311

SDTSA

Charlotte

0

0

0

SDTSA

Dallas

9635
0

123,761
0

54,248
0

SDTSA
SDTSA

Charlotte
Atlanta

9820

24,198

11,048

SDTSA

Atlanta

9880

7,331

3,508

SDTSA

Atlanta

9825
9970

7,867
2,329

3,419
891

SDTSA
SDTSA

Charlotte
Charlotte

9550

120,294

55,734

SDTSA

Atlanta

0

0

0

SDTSA

Atlanta

9815
9760

474,100
1,919

184,305
811

SDTSA
SDTSA

Charlotte
Charlotte

9260

58

36

State Res.

Charlotte

9400

57

21

State Res.

Atlanta

9240

124

37

State Res.

Atlanta

9230

58

28

State Res.

Charlotte

9370

504

194

State Res.

New York

9100

0

0

State Res.

Boston

9330

0

0

State Res.

Philadelphia

9150

2

1

State Res.

Boston

118

Tribe Name

Paucatuck Eastern
Pequot Indians

Paucatuck Eastern
Pequot (state)
Reservation

9280

26

19

2010
Census
Areas
Eligible for
Delineation
State Res.

Schaghticoke Tribe

Schaghticoke
(state) Reservation
Poospatuck (state)
Reservation

9350

9

4

State Res.

Boston

9300

283

104

State Res.

New York

Poospatuck Indian
Nation

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

Regional
Census
Center

Boston

119

Appendix 2. Justifications for Unmet Criteria and Thresholds
Throughout the QC process, unmet population and housing unit thresholds as well as noncontiguous
areas must be justified. This appendix lists all expected justifications for each entity type. Expected
justifications may be selected from the pull-down menus in the QC Tool. Custom justifications may
also be typed directly into the combination text box pull-down menus in the QC Tool.
Alaska Native village statistical areas (ANVSAs)
Acronyms ANV: Alaska Native village, ANRC: Alaska Native Regional Corporation, HU: housing units, pop: population, UA: urbanized
area

Below 3 HUs per Sq. Mile
a. New ANV HUs built since 2000.
b. Includes ANV area w/o HUs (ANV government structures, ANV ceremonial areas,
ANV businesses, and/or ANV subsistence campsites).
c. Includes area of planned ANV development (pre-2020).
d. HU counts provided are not correct.
Above 325 Sq. Miles
a. ANV pop/HUs throughout ANVSA and cannot be separated from non-ANV pop/HUs.
More Than One ANRC
a. ANV HUs located outside of ANRC.
b. ANRC boundary is incorrect.
Below 30% Alaska Native Population
a. ANV pop throughout ANVSA and cannot be separated from non-ANV pop.
b. Seasonally occupied ANV HUs included.
c. Pop counts provided are incorrect.
Noncontiguous Areas
a. Below 30% Alaska Native and/or 3 HUs per square mile if contiguous.
b. Larger than 325 square miles in area if contiguous.
c. Large water area excluded.
d. Military installation and/or urbanized area excluded.
e. Separate seasonal occupation areas included.
f. ANV has two or more separate populated centers.
Includes UA (urbanized area)
No justifications for ANVSAs within the two UAs (Anchorage and Fairbanks) in Alaska.

120

Tribal designated statistical areas (TDSAs)
Acronyms HU: housing units, pop: population, UA: urbanized area

Below 30% American Indian Population
a. Tribal pop throughout TDSA and cannot be separated from non-American Indian pop.
b. Pop counts provided are incorrect.
Below 3 HUs per Sq. Mile
a. New tribal HUs built since 2000.
b. Includes tribal area w/o HUs (tribal government structures, tribal ceremonial areas, and/or
tribal businesses).
c. Includes area of planned tribal development (pre-2020).
d. HU counts provided are not correct.
Below 1,200 pop and/or 480 HUs
a. Tribe does not have enough enrolled members and/or American Indians receiving tribal
governmental services.
b. Below 30% American Indian and/or 3 HUs per square mile if threshold met.
c. New tribal HUs built since 2000.
d. Larger than other AIAs in region and/or state if more pop/HUs included.
e. Pop and/or HU counts provided are incorrect.
Noncontiguous Areas
a. Below 30% American Indian and/or 3 HUs per square mile if contiguous.
b. Larger than other AIAs in region and/or state if contiguous.
c. Large water area excluded.
d. Military installation and/or urbanized area excluded.
e. Tribe has two or more separate populated centers.
f. Noncontiguous area includes tribal area w/o HUs (tribal government structures, tribal
ceremonial areas, and/or tribal businesses).
Includes UA (urbanized area)
a. Area >30% American Indian pop and/or includes significant portion of tribal members.
b. Includes tribal area w/o HUs (tribal government structures, tribal ceremonial areas, and/or
tribal businesses).

121

State designated tribal statistical areas (SDTSAs)
Acronyms HU: housing units, pop: population, UA: urbanized area

Below 30% American Indian Pop
a. Tribal pop throughout SDTSA and cannot be separated from non-American Indian pop.
b. Pop counts provided are incorrect.
Below 3 HUs per Sq Mile
a. New tribal HUs built since 2000.
b. Includes tribal area w/o HUs (tribal government structures, tribal ceremonial areas, and/or
tribal businesses).
c. Includes area of planned tribal development (pre-2020).
d. HU counts provided are not correct.
Below 1,200 Pop and/or 480 HUs
a. Tribe does not have enough enrolled members and/or American Indians receiving tribal
governmental services.
b. Below 30% American Indian and/or 3 HUs per square mile if threshold met.
c. New tribal HUs built since 2000.
d. Larger than other AIAs in region and/or state if more pop/HUs included.
e. Pop and/or HU counts provided are incorrect.
Noncontiguous Areas
a. Below 30% American Indian and/or 3 HUs per square mile if contiguous.
b. Larger than other AIAs in region and/or state if contiguous.
c. Large water area excluded.
d. Military installation and/or urbanized area excluded.
e. Tribe has two or more separate populated centers.
f. Noncontiguous area includes tribal area w/o HUs (tribal government structures, tribal
ceremonial areas, and/or tribal businesses).
Includes UA (urbanized area)
a. Area >30% American Indian pop and/or includes significant portion of tribal members.
b. Includes tribal area w/o HUs (tribal government structures, tribal ceremonial areas, and/or
tribal businesses).

122

OMB No. 0607-0795: Approval Expires 03/31/09

Tribal census tracts
Acronyms HU: housing units, pop: population

Below 1,200 Pop
a. Includes >480 HUs.
b. AIR/ORTL does not include enough pop.
c. New tribal HUs built since 2000; will meet threshold.
d. Includes area for new planned HUs (pre-2020).
e. Pop counts provided are incorrect.
Below 480 HUs
a. Includes >1,200 pop.
b. AIR/ORTL does not include enough HUs.
c. New tribal HUs built since 2000; will meet threshold.
d. Includes area for new planned HUs (pre-2020).
e. HU counts provided are not correct.
Above 8,000 Pop
a. Includes <3,200 HUs.
b. Pop all associated with the same GQ.
c. Large amount of seasonally occupied HUs.
d. Pop counts provided are incorrect.
Above 3,200 HUs
a. Includes <8,000 pop.
b. Large amount of seasonally occupied HUs.
c. Large amount of HUs reserved for cultural reasons; not vacant.
d. Large amount of HUs uninhabitable.
e. HU counts provided are not correct.
Noncontiguous Areas
a. AIR/ORTL is noncontiguous.

Tribal block groups
Acronyms HU: housing units, pop: population

Below 600 Pop
a. Includes >240 HUs.
b. AIR/ORTL does not include enough pop.
c. New tribal HUs built since 2000; will meet threshold.
d. Includes area for new planned HUs (pre-2020).
e. Pop counts provided are incorrect.
Below 240 HUs
a. Includes >600 pop.
b. AIR/ORTL does not include enough HUs.

c. New tribal HUs built since 2000; will meet threshold.
d. Includes area for new planned HUs (pre-2020).
e. HU counts provided are not correct.
Above 3,000 Pop
a. Includes <1,200 HUs.
b. Pop all associated with the same GQ.
c. Large amount of seasonally occupied HUs.
d. Pop counts provided are incorrect.
Above 1,200 HUs
a. Includes <3,000 pop.
b. Large amount of seasonally occupied HUs.
c. Large amount of HUs reserved for cultural reasons; not vacant.
d. Large amount of HUs uninhabitable.
e. HU counts provided are not correct.
Noncontiguous Areas
a. AIR/ORTL is noncontiguous.
OTSA tribal subdivisions
Noncontiguous Areas
a. Tribal subdivisions are noncontiguous.
Census designated places (CDPs)
Acronyms GQ: group quarters, HU: housing units, pop: population

Below 10 HUs
a. Includes GQ.
b. New HUs built since 2000; will meet threshold.
c. Includes area for new planned HUs (pre-2020).
d. HU counts provided are not correct.
Noncontiguous Areas
a. Military installation excluded.
b. CDP has two or more separate populated centers, but is considered one community.
c. CDP is too large if contiguous.

124

Appendix 3. Glossary of Terms
2010 Census tabulation blocks Blocks determined in October 2010 that will be used to tabulate the
data used to report the 2010 Census.
Alaska Native village statistical area (ANVSA) ANVSAs are statistical geographic entities
representing the residences, permanent and/or seasonal, for Alaska Native members of the defining
Alaska Native village (ANV) and that are located within the ANV’s historic/traditional region.
American Community Survey The American Community Survey is a Census Bureau survey that is
sent to a small percentage of our population on a rotating basis. It is also conducted in Puerto Rico,
where it is called the Puerto Rico Community Survey.
American FactFinder The Census Bureau's data website and search tool located at www.census.gov
(click on “American FactFinder” in the left menu).
American Indian off-reservation trust lands (ORTLs)American Indian trust land is an area for which
the United States holds title in trust for the benefit of an American Indian tribe or for an individual
American Indian. Trust land may be located on or off a reservation; however, the Census Bureau
recognizes and tabulates data only for off-reservation trust land. Census data always associates offreservation trust land with a specific federally recognized reservation and/or tribal government.
American Indian reservation (AIR) A federal American Indian reservation is an area that has been set
aside by the United States for the use of one or more federally recognized American Indian tribes. Its
boundary is defined by tribal treaty, agreement, executive or secretarial order, federal statute, or judicial
determination. The Census Bureau recognizes a federal reservation as territory over which a tribe(s) has
primary governmental authority. A state American Indian reservation is an area that a state government
has allocated to a tribe recognized by that state, but not by the federal government. American Indian
reservations are known as colonies, communities, Indian communities, Indian villages, pueblos,
rancherias, ranches, reservations, reserves, and villages.
Block Definition Project (BDP) The BDP provides an opportunity for tribes to review the features that
we plan to hold as 2010 tabulation block boundaries and to flag additional features that tribes wish to be
included as 2010 tabulation block boundaries.
Boundary and Annexation Survey (BAS) An annual survey conducted by the Census Bureau to
collect and maintain information on the inventory, status, boundaries, and names of all governmental
units.
Census Designated Place (CDP) CDPs represent locally-known, unincorporated communities that
contain a mix of residential, commercial, cultural, and/or retail uses similar to that of an incorporated
place of similar size in a similar geographic setting.
Feature A group of connected line segments with the same primary name and classification.

125

Feature extension A nonvisible line from the end of a road that extends at an angle of 180 degrees and
is no longer than 300 feet in length and connects the road to a non-road feature.
Federal Information Processing Standards (FIPS) code Codes that are assigned for a variety of
geographic entities, including American Indian area, Alaska Native area, Hawaiian home land,
congressional district, county, county subdivision, metropolitan area, place, and state. The objective of
FIPS codes is to improve the ability to use the data resources of the federal government and avoid
unnecessary duplication and incompatibilities in the collection, processing, and dissemination of data.
Geographic Areas Branch (GAB) The branch in the Census Bureau’s Geography Division responsible
for managing the geographic components of the Tribal Statistical Areas Program.
Geographic Information System (GIS) A collection of computer hardware, software, and geographic
data for capturing, managing, analyzing, and displaying all forms of geographically referenced
information.
Incorporated place A type of governmental unit, incorporated under state law as a city, town (except in
New England, New York, and Wisconsin), borough (except in Alaska and New York), or village,
generally to provide specific governmental services for a concentration of people within legally
prescribed boundaries.
Minor civil division (MCD) The primary governmental or administrative division of a county in many
states.
Noncontiguous Geographic areas that are not adjacent to one another and do not share a common
boundary.
Nonvisible boundary Boundaries, such as city, town, township, and property lines that do not follow a
physical feature.
Oklahoma tribal statistical area (OTSA) OTSAs are identified and delineated by the Census Bureau
in conjunction with federally recognized tribes and are intended to provide a geographic framework for
tabulating statistical data for federally recognized American Indian tribes that had an AIR in Oklahoma
prior to statehood.
OTSA tribal subdivisions Tribal subdivisions are units of self-government and/or administration within
an AIR and/or ORTL for a federally recognized tribe, or an OTSA, that serve social, cultural, and/or
legal purposes for the tribal government.
Regional Census Center (RCC) Temporary offices set up approximately two years prior to the
decennial census. The geographic staff from the permanent Regional Offices are assigned to the RCCs.
Relationship (geographic) A geographic area that shares a boundary with one or more other geographic
areas.

126

Shapefiles An ArcView GIS data set used to represent a set of geographic features such as streets,
hospital locations, trade areas, and ZIP Code boundaries. Shapefiles can represent point, line, or area
features. Each feature in a shapefile represents a single geographic feature and its attributes.
State liaison Person designated by the governor of each state with state recognized American Indian
tribes to work with the Census Bureau on the Tribal Statistical Areas Program.
State designated tribal statistical area (SDTSA) A tribal statistical area delineated for a state
recognized American Indian tribe that does not have an American Indian reservation. A SDTSA should
represent a compact, contiguous area containing a statistically significant concentration of people who
identify with a specific state recognized American Indian tribe in which there is structured or organized
tribal activity.
State American Indian reservation State American Indian Reservations (AIRs) and their legal
boundaries are established pursuant to state law. States may have an established process whereby staterecognized tribes can obtain a reservation. Several eastern states have continued to recognize state AIRs
established through laws, often treaties, of one of the original thirteen colonial assemblies and/or Great
Britain during the colonial era.
State Reservation Program (SRP) The SRP occurs once before each decennial census, and is a survey
of state American Indian reservations for those states with state-recognized tribes that are not also
federally recognized. Through the State Reservation Program, the Census Bureau accepts legal
boundary, name, official status updates as well as additions and updates to features such as roads or
rivers that serve as a boundary for the state AIR, as well as address range break information at the
boundaries.
Tribal block group A tribal statistical area that represents a collection of census blocks. Tribal block
groups nest within tribal census tracts and like tribal census tracts they are specifically delineated for
federall y recognized American Indian reservations (AIRs) and/or off-reservation trust lands (ORTLs)
without the imposition of state or county boundaries. Tribal block groups are otherwise conceptually
similar and equivalent to standard block groups.
Tribal census tract A tribal statistical area specifically delineated for federally recognized American
Indian reservations (AIRs) and/or off-reservation trust lands (ORTLs) without the imposition of state or
county boundaries. Tribal census tracts are otherwise conceptually similar and equivalent to standard
census tracts.
Tribal designated statistical areas (TDSA) A tribal statistical area delineated by a federally recognized
tribe that does not have an American Indian reservation and/or off-reservation trust lands. A TDSA
should represent a compact, contiguous area containing a statistically significant concentration of people
who identify with a specific federally recognized American Indian tribe in which there is structured or
organized tribal activity.
Tribal Statistical Areas Program (TSAP) The Tribal Statistical Areas Program (TSAP) is offered as a
part of the 2010 Decennial Census. It is a comprehensive but voluntary opportunity to update or

127

delineate, as appropriate, the diverse geographic statistical areas represented by American Indian and
Alaska Native areas (AIANAs).
Urbanized Areas (UAs) An urbanized area consists of densely settled territory that contains 50,000 or
more people. The Census Bureau delineates UAs to provide a better separation of urban and rural
territory, population, and housing in the vicinity of large places. UAs are redefined after each decennial
census. The UAs utilized in TSAP were defined just after 2000 using Census 2000 data.

128

Appendix 4. List of Shapefiles Included on the TSAP CD
Layer
Alaska Native Regional Corporations (ANRC)
American Indian / Alaska Native Areas (AIANA)
Statistical
American Indian Areas (AIA) -Legal
American Indian Tribal Subdivisions (AITS) - Legal
American Indian Tribal Subdivisions (AITS) - Statistical
Traffic Analysis Zones (TAZ)
Urban Growth Areas
Census Block Groups
Census Blocks – Current
Census Blocks – Census 2000
Census Tracts
Census Designated Places (CDP)
Consolidated Cities
Counties and Equivalent Areas
County Subdivisions - Legal
County Subdivisions - Statistical
Incorporated Places
States and Equivalent Areas
2000 Urbanized Areas
All Lines
Area Landmark
Hydrography - Area
Point Landmarks

Shapefile
Name
anrc
aias
aial
aitsl
aitss
taz
uga
bg
tabblock
tabblock2000
curtracts
cdp
concity
county
mcd
mcd
place
state
uac
edges
arealm
water
pointlm

129

Appendix 5. Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail:
charlotte.rcc.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 488-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th Street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

130

2010 Census Tribal Statistical Areas Program

Guidelines for Delineating Statistical Areas within
American Indian Areas

Version 1
January 2008

1. Introduction.................................................................................................................. 3
2. Background .................................................................................................................. 5
2.1.1 Background and Comparison of Tribal census tracts and block groups to
standard census tracts and block groups ..................................................................... 5
2.1.2 The Importance of Population and Housing Unit Thresholds ........................... 8
2.1.3 Census Designated Places.................................................................................. 9
2.1.4 Block Definition Project (BDP)......................................................................... 9
2.2 Tribes eligible to delineate TCTs, TBGs, CDPs and participate in the BDP .. 11
2.3 The Boundary and Annexation Survey .............................................................. 11
2.4 Schedule ................................................................................................................. 12
2.5 Materials needed for delineating TCTs, TBGs, CDPs and suggesting 2010
tabulation census block boundaries .......................................................................... 12
2.6 Important information on features ..................................................................... 14
2.6.1 Acceptable features for use as statistical area boundaries ............................... 14
2.6.3 Boundary feature updates ................................................................................ 15
2.7 Current state of Census road features ................................................................ 15
2.7.1 Guidelines for Updating Features .................................................................... 16
2.8 Feature Extension Criteria................................................................................... 16
3. Criteria......................................................................................................................... 17
3.1 Tribal census tract Criteria and Guidelines....................................................... 17
3.2 Tribal block group criteria and guidelines:........................................................ 17
3.3 Special Land Use TCTs and TBGs...................................................................... 18
3.4 Census designated place criteria and guidelines:............................................... 19
Guidelines for delineating census designated places are: ............................................. 19
4. Procedures ................................................................................................................... 20
4.1 Annotation of Maps .............................................................................................. 20
4.1.1 Example ........................................................................................................... 21
4.2 Transmitting Completed Submissions and Census Bureau Review ................ 22
4.3 Verification ............................................................................................................ 22
Appendix A – American Indian statistical areas eligible for delineation .................. 23
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder...................................................................................................... 39
Appendix C – Regional Census Center’s Contact Information.................................. 44

2

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people
and the economy. The U.S. Constitution mandates that a census be taken every 10 years
in order to reapportion the House of Representatives. The data gathered by the decennial
census and other Census Bureau programs are used for several other purposes, including
the allocation and distribution of funds to state, local and tribal governments. Census
information shapes important policy decisions that in turn shape the nation’s social and
economic conditions. While best known for the decennial census, the Census Bureau
conducts numerous surveys and censuses that measure changing individual and
household demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need.
Many tribal communities use census information to attract new business and plan for
growth. In fact, many tribes and tribal organizations use census data to plan new
facilities and programs for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has developed the Tribal
Statistical Area Program (TSAP) to collect updates to the inventory and boundaries of
American Indian and Alaska Native statistical geographic areas. Federally recognized
tribes with reservations or trust lands also have the opportunity to suggest features that
could be used as 2010 tabulation block boundaries as part of the Block Definition Project
(BDP). Participation in the TSAP is voluntary. If your tribe chooses not to participate,
the Census Bureau may revise the boundary of an existing area or delineate a new area in
accordance with published criteria and guidelines. The TSAP includes the following
statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts (TCTs) and tribal block groups (TBGs) on American Indian
reservations (AIRs) and/or off-reservation trust lands (ORTLs)
census designated places (CDPs)

The Census Bureau will tabulate statistical data from the 2010 Census for each entity
type listed above, and will continue to use these areas to provide data from the American
Community Survey (ACS) through the coming decade. Meaningful statistical data from
the 2010 Census and ACS provide tribes and other data users with a tool to help them
make informed decisions and plan for community services. More information about the
background and components of these geographic areas as well as the delineation update
criteria and guidelines can be found in the Federal Register notice Vol. 73, No. 221 /
Friday, November 14, 2008, page 67470. This notice can also be accessed from our
TSAP webpage:
http://www.census.gov/geo/www/tsap2010/tsap2010.html

3

Each federally recognized tribe with a reservation or off-reservation trust land is eligible
to delineate CDPs and suggest boundaries to be held as 2010 Census block boundaries.
Your tribe may also be eligible to delineate multiple TCTs and/or TBGs. See Appendix
A for a list of all federally recognized tribes and the types of statistical American Indian
Areas (AIAs) they are eligible to delineate.
Tribes wishing to participate in the TSAP will have the option of delineating their
geographic statistical areas using paper maps or Census Bureau-provided shapefiles and
an ESRI® ArcGIS® extension specific to this program. Participants who chose to
submit changes using the digital method must have ArcGIS version 9.2 or 9.3. These
guidelines provide instructions for the use of paper maps. There are separate guidelines
for the use of the ESRI extension which are found on the data disc supplied by the
Census Bureau.
The TSAP Extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides
a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management
features of the extension. In addition to the inherent functionality of the ArcGIS
software, the extension’s unique editing tools consist of geographic area assignment,
block boundary definition, tribal tract/tribal block group type attribution, as well as line
editing and polygon split/merge functions. The option of using either the TSAP
extension or the paper maps to submit changes is at the complete discretion of each tribe
as neither is preferred over the other by the Census Bureau. However, depending on the
number anticipated updates and/or their complexity, you might consider using the TSAP
extension which offers you the ability to view population density within American Indian
statistical areas and allow you to more clearly add or remove area or adjust boundaries.
If you are interested in using this GIS application to submit your boundaries and you
have ArcGIS 9.2 or 9.3 software, but did not receive the ArcGIS extension software or
digital data files along with your materials, please contact the Census Bureau’s Regional
Census Center (RCC). 1 You may also contact the RCC staff to ask other questions or to
arrange for training.
These guidelines explain the criteria and complete instructions for delineating TCTs,
TBGs and CDPs and suggesting 2010 tabulation block boundaries using paper maps.
The topics covered are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
1

Background and description of each entity type
Explanation of eligibility
Schedule
Required materials
Criteria
Procedures for annotating of maps
Procedures for transmitting completed submissions
Census Bureau submission review
See Appendix A to find the RCC assigned to help you and Appendix C for contact.

4

ƒ

Verification

Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is
used to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical
tribal entities for use in tabulating and publishing data from the 2010 Census, the
American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours
per respondent, including time for reviewing instructions, assembling materials,
organizing and reviewing the information, and reporting any needed changes. We
anticipate that an estimated 650 participants will respond. Remaining entities may be
worked by Census Bureau regional staff. For larger areas or areas with many changes,
however, the respondent burden may be 180 hours or longer to complete. Please send
comments regarding this burden estimate or any other aspect of this collection of
information, including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 06070795” as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background
2.1.1 Background and Comparison of Tribal census tracts and block groups to standard
census tracts and block groups
Census tracts are the oldest and one of the most utilized statistical geographic entities for
which the Census Bureau tabulates data. The primary purpose of census tracts is to
provide a set of nationally consistent small, statistical geographic units, with stable
boundaries that facilitate analysis of data across time.

5

Tribal census tracts are statistical geographic entities defined by the Census Bureau in
cooperation with tribal officials, unique to and within the boundaries of federally
recognized American Indian reservations and/or off-reservation trust lands. Tribal census
tracts recognize the unique statistical data needs of federally recognized American Indian
tribes. The delineation allows for an unambiguous presentation of tract-level data
specific to the American Indian reservation and/or off-reservation trust lands without the
imposition of state or county boundaries.
For Census 2000 products in which data were presented by state and county, the standard
state/county census tract hierarchy was maintained, even for territory contained within an
AIR and/or ORTL. In such instances, the state/county portions of a tribal census tract
were identified as individual standard census tracts. These standard census tracts may not
have met the minimum population or housing unit thresholds, potentially limiting sample
data reliability or availability for both the tribal census tract and the derived standard
tracts. For the 2010 Census, the Census Bureau will identify tribal census tracts and
tribal block groups as a geographic framework completely separate from standard census
tracts and standard block groups (Figure 1). The change for tribal census tracts and tribal
block groups for the 2010 Census seeks to eliminate, in part, the data issues associated
with the Census 2000 approach, so that for the 2010 Census more census tracts and block
groups, both tribal and standard, will meet the population and housing unit thresholds.
The proposed separation of these two geographic frameworks will apply to data
tabulation products, as well as to geographic information products.

Figure 1: In Census 2000, standard and tribal tracts were both used to present data in the
standard data hierarchy. In this example, the tribal tract above would have been split by a
6

county boundary, creating tracts that did not meet the criteria potentially limiting sample
data reliability or availability. For Census 2010, tribal tract and block group boundaries
will be completely independent from standard tracts and block groups.
The primary operational benefit of this change for the tribes is that they do not have to
work with any other governments or data users in delineating their tribal census tracts and
tribal block groups. Delineating tribal census tract and tribal block groups allow tribes to
derive more meaningful data for specific geographic areas within their AIRs and/or
ORTLs. Standard census tracts and standard block groups are delineated by a primary
participant in the Participant Statistical Areas Program (PSAP) (usually a regional
planning organization or county government agency), with input from a large variety of
data users who may represent competing interests. Tribes are encouraged to work with
the other PSAP participants for any areas in which they are interested 2 , on and off their
AIRs and/or ORTLs, to help define standard census tracts and standard block groups.
For federally recognized American Indian tribes with AIRs and/or ORTLs that have more
than 2,400 residents or 960 housing units (using Census 2000 data or more current tribal
data), the Census Bureau will offer the tribal government the opportunity to delineate
multiple tribal census tracts and tribal block groups on their AIR and/or ORTL. For
federally recognized tribes with an AIR and/or ORTLs that have fewer than 2,400
residents or 960 housing units, the Census Bureau will define one tribal census tract
coextensive with the AIR and/or ORTL. Federally recognized tribes with AIRs and/or
ORTLs that have at least 1,200 residents or 480 housing units may define multiple tribal
block groups on their AIR and/or ORTL. For federally recognized tribes with an AIR
and/or ORTLs that have fewer than 1,200 residents or 480 housing units, the Census
Bureau will define one tribal block group coextensive with the AIR and/or ORTL.
Tables 1 and 2 provide population and housing unit thresholds for both standard and
tribal census tracts and block groups.

All tribal census tracts and tribal block groups must follow all of the published criteria
and guidelines for standard block groups and standard census tracts (see section 3 for
criteria and guidelines), except that they do not have to nest within states or counties.
2

Contact your RCC if your tribe is interested in participating in PSAP (See Appendix C).

7

They must nest within an individual AIR and/or ORTL and must be identified uniquely
so as to clearly distinguish them from standard census tracts and block groups.
While there will be a separate hierarchy for standard and tribal census tracts and block
groups in 2010, there will only be one set of 2010 tabulation blocks. Tabulation blocks
are the smallest geographic unit for which the Census Bureau tabulates decennial census
data. Tabulation blocks will be numbered with a 4-digit code, the first digit being the
number of the standard block group in which it nests. For example, tabulation block
1001 is in standard block group 1 and block 2001 is in standard block group 2. Because
census blocks will be numbered within standard block groups and tribal block groups will
be identified uniquely from standard block groups, there will not be a relationship
between tribal block group identifiers and census block numbers. Thus, tribal block
group A might contain census blocks numbered in different ‘‘thousand’’ ranges (e.g.,
blocks 1001, 2001, and 3001).
2.1.2 The Importance of Population and Housing Unit Thresholds
Tribal census tracts and tribal block groups defined for the 2010 Census will be used to
tabulate data from the ACS. As a general rule, estimates from programs providing
sample data, including the ACS, for geographic areas with smaller populations will be
subject to higher sampling variances than comparable estimates for areas with larger
populations. In addition, the availability and amount of data published for geographic
areas with small populations may be reduced compared to that for geographic areas with
larger populations. Aiming to create tribal census tracts that meet the optimal population
of 4,000 or the optimal housing unit threshold of 1,600, and at least maintaining the
minimum population threshold of 1,200 or 480 housing units, will improve the reliability
and availability of data, and PSAP and TSAP participants should consider these factors
when defining both tribal and standard tracts. A similar relationship between size of
population and reliability and availability of data applies to tribal block groups and
standard block groups.
All statistical geographic entities, are reviewed by the Census Bureau, compared against
published criteria and guidelines, and accepted on a case-by-case basis. The Census
Bureau uses Census 2000 population and housing unit counts to verify that a tribal census
tract or tribal block group meets the thresholds, and if the thresholds are not met, the
Census Bureau may ask for other supporting information, such as tribal or local estimates
for the same area. Housing unit counts will be emphasized over population counts for
seasonal and other unique communities that may have no or low population on Census
Day (April 1). The housing unit thresholds are based on a national average of 2.5 persons
per housing unit. The Census Bureau recognizes that there are regional variations to this
average, and will take this into consideration when reviewing all tribal census tract and
tribal block group proposals, if notified. On a case-by-case basis, the Census Bureau may
waive the maximum population and housing thresholds, if requested, and if supplied an
appropriate explanation. Both population and housing unit data can be found by
accessing American FactFinder on the Census Bureau’s internet website. Directions for
obtaining this data can be found in Appendix B.

8

2.1.3 Census Designated Places
CDPs are statistical geographic areas representing closely settled, unincorporated
communities, which are locally recognized and identified by name. They are the
statistical equivalents of incorporated places, with the primary differences being the lack
of both a legally defined boundary and an active, functioning governmental structure,
chartered by the state and administered by elected officials. The primary goal of CDPs is
to map a boundary for and provide statistics for well-known, unincorporated localities. A
CDP generally consists of a contiguous cluster of census blocks comprising a single piece
of territory and containing a mix of residential and commercial uses similar to that of an
incorporated place of similar size. Some CDPs, however, may be predominantly
residential; such places should represent recognizably distinct, locally known
communities, but not typical suburban subdivisions.
CDPs are delineated through both the TSAP and the PSAP for the 2010 Census.
Federally recognized tribes with AIRs, ORTLs, or OTSAs may update or delineate new
CDPs within the boundary of their reservation, trust lands, or OTSA through the TSAP.
Tribes that would like to delineate CDPs for communities completely off their legal or
statistical area should work through the PSAP with the primary participants for the areas
in which they are interested. Contact your RCC for more information on PSAP.
2.1.4 Block Definition Project (BDP)
The BDP provides an opportunity for tribes to flag existing features that tribes want the
Census Bureau to use as 2010 tabulation block boundaries. In some cases, there may be a
physical or visible feature that is significant to the landscape and serves as a determining
factor in how population has settled on the reservation. If this is the case and the Census
Bureau does not show this feature on our map, the tribe may want to add the feature and
identify it as a suggested 2010 block boundary. Examples of this type of feature are:
above ground pipelines, ridgelines, irrigation systems, fence lines, or the edge of a
canyon. These types of features are not standard for inclusion on Census files and
products because we have no standard method for updating or collecting them. They do
however, make excellent boundaries for statistical areas such as tribal tracts, CDPs or
census blocks. For this reason they are acceptable for inclusion in the Block Definition
Project. Upon receipt of a block boundary suggestion the Census Bureau will determine
its eligibility for inclusion as a 2010 tabulation block boundary.
Below is a list of all the feature and boundary types that are currently already planned to
be held as 2010 Census tabulation block boundaries and therefore do not need to be noted
as suggested holds on the paper maps. In some instances you may not want a feature to
become a 2010 Census tabulation block boundary such as where there are roads
identified in our files as double lined roads. Due to recent updates to our data, there are
now many more roads identified as double line roads that, in the past, were classified as
single line roads. This causes the area in the middle (a median strip for example) to
become a long narrow block. If you do not want the polygon formed by the two road
edges to be a separate 2010 Census tabulation block, you may want to consistently flag
one of the edges with a “Do Not Hold.”
9

Note: If any other program sponsored by the Census Bureau uses that line as a boundary,
the Census Bureau will override the “Do Not Hold” status of the line.
Entities: The boundaries, as of January 1, 2010, for each of the entities listed below, are
planned 2010 Census tabulation block boundaries and therefore do not have to be flagged
as a 2010 block boundary.
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Hawaiian home land
Alaska Native village statistical area
Oklahoma tribal statistical area
state-designated tribal statistical area
Tribal Designated Statistical Area
American Indian joint use area
Alaska Native Regional Corporation
tribal subdivision
tribal census tract
tribal block group
state or state equivalent
county or county equivalent
county subdivision
incorporated place
consolidated city
census designated place
census tract
block group
block area group
congressional district
state legislative district (upper chamber)
state legislative district (lower chamber)
voting district
elementary school district
secondary school district
unified school district
special school administrative area
urban growth area
military installation
national park service land

Features: The features listed below will qualify as 2010 Census tabulation block
boundaries based on criteria.
ƒ
ƒ
ƒ
ƒ

primary road
secondary road
local neighborhood road, rural road, city street
vehicular trail (road passable only by a 4-wheel drive)
10

ƒ
ƒ

main line railroad feature
perennial water

2.2 Tribes eligible to delineate TCTs, TBGs, CDPs and participate in the BDP
Federally recognized tribes are eligible to delineate TCTs, TBGs, CDPs, or participate in
the BDP if they have a reservation or off-reservation trust lands. Federal recognition of
an American Indian tribe specifically means that the tribe is recognized by and eligible to
receive services from the Bureau of Indian Affairs (BIA). BIA recognition is determined
by inclusion of a tribe on the BIA’s list of recognized tribes or by addenda to the list as
published by the BIA.
All AIR and ORTLs will have at least one TCT and one TBG. If the AIR and/or ORTL
have enough population or housing units to meet the minimum population and/or housing
unit count thresholds (1,200 and 480 respectively) for the tribe is eligible to delineate
multiple TCTs and TBGs. Likewise, if the AIR and/or ORTL have enough population or
housing units to meet the minimum population or housing unit count thresholds (600 and
240 respectively), the tribe is eligible to delineate multiple TBGs. (If you are interested
in obtaining Census 2000 population and housing unit counts for TCTs, TBGs, blocks or
other areas, you can find that information on the Census Bureau’s website. See Appendix
B for instructions on obtaining that information through the American FactFinder). All
federally recognized tribes with AIRs/ORTLs, regardless of population or housing unit
counts are eligible to delieate CDPs and participate in the BDP.
Participation in TSAP is voluntary. If your tribe chooses not to participate, the Census
Bureau will delineate TCTs and TBGs for your AIR/ORTL in accordance with published
criteria and guidelines. The Census Bureau will not delineate any CDPs. For a complete
list of all federally recognized tribes and the statistical areas they are eligible to delineate
through TSAP, see Appendix B.
2.3 The Boundary and Annexation Survey
The Boundary and Annexation Survey (BAS) is an annual Census Bureau survey of legal
geographic entities that includes federal AIRs, ORTLs, and any associated tribal
subdivisions. Whereas the TSAP provides the process for reviewing and updating those
AIAs that are statistical geographic entities (TCTs, TBGs, and CDPs), the BAS provides
the process for reviewing and updating AIAs that are legal federal geographic entities,
such as the reservation itself, tribal subdivisions and ORTLs. Its purpose is to determine,
solely for data collection and tabulation by the Census Bureau, the complete and current
inventory and the correct names, legal descriptions, official status, and official, legal
boundaries of the legal geographic entities with governmental authority over certain areas
within the United States, as of January 1 of the survey year. The BAS also collects
specific information to document the legal actions that established a boundary or imposed
a boundary change. In support of the government-to-government relationship with
federally recognized American Indian tribes, the Census Bureau works directly with
tribal officials on the BAS. Through the BAS, the Census Bureau also accepts updates to
features such as roads or rivers, and address range break information at the boundaries. If

11

you wish to update boundaries for you reservation, off-reservation trust lands or legal
tribal subdivisions, you should do so through the BAS.
For more information about the BAS, contact your RCC or see the Census Bureau's Web
site at http://www.census.gov/geo/www/bas/bashome.html. The BAS Respondent
Guide for federally recognized tribes is available at:
http://www.census.gov/geo/www/bas/bas09/bas09_mat_aia.html
2.4 Schedule
In October 2008, the Census Bureau mailed formal letters to tribal officials inviting them
to participate in TSAP. These guidelines accompany the paper maps required to
complete the work. Tribes have 120 days from the date they receive these materials to
review and submit their geographic statistical area delineations or updates to the Census
Bureau’s RCC. In late 2009, after the Census Bureau has reviewed and incorporated
your delineations into our geographic database, you will receive new maps or digital files
so that you can verify that the Census Bureau has inserted your boundaries correctly. If
you have questions regarding your delineation or submission, assistance will be available
from geographers at the Census Bureau’s RCC.
2.5 Materials needed for delineating TCTs, TBGs, CDPs and suggesting 2010
tabulation census block boundaries
The types of paper maps you receive will vary depending on the size and mapping
complexity of each federal AIR/ORTLs. Federal AIR/ORTLs that are smaller in land
area may only receive a single mapsheet while federal AIR/ORTLs with large land areas
may receive an index map, a series of parent maps, and a number of inset maps. An
index map shows the complete federal AIR/ORTL with gridlines defining specific areas
shown on each parent map. A parent map shows a detailed version of a single grid box
from the index map, and an inset map shows finer details of areas within the parent map
where the feature network is too dense to represent clearly at the map scale of the parent
map. You can think of the inset map as a “blow-up” of a specific area.

Figure 2: Example of Index, Parent and Inset maps

12

The RCC will provide federally recognized tribes with AIRs and/or ORTLs with an index
map depicting the federal AIR/ORTL boundary(s) and all associated parent and inset
maps. The maps will show the tribal census tracts and tribal block group boundaries that
were delineated prior to Census 2000 within the most current AIR/ORTL boundary.
These boundaries should closely match the Census 2000 tribal census tracts and block
groups, except on those AIR/ORTLs that have had significant boundary changes since
2000. Figures 3 and 4 show the boundaries on your maps and how they are symbolized.

Figure 3: Example of Census map symbology for TCTs, TBGs, and census blocks.

Figure 4: TSAP map symbology
13

The Census Bureau requests that participants use a pencil with orange lead to annotate
tribal census tract boundaries, a pencil with brown lead to annotate block group
boundaries, and a pencil with red lead to annotate census designated places on the paper
maps provided. Procedures for annotating the paper maps are detailed in section 4.
2.6 Important information on features
2.6.1 Acceptable features for use as statistical area boundaries
Statistical area boundaries may follow specified legal or administrative boundaries that
do not change greatly over time. A list of legal or administrative boundaries is provided
below:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

American Indian reservation
Off-reservation trust land
Tribal subdivision
State
County
County subdivision
Incorporated place

Statistical area boundaries may also follow permanent, visible features, such as roads,
perennial streams, railroads, and high-tension power lines. Permanent visible features
should be easily locatable in the field by Census Bureau staff without ambiguity. The
acceptable visible boundary features are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (main)
carline, streetcar track, monorail, other mass transit rail
interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county
highway, secondary and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
14

ƒ

fencelines

Natural topographic features include the crests of well-defined mountain ridges; the rims
or bases of sharply defined escarpments, cliffs, or bluffs; the position of dry ravines or
arroyos; as well as other features as long as the features are not also mimicked by another
visible feature, have no housing in the vicinity, and are easily located on the ground.
2.6.3 Boundary feature updates
Data user and Census Bureau experience has shown that some features make better
boundaries than others, and the same type of feature can make an excellent boundary in
one place and a poor one in another. Rivers, major canals, lakes, and other bodies of
water often make good statistical area boundaries because they generally limit access
from one area to another and rarely change relative location. Other features that limit
access between areas, such as interstate and other major highways, railroad tracks, and
the ridges of mountain ranges, also make good statistical area boundaries. In some
instances, however, such a feature unifies a community, for example, a lake forming the
core of a recreational housing development or a through street forming the spine of a
subdivision. In these circumstances, the statistical area boundary should include the
entire area of the lake or both sides of a unifying street to better encompass similar
community patterns.
In general, when delineating boundaries in bodies of water represented as polygons and
having area (lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow
a line bisecting the water body rather than following a shoreline. Wherever possible, use
an existing line in water (for example, a county line in the middle of a river) rather than
adding a new line.
Officials delineating statistical AIAs may only add nonvisible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and
ridgelines, are not available and they aid in a statistical AIA meeting other specific,
delineation criteria and/or guidelines. The Census Bureau staff will contact you if they
require more information or have questions about feature updates submitted as part of our
2010 TSAP.
2.7 Current state of Census road features
The Census Bureau has spent the last six years enhancing the spatial accuracy of the
roads in our geographic database system. The local files used during this project were
required to have an overall average accuracy of 7.6 meters while some files were more
accurate.
Although much of the street network is vastly improved, as you work with our maps you
may notice that in some counties the street and boundary features look distorted. A line
that should be straight may have a noticeable kink or pointed shape. The Census Bureau
is working to correct these problems, therefore if you need to use a feature that is
distorted follow the guidelines below.

15

The Census Bureau is now moving forward with our 2010 Census field canvassing and
collection activities. This means that we are no longer processing realignments to our
street network. What is critical for the success of the 2010 Census data tabulation is the
location of roads relative to the tabulation entity boundary. As long as the road is within
the correct entity, the population and housing will be properly reported. The guidelines
below also explain what updates are acceptable as part of the TSAP.
It is critical that participants understand that TSAP is not intended for street feature
updates except where a boundary follows a road (or other visible feature such as a
stream) and the road is not reflected in our file. For this reason the Census Bureau can
not accept street (or other) feature updates that do not follow the guidelines below:
2.7.1 Guidelines for Updating Features
1. If a feature is missing and it forms the boundary for the area you are defining, add the
feature and provide the name.
2. If you can not correctly delineate the boundary for an entity you are updating because
the feature you need to follow is incorrectly located, mislabeled or distorted in the
Census Bureau’s map, we request that you fix that feature only. In addition, we
request that you report the problem area to the Census Bureau (through your RCC) by
sending information describing the incorrect feature and the specific entity boundary
affected.
3. Do not add streets that are missing for an entire housing development (add only
streets that are needed to form a boundary). We will be adding new or missing streets
during our address canvassing operation which will occur in the spring and early
summer of 2009. The Census Bureau will provide verification materials for each
participant that returns their submission in the correct format and within the allotted
120 days. These materials will show the results of address canvassing. If these
streets are still missing at that time, we will accept these streets as adds.
2.8 Feature Extension Criteria
If you want to use an existing feature that doesn’t form a closed polygon, you may add a
short line to connect the features and close the polygon. The Census Bureau refers to
these lines as feature extensions and several requirements pertain. To avoid creating
ambiguous Census block boundaries, we require that feature extensions:
ƒ Are no longer than 300 feet;
ƒ Are straight lines from the end of a road and intersecting a non-road feature
(These include all hydrographic features, pipelines, powerlines, and railroads.);
ƒ Do not intersect a cul-de-sac.

16

3. Criteria
The following criteria and guidelines were developed to help ensure that the statistical
areas delineated for the 2010 Census and beyond support their intended purpose, to
provide useful and meaningful data for the respective tribe, and enhance the ability of
data users to make comparisons between data for the various types of AIAs. Criteria are
rules that must be followed by all officials delineating statistical AIAs for the 2010
Census, while guidelines are the Census Bureau’s suggested approach for improving the
relevance and utility of statistical AIAs.
3.1 Tribal census tract Criteria and Guidelines
The tribal census tract criteria are:
1. TCTs may not cross AIR/ORTL boundaries.
2. The entire land and water area of an AIR/ORTL must be covered by one or more
TCTs.
3. TCTs should be labeled by writing “T” followed by three digits, beginning with
“T001, T002, etc.” Be sure that each new TCT label number is only used once
within the AIR/ORTL.
Guidelines for delineating tribal census tracts are:
1. Census tracts should have 4,000 people or 1,600 housing units. Meeting or
exceeding the optimum thresholds will help improve the reliability of sample data
for TCTs.
2. Each TCT must encompass at least 1,200 people or at least 480 housing units
unless it is flagged as a special land use tract (see section 3.5).
3. A TCT must comprise a reasonably compact and contiguous land area.
4. TCT boundaries should follow visible and identifiable features.
3.2 Tribal block group criteria and guidelines:
The tribal block group criteria are:
1. TBGs must not cross TCT boundaries.
2. Because TCTs must cover the entire area of each AIR/ORTL, by definition, TBGs
also must cover the entire area of each AIR/ORTL.
3. TBGs will be designated with a single capital letter from “A” through “K” (except for
the letter “I”). Tribal block group identifiers must be unique within TCTs.
Guidelines for delineating tribal block groups are:
1. Each block group must encompass at least 600 people or at least 240 housing units
unless it is coextensive with a flagged special land use tract (see section 3.5).
2. A block group must comprise a reasonable compact, contiguous land area.
3. Noncontiguous block groups are permitted only where a contiguous area or
inaccessible area would not meet population or housing unit count requirements for a
separate TBG, in which case the non contiguous or inaccessible area must be
combined with a proximate block group.

17

Figure 5: This is an example of an acceptable noncontiguous TBGs and TCTs.
4. Block group boundaries should follow visible and identifiable features.
In the handful of cases where there are Joint Use Areas, the Census Bureau will
automatically delineate one tribal census tract containing one tribal block group in each
of those areas. Tribes are not responsible for making these delineations on their maps.
3.3 Special Land Use TCTs and TBGs
To recognize and distinguish the special uses of some parcels of land, the Census Bureau
allows for the definition of special land use tribal census tracts or block groups. Specific
areas such as ceremonial grounds, historic sites, and parks can be identified as special
land use TCTs or TBGs. These areas must have an official name, generally have little or
no residential population or housing unit (or meet the non special land use TCT or TBG
population and housing unit thresholds) and must be contiguous. If located in a densely
populated urban area, a special land use TCT or TBG must have an area measurement of
approximately 1 square mile or more. If delineated completely outside an urban area, a
special land use TCT or TBG must have an area of approximately 10 square miles or
more. Participants are not required to delineate special land use TCTs or TBGs.
18

The Census Bureau recognizes that some special land use areas not intended for
residential population, such as parks, may contain some population, such as caretakers or
the homeless. Our intent is to allow for the delineation of parks and other special land
use areas as separate TCTs and therefore we will accept such areas as special land use
TCTs even if some, but very little, residential population is present.
3.4 Census designated place criteria and guidelines:
The census designated place criteria are:
1. CDPs cannot be coextensive with an entire AIR, ORTL, OTSA, or any other AIA, but
may extend off AIRs, ORTLs, or OTSAs.
2. A CDP may not have the same name as an adjacent or nearby incorporated place. If
the community does not have a name that distinguishes it from other nearby
communities, then the community is not a distinct place and should not be submitted
as a CDP.
3. A CDP may not be located, either partially or entirely, within an incorporated place or
another CDP.
4. A CDP must not cross state boundaries, but may be located in more than one county.
Guidelines for delineating census designated places are:
1. A CDP constitutes a single, closely settled center of population that is named. To the
extent possible, individual unincorporated communities should be identified as
separate CDPs.
2. A CDP is defined to provide data for a single named locality, therefore the Census
Bureau does not encourage delineating CDPs that comprise a combination of places
or are identified by hyphenated names. For example, CDPs such as Poplar-Cotton
Center and Downieville-Lawson-Dumont are no longer acceptable. Prior to Census
2000 communities were sometimes combined as a single CDP in order to comply
with the Census Bureau minimum population requirements. The Census Bureau’s
elimination of population threshold criteria has made such combinations unnecessary.
3. Multiple communities may only be combined to form a single CDP when the
identities of these communities have become so intertwined that the communities are
commonly perceived and referenced as a single place.
4. Multiple communities also may be defined as a single CDP when there is no
distinguishable or suitable feature in the landscape that can be used as a boundary
between the communities, even if the two communities still have separate identities.
5. There is no minimum population or housing unit thresholds for defining CDPs
however, a CDP must contain some population or housing units or both. Participants
submitting boundaries for places with less than ten housing units may be asked to
provide additional information attesting to the existence of the CDP.
6. CDP boundaries should follow the visible features outlined in section 2.6. CDP
boundaries may follow other nonvisible features in instances where reliance upon
visible features will result in over bounding of the CDP and the intent is to include
housing units on both sides of a road or street feature. Such non visible boundaries

19

might include parcel boundaries and public land survey system lines; national, state,
or local park boundaries.
7. The CDP name should be one that is recognized and used in daily communication by
the residents of the community.
8. A CDP should have population during at least one entire season of the year, and have
a higher housing unit and population density than surrounding areas.

4. Procedures
4.1 Annotation of Maps
The Census Bureau suggests the following procedures for delineating TCTs, TBGs,
CDPs and for suggesting Census 2010 Block Boundaries:
1. Compare your source materials with the Census Bureau’s maps. The goal of the
TSAP is to delineate statistical areas that adhere to the criteria and guidelines outlined
in section 3. Following these guidelines will provide your tribe with census and
survey statistics throughout the next decade.
2. If after reviewing our maps you believe that the boundary of your tribes federal
reservation or trust land is inaccurate as portrayed on the Census Bureau’s maps,
please refer to section 2.3 The Boundary and Annexation Survey for more
information or contact your RCC.
3. If you are satisfied with how the TCTs, TBGs, and/or CDPs are portrayed on the map,
and you do not wish to identify any features for use as 2010 census block boundaries,
fill out and sign the form attached to the cover letter that came with your materials.
Return the form to the RCC using the postage paid envelope provided.
4. If you need to update or delineate new TCTs, TBGs, and/or CDPs, annotate the maps
with the revised or new boundary, name and number (T001, T002, etc.) updates and
revisions. Use the following sequence when annotating the boundaries of Census
2010 statistical areas, according to the criteria provided in section 3.
Do not add street or other features unless you are adding a feature that forms the
boundary of a TCT, TBG and/or CDP or is a suggested block boundary. The Census
Bureau will not accept new road features at this time unless the road or other feature is
used to delineate a boundary or to suggest a block boundary. When adding a feature for
these purposes, use a black lead pencil to add and label the feature then use the
appropriate colored pencil as described below to annotate the feature as a boundary. If a
feature is incorrectly located, mislabeled or distorted on the Census Bureau’s maps to the
extent that you cannot correctly delineate a boundary using that feature, please draw your
boundary following the problematic feature and using the appropriate colored pencil.
Also, be sure to contact your RCC to describe the location and nature of the problem.
a. Annotate the TCT boundaries and numbers T001, T002, etc. in orange
pencil. It is not necessary to annotate a TCT if you only have one TCT
that will be coextensive with the AIR and/or ORTL. The Census Bureau
will automatically identify 1 TCT for each reservation with a population
of less than 1,200.

20

b. Next annotate the TBG boundaries and labels (A, B, C, etc.) in brown
pencil. (Because TBGs nest within TCTs, there is no need to annotate
brown lines alongside or on top of census tract boundaries.) There is no
need to annotate a TBG, if you only have one TBG coextensive with the
AIR and/or ORTL. The Census Bureau will automatically identify 1 TBG
for each TCT with a population of less than 600.
c. Then annotate the maps with the CDP updates in red pencil. CDPs do not
inherently follow any other statistical boundary. However, where a CDP
boundary follows an annotated color boundary for either a revised TCT
(orange), or TBG (brown), annotate red circles along the portions of the
colored lines where the revised CDPs boundaries are coincident with any
other revised statistical areas. (It is not required to delineate CDPs.)
5. If the CDP name requires revision, cross out the old name and clearly label the new
name in red within the boundary of the federal AIR.
6. On the paper map, revise an existing boundary by drawing “X”s along the boundary
using the appropriate colored pencil (orange for TCT boundary, brown for TBG
boundary, red for CDP boundary).
7. If you want to suggest a feature as a 2010 tabulation block boundary, highlight the
feature in purple. If you wish to indicate a feature should not be held as a 2010
tabulation block boundary, draw triangles on the feature using a purple pencil.
4.1.1 Example

21

Figure 6: In this example, the tribal block group boundary has been changed. The old
boundary has been crossed out and the new boundary has been marked using a brown
pencil. A CDP has been created and where the two statistical areas now share a
boundary, the CDP is delineated using red circles. Also, a road in the lower left hand
corner has marked with purple pencil, showing that it is to be held as a 2010 tabulation
block boundary.
4.2 Transmitting Completed Submissions and Census Bureau Review
Please return all maps to the RCC in the same tube/box/envelope you received it in and
for your convenience use the mailing label provided. The Census Bureau RCC
geographic staff will review that the submitted TCTs, TBGs, CDPs and block boundary
suggestions to make sure they are complete and meet all criteria and other requirements.
Where the criteria have not been met, they will review the submitted justification or call
to acquire justification.
The Census Bureau’s RCC staff will provide feedback to the participant on their
submission, and if necessary provide additional guidance on the criteria and guidelines
usage. They may also need to contact you with any questions or concerns regarding the
submission. The Census Bureau reserves the right to modify, create, or reject any
boundary or attribute as needed to meet the final program criteria and guidelines, or to
maintain geographic relationships before the tabulation geography is finalized for the
2010 Census.
4.3 Verification
As long as a submission for TSAP is received by the Census Bureau within the 120 day
schedule, each participating tribe will be eligible for a verification phase. During
verification, the Census Bureau provides new materials to reflect how we inserted the
submitted TCT, TBG, and CDPs into our database. The verification materials will be
provided in late 2009. At that time, tribes may review the new areas and as needed make
minor boundary corrections.

22

Appendix A – American Indian statistical areas eligible for delineation
Tribe Name

Jamul Indian Village
Washoe Tribe (Woodfords Community)
Yavapai-Apache Nation of the Camp Verde
Indian Reservation
Yavapai-Prescott Tribe of the Yavapai
Reservation
Yerington Paiute Tribe of the Yerington
Colony & Campbell Ranch
Hannahville Indian Community
Pueblo of Zia
Inaja Band of Diegueno Mission Indians of the
Inaja and Cosmit Reservation
Bay Mills Indian Community
Grand Traverse Band of Ottawa & Chippewa
Indians
Yomba Shoshone Tribe of the Yomba
Reservation
Te-Moak Tribe of Western Shoshone Indians
(Wells Band)
Fort Independence Indian Community of
Paiute Indians of the Fort Independence
Reservation
Washoe Tribe
La Jolla Band of Luiseno Mission Indians of
the La Jolla Reservation
Walker River Paiute Tribe of the Walker River
Reservation

Area Name

Census
Area
Code

Census 2000
Population

Census 2000
Housing Units

2010 Census Areas
Eligible for Delineation

Regional
Census
Center

Jamul Indian Village
Woodfords Community
Yavapai-Apache Nation
Reservation

1670
4665

1
219

1
61

CDP, BDP
CDP, BDP

Los Angeles
Denver

4708

743

197

CDP, BDP

Denver

Yavapai-Prescott Reservation

4710

182

60

CDP, BDP

Denver

Yerington Colony
Hannahville Community
Zia Pueblo and Off-Reservation
Trust Land

4725
1410

139
395

54
109

CDP, BDP
CDP, BDP

Denver
Detroit

4770

646

189

CDP, BDP

Denver

Inaja and Cosmit Reservation
Bay Mills Reservation

1560
0170

0
812

0
333

CDP, BDP
CDP, BDP

Los Angeles
Detroit

Grand Traverse Reservation

1370

545

166

CDP, BDP

Detroit

Yomba Reservation

4740

96

36

CDP, BDP

Denver

Wells Colony

4580

54

24

CDP, BDP

Denver

Fort Independence Reservation
Washoe Ranches

1195
4560

86
0

42
0

CDP, BDP
CDP, BDP

Los Angeles
Denver

La Jolla Reservation

1850

390

143

CDP, BDP

Los Angeles

Walker River Reservation

4515

853

339

CDP, BDP

Denver

23

Skull Valley Band of Goshute Indians
Tonto Apache Tribe
Pueblo of Tesuque
Seminole Tribe
Summit Lake Paiute Tribe
La Posta Band of Diegueno Mission Indians of
the La Posta Indian Reservation
Washoe Tribe (Stewart Community)
Paiute-Shoshone Indians of the Lone Pine
Community of the Lone Pine Reservation
Te-Moak Tribe of Western Shoshone Indians
(South Fork Band)
Winnemucca Indian Colony
Minnesota Chippewa Tribe
Big Sandy Rancheria of Mono Indians
Big Pine Band of Owens Valley Paiute
Shoshone Indians of the Big Pine Reservation
Capitan Grande Band of Diegueno Mission
Indians: Barona Group of Capitan Grande
Band of Mission Indians of the Barona
Reservation
Augustine Band of Cahuilla Indians
Upper Sioux Community
Shakopee Mdewakanton Sioux Community
Cabazon Band of Mission Indians
Minnesota Chippewa Tribe (Mille Lacs Band)
Sac & Fox Nation of Missouri in Kansas and
Nebraska
Sac & Fox Tribe of the Mississippi in Iowa
Prairie Island Indian Community
Nottawaseppi Huron Band of the Potawatomi

Skull Valley Reservation
Tonto Apache Reservation
Tesuque Pueblo
Tampa Reservation
Summit Lake Reservation

3840
4235
4170
4130
4045

31
132
806
0
15

11
38
327
0
15

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Denver
Denver
Denver
Atlanta
Denver

La Posta Reservation
Stewart Community

1895
3980

18
196

6
62

CDP, BDP
CDP, BDP

Los Angeles
Denver

Lone Pine Reservation

1970

212

100

CDP, BDP

Los Angeles

South Fork Reservation
Winnemucca Colony
Minnesota Chippewa Trust Land
Big Sandy Rancheria

3930
4635
2285
0265

123
62
78
98

62
21
43
34

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Denver
Denver
Kansas City
Los Angeles

Big Pine Reservation

0250

462

181

CDP, BDP

Los Angeles

Barona Reservation
Augustine Reservation
Upper Sioux Reservation
Shakopee Mdewakanton Sioux
Community
Cabazon Reservation
Sandy Lake Reservation

0155
0125
4445

536
0
57

162
0
31

CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Los Angeles
Kansas City

3680
0415
3385

338
806
70

120
192
22

CDP, BDP
CDP, BDP
CDP, BDP

Kansas City
Los Angeles
Kansas City

3285

217

79

CDP, BDP

Kansas City

3280
2985
1550

761
199
11

267
65
7

CDP, BDP
CDP, BDP
CDP, BDP

Kansas City
Kansas City
Detroit

Sac and Fox Reservation
Sac and Fox/Meskwaki
Reservation
Prairie Island Indian Community
Huron Potawatomi Reservation

24

Campo Band of Diegueno Mission Indians of
the Campo Indian Reservation
Cold Springs Rancheria of Mono Indians
Lower Sioux Indian Community of Minnesota
Mdewakanton Sioux Indians of the Lower
Sioux Reservation
Iowa Tribe of Kansas and Nebraska
Capitan Grande Band of Diegueno Mission
Indians: Barona Group of Capitan Grande
Band of Mission Indians of the Barona
Reservation
Minnesota Chippewa Tribe (Grand Portage
Band)
Minnesota Chippewa Tribe (Bois Forte Band
(Nett Lake))
Capitan Grande Band of Diegueno Mission
Indians: Viejas (Baron Long) Group of
Capitan Grande Band of Mission Indians of
the Viejas Reservation
Pokagon Band of Potawatomi Indians
Keweenaw Bay Indian Community of L'Anse
and Ontonagon Bands
Little Traverse Bay Bands of Odawa Indians
Ewiiaapaayp Band of Kumeyaay Indians
Little River Band of Ottawa Indians
Lac Vieux Desert Band of Lake Superior
Chippewa Indians
Cahuilla Band of Mission Indians of the
Cahuilla Reservation
Narragansett Indian Tribe
Passamaquoddy Tribe - Indian Township
Reservation
Sokaogon Chippewa Community of Chippewa
Indians
St. Croix Chippewa Indians

Campo Reservation
Cold Springs Rancheria

0450
0720

351
193

111
46

CDP, BDP
CDP, BDP

Los Angeles
Los Angeles

Lower Sioux Reservation
Iowa (KS-NE) Reservation

2055
1590

335
168

116
67

CDP, BDP
CDP, BDP

Kansas City
Kansas City

Capitan Grande Reservation

0495

0

0

CDP, BDP

Los Angeles

Grand Portage Reservation

1355

557

286

CDP, BDP

Kansas City

Bois Forte Reservation

0335

657

398

CDP, BDP

Kansas City

Capitan Grande Reservation
Pokagon Reservation

0495
2890

0
0

0
0

CDP, BDP
CDP, BDP

Los Angeles
Detroit

Ontonagon Reservation
Little Traverse Bay Reservation
Ewiiaapaayp Reservation
Little River Reservation

2580
1963
1065
1960

0
0
0
2

0
0
0
2

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Detroit
Detroit
Los Angeles
Detroit

Lac Vieux Desert Reservation

1830

135

50

CDP, BDP

Detroit

Cahuilla Reservation
Narragansett Reservation

0435
2415

154
60

56
20

CDP, BDP
CDP, BDP

Los Angeles
Boston

Indian Township Reservation

1575

676

261

CDP, BDP

Boston

Sokaogon Chippewa Community
St. Croix Reservation

3885
3305

392
641

167
208

CDP, BDP
CDP, BDP

Chicago
Chicago

25

Red Cliff Band of Lake Superior Chippewa
Indians
Ho-Chunk Nation
Forest County Potawatomi Community
Wampanoag Tribe of Gay Head
Tuscarora Nation
Tonawanda Band of Seneca Indians
Passamaquoddy Tribe - Pleasant Point
Reservation
Penobscot Tribe
Passamaquoddy Tribe - Pleasant Point
Reservation
Passamaquoddy Tribe - Indian Township
Reservation
Alabama-Coushatta Tribes
Miccosukee Tribe of Indians
Confederated Tribes of the Chehalis
Reservation
Los Coyotes Band of Cahuilla and Cupeno
Indians
Seminole Tribe
Seminole Tribe
Seminole Tribe
Oneida Nation
Seminole Tribe
Seneca Nation
Poarch Band of Creek Indians
Seminole Tribe
Houlton Band of Maliseet Indians
Mashantucket Pequot Tribe
Mohegan Indian Tribe
Chitimacha Tribe
Seminole Tribe

Red Cliff Reservation
Ho-Chunk Nation Reservation
Forest County Potawatomi
Community
Wampanoag-Aquinnah
Tuscarora Reservation
Tonawanda Reservation

3085
1450

1,078
960

429
349

CDP, BDP
CDP, BDP

Chicago
Chicago

1135
4530
4360
4225

531
91
1,138
543

174
34
398
197

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Chicago
Boston
Boston
Boston

Pleasant Point Reservation
Penobscot Reservation

2850
2760

640
584

256
364

CDP, BDP
CDP, BDP

Boston
Boston

Passamaquoddy Trust Land

2695

0

88

CDP, BDP

Boston

Passamaquoddy Trust Land
Alabama-Coushatta Reservation
Miccosukee Reservation

2695
0050
2240

0
480
0

88
203
0

CDP, BDP
CDP, BDP
CDP, BDP

Boston
Dallas
Atlanta

Chehalis Reservation

0575

691

214

CDP, BDP

Seattle

Los Coyotes Reservation
Brighton Reservation
Big Cypress Reservation
Coconut Creek Trust Land
Oneida (NY) Reservation
Immokalee Reservation
Oil Springs Reservation
Poarch Creek Reservation
Seminole Trust Land
Houlton Maliseet Reservation
Mashantucket Pequot Reservation
Mohegan Reservation
Chitimacha Reservation
Fort Pierce Reservation

1995
0360
0225
0690
2555
1555
2535
2865
3665
1530
2145
2320
0635
1260

70
566
142
0
26
175
11
211
0
136
325
2
409
2

23
216
55
0
20
62
20
101
0
54
114
1
168
1

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Atlanta
Atlanta
Atlanta
Boston
Atlanta
Boston
Atlanta
Atlanta
Boston
Boston
Boston
Dallas
Atlanta

26

Flandreau Santee Sioux Tribe
Pueblo of Santa Ana
Reno-Sparks Indian Colony
Ponca Tribe of Nebraska
Paiute Indian Tribe
Northwestern Band of Shoshone Nation
(Washakie)
Moapa Band of Paiute Indians of the Moapa
River Indian Reservation
Ak Chin Indian Community of the Maricopa
(Ak Chin) Indian Reservation
Lovelock Paiute Tribe of the Lovelock Indian
Colony
Las Vegas Tribe of Paiute Indians of the Las
Vegas Indian Colony
Kaibab Band of Paiute Indians of the Kaibab
Indian Reservation
Havasupai Tribe of the Havasupai Reservation
Confederated Tribes of the Goshute
Reservation
Fort Mojave Indian Tribe
Catawba Indian Nation
Washoe Tribe (Dresslerville Colony)
Coushatta Tribe
Kickapoo Traditional Tribe
Tunica-Biloxi Indian Tribe
Ysleta Del Sur Pueblo
Te-Moak Tribe of Western Shoshone Indians
(Battle Mountain Band)
Fort McDowell Yavapai Nation
Washoe Tribe (Carson Colony)
Fort McDermitt Paiute and Shoshone Tribes of
the Fort McDermitt Indian Reservation

Flandreau Reservation
Santa Ana Pueblo
Reno-Sparks Colony
Ponca (NE) Trust Land
Paiute (UT) Reservation
Northwestern Shoshone
Reservation

1100
3480
3130
2900
2625

408
487
881
0
270

137
197
282
0
84

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Denver
Denver
Denver
Denver
Denver

2505

0

0

CDP, BDP

Denver

Moapa River Reservation

2315

206

90

CDP, BDP

Denver

Maricopa (Ak Chin) Reservation

2130

742

234

CDP, BDP

Denver

Lovelock Colony

2015

103

38

CDP, BDP

Denver

Las Vegas Colony

1915

108

37

CDP, BDP

Denver

Kaibab Reservation
Havasupai Reservation

1720
1440

196
503

88
161

CDP, BDP
CDP, BDP

Denver
Denver

Goshute Reservation
Fort Mojave Reservation
Catawba Reservation
Dresslerville Colony
Coushatta Reservation
Kickapoo (TX) Reservation
Tunica-Biloxi Reservation
Ysleta Del Sur Pueblo

1340
1235
0525
0940
0795
1775
4315
4755

105
1,043
494
315
25
420
89
421

45
416
174
116
14
104
34
116

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Denver
Denver
Charlotte
Denver
Dallas
Dallas
Dallas
Dallas

Battle Mountain Reservation
Fort McDowell Reservation
Carson Colony

0165
1220
0510

124
824
286

63
275
105

CDP, BDP
CDP, BDP
CDP, BDP

Denver
Denver
Denver

Fort McDermitt Reservation

1210

309

119

CDP, BDP

Denver

27

Duckwater Shoshone Tribe of the Duckwater
Reservation
Te-Moak Tribe of Western Shoshone Indians
(Elko Band)
Ely Shoshone Tribe
Paiute-Shoshone Tribe of the Fallon
Reservation and Colony
Paiute-Shoshone Tribe of the Fallon
Reservation and Colony
Santee Sioux Nation
Yerington Paiute Tribe of the Yerington
Colony & Campbell Ranch
Confederated Tribes of the Coos, Lower
Umpqua and Siuslaw Indians
Lytton Rancheria
Quileute Tribe of the Quileute Reservation
Chicken Ranch Rancheria of Me-Wuk Indians
Cachil DeHe Band of Wintun Indians of the
Colusa Indian Community of the Colusa
Rancheria
Pit River Tribe
Guidiville Rancheria
Nisqually Indian Tribe of the Nisqually
Reservation
Bear River Band of the Rohnerville Rancheria
Middletown Rancheria of Pomo Indians
Cher-Ae Heights Indian Community of the
Trinidad Rancheria
Coquille Tribe
Cortina Indian Rancheria of Wintun Indians
Wiyot Tribe
Lower Elwha Tribal Community of the Lower
Elwha Reservation
Cow Creek Band of Umpqua Indians
Robinson Rancheria of Pomo Indians

Duckwater Reservation

0975

149

65

CDP, BDP

Denver

Elko Colony
Ely Reservation

1005
1040

729
133

257
67

CDP, BDP
CDP, BDP

Denver
Denver

Fallon Paiute-Shoshone Colony
Fallon Paiute-Shoshone
Reservation
Santee Reservation

1070

123

51

CDP, BDP

Denver

1075
3565

620
878

256
368

CDP, BDP
CDP, BDP

Denver
Denver

Campbell Ranch
Coos, Lower Umpqua, and
Siuslaw Reservation
Lytton Rancheria
Quileute Reservation
Chicken Ranch Rancheria

0440

446

80

CDP, BDP

Denver

0770
2075
3030
0620

25
0
371
11

9
0
128
4

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle
Seattle

Colusa Rancheria
Roaring Creek Rancheria
Guidiville Rancheria

0750
3185
1400

77
9
2

25
5
1

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Nisqually Reservation
Rohnerville Rancheria
Middletown Rancheria

2460
3220
2255

588
98
73

178
29
20

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Trinidad Rancheria
Coquille Reservation
Cortina Rancheria
Table Bluff Reservation

4275
0775
0780
4095

73
258
19
97

37
98
9
35

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle
Seattle

Lower Elwha Reservation
Cow Creek Reservation
Robinson Rancheria

2040
0815
3195

315
22
153

99
8
43

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

28

Mooretown Rancheria of Maidu Indians
Klamath Tribes
United Auburn Indian Community
Tuolumne Band of Me-Wuk Indians of the
Tuolumne Rancheria
Utu Utu Gwaitu Paiute Tribe of the Benton
Paiute Reservation
Berry Creek Rancheria of Maidu Indians
Pit River Tribe
Manchester Band of Pomo Indians of the
Manchester-Point Arena Rancheria
Big Valley Band of Pomo Indians of the Big
Valley Rancheria
Confederated Tribes of the Warm Springs
Reservation
Blue Lake Rancheria
Bridgeport Paiute Indian Colony
Burns Paiute Tribe of the Burns Paiute Indian
Colony
Cedarville Rancheria
Confederated Tribes and Bands of the Yakama
Nation
Pit River Tribe
Elem Indian Colony of Pomo Indians of the
Sulphur Bank Rancheria
Big Lagoon Rancheria
Hopland Band of Pomo Indians of the Hopland
Rancheria
Susanville Indian Rancheria
Redwood Valley Rancheria of Pomo Indians
Pit River Tribe
Manzanita Band of Diegueno Mission Indians
of the Manzanita Reservation

Mooretown Rancheria
Klamath Reservation
Auburn Rancheria

2340
1785
0120

166
9
0

52
6
0

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Tuolumne Rancheria

4330

168

68

CDP, BDP

Seattle

Benton Paiute Reservation
Berry Creek Rancheria
Big Bend Rancheria

0185
0200
0215

50
138
0

30
40
0

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Manchester-Point Arena Rancheria

2100

197

65

CDP, BDP

Seattle

Big Valley Rancheria

0275

225

64

CDP, BDP

Seattle

Celilo Village
Blue Lake Rancheria
Bridgeport Reservation

0560
0325
0350

44
78
43

22
41
21

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Burns Paiute Colony
Cedarville Rancheria

0400
0555

171
26

57
9

CDP, BDP
CDP, BDP

Seattle
Seattle

Celilo Village
Montgomery Creek Rancheria

0560
2330

44
5

22
2

CDP, BDP
CDP, BDP

Seattle
Seattle

Sulphur Bank Rancheria
Big Lagoon Rancheria

4030
0240

69
24

15
9

CDP, BDP
CDP, BDP

Seattle
Seattle

Hopland Rancheria
Susanville Rancheria
Redwood Valley Rancheria
Reservation
Likely Rancheria

1515
4060

45
298

18
95

CDP, BDP
CDP, BDP

Seattle
Seattle

3115
1955

263
0

87
0

CDP, BDP
CDP, BDP

Seattle
Seattle

Manzanita Reservation

2115

69

29

CDP, BDP

Los Angeles

29

Cahto Indian Tribe of the Laytonville
Rancheria
Confederated Tribes of the Umatilla
Reservation
Round Valley Indian Tribes of the Round
Valley Reservation
Sherwood Valley Rancheria of Pomo Indians
Greenville Rancheria of Maidu Indians
Jackson Rancheria of Me-Wuk Indians
Jamestown S'Klallam Tribe
Kalispel Indian Community of the Kalispel
Reservation
Sauk-Suiattle Indian Tribe
Rumsey Indian Rancheria of Wintun Indians
Karuk Tribe
Kootenai Tribe
Hoh Indian Tribe of the Hoh Indian
Reservation
Smith River Rancheria
Nooksack Indian Tribe
Dry Creek Rancheria of Pomo Indians
Stillaguamish Tribe
Elk Valley Rancheria
Enterprise Rancheria of Maidu Indians
Kashia Band of Pomo Indians of the Stewarts
Point Rancheria
Grindstone Indian Rancheria of WintunWailaki Indians
Snoqualmie Tribe
Coyote Valley Band of Pomo Indians
Skokomish Indian Tribe of the Skokomish
Reservation
Pit River Tribe

Laytonville Rancheria

1925

188

61

CDP, BDP

Seattle

Celilo Village

0560

44

22

CDP, BDP

Seattle

Round Valley Reservation
Sherwood Valley Rancheria
Greenville Rancheria
Jackson Rancheria
Jamestown S'Klallam Reservation

3250
3735
1380
1640
1655

300
179
22
2
16

108
49
9
1
8

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle

Kalispel Reservation
Sauk-Suiattle Reservation
Rumsey Rancheria
Karuk Reservation
Kootenai Reservation

1735
3625
3265
1750
1800

206
45
36
333
75

63
16
11
124
24

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle

Hoh Reservation
Smith River Rancheria
Nooksack Reservation
Dry Creek Rancheria
Stillaguamish Reservation
Elk Valley Rancheria
Enterprise Rancheria

1460
3855
2475
0955
4000
1010
1055

102
62
547
53
102
77
1

33
21
142
15
31
36
1

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

Stewarts Point Rancheria

3985

57

17

CDP, BDP

Seattle

Grindstone Rancheria
Snoqualmie Reservation
Coyote Valley Reservation

1395
3860
0825

162
0
104

49
0
31

CDP, BDP
CDP, BDP
CDP, BDP

Seattle
Seattle
Seattle

Skokomish Reservation
Lookout Rancheria

3825
1980

730
7

279
5

CDP, BDP
CDP, BDP

Seattle
Seattle

30

Fort Bidwell Indian Community of the Fort
Bidwell Reservation
Confederated Tribes of the Siletz Reservation
Shoalwater Bay Tribe of the Shoalwater Bay
Indian Reservation
Confederated Tribes of the Grand Ronde
Community
Shingle Springs Band of Miwok Indians,
Shingle Springs Rancheria (Verona Tract)
Squaxin Island Tribe of the Squaxin Island
Reservation
Capitan Grande Band of Diegueno Mission
Indians: Viejas (Baron Long) Group of
Capitan Grande Band of Mission Indians of
the Viejas Reservation
Alturas Indian Rancheria
Resighini Rancheria
Twenty-Nine Palms Band of Mission Indians
Tule River Indian Tribe of the Tule River
Reservation
Redding Rancheria
Death Valley Timbi-Sha Shoshone Band
Table Mountain Rancheria
Sycuan Band of the Kumeyaay Nation
Santa Ysabel Band of Diegueno Mission
Indians of the Santa Ysabel Reservation
Santa Ynez Band of Chumash Mission Indians
of the Santa Ynez Reservation
Santa Rosa Band of Cahuilla Indians
Santa Rosa Indian Community of the Santa
Rosa Rancheria
San Pasqual Band of Diegueno Mission
Indians
Pit River Tribe

Fort Bidwell Reservation
Siletz Reservation

1170
3795

108
308

47
104

CDP, BDP
CDP, BDP

Seattle
Seattle

Shoalwater Bay Reservation

3780

70

35

CDP, BDP

Seattle

Grand Ronde Community

1365

55

19

CDP, BDP

Seattle

Shingle Springs Rancheria

3750

57

16

CDP, BDP

Seattle

Squaxin Island Reservation

3955

405

127

CDP, BDP

Seattle

Viejas Reservation
Alturas Rancheria
Resighini Rancheria
Twenty-Nine Palms Reservation

4500
0095
3145
4375

394
2
36
0

148
2
6
0

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Seattle
Seattle
Los Angeles

Tule River Reservation
Redding Rancheria
Timbi-Sha Shoshone Reservation
Table Mountain Rancheria
Sycuan Reservation

4300
3095
4180
4110
4090

566
45
0
11
33

179
17
0
4
14

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Seattle
Los Angeles
Los Angeles
Los Angeles

Santa Ysabel Reservation

3550

250

102

CDP, BDP

Los Angeles

Santa Ynez Reservation
Santa Rosa Reservation

3540
3525

122
65

42
25

CDP, BDP
CDP, BDP

Los Angeles
Los Angeles

Santa Rosa Rancheria

3520

517

125

CDP, BDP

Los Angeles

San Pasqual Reservation
XL Ranch Rancheria

3460
4680

752
14

228
13

CDP, BDP
CDP, BDP

Los Angeles
Seattle

31

Paskenta Band of Nomlaki Indians
Mesa Grande Band of Diegueno Mission
Indians of the Mesa Grande Reservation
Soboba Band of Luiseno Indians of the Soboba
Reservation
Northfork Rancheria of Mono Indians
San Manuel Band of Serrano Mission Indians
of the San Manuel Reservation
Pauma Band of Luiseno Mission Indians of the
Pauma & Yuima Reservation
Habematolel Pomo of Upper Lake
Upper Skagit Indian Tribe
Pinoleville Pomo Nation
Pechanga Band of Luiseno Mission Indians of
the Pechanga Reservation
Pit River Tribe
Picayune Rancheria of Chukchansi Indians
Port Gamble Indian Community of the Port
Gamble Reservation
Quartz Valley Indian Community of the
Quartz Valley Reservation
Ramona Band or Village of Cahuilla Mission
Indians
Morongo Band of Cahuilla Mission Indians of
the Morongo Reservation
Ione Band of Miwok Indians
Scotts Valley Band of Pomo Indians
Mechoopda Indian Tribe of Chico Rancheria
Buena Vista Rancheria of Me-Wuk Indians
California Valley Miwok Tribe
Cloverdale Rancheria of Pomo Indians
Cowlitz Indian Tribe
Federated Indians of Graton Rancheria

Paskenta Rancheria

2685

0

0

CDP, BDP

Seattle

Mesa Grande Reservation

2190

75

19

CDP, BDP

Los Angeles

Soboba Reservation
North Fork Rancheria

3870
2495

522
9

173
2

CDP, BDP
CDP, BDP

Los Angeles
Los Angeles

San Manuel Reservation

3445

74

27

CDP, BDP

Los Angeles

Pauma and Yuima Reservation
Upper Lake Rancheria
Upper Skagit Reservation
Pinoleville Rancheria

2715
4430
4455
2820

186
82
238
136

53
34
76
42

CDP, BDP
CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Seattle
Seattle
Seattle

Pechanga Reservation
Pit River Trust Land
Picayune Rancheria

2745
2835
2775

467
9
20

163
4
16

CDP, BDP
CDP, BDP
CDP, BDP

Los Angeles
Seattle
Los Angeles

Port Gamble Reservation

2910

699

226

CDP, BDP

Seattle

Quartz Valley Reservation

3020

126

58

CDP, BDP

Seattle

Ramona Village

3070

0

0

CDP, BDP

Los Angeles

Morongo Reservation
Ione Band of Miwok TDSA
Tribal Area Placeholder
Mechoopda TDSA
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder

2360
8300
0000
8450
0000
0000
0000
0000
0000

954
8
0
3,198
0
0
0
0
0

345
4
0
1,162
0
0
0
0
0

CDP, BDP
TDSA
TDSA
TDSA
TDSA
TDSA
TDSA
TDSA
TDSA

Los Angeles
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

32

Samish Indian Tribe
Potter Valley Tribe
Match-e-be-nash-she-wish Band of
Pottawatomi Indians
Mashpee Wampanoag Tribe
Cayuga Nation of New York
Lower Lake Rancheria

Samish TDSA
Tribal Area Placeholder

8750
0000

33,265
0

18,901
0

Tribal Area Placeholder
Tribal Area Placeholder
Cayuga Nation TDSA
Tribal Area Placeholder

0000
0000
8100
0000

0
0
10,707
0

0
0
4,906
0

Seneca Nation

Allegany Reservation

0080

6,804

3,035

Eastern Band of Cherokee Indians

Eastern Cherokee Reservation

0990

8,092

3,194

Oneida Tribe of Indians

Oneida (WI) Reservation

2560

21,321

7,559

Menominee Indian Tribe
Lac du Flambeau Band of Lake Superior
Chippewa Indians of the Lac du Flambeau
Reservation
Lac Courte Oreilles Band of Lake Superior
Chippewa Indians

Menominee Reservation

2175

3,225

932

Lac du Flambeau Reservation

1825

2,995

2,907

Lac Courte Oreilles Reservation

1815

2,900

1,990

St. Regis Mohawk Reservation

3320

2,699

977

Swinomish Reservation

4075

2,664

1,302

Cattaraugus Reservation

0540

2,412

901

Umatilla Reservation

4405

2,927

1,065

Warm Springs Reservation

4545

3,314

884

Saint Regis Mohawk Tribe
Swinomish Indians of the Swinomish
Reservation
Seneca Nation
Confederated Tribes of the Umatilla
Reservation
Confederated Tribes of the Warm Springs
Reservation
Seminole Tribe
Confederated Tribes and Bands of the Yakama
Nation

Hollywood Reservation

1475

2,051

1,498

Yakama Reservation

4690

31,799

9,128

Tulalip Tribes of the Tulalip Reservation

Tulalip Reservation

4290

9,246

3,638

TDSA
TDSA

Seattle
Seattle

TDSA
TDSA
TDSA
TDSA
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Detroit
Boston
Boston
Seattle

Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Boston
Charlotte
Chicago
Chicago

Chicago
Chicago
Boston
Seattle
Boston
Seattle
Seattle
Atlanta
Seattle
Seattle

33

Spirit Lake Tribe
Coeur D'Alene Tribe of the Coeur D'Alene
Reservation
Ute Indian Tribe of the Uintah & Ouray
Reservation

Spirit Lake Reservation

3935

4,435

1,534

Coeur d'Alene Reservation

0705

6,551

4,015

Uintah and Ouray Reservation

4390

19,182

8,700

Turtle Mountain Band of Chippewa Indians
Confederated Tribes of the Colville
Reservation

Turtle Mountain Reservation

4345

8,331

2,656

Colville Reservation

0760

7,587

3,309

Tohono O'odham Nation

Tohono O'odham Reservation

4200

10,787

3,572

Navajo Nation
Standing Rock Sioux Tribe of North & South
Dakota

Navajo Nation Reservation

2430

180,462

68,744

Standing Rock Reservation

3970

8,250

2,762

Winnebago Tribe
Southern Ute Indian Tribe of the Southern Ute
Reservation

Winnebago Reservation

4625

2,588

875

Southern Ute Reservation

3925

11,159

4,796

Pueblo of Santo Domingo

Santo Domingo Pueblo

3585

3,166

601

Pueblo of Santa Clara

Santa Clara Pueblo

3495

10,658

4,435

Pueblo of San Felipe

San Felipe Pueblo

3400

3,185

738

Pueblo of Sandia
San Carlos Apache Tribe of the San Carlos
Reservation

Sandia Pueblo

3370

4,414

1,622

San Carlos Reservation

3355

9,385

2,497

Taos Pueblo

4140

4,492

2,491

Kickapoo (KS) Reservation

1770

4,419

1,902

Fort Yuma Reservation

1280

2,376

962

Pueblo of Taos
Kickapoo Tribe of Indians of the Kickapoo
Reservation
Quechan Tribe of the Fort Yuma Indian
Reservation

Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Denver
Seattle
Denver
Denver
Seattle
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Kansas City
Los Angeles

34

Torres Martinez Desert Cahuilla Indians

Torres-Martinez Reservation

4255

4,146

933

Agua Caliente Band of Cahuilla Indians
Minnesota Chippewa Tribe (White Earth
Band)
Red Lake Band of Chippewa Indians of the
Red Lake Reservation

Agua Caliente Reservation

0020

21,358

20,926

White Earth Reservation

4595

9,192

4,992

Red Lake Reservation

3100

5,162

1,419

Osage Nation

Osage Reservation

2595

44,437

18,826

Arapahoe Tribe of the Wind River Reservation

Wind River Reservation

4610

23,250

9,375

Minnesota Chippewa Tribe (Leech Lake Band)

Leech Lake Reservation

1940

10,205

6,828

Shoshone Tribe of the Wind River Reservation
Minnesota Chippewa Tribe (Fond du Lac
Band)
Keweenaw Bay Indian Community of L'Anse
and Ontonagon Bands

Wind River Reservation

4610

23,250

9,375

Fond du Lac Reservation

1125

3,728

1,513

L'Anse Reservation

1880

3,672

1,664

Saginaw Chippewa Indian Tribe

Isabella Reservation

1610

25,838

10,584

Zuni Tribe of the Zuni Reservation

Zuni Reservation

4785

7,758

2,107

Yankton Sioux Tribe
Chippewa-Cree Indians of the Rocky Boy's
Reservation

Yankton Reservation

4700

6,500

2,581

Rocky Boy's Reservation

3205

2676

698

Mille Lacs Reservation

2270

4,704

2,869

Colorado River Reservation

0735

9,201

5,894

Salt River Reservation

3340

6,405

2,526

Fort Berthold Reservation

1160

5,915

2,881

Minnesota Chippewa Tribe (Mille Lacs Band)
Colorado River Indian Tribes of the Colorado
River Indian Reservation
Salt River Pima-Maricopa Indian Community
of the Salt River Reservation
Three Affiliated Tribes of the Fort Berthold
Reservation

Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Los Angeles
Los Angeles
Kansas City
Kansas City
Kansas City
Denver
Kansas City
Denver
Kansas City
Detroit
Detroit
Denver
Denver
Denver
Kansas City
Denver
Denver
Denver

35

Fort Belknap Indian Community of the Fort
Belknap Reservation of Montana
White Mountain Apache Tribe of the Fort
Apache Reservation
Confederated Salish & Kootenai Tribes of the
Flathead Reservation
Muckleshoot Indian Tribe of the Muckleshoot
Reservation
Assiniboine and Sioux Tribes of the Fort Peck
Indian Reservation

Fort Belknap Reservation

1150

2,959

967

Fort Apache Reservation

1140

12,429

3,532

Flathead Reservation

1110

26,172

12,679

Muckleshoot Reservation

2375

3,606

1,333

Fort Peck Reservation

1250

10,321

3,755

Crow Tribe
Gila River Indian Community of the Gila
River Indian Reservation

Crow Reservation

0845

6,894

2,280

Gila River Reservation

1310

11,257

2,901

Cocopah Tribe
Cheyenne River Sioux Tribe of the Cheyenne
River Reservation
Blackfeet Tribe of the Blackfeet Indian
Reservation

Cocopah Reservation

0695

1,025

970

Cheyenne River Reservation

0605

8,470

3,004

Blackfeet Reservation

0305

10,100

3,583

Pueblo of Acoma
Suquamish Indian Tribe of the Port Madison
Reservation

Acoma Pueblo

0010

2,802

1,004

Port Madison Reservation

2925

6,536

2,884

Puyallup Tribe of the Puyallup Reservation

Puyallup Reservation

3000

41,341

16,388

Nez Perce Tribe

Nez Perce Reservation

2445

17,959

7,940

Hoopa Valley Tribe

Hoopa Valley Reservation

1490

2,633

1,001

Mississippi Band of Choctaw Indians
Shoshone-Bannock Tribes of the Fort Hall
Reservation

Mississippi Choctaw Reservation

2300

5,190

1,411

Fort Hall Reservation

1185

5,762

2,011

Pueblo of Pojoaque

Pueblo of Pojoaque

2990

2,712

1,179

Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Denver
Denver
Denver
Seattle
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Seattle
Seattle
Seattle
Seattle
Dallas
Seattle
Denver

36

Oglala Sioux Tribe of the Pine Ridge
Reservation

Pine Ridge Reservation

2810

15,521

3,931

Pascua Yaqui Tribe

Pascua Yaqui Reservation

2680

3,315

785

Omaha Tribe

Omaha Reservation

2550

5,194

1,837

Lummi Tribe of the Lummi Reservation
Northern Cheyenne Tribe of the Northern
Cheyenne Indian Reservation
Rosebud Sioux Tribe of the Rosebud Indian
Reservation
Mescalero Apache Tribe of the Mescalero
Reservation
Sisseton-Wahpeton Oyate of the Lake
Traverse Reservation

Lummi Reservation

2070

4,193

1,749

Northern Cheyenne Reservation

2490

4,470

1,328

Rosebud Reservation

3235

10,469

3,166

Mescalero Reservation

2205

3,156

916

Lake Traverse Reservation

1860

10,408

5,184

Pueblo of Laguna

Laguna Pueblo

1840

3,815

1,238

Jicarilla Apache Nation

Jicarilla Apache Reservation

1700

2,755

972

Pueblo of Isleta

Isleta Pueblo

1625

3,166

1,204

Hopi Tribe

Hopi Reservation

1505

6,946

2,512

Ohkay Owingeh
Stockbridge-Munsee Community of Mohican
Indians
Bad River Band of the Lake Superior Tribe of
Chippewa Indians of the Bad River
Reservation
Quinault Tribe of the Quinault Reservation

Ohkay Owingeh

2510

6,748

2,554

Stockbridge Munsee Community

4015

1,527

676

Tribal BG, CDP, BDP

Chicago

Bad River Reservation
Quinault Reservation
Prairie Band Potawatomi
Reservation
Pueblo de Cochiti
Sault Ste. Marie Reservation

0140
3040

1,411
1,370

595
487

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Chicago
Seattle

2980
0680
3635

1,238
1,502
1,676

428
625
673

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Kansas City
Denver
Detroit

Prairie Band of Potawatomi Nation
Pueblo of Cochiti
Sault Ste. Marie Tribe of Chippewa Indians

Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP
Tribal Tracts, Tribal
BG, CDP, BDP

Denver
Denver
Denver
Seattle
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver
Denver

37

Metlakatla Indian Community, Annette Island
Reserve
Crow Creek Sioux Tribe of the Crow Creek
Reservation
Shoshone-Paiute Tribes of the Duck Valley
Reservation
Makah Indian Tribe of the Makah Indian
Reservation
Hualapai Indian Tribe of the Hualapai Indian
Reservation
Pueblo of Jemez
Lower Brule Sioux Tribe of the Lower Brule
Reservation
Ute Mountain Tribe of the Ute Mountain
Reservation
Spokane Tribe of the Spokane Reservation
Pueblo of Picuris
Pyramid Lake Paiute Tribe of the Pyramid
Lake Reservation
Pueblo of San Ildefonso
Pueblo of Nambe
Chemehuevi Indian Tribe of the Chemehuevi
Reservation
Onondaga Nation
Bishop Paiute Tribe
Rincon Band of Luiseno Mission Indians of
the Rincon Reservation
Yurok Tribe of the Yurok Reservation
Pala Band of Luiseno Mission Indians of the
Pala Reservation

Annette Island Reserve

0110

1,447

562

Tribal BG, CDP, BDP

Seattle

Crow Creek Reservation

0855

2,225

617

Tribal BG, CDP, BDP

Denver

Duck Valley Reservation

0965

1,265

457

Tribal BG, CDP, BDP

Denver

Makah Reservation

2085

1,356

533

Tribal BG, CDP, BDP

Seattle

Hualapai Reservation
Jemez Pueblo

1545
1685

1,353
1,958

475
504

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Denver
Denver

Lower Brule Reservation

2030

1,353

392

Tribal BG, CDP, BDP

Denver

Ute Mountain Reservation
Spokane Reservation
Picuris Pueblo

4470
3940
2785

1,687
2,004
1,801

570
701
883

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Denver
Seattle
Denver

Pyramid Lake Reservation
San Ildefonso Pueblo
Nambe Pueblo

3010
3415
2400

1,734
1,524
1,764

687
626
735

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Denver
Denver
Denver

Chemehuevi Reservation
Onondaga Reservation
Bishop Reservation

0585
2570
0290

345
1,473
1,441

699
311
530

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Los Angeles
Boston
Los Angeles

Rincon Reservation
Yurok Reservation

3165
4760

1,495
1,103

385
604

Tribal BG, CDP, BDP
Tribal BG, CDP, BDP

Los Angeles
Seattle

Pala Reservation

2635

1,573

408

Tribal BG, CDP, BDP

Los Angeles

38

Appendix B – Procedures for accessing population and housing unit
data from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

39

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

40

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the
first data set listed which is “Census 2000 Summary File 1.” You may want to scroll
through the other data sets to see what other information is available for your future
reference.

41

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example we will access tribal block group data, but you can also
access data for reservations, off-reservation trust lands, tracts, blocks, and many other
geographic areas.

42

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1”
that you are looking for. Remember that you may select multiple data types.

6. After clicking “Show Result” you will now see the data you have requested.

43

Appendix C – Regional Census Center’s Contact Information
Atlanta Regional Census Center
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 331-1570
E-mail: atlanta.geography@census.gov

Detroit Regional Census Center
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston Regional Census Center
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (857) 362-9380
E-mail: boston.geography@census.gov

Kansas City Regional Census Center
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 298-9614
E-mail:
kansas.city.geography@census.gov

Charlotte Regional Census Center
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200 or 1-866-5115822
Fax: (704) 909-6714
E-mail: charlotte.geography@census.gov

Los Angeles Regional Census Center
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago Regional Census Center
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York Regional Census Center
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 233-2410
E-mail:
new.york.rcc.geography@census.gov

Dallas Regional Census Center
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (972) 755-3705
E-mail: dallas.geography@census.gov

Philadelphia Regional Census Center
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 717-8001
E-mail:
philadelphia.geography@census.gov

Denver Regional Census Center
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 897-6415
E-mail:
denver.rcc.geography@census.gov

Seattle Regional Census Center
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

44

2010 Census Tribal Statistical Areas Program

Guidelines for Delineating
Tribal Designated Statistical Areas

Version 1
January 2008

1. Introduction................................................................................................................... 3
2. Background on TDSAs and the TSAP ........................................................................ 5
2.1 Purpose of TDSAs ................................................................................................... 5
2.2 Tribes Eligible to Delineate TDSAs....................................................................... 6
2.3 Schedule ................................................................................................................... 6
2.4 Program Materials.................................................................................................. 6
2.5 Important Information on Features...................................................................... 8
2.5.1 Acceptable Features for Use as TDSA Boundaries ........................................... 8
2.5.2 Boundary Feature Updates................................................................................. 9
Guidelines for Updating Features ............................................................................... 9
2.6 Feature Extension Criteria................................................................................... 10
3. Criteria......................................................................................................................... 10
3.1 All Tribal Designated Statistical Areas must follow these criteria: ................. 10
3.2 All Tribal Designated Statistical Areas should follow these guidelines:.......... 11
3.3 Things to consider when delineating TDSAs...................................................... 11
4. Procedures ................................................................................................................... 12
4.1 Annotating Maps................................................................................................... 12
4.1.1 The Census Bureau suggests the following procedures for reviewing and
revising an existing Tribal Designated Statistical Area: .......................................... 12
4.1.2 The Census Bureau suggests the following procedures for delineating a new
TDSA: ....................................................................................................................... 13
4.1.3 Examples.......................................................................................................... 13
4.2 Transmitting Completed Submissions and Census Bureau Review ................ 15
4.3 Verification ............................................................................................................ 15
Appendix A – American Indian and Alaska Native Tribe Areas Eligible for
Delineation ....................................................................................................................... 16
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder...................................................................................................... 39
Appendix C - Regional Census Center’s Contact Information .................................. 44

2

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people
and the economy. The U.S. Constitution mandates that a census be taken every 10 years
in order to reapportion the House of Representatives. The data gathered by the decennial
census and other Census Bureau programs are used for several other purposes, including
the allocation and distribution of funds to state, local and tribal governments. Census
information shapes important policy decisions that in turn shape the nation’s social and
economic conditions. While best known for the decennial census, the Census Bureau
conducts numerous surveys and censuses that measure changing individual and
household demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need.
Many tribal communities use census information to attract new business and plan for
growth. In fact, many tribes and tribal organizations use census data to plan new
facilities and programs for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has created the Tribal
Statistical Areas Program (TSAP) to collect updates to the inventory and boundaries of
American Indian and Alaska Native statistical geographic areas. Participation in the
TSAP is voluntary however, if your tribe chooses not to participate, the Census Bureau
may update the boundary of an existing area or delineate a new area in accordance with
published criteria and guidelines. The TSAP includes the following statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts (TCTs) and tribal block groups (TBGs) on American Indian
reservations (AIRs)/ off-reservation trust lands (ORTLs)
census designated places (CDPs)

The Census Bureau will tabulate statistical data from the 2010 Census for each entity
type listed above, and will continue to use these areas to provide data from the American
Community Survey (ACS) through the coming decade. Meaningful statistical data from
the 2010 Census and the ACS provide tribes and other data users with a tool to help them
make informed decisions and plan for community services. More information about the
background and components of these geographic areas can be found in the Federal
Register notice Vol. 73, No. 221 / Friday, November 14, 2008, page 67470 which can be
accessed from the TSAP website at
http://www.census.gov/geo/www/tsap2010/tsap2010.html.
These guidelines explain the criteria and complete instructions for delineating TDSAs
using paper maps. The subjects covered are:
ƒ

Background on the TSAP and TDSAs

3

ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Tribes Eligible to Delineate TDSAs
Schedule
Required Materials
TDSA Criteria
Procedures for Annotating Maps
Procedures for Transmitting Completed Submissions
Census Bureau Submission Review
Verification

Those wishing to delineate TDSAs will have the option of using their paper maps or
Census Bureau-provided Geographic Information System (GIS) data, tools, shapefiles,
and ESRI® extension specific to this program. Participants who choose to submit
changes using the digital method must have ArcGIS® 9.2.
The TSAP Extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides
a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management
features of the extension. In addition to the inherent functionality of the ArcGIS
software, the extension’s unique editing tools consist of geographic area assignment, as
well as line editing and polygon split/merge functions. The option of using either the
TSAP extension or the paper maps to submit changes is at the complete discretion of
each tribe as neither is preferred over the other by the Census Bureau. However,
depending on the number anticipated updates and/or their complexity, you might consider
using the TSAP extension which offers you the ability to view population density within
American Indian statistical areas and allow you to more clearly add or remove area or
adjust boundaries. If you are interested in using a GIS application to submit your
boundaries and you have ArcGIS 9.2 or 9.3 software, but did not receive the ArcGIS
extension software or digital data files along with your materials, please contact your
Regional Census Center. You may also contact RCC staff to ask other questions or
arrange for training 1 .
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is
used to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical
tribal entities for use in tabulating and publishing data from the 2010 Census, the
American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours
per respondent, including time for reviewing instructions, assembling materials,
organizing and reviewing the information, and reporting any needed changes. We
anticipate that an estimated 650 participants will respond. Remaining entities may be
1

See Appendix C for RCC contact information.

4

worked by Census Bureau regional staff. For larger areas or areas with many changes,
however, the respondent burden may be 180 hours or longer to complete. Please send
comments regarding this burden estimate or any other aspect of this collection of
information, including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 06070795” as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background on TDSAs and the TSAP
2.1 Purpose of TDSAs
In an effort to improve the presentation of data for federally recognized American Indians
that did not have a reservation or off-reservation trust lands, boundaries for TDSAs were
first introduced for the 1990 Census of Population and Housing, and then revised during
Census 2000. Prior to 1990, data were only tabulated for federal and state recognized
reservations and off-reservation trust lands, legal tribal subdivisions and the Historic
Areas of Oklahoma (now called OTSAs). As part of the 2010 Census, TSAP eligible
tribal officials will again have the opportunity to review and update the boundaries of
their existing TDSA or delineate new TDSA.
The primary purpose for delineating a TDSA is to obtain meaningful statistical data for a
recognized tribe within a geographic area encompassing a substantial concentration of
tribal members. TDSAs are intended to identify lands associated with federally
recognized tribes that do not have an American Indian reservation or off-reservation trust
lands and provide them with meaningful statistical data that is relevant to their current
data needs and present day location. A TDSA is intended to be comparable to the AIRs
within the same state or region, especially those for tribes that are of similar size, for
analyzing data over time and to provide a way to obtain comparable data. The
boundaries of a TDSA may not necessarily include all tribal members if, for example, a
tribe has tribal members living in many areas of the county or state. TDSAs do not depict
land ownership or represent an area over which a tribe has any form of governmental
authority or jurisdiction, nor do they represent all of the traditional or historical areas
associated with the tribe, including areas used for subsistence activities. A TDSA should
5

represent a geographic area where there is a concentration of tribal population currently
living and where the tribe has social, economic or historical ties to the land. These
should be evidenced by the existence of tribally owned businesses, buildings, meeting
areas or culturally significant structures.
Statistical data will be tabulated for all people living within the boundaries of a TDSA
(including non-tribal members), and also for all tribal members regardless of where they
reside in the state or nation. Each individual, whether or not he or she is located on a
tribal area, will have the same opportunity to identify their tribal affiliation. While data
tabulated for a well defined TDSA will provide a rich source of statistical and
demographic information for your statistical area, it is not necessary for an individual to
be living within the boundary of the TDSA to be counted as part of the tribe.
2.2 Tribes Eligible to Delineate TDSAs
Every federally recognized tribe without a reservation or off-reservation trust land and
based outside of Alaska, Hawaii and Oklahoma are eligible to update or delineate a
TDSA. Federal recognition of an American Indian tribe specifically means that the tribe
is recognized by and eligible to receive services from the Bureau of Indian Affairs (BIA).
BIA recognition is determined by inclusion of a tribe on the BIA’s list of recognized
tribes or by addenda to the list as published by BIA. If you do have a recognized AIR
and/or ORTL and therefore believe you are not eligible to delineate a TDSA, please
contact your RCC. If the TDSA official declines or defers participation, the Census
Bureau will use the TDSA boundaries delineated for Census 2000, modified as needed to
meet the Census 2010 criteria. If no TDSA was defined for the Census 2000, the Census
Bureau will most likely not delineate one for 2010 without tribal participation.
2.3 Schedule
In fall 2008, the Census Bureau mailed formal invitation letters to tribal officials eligible
to delineate a TDSA. These guidelines and accompanying paper maps required to
complete the work are scheduled to arrive in January 2009. You will have 120 days from
the date you receive these materials to review and submit your TDSA delineations or
updates to the Census Bureau’s RCC. In the fall of 2009, after the Census Bureau has
reviewed and incorporated your TDSA into our geographic database, you will receive
new maps or digital files so that you can verify that we have inserted your boundaries
correctly. If you have questions regarding your delineation or submission, assistance will
be available from geographers at your RCC.
2.4 Program Materials
The paper map types you receive will depend on the size and mapping complexity of
your TDSA. A TDSA that is smaller in land area may only receive a single mapsheet.
TDSAs with large land area may receive an index map, a series of parent maps, and a
number of inset maps. An index map shows the complete TDSA with gridlines defining
specific areas shown on each parent map. A parent map shows a detailed version of a
single grid box from the index map, and an inset map shows finer details of areas within
the parent map where the feature network is too dense to represent clearly at the map

6

scale of the parent sheet. You can think of the inset map as a “blow-up” of a specific
area.

Figure 1: Example of Index, Parent and Inset maps
If your tribe has a Census 2000 TDSA delineation, your map will depict the Census 2000
TDSA boundary with a one mile fringe area. If your updates include area outside of this
fringe area, please contact your RCC for maps depicting this additional area.
If your tribe did not have a Census 2000 TDSA, your RCC will provide county maps for
the area in which the TDSA might be delineated. If the TDSA should be delineated in
counties for which you did not receive maps, please contact the RCC and they will
provide you with the county maps you need. Figure 2 shows entity boundaries that are
shown on your maps and how they are symbolized.

Figure 2: Tribal areas map symbology

7

The Census Bureau requests that participants use a pencil with red lead to annotate TDSA
boundaries on the paper maps provided. Procedures for annotating the paper maps are
detailed in section 4.
2.5 Important Information on Features
2.5.1 Acceptable Features for Use as TDSA Boundaries
TDSA boundaries should follow specified legal or administrative boundaries that do not
change greatly over time, or permanent, visible features, such as roads, perennial streams,
railroads, and high-tension power lines. Permanent visible features should be easily
locatable in the field by Census Bureau staff without ambiguity. The acceptable visible
boundary features are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (main)
carline, streetcar track, monorail, other mass transit rail
interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county
highway, secondary and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
fencelines

Natural topographic features include the crests of well-defined mountain ridges; the rims
or bases of sharply defined escarpments, cliffs, or bluffs; the position of dry ravines or
arroyos; as well as other features as long as the features are not also mimicked by another
visible feature, have no housing in the vicinity, and are easily located on the ground.
Data user and Census Bureau experience has shown that some features make better
boundaries than others, and the same type of feature can make an excellent boundary in
one place and a poor one in another. Rivers, major canals, lakes, and other bodies of
water often make good statistical area boundaries because they generally limit access
from one area to another and rarely change relative location. Other features that limit
access between areas, such as interstate and other major highways, railroad tracks, and
the ridges of mountain ranges, also make good statistical area boundaries. In some
8

instances, however, such a feature unifies a community, for example, a lake forming the
core of a recreational housing development or a through street forming the spine of a
subdivision. In these circumstances, the statistical area boundary should include the entire
area of the lake or both sides of a unifying street to better encompass similar community
patterns.
In general, when delineating boundaries in bodies of water represented as polygons and
having area (lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow
a line bisecting the water body rather than following a shoreline. If possible, use an
existing line in water (for example, a city limit in the middle of a river) rather than adding
a new line.
Officials delineating TDSAs may only add non-visible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and
ridgelines, are not available and they aid in a TDSA meeting other specific delineation
criteria and/or guidelines. The Census Bureau staff will contact you if they require more
information or have questions about feature updates submitted as part of the 2010 TSAP.
2.5.2 Boundary Feature Updates
The Census Bureau has spent the last six years enhancing the spatial accuracy of the
roads in our database system. The local files used during this project were required to
have an overall average accuracy of 7.6 meters while some files had better accuracy.
Although much of the street network is vastly improved, as you work with our maps you
may notice that in some counties the street and boundary features look distorted. A line
that should be straight may have a noticeable kink or pointed shape. The Census Bureau
is working to correct these problems, and if you need to use a feature that is distorted in
our maps follow the guidelines below.
The Census Bureau is also now moving forward with our 2010 Census field canvassing
and collection activities. This means that we are no longer processing realignments to
our street network. What is critical for the success of the 2010 Census data tabulation is
the location of roads relative to the tabulation entity boundary. As long as the road is
within the correct entity, the population and housing will be properly reported. The
guidelines below also explain what updates are acceptable as part of the TSAP.
It is critical that participants understand that the TSAP is not intended for street feature
updates except where a boundary follows a road (or other visible feature such as a
stream) and the road is not reflected in our file. For this reason the Census Bureau can
not accept street (or other) feature updates that do not follow the guidelines below:
Guidelines for Updating Features
1. If a road is missing and it forms the boundary for the area you are defining, add
the road and provide the name.
2. If you can not correctly delineate the boundary for an entity you are updating
because the feature you need to follow is incorrectly located, mislabeled or
distorted in the Census Bureau’s file, we request that you fix that feature only. In
9

addition, we request that you report the problem area to the Census Bureau
(through your RCC) by sending information describing the incorrect feature and
the specific entity boundary affected.
3. Do not add streets that are missing for an entire housing development (add only
streets that are needed to form a boundary). We will be adding new or missing
streets during our address canvassing operation which will occur in the spring and
early summer of 2009. The Census Bureau will provide verification materials to
each participant that returns their submission in the correct format and within the
allotted 120 days that will show the results of address canvassing. If these streets
are still missing at that time, we will accept these as adds.
2.6 Feature Extension Criteria
If you want to use an existing feature that doesn’t form a closed polygon, you may add a
short line to connect the features and close the polygon. The Census Bureau refers to
these lines as feature extensions and several requirements pertain. To avoid creating
ambiguous Census block boundaries, we require that feature extensions:
ƒ Are no longer than 300 feet;
ƒ Are straight lines from the end of a road and intersecting a non-road feature
(These include all hydrographic features, pipelines, powerlines, and railroads.);
ƒ Do not intersect a cul-de-sac.

3. Criteria
All American Indian Areas (AIAs) must follow a standard set of criteria that support a
shared purpose of providing a meaningful and relevant geographic framework for
tabulating data for the Census. It is the responsibility of the Census Bureau to ensure that
geographic entity criteria can achieve the goal of providing meaningful, relevant, and
reliable statistical data, and that the final criteria for geographic entities are met. While
aware that there are secondary uses of geographic entities and the data tabulated for them,
the Census Bureau will not modify their boundaries or attributes specifically to meet
these secondary uses, including those of other government agencies. If a change is made
to a geographic entity to meet one specific purpose, it may be detrimental for other
programs that also use these entities. The Census Bureau will use the criteria and
guidelines listed below to help ensure that the TDSAs delineated for the 2010 Census
meet their definition, support the intended purpose of the program, provide useful and
meaningful data for the tribe they represent, and enhance the ability of data users to make
more meaningful comparisons between data.
Criteria are rules that must be followed by all officials delineating statistical AIAs for the
2010 Census, while guidelines are suggestions for improving the relevance and utility of
statistical AIAs.
3.1 All Tribal Designated Statistical Areas must follow these criteria:
1. A TDSA must contain some American Indian population and housing.
2. A TDSA may not overlap with any other AIA, at the same level of the geographic
hierarchy.
10

3. A TDSA may not completely surround another legal or statistical AIA at the same
level of the geographic hierarchy.
4. A TDSA may not include more water area than land area.
5. Officials delineating TDSAs may only add nonvisible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and
ridgelines, are not available and they aid in a TDSA meeting other specific,
delineation criteria and/or guidelines.
6. The Census Bureau will evaluate the submitted name to ensure that each TDSAs
name is clearly distinguishable from the name of any other legal or statistical AIA.
7. TDSAs may not include military areas.
8. TDSAs may not be delineated in Hawaii, Oklahoma or Alaska, nor will those existing
in Alaska continue to be recognized.
9. The name of a TDSA will be determined by the tribe or tribes, in conjunction with the
Census Bureau.
10. The name must also reflect one of two conditions: the tribe that has the largest
population currently residing within the TDSA, or the name of the tribe most
commonly associated with the area that the TDSA encompasses.
3.2 All Tribal Designated Statistical Areas should follow these guidelines:
1. TDSAs should be comparable in area to the AIRs and/or ORTLs of other tribes with
similar numbers of members in the same state and/or region.
2. American Indians should constitute a large proportion of the population within a
TDSA, and of the American Indian population, the majority should be members of
the delineating tribe.
3. As a minimum, TDSAs should have a population of 1,200 individuals or 480 housing
units.
4. A TDSA should include an area where there is structured and organized tribal
activity, including tribal headquarters, tribal service centers, meeting areas and
buildings, ceremonial grounds, tribally owned commercial locations, etc.
5. TDSAs should not contain large areas without housing or population. A housing unit
density of at least three housing units per square mile is suggested.
6. TDSAs should be contiguous.
7. Water area should be included only to maintain contiguity, to provide a generalized
version of the shoreline, or if the water area is completely surrounded by land area
included in the TDSA.
8. TDSA boundaries should follow visible, physical features, such as rivers, streams,
shorelines, roads, and ridgelines.
9. TDSA boundaries may follow the nonvisible, legally defined boundaries of AIRs,
ORTLs, states, counties, or incorporated places.
3.3 Things to consider when delineating TDSAs
Since TDSAs also will be used to tabulate and present period estimates from the ACS,
defining officials should consider that, as a general rule, period estimates of demographic
characteristics for geographic entities with small populations will be subject to higher
variances than comparable estimates for geographic entities with larger populations. In
11

addition, the Census Bureau’s disclosure rules may have the effect of restricting the
availability and amount of data for geographic entities with small populations. The more
closely a TDSA’s boundary relates to the distribution of tribal members and American
Indians receiving governmental services from the tribe, and does not include large
numbers of people and households not affiliated with the tribe, the more likely that data
presented for the TDSA will accurately reflect the characteristics of the intended tribal
population.
Although eligible, in a few cases a tribe may elect not to delineate a TDSA if it will not
provide meaningful, relevant, or reliable statistical data because the member population
now resides in numerous other locations or has been completely subsumed by nonmember and/or non-American Indian populations. In such instances, defining a TDSA
will not improve the presentation of statistical data relating to tribal members. These
tribes may still be able to receive meaningful, relevant, and reliable statistical data for
their tribal membership at higher levels of census geography through the characteristic of
tribal affiliation. Both population and housing unit data can be found by accessing
American FactFinder on the Census Bureau’s internet website. Directions for obtaining
this data can be found in Appendix B.

4. Procedures
4.1 Annotating Maps
4.1.1 The Census Bureau suggests the following procedures for reviewing and revising an
existing Tribal Designated Statistical Area:
1. Compare your source materials with the Census Bureau’s maps.
2. If you are satisfied with how the TDSA boundary is currently portrayed on the
Census Bureau’s maps, fill out and sign the form attached to the cover letter that
came with your materials, indicating there is “no change” to the boundary. Return the
form to the RCC using the postage paid envelope provided.
3. If you need to change the TDSA boundary, cross out the old boundary with an “X”
using a pencil with red lead. Mark the ends of the deletion with red hatch marks (//).
4. Using a pencil with red lead, plot the revised boundaries on the Census Bureau’s map.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your TDSA. The Census Bureau will not
accept new road features at this time unless the road or other feature is
necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature, then use a red pencil to highlight the
feature as a TDSA boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your TDSA
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact your RCC to
describe the location and nature of the problem.

12

c. Please remember to adjust your TDSA boundary to follow the acceptable
features described in section 2.5.
5. Review the name of the 2000 TDSA. If the name is still appropriate for the TDSA,
make no annotation. If the name requires revision, cross out the old name and clearly
label the new name in red within the boundary of the TDSA.
4.1.2 The Census Bureau suggests the following procedures for delineating a new TDSA:
1. If you do not wish to delineate a TDSA, fill out and sign the form attached to the
cover letter that came with your materials, indicating you do not wish to delineate a
TDSA.
2. Compare your source materials with the Census Bureau’s map(s).
3. Using a pencil with red lead, plot the boundary on the Census Bureau’s map(s).
4. If a feature that is not on the map(s) is required as the boundary of the TDSA, use a
black lead pencil to add and label the new feature and the red pencil to highlight the
feature as a TDSA boundary.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your TDSA. The Census Bureau will not
accept new road features at this time unless the road or other feature is
necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature, then use a red pencil to highlight the
feature as a TDSA boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your TDSA
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact your RCC to
describe the location and nature of the problem.
5. Ensure that the TDSA boundary follows the acceptable feature described in section
2.5.
6. Clearly label the name of the new TDSA in red within the boundary of the TDSA.
4.1.3 Examples

13

Figure 3: In this image, area is being added to an existing TDSA.

Figure 4: In this image, area is being removed from an existing TDSA.

14

4.2 Transmitting Completed Submissions and Census Bureau Review
Please return all maps to the RCC in the same tube/box/envelope you received it in and
be sure to use the mailing label provided. The Census Bureau RCC geographic staff will
verify that the submitted TDSAs are complete, meet all criteria and other requirements
and, where the criteria have not been met, a valid justification is provided.
The Census Bureau will provide feedback to you on your submission, and if necessary
provide additional guidance on the criteria and guidelines usage. The Census Bureau will
contact your tribe with any questions or concerns regarding the submission. The Census
Bureau reserves the right to modify, create, or reject any boundary or attribute as needed
to meet the final program criteria and guidelines, or to maintain geographic relationships
before the tabulation geography is finalized for the 2010 Census.
4.3 Verification
If you return your submissions within 120 days, the Census Bureau will provide you with
a new map which your tribe can use to verify that the Census Bureau staff inserted the
boundary of the TDSA correctly. The verification map will be provided in late 2009. At
that time it would be possible for tribes to make minor boundary changes or add features
that still may be missing from our maps.

15

Appendix A – American Indian and Alaska Native Tribe Areas Eligible
for Delineation
Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Absentee-Shawnee Tribe of Indians Citizen Potawatomi NationAbsentee Shawnee OTSA

5600

106,624

Adai Caddo Tribe
Agdaagux Tribe of King Cove
Agua Caliente Band of Cahuilla
Indians

Adais Caddo SDAISA
King Cove ANVSA
Agua Caliente Reservation

9510
6735
0020

39,080
792
21,358

Ak Chin Indian Community of the
Maricopa (Ak Chin) Indian
Reservation

Maricopa (Ak Chin) Reservation 2130

742

234 CDP, BDP

Denver

Akiachak Native Community
Akiak Native Community
Alabama-Coushatta Tribes

Akiachak ANVSA
6020
Akiak ANVSA
6025
Alabama-Coushatta Reservation 0050

585
309
480

189 ANVSA
76 ANVSA
203 CDP, BDP

Seattle
Seattle
Dallas

Alatna Village
Alexander Creek, Incorporated
Algaaciq Native Village
Allakaket Village
Alturas Indian Rancheria
Angoon Community Association
Anvik Village
Apache Tribe

Alatna ANVSA
Alexander Creek (Susitna)
Algaacig ANVSA
Allakaket ANVSA
Alturas Rancheria
Angoon ANVSA
Anvik ANVSA
Kiowa-Comanche-Apache-Fort
Sill Apache OTSA

6040
6055
6065
6070
0095
6100
6125
5720

35
0
373
133
2
572
104
193,260

17 ANVSA
0 ANVSA
127 ANVSA
68 ANVSA
2 CDP, BDP
221 ANVSA
49 ANVSA
81,174 AITS

Arapahoe Tribe of the Wind River
Reservation

Wind River Reservation

4610

23,245

9,369 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Asa'carsarmiut Tribe
Mountain Village ANVSA
Assiniboine and Sioux Tribes of the Fort Peck Reservation
Fort Peck Indian Reservation

6975
1250

755
10,321

211 ANVSA
Seattle
3,755 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Atqasuk Village
Atqasuk ANVSA
Augustine Band of Cahuilla Indians Augustine Reservation

6165
0125

228
0

Ayakulik, Incorporated
Ayakulik
Bad River Band of the Lake
Bad River Reservation
Superior Tribe of Chippewa Indians
of the Bad River Reservation

6170
0140

1,411

Bay Mills Indian Community
Bay Mills Reservation
Bear River Band of the Rohnerville Rohnerville Rancheria
Rancheria

0170
3220

Beaver Village
Berry Creek Rancheria of Maidu
Indians

6190
0200

Beaver ANVSA
Berry Creek Rancheria

41,192 AITS

Regional
Census
Center
Kansas City

16,890 SDTSA
Dallas
207 ANVSA
Seattle
20,926 Tribal Tracts,
Los Angeles
Tribal BG, CDP,
BDP

60 ANVSA
0 CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Kansas City

Seattle
Los Angeles

ANVSA
595 Tribal Block,
CDP, BDP

Seattle
Chicago

605
98

260 CDP, BDP
29 CDP, BDP

Detroit
Seattle

84
0

54 ANVSA
0 CDP, BDP

Seattle
Seattle

16

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Big Lagoon Rancheria
Big Lagoon Rancheria
Big Pine Band of Owens Valley
Big Pine Reservation
Paiute Shoshone Indians of the Big
Pine Reservation

0240
0250

24
462

9 CDP, BDP
181 CDP, BDP

Seattle
Los Angeles

Big Sandy Rancheria of Mono
Indians

Big Sandy Rancheria

0265

98

34 CDP, BDP

Los Angeles

Big Valley Band of Pomo Indians of Big Valley Rancheria
the Big Valley Rancheria

0275

225

64 CDP, BDP

Seattle

Birch Creek Tribe
Bishop Paiute Tribe

Birch Creek ANVSA
Bishop Reservation

6235
0290

28
1,441

Blackfeet Tribe of the Blackfeet
Indian Reservation

Blackfeet Reservation

0305

10,100

Blue Lake Rancheria
Blue Lake Rancheria
Bridgeport Paiute Indian Colony
Bridgeport Reservation
Buena Vista Rancheria of Me-Wuk Tribal Area Placeholder
Indians

0325
0350
0000

78
43
0

41 CDP, BDP
21 CDP, BDP
0 TDSA

Seattle
Seattle
Seattle

Burns Paiute Tribe of the Burns
Paiute Indian Colony

Burns Paiute Colony

0400

167

56 CDP, BDP

Seattle

Cabazon Band of Mission Indians Cabazon Reservation
Cachil DeHe Band of Wintun
Colusa Rancheria
Indians of the Colusa Indian
Community of the Colusa Rancheria

0415
0750

806
77

192 CDP, BDP
25 CDP, BDP

Caddo Nation

Caddo-Wichita-Delaware OTSA 5540

14,638

Cahto Indian Tribe of the
Laytonville Rancheria

Laytonville Rancheria

22 ANVSA
530 Tribal Block,
CDP, BDP

Seattle
Los Angeles

3,583 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

6,897 AITS

Los Angeles
Seattle

Kansas City

1925

188

61 CDP, BDP

Seattle

Cahuilla Band of Mission Indians of Cahuilla Reservation
the Cahuilla Reservation

0435

154

56 CDP, BDP

Los Angeles

California Valley Miwok Tribe
Campo Band of Diegueno Mission
Indians of the Campo Indian
Reservation

Tribal Area Placeholder
Campo Reservation

0000
0450

0
351

0 TDSA
111 CDP, BDP

Seattle
Los Angeles

Capitan Grande Band of Diegueno
Mission Indians: Barona Group of
Capitan Grande Band of Mission
Indians of the Barona Reservation

Barona Reservation

0155

536

162 CDP, BDP

Los Angeles

Capitan Grande Band of Diegueno
Mission Indians: Barona Group of
Capitan Grande Band of Mission
Indians of the Barona Reservation

Capitan Grande Reservation

0495

0

0 CDP, BDP

Los Angeles

Capitan Grande Band of Diegueno
Mission Indians: Viejas (Baron
Long) Group of Capitan Grande
Band of Mission Indians of the
Viejas Reservation

Viejas Reservation

4500

394

148 CDP, BDP

Los Angeles

17

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

2010 Census
Areas Eligible
for Delineation
0 CDP, BDP

Regional
Census
Center

Capitan Grande Band of Diegueno
Mission Indians: Viejas (Baron
Long) Group of Capitan Grande
Band of Mission Indians of the
Viejas Reservation

Capitan Grande Reservation

0495

Caswell Native Association,
Incorporated

Caswell

6260

Catawba Indian Nation
Cayuga Nation of New York
Cedarville Rancheria
Chalkyitsik Village
Cheesh-Na Tribe
Chemehuevi Indian Tribe of the
Chemehuevi Reservation

Catawba Reservation
Cayuga Nation TDSA
Cedarville Rancheria
Chalkyitsik ANVSA
Chistochina ANVSA
Chemehuevi Reservation

0525
8100
0555
6265
6325
0585

494
10,707
26
83
75
345

Cher-Ae Heights Indian Community Trinidad Rancheria
of the Trinidad Rancheria

4275

52

Cherokee Nation
Cherokee Tribe of Northeast
Alabama

Cherokee OTSA
Cherokee Tribe of Northeast
Alabama SDAISA

5550
9560

462,327
173

204,270 AITS
92 SDTSA

Cherokees of Southeast Alabama

Cherokees of Southeast Alabama 9550
SDAISA

120,294

55,734 SDTSA

6285
5560
0605

765
157,869
8,466

190 ANVSA
Seattle
66,836 AITS
Kansas City
3,002 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Chickahominy Indian Tribe
Chickahominy Indians Eastern
Division

Chickahominy SDAISA
9580
Eastern Chickahominy SDAISA 9675

3,313
104

Chickaloon Native Village
Chickasaw Nation
Chicken Ranch Rancheria of MeWuk Indians

Chickaloon ANVSA
Chickasaw OTSA
Chicken Ranch Rancheria

6290
5580
0620

16,918
277,416
11

Chignik Bay Tribal Council
Chignik Lake Village
Chilkat Indian Village
Chilkoot Indian Association
Chinik Eskimo Community
Chippewa-Cree Indians of the
Rocky Boy's Reservation

Chignik ANVSA
Chignik Lake ANVSA
Chilkat ANVSA
Chilkoot ANVSA
Golovin ANVSA
Rocky Boy's Reservation

6295
6305
6310
6315
6540
3205

79
145
139
338
144
1,605

Chitimacha Tribe
Choctaw Apache Tribe
Choctaw Nation
Chuloonawick Native Village
Circle Native Community

Chitimacha Reservation
Apache Choctaw SDAISA
Choctaw OTSA
Chulloonawick ANVSA
Circle ANVSA

0635
9515
5590
6340
6350

409
23,459
224,472
0
100

Chevak Native Village
Chevak ANVSA
Cheyenne and Arapahoe Tribes
Cheyenne-Arapaho OTSA
Cheyenne River Sioux Tribe of the Cheyenne River Reservation
Cheyenne River Reservation

0

Census
2000
Housing
Units

ANVSA
174 CDP, BDP
4,906 TDSA
9 CDP, BDP
62 ANVSA
39 ANVSA
699 Tribal Block,
CDP, BDP
28 CDP, BDP

1,311 SDTSA
42 SDTSA
6,393 ANVSA
127,634 AITS
4 CDP, BDP
80 ANVSA
50 ANVSA
85 ANVSA
186 ANVSA
54 ANVSA
426 Tribal Block,
CDP, BDP
168 CDP, BDP
13,671 SDTSA
101,877 AITS
1 ANVSA
42 ANVSA

Los Angeles

Seattle
Charlotte
Boston
Seattle
Seattle
Seattle
Los Angeles
Seattle

Kansas City
Atlanta
Atlanta

Charlotte
Charlotte
Seattle
Kansas City
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Denver
Dallas
Dallas
Kansas City
Seattle
Seattle

18

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Citizen Potawatomi Nation

Citizen Potawatomi NationAbsentee Shawnee OTSA

5600

106,624

Clifton Choctaw Tribe
Cloverdale Rancheria of Pomo
Indians

Clifton Choctaw SDAISA
Tribal Area Placeholder

9630
0000

476
0

Cocopah Tribe

Cocopah Reservation

0695

1,025

970 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Coeur D'Alene Tribe of the Coeur
D'Alene Reservation

Coeur d'Alene Reservation

0705

6,551

4,015 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

Coharie Tribe
Cold Springs Rancheria of Mono
Indians

Coharie SDAISA
Cold Springs Rancheria

9635
0720

123,761
193

0735

9,201

Comanche Nation

Kiowa-Comanche-Apache-Fort 5720
Sill Apache OTSA

193,260

Confederated Salish & Kootenai
Tribes of the Flathead Reservation

Flathead Reservation

1110

26,172

Confederated Tribes and Bands of
the Yakama Nation

Celilo Village

0560

44

Confederated Tribes and Bands of
the Yakama Nation

Yakama Reservation

4690

31,646

Confederated Tribes of the Chehalis Chehalis Reservation
Reservation

0575

691

Confederated Tribes of the Colville Colville Reservation
Reservation

0760

7,582

Confederated Tribes of the Coos,
Coos, Lower Umpqua, and
Lower Umpqua and Siuslaw Indians Siuslaw Reservation

0770

11

1 CDP, BDP

Seattle

Confederated Tribes of the Goshute Goshute Reservation
Reservation

1340

105

45 CDP, BDP

Denver

Confederated Tribes of the Grand
Ronde Community

Grand Ronde Community

1365

0

0 CDP, BDP

Seattle

Confederated Tribes of the Siletz
Reservation

Siletz Reservation

3795

308

104 CDP, BDP

Seattle

Confederated Tribes of the Umatilla Celilo Village
Reservation

0560

44

22 CDP, BDP

Seattle

Confederated Tribes of the Umatilla Umatilla Reservation
Reservation

4405

2,927

Confederated Tribes of the Warm
Springs Reservation

0560

44

Colorado River Indian Tribes of the Colorado River Reservation
Colorado River Indian Reservation

Celilo Village

41,192 AITS

Regional
Census
Center

205 SDTSA
0 TDSA

54,248 SDTSA
46 CDP, BDP

Kansas City
Dallas
Seattle

Charlotte
Los Angeles

5,894 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
81,174 AITS

Kansas City

12,679 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
22 CDP, BDP

Seattle

9,087 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
214 CDP, BDP

Seattle

3,303 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

1,065 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
22 CDP, BDP

Seattle

19

Tribe Name

Confederated Tribes of the Warm
Springs Reservation

Area Name

Warm Springs Reservation

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

4545

3,311

883 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

Coquille Tribe
Coquille Reservation
Cortina Indian Rancheria of Wintun Cortina Rancheria
Indians

0775
0780

258
19

98 CDP, BDP
9 CDP, BDP

Seattle
Seattle

Coushatta Tribe
Cow Creek Band of Umpqua
Indians

Coushatta Reservation
Cow Creek Reservation

0795
0815

25
22

14 CDP, BDP
8 CDP, BDP

Dallas
Seattle

Cowlitz Indian Tribe
Coyote Valley Band of Pomo
Indians

Tribal Area Placeholder
Coyote Valley Reservation

0000
0825

0
104

0 TDSA
31 CDP, BDP

Seattle
Seattle

Craig Community Association
Crow Creek Sioux Tribe of the
Crow Creek Reservation

Craig ANVSA
Crow Creek Reservation

6385
0855

1,725
2,225

737 ANVSA
617 Tribal Block,
CDP, BDP

Seattle
Denver

Crow Tribe

Crow Reservation

0845

6,894

2,280 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Curyung Tribal Council
Death Valley Timbi-Sha Shoshone
Band

Dillingham ANVSA
Timbi-Sha Shoshone
Reservation

6405
4180

2,466
0

1,000 ANVSA
0 CDP, BDP

Seattle
Los Angeles

Delaware Nation

Caddo-Wichita-Delaware OTSA 5540

14,638

6,897 AITS

Kansas City

Douglas Indian Association
Dry Creek Rancheria of Pomo
Indians

Douglass ANVSA
Dry Creek Rancheria

6420
0955

5,297
53

2,372 ANVSA
15 CDP, BDP

Seattle
Seattle

Duckwater Shoshone Tribe of the
Duckwater Reservation

Duckwater Reservation

0975

149

65 CDP, BDP

Denver

Eastern Band of Cherokee Indians

Eastern Cherokee Reservation

0990

8,092

Eastern Shawnee Tribe
Echota Cherokee Tribe
Egegik Village
Eklutna Native Village
Ekwok Village
Elem Indian Colony of Pomo
Indians of the Sulphur Bank
Rancheria

Eastern Shawnee OTSA
Echota Cherokee SDAISA
Egegik ANVSA
Eklutna ANVSA
Ekwok ANVSA
Sulphur Bank Rancheria

5640
9680
6445
6450
6460
4030

661
65,068
116
394
130
69

278 AITS
26,997 SDTSA
286 ANVSA
141 ANVSA
56 ANVSA
15 CDP, BDP

Elk Valley Rancheria
Ely Shoshone Tribe
Emmonak Village
Enterprise Rancheria of Maidu
Indians

Elk Valley Rancheria
Ely Reservation
Emmonak ANVSA
Enterprise Rancheria

1010
1040
6480
1055

77
133
767
1

36 CDP, BDP
67 CDP, BDP
218 ANVSA
1 CDP, BDP

Evansville Village
Ewiiaapaayp Band of Kumeyaay
Indians

Evansville ANVSA
Ewiiaapaayp Reservation

6490
1065

71
0

66 ANVSA
0 CDP, BDP

3,194 Tribal Tracts,
Charlotte
Tribal BG, CDP,
BDP
Kansas City
Atlanta
Seattle
Seattle
Seattle
Seattle

Seattle
Denver
Seattle
Seattle
Seattle
Los Angeles

20

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Federated Indians of Graton
Rancheria

Tribal Area Placeholder

0000

0

Flandreau Santee Sioux Tribe
Forest County Potawatomi
Community

Flandreau Reservation
Forest County Potawatomi
Community

1100
1135

408
524

Fort Belknap Indian Community of Fort Belknap Reservation
the Fort Belknap Reservation of
Montana

1150

2,959

Fort Bidwell Indian Community of
the Fort Bidwell Reservation

1170

108

47 CDP, BDP

Seattle

Fort Independence Indian
Fort Independence Reservation
Community of Paiute Indians of the
Fort Independence Reservation

1195

86

42 CDP, BDP

Los Angeles

Fort McDermitt Paiute and
Shoshone Tribes of the Fort
McDermitt Indian Reservation

Fort McDermitt Reservation

1210

309

119 CDP, BDP

Fort McDowell Yavapai Nation
Fort Mojave Indian Tribe
Fort Sill Apache Tribe

Fort McDowell Reservation
1220
Fort Mojave Reservation
1235
Kiowa-Comanche-Apache-Fort 5720
Sill Apache OTSA

824
813
193,260

275 CDP, BDP
339 CDP, BDP
81,174 AITS

Four Winds Tribe
Four Winds Cherokee SDAISA 9720
Galena Village
Galena ANVSA
6525
Gila River Indian Community of the Gila River Reservation
1310
Gila River Indian Reservation

79,657
675
11,257

Fort Bidwell Reservation

Gold Creek-Susitna Association,
Incorporated

Gold Creek

6537

Grand Traverse Band of Ottawa &
Chippewa Indians

Grand Traverse Reservation

1370

Greenville Rancheria of Maidu
Indians

Greenville Rancheria

Grindstone Indian Rancheria of
Wintun-Wailaki Indians

0 TDSA

Regional
Census
Center

137 CDP, BDP
170 CDP, BDP

Seattle
Denver
Chicago

967 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Denver

Denver
Denver
Kansas City

34,316 SDTSA
Dallas
259 ANVSA
Seattle
2,901 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
ANVSA

Seattle

0

0 CDP, BDP

Detroit

1380

22

9 CDP, BDP

Seattle

Grindstone Rancheria

1395

162

49 CDP, BDP

Seattle

Guidiville Rancheria
Gulkana Village
Habematolel Pomo of Upper Lake
Haliwa-Saponi Tribe
Hannahville Indian Community
Hassanamisco Band of the Nipmuc
Nation

Guidiville Rancheria
Gulkana ANVSA
Upper Lake Rancheria
Haliwa-Saponi SDAISA
Hannahville Community
Hassanamisco (state)
Reservation

1400
6560
4430
9745
1410
9150

0
164
82
8,272
295
2

0 CDP, BDP
74 ANVSA
34 CDP, BDP
3,384 SDTSA
81 CDP, BDP
1 State Res.

Havasupai Tribe of the Havasupai
Reservation

Havasupai Reservation

1440

503

161 CDP, BDP

Denver

Healy Lake Village
Healy Lake ANVSA
Ho-Chunk Nation
Ho-Chunk Nation Reservation
Hoh Indian Tribe of the Hoh Indian Hoh Reservation
Reservation

6575
1450
1460

37
638
102

21 ANVSA
223 CDP, BDP
33 CDP, BDP

Seattle
Chicago
Seattle

Holy Cross Village
Hoonah Indian Association

6585
6590

227
860

81 ANVSA
384 ANVSA

Seattle
Seattle

Holy Cross ANVSA
Hoonah ANVSA

Seattle
Seattle
Seattle
Charlotte
Detroit
Boston

21

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Hoopa Valley Tribe

Hoopa Valley Reservation

1490

2,633

1,001 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

Hopi Tribe

Hopi Reservation

1505

6,815

2,480 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Hopland Band of Pomo Indians of
the Hopland Rancheria

Hopland Rancheria

1515

14

Houlton Band of Maliseet Indians
Hualapai Indian Tribe of the
Hualapai Indian Reservation

Houlton Maliseet Reservation
Hualapai Reservation

1530
1545

0
1,353

Hughes Village
Hughes ANVSA
Huslia Village
Huslia ANVSA
Hydaburg Cooperative Association Hydaburg ANVSA

6605
6610
6615

78
293
382

Igiugig Village
Inaja Band of Diegueno Mission
Indians of the Inaja and Cosmit
Reservation

6620
1560

53
0

20 ANVSA
0 CDP, BDP

Seattle
Los Angeles

Ione Band of Miwok Indians
Ione Band of Miwok TDSA
Iowa Tribe of Kansas and Nebraska Iowa (KS-NE) Reservation

8300
1590

8
168

4 TDSA
67 CDP, BDP

Seattle
Kansas City

Iowa Tribe of Oklahoma
Iqurmuit Traditional Council
Ivanoff Bay Village
Jackson Rancheria of Me-Wuk
Indians

Iowa OTSA
Russian Mission ANVSA
Ivanof Bay ANVSA
Jackson Rancheria

5670
7315
6650
1640

6,148
296
22
2

2,536 AITS
81 ANVSA
12 ANVSA
1 CDP, BDP

Kansas City
Seattle
Seattle
Seattle

Jamestown S'Klallam Tribe

Jamestown S'Klallam
Reservation

1655

9

4 CDP, BDP

Jamul Indian Village
Jicarilla Apache Nation

Jamul Indian Village
Jicarilla Apache Reservation

1670
1700

1
2,755

Kaguyak Village
Kaguyak
Kaibab Band of Paiute Indians of the Kaibab Reservation
Kaibab Indian Reservation

6660
1720

196

ANVSA
88 CDP, BDP

Seattle
Denver

Kaktovik Village
Kalispel Indian Community of the
Kalispel Reservation

6680
1735

293
206

95 ANVSA
63 CDP, BDP

Seattle
Seattle

Karuk Tribe
Karuk Reservation
Kashia Band of Pomo Indians of the Stewarts Point Rancheria
Stewarts Point Rancheria

1750
3985

57
57

17 CDP, BDP
17 CDP, BDP

Seattle
Seattle

Kasigluk Traditional Elders Council Kasigluk ANVSA

6710

543

110 ANVSA

Kaw Nation
Kenaitze Indian Tribe
Ketchikan Indian Corporation

5690
6720
6725

6,123
29,320

2,759 AITS
14,124 ANVSA
ANVSA

Igiugig ANVSA
Inaja and Cosmit Reservation

Kaktovik ANVSA
Kalispel Reservation

Kaw OTSA
Kenaitze ANVSA
Ketchikan

6 CDP, BDP

Seattle

0 CDP, BDP
475 Tribal Block,
CDP, BDP

Boston
Denver

39 ANVSA
111 ANVSA
154 ANVSA

Seattle
Seattle
Seattle

Seattle

1 CDP, BDP
Los Angeles
972 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Seattle
Kansas City
Seattle
Seattle

22

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Keweenaw Bay Indian Community Ontonagon Reservation
of L'Anse and Ontonagon Bands

2580

0

Keweenaw Bay Indian Community L'Anse Reservation
of L'Anse and Ontonagon Bands

1880

3,538

Kian Tree Corporation
Kickapoo Traditional Tribe
Kickapoo Tribe of Indians of the
Kickapoo Reservation

Canyon Village
Kickapoo (TX) Reservation
Kickapoo (KS) Reservation

6257
1775
1770

Kickapoo Tribe of Oklahoma
King Island Native Community
King Salmon Tribe
Kiowa Indian Tribe

Kickapoo OTSA
Ukivok (King Island)
King Salmon
Kiowa-Comanche-Apache-Fort
Sill Apache OTSA

5700
7675
6740
5720

193,260

Klamath Tribes
Klawock Cooperative Association
Knik Tribe
Kokhanok Village
Kootenai Tribe
Koyukuk Native Village
La Jolla Band of Luiseno Mission
Indians of the La Jolla Reservation

Klamath Reservation
Klawock ANVSA
Knik ANVSA
Kokhanok ANVSA
Kootenai Reservation
Koyukuk ANVSA
La Jolla Reservation

1785
6765
6785
6800
1800
6830
1850

La Posta Band of Diegueno Mission La Posta Reservation
Indians of the La Posta Indian
Reservation

420
4,419

2010 Census
Areas Eligible
for Delineation
0 CDP, BDP

Regional
Census
Center
Detroit

1,613 Tribal Tracts,
Detroit
Tribal BG, CDP,
BDP
ANVSA
Seattle
104 CDP, BDP
Dallas
1,902 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP
7,130 AITS
ANVSA
ANVSA
81,174 AITS

Kansas City
Seattle
Seattle
Kansas City

9
854
31,969
174
75
101
390

6 CDP, BDP
368 ANVSA
16,333 ANVSA
59 ANVSA
24 CDP, BDP
55 ANVSA
143 CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Los Angeles

1895

18

6 CDP, BDP

Los Angeles

Lac Courte Oreilles Band of Lake
Superior Chippewa Indians

Lac Courte Oreilles Reservation 1815

2,886

1,980 Tribal Tracts,
Chicago
Tribal BG, CDP,
BDP

Lac du Flambeau Band of Lake
Superior Chippewa Indians of the
Lac du Flambeau Reservation

Lac du Flambeau Reservation

1825

2,995

2,907 Tribal Tracts,
Chicago
Tribal BG, CDP,
BDP

Lac Vieux Desert Band of Lake
Superior Chippewa Indians

Lac Vieux Desert Reservation

1830

135

50 CDP, BDP

Detroit

Las Vegas Tribe of Paiute Indians of Las Vegas Colony
the Las Vegas Indian Colony

1915

108

37 CDP, BDP

Denver

Lesnoi Village
Levelock Village
Lime Village
Little River Band of Ottawa Indians

Lesnoi (Woody Island)
Levelock ANVSA
Lime Village ANVSA
Little River Reservation

6860
6865
6875
1960

122
6
2

ANVSA
50 ANVSA
24 ANVSA
2 CDP, BDP

Seattle
Seattle
Seattle
Detroit

Little Shell Tribe of Chippewa
Indians

Tribal Area Placeholder

0000

0

0 SDTSA

Denver

Little Traverse Bay Bands of Odawa Little Traverse Bay Reservation 1963
Indians

0

0 CDP, BDP

Detroit

70

23 CDP, BDP

Los Coyotes Band of Cahuilla and
Cupeno Indians

Los Coyotes Reservation

1995

18,544

Census
2000
Housing
Units

Los Angeles

23

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Lovelock Paiute Tribe of the
Lovelock Indian Colony

Lovelock Colony

2015

103

Lower Brule Sioux Tribe of the
Lower Brule Reservation

Lower Brule Reservation

2030

1,353

Lower Elwha Tribal Community of Lower Elwha Reservation
the Lower Elwha Reservation

2040

Lower Lake Rancheria
Tribal Area Placeholder
Lower Muscogee Creek Tribe
Tama (state) Reservation
Lower Sioux Indian Community of Lower Sioux Reservation
Minnesota Mdewakanton Sioux
Indians of the Lower Sioux
Reservation
Lumbee Tribe
Lummi Tribe of the Lummi
Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

38 CDP, BDP

Denver

392 Tribal Block,
CDP, BDP

Denver

260

84 CDP, BDP

Seattle

0000
9400
2055

0
57
335

0 TDSA
21 State Res.
116 CDP, BDP

Lumbee SDAISA
Lummi Reservation

9815
2070

474,100
4,193

Lytton Rancheria
MaChis Lower Creek Tribe
Makah Indian Tribe of the Makah
Indian Reservation

Lytton Rancheria
MaChis Lower Creek SDAISA
Makah Reservation

2075
9820
2085

0
24,198
1,356

Manchester Band of Pomo Indians
of the Manchester-Point Arena
Rancheria

Manchester-Point Arena
Rancheria

2100

197

65 CDP, BDP

Manley Hot Springs Village
Manokotak Village
Manzanita Band of Diegueno
Mission Indians of the Manzanita
Reservation

Manley Hot Springs ANVSA
Manokotak ANVSA
Manzanita Reservation

6900
6905
2115

72
399
69

105 ANVSA
106 ANVSA
29 CDP, BDP

Seattle
Seattle
Los Angeles

Mashantucket Pequot Tribe

Mashantucket Pequot
Reservation

2145

315

111 CDP, BDP

Boston

Mashpee Wampanoag Tribe
Tribal Area Placeholder
Match-e-be-nash-she-wish Band of Tribal Area Placeholder
Pottawatomi Indians

0000
0000

0
0

Mattaponi Indian Tribe
McGrath Native Village
Mechoopda Indian Tribe of Chico
Rancheria

Mattaponi (state) Reservation
McGrath ANVSA
Mechoopda TDSA

9230
6895
8450

58
401
3,198

28 State Res.
213 ANVSA
1,162 TDSA

Meherrin Tribe
Menominee Indian Tribe

Meherrin SDAISA
Menominee Reservation

9825
2175

7,867
3,216

3,419 SDTSA
Charlotte
929 Tribal Tracts,
Chicago
Tribal BG, CDP,
BDP

Mentasta Traditional Council
Mentasta Lake ANVSA
Mesa Grande Band of Diegueno
Mesa Grande Reservation
Mission Indians of the Mesa Grande
Reservation

6945
2190

125
75

Mescalero Apache Tribe of the
Mescalero Reservation

2205

3,156

Mescalero Reservation

Seattle
Atlanta
Kansas City

184,305 SDTSA
Charlotte
1,749 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
0 CDP, BDP
11,048 SDTSA
533 Tribal Block,
CDP, BDP

0 TDSA
0 TDSA

68 ANVSA
19 CDP, BDP

Seattle
Atlanta
Seattle
Seattle

Boston
Detroit
Charlotte
Seattle
Seattle

Seattle
Los Angeles

916 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

24

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Metlakatla Indian Community,
Annette Island Reserve

Annette Island Reserve

0110

1,447

Miami Tribe
Miccosukee Tribe of Indians
Middletown Rancheria of Pomo
Indians

Miami OTSA
Miccosukee Reservation
Middletown Rancheria

5730
2240
2255

Minchumina Natives Incorporated
Minnesota Chippewa Tribe

Lake Minchumina
6850
Minnesota Chippewa Trust Land 2285

Minnesota Chippewa Tribe (Bois
Forte Band (Nett Lake))

Bois Forte Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

562 Tribal Block,
CDP, BDP

Seattle

271
0
73

103 AITS
0 CDP, BDP
20 CDP, BDP

Kansas City
Atlanta
Seattle

0

ANVSA
0 CDP, BDP

Seattle
Kansas City

0335

657

398 CDP, BDP

Kansas City

Minnesota Chippewa Tribe (Fond du Fond du Lac Reservation
Lac Band)

1125

3,728

Minnesota Chippewa Tribe (Grand Grand Portage Reservation
Portage Band)

1355

557

Minnesota Chippewa Tribe (Leech
Lake Band)

Leech Lake Reservation

1940

10,205

Minnesota Chippewa Tribe (Mille
Lacs Band)

Sandy Lake Reservation

3385

70

Minnesota Chippewa Tribe (Mille
Lacs Band)

Mille Lacs Reservation

2270

4,548

2,826 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP

Minnesota Chippewa Tribe (White
Earth Band)

White Earth Reservation

4595

9,188

4,991 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP

Mississippi Band of Choctaw
Indians

Mississippi Choctaw Reservation 2300

4,311

1,184 Tribal Tracts,
Dallas
Tribal BG, CDP,
BDP

1,512 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP
286 CDP, BDP

Kansas City

6,828 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP
22 CDP, BDP

Kansas City

Moapa Band of Paiute Indians of the Moapa River Reservation
Moapa River Indian Reservation

2315

206

90 CDP, BDP

Denver

Modoc Tribe
Modoc OTSA
Mohegan Indian Tribe
Mohegan Reservation
Montana Creek Native Association, Montana Creek
Incorporated

5740
2320
6970

228
2

79 AITS
1 CDP, BDP
ANVSA

Kansas City
Boston
Seattle

Mooretown Rancheria of Maidu
Indians

Mooretown Rancheria

2340

166

52 CDP, BDP

Seattle

Morongo Band of Cahuilla Mission Morongo Reservation
Indians of the Morongo Reservation

2360

954

345 CDP, BDP

MOWA Band of Choctaw Indians

MOWA Choctaw (state)
Reservation

9240

124

37 State Res.

Muckleshoot Indian Tribe of the
Muckleshoot Reservation

Muckleshoot Reservation

2375

3,597

Muscogee (Creek) Nation

Creek OTSA

5620

704,565

Los Angeles

Atlanta

1,329 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
306,727 AITS

Kansas City

25

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Nagamut, Limited
Naknek Native Village
Nanticoke Indian Tribe

Nagamut
6985
Naknek ANVSA
6990
Nanticoke Indian Tribe SDAISA 9830

Nanticoke Lenni-Lenape Indians

Nanticoke Lenni Lenape
SDAISA

Narragansett Indian Tribe
Native Village of Afognak
Native Village of Akhiok
Native Village of Akutan
Native Village of Aleknagik
Native Village of Ambler
Native Village of Atka
Native Village of Barrow Inupiat
Traditional Government
Native Village of Belkofski
Native Village of Brevig Mission
Native Village of Buckland
Native Village of Cantwell
Native Village of Chanega
Native Village of Chignik Lagoon
Native Village of Chitina
Native Village of Chuathbaluk
Native Village of Council
Native Village of Deering
Native Village of Diomede
Native Village of Eagle
Native Village of Eek
Native Village of Ekuk
Native Village of Elim
Native Village of Eyak
Native Village of False Pass
Native Village of Fort Yukon
Native Village of Gakona
Native Village of Gambell
Native Village of Georgetown
Native Village of Goodnews Bay
Native Village of Hamilton
Native Village of Hooper Bay
Native Village of Kanatak
Native Village of Karluk
Native Village of Kiana
Native Village of Kipnuk
Native Village of Kivalina
Native Village of Kluti Kaah
Native Village of Kobuk
Native Village of Kongiganak

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

678
22,683

ANVSA
455 ANVSA
17,594 SDTSA

Seattle
Seattle
Philadelphia

9835

12,316

2,959 SDTSA

Philadelphia

Narragansett Reservation
Afognak
Akhiok ANVSA
Akutan ANVSA
Aleknagik ANVSA
Ambler ANVSA
Atka ANVSA
Barrow ANVSA

2415
6005
6015
6030
6045
6075
6150
6175

60

20 CDP, BDP
ANVSA
34 ANVSA
38 ANVSA
107 ANVSA
98 ANVSA
41 ANVSA
1,620 ANVSA

Boston
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

Belkofski ANVSA
Brevig Mission ANVSA
Buckland ANVSA
Cantwell ANVSA
Chenega ANVSA
Chignik Lagoon ANVSA
Chitina ANVSA
Chuathbaluk ANVSA
Council ANVSA
Deering ANVSA
Inalik ANVSA
Eagle ANVSA
Eek ANVSA
Ekuk ANVSA
Elim
Eyak ANVSA
False Pass ANVSA
Fort Yukon ANVSA
Gakona ANVSA
Gambell ANVSA
Georgetown ANVSA
Goodnews Bay ANVSA
Hamilton ANVSA
Hooper Bay ANVSA
Kanatak
Karluk ANVSA
Kiana ANVSA
Kipnuk ANVSA
Kivalina ANVSA
Copper Center ANVSA
Kobuk ANVSA
Kongiganak ANVSA

6195
6240
6250
6255
6280
6300
6330
6335
6380
6400
6630
6430
6440
6455
6470
6495
6500
6515
6520
6530
6535
6545
6570
6595
6695
6700
6730
6750
6755
6365
6790
6810

4 ANVSA
76 ANVSA
89 ANVSA
177 ANVSA
27 ANVSA
68 ANVSA
41 ANVSA
43 ANVSA
40 ANVSA
61 ANVSA
47 ANVSA
57 ANVSA
83 ANVSA
73 ANVSA
ANVSA
65 ANVSA
40 ANVSA
317 ANVSA
39 ANVSA
187 ANVSA
4 ANVSA
87 ANVSA
0 ANVSA
239 ANVSA
3,997 ANVSA
24 ANVSA
133 ANVSA
154 ANVSA
80 ANVSA
281 ANVSA
45 ANVSA
90 ANVSA

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

80
713
221
309
92
4,581
0
276
406
222
86
103
106
119
0
136
146
77
280
2
168
64
595
84
649
3
230
0
1,014
10,252
27
388
644
377
492
109
359

26

Tribe Name

Native Village of Kotzebue
Native Village of Koyuk
Native Village of Kwigillingok
Native Village of Kwinhagak
Native Village of Larsen Bay
Native Village of Marshall
Native Village of Mary's Igloo
Native Village of Mekoryuk
Native Village of Minto
Native Village of Nanwalek
Native Village of Napaimute
Native Village of Napakiak
Native Village of Napaskiak
Native Village of Nelson Lagoon
Native Village of Nightmute
Native Village of Nikolski
Native Village of Noatak
Native Village of Nuiqsut
Native Village of Nunam Iqua
Native Village of Nunapitchuk
Native Village of Ouzinkie
Native Village of Paimiut
Native Village of Perryville
Native Village of Pilot Point
Native Village of Pitka's Point
Native Village of Point Hope
Native Village of Point Lay
Native Village of Port Graham
Native Village of Port Heiden
Native Village of Port Lions
Native Village of Ruby
Native Village of Saint Michael
Native Village of Savoonga
Native Village of Scammon Bay
Native Village of Selawik
Native Village of Shaktoolik
Native Village of Shishmaref
Native Village of Shungnak
Native Village of Stevens
Native Village of Tanacross
Native Village of Tanana
Native Village of Tatitlek
Native Village of Tazlina
Native Village of Teller
Native Village of Tetlin
Native Village of Tuntutuliak

Area Name

Kotzebue ANVSA
Koyuk ANVSA
Kwigillingok ANVSA
Kwinhagak ANVSA
Larsen Bay ANVSA
Marshall ANVSA
Mary's Igloo ANVSA
Mekoryuk ANVSA
Minto ANVSA
Nanwalek ANVSA
Napaimute ANVSA
Napakiak ANVSA
Napaskiak ANVSA
Nelson Lagoon ANVSA
Nightmute ANVSA
Nikolski ANVSA
Noatak ANVSA
Nuiqsut ANVSA
Nunam Iqua ANVSA
Nunapitchuk ANVSA
Ouzinkie ANVSA
Paimiut ANVSA
Perryville ANVSA
Pilot Point ANVSA
Pitkas Point ANVSA
Point Hope ANVSA
Point Lay ANVSA
Port Graham ANVSA
Port Heiden ANVSA
Port Lions ANVSA
Ruby ANVSA
St. Michael ANVSA
Savoonga ANVSA
Scammon Bay ANVSA
Selawik ANVSA
Shaktoolik ANVSA
Shishmaref ANVSA
Shungnak ANVSA
Stevens Village ANVSA
Tanacross ANVSA
Tanana ANVSA
Tatitlek ANVSA
Tazlina ANVSA
Teller ANVSA
Tetlin ANVSA
Tuntutuliak ANVSA

Census
Census
Area
2000
Code Population
6820
6825
6840
6845
6855
6910
6915
6935
6965
6995
7005
7010
7020
7025
7065
7075
7085
7125
7133
7135
7180
7185
7215
7225
7235
7250
7255
7265
7270
7275
7310
7375
7415
7425
7430
7450
7465
7470
7520
7535
7540
7555
7560
7570
7580
7640

3,082
297
338
555
115
349
0
210
258
177
0
353
390
83
208
39
428
433
164
466
225
2
107
100
125
757
247
171
119
256
188
368
643
465
772
230
562
256
87
140
308
107
339
268
124
370

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

1,007 ANVSA
95 ANVSA
78 ANVSA
153 ANVSA
70 ANVSA
104 ANVSA
5 ANVSA
96 ANVSA
99 ANVSA
54 ANVSA
16 ANVSA
101 ANVSA
95 ANVSA
33 ANVSA
54 ANVSA
28 ANVSA
106 ANVSA
126 ANVSA
45 ANVSA
120 ANVSA
86 ANVSA
1 ANVSA
45 ANVSA
60 ANVSA
42 ANVSA
215 ANVSA
67 ANVSA
82 ANVSA
56 ANVSA
106 ANVSA
107 ANVSA
93 ANVSA
160 ANVSA
114 ANVSA
188 ANVSA
66 ANVSA
148 ANVSA
64 ANVSA
43 ANVSA
53 ANVSA
166 ANVSA
57 ANVSA
173 ANVSA
67 ANVSA
66 ANVSA
97 ANVSA

Regional
Census
Center
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

27

Tribe Name

Area Name

Census
Census
Area
2000
Code Population
325
193
747
152

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Native Village of Tununak
Native Village of Tyonek
Native Village of Unalakleet
Native Village of Venetie Tribal
Government (Arctic Village)

Tununak ANVSA
Tyonek ANVSA
Unalakleet ANVSA
Arctic Village ANVSA

7645
7655
7690
6140

93 ANVSA
90 ANVSA
242 ANVSA
67 ANVSA

Seattle
Seattle
Seattle
Seattle

Native Village of Venetie Tribal
Government (Venetie Village)

Venetie

7725

ANVSA

Seattle

Native Village of Wales
Native Village of White Mountain
Navajo Nation

Wales ANVSA
White Mountain ANVSA
Navajo Nation Reservation

7740
7745
2430

152
203
155,214

Nenana Native Association
New Koliganek Village Council
New Stuyahok Village
Newhalen Village
Newtok Village
Nez Perce Tribe

Nenana ANVSA
New Koliganek ANVSA
New Stuyahok ANVSA
Newhalen ANVSA
Newtok ANVSA
Nez Perce Reservation

7030
7040
7050
7035
7055
2445

402
182
471
160
321
17,959

210 ANVSA
77 ANVSA
107 ANVSA
51 ANVSA
67 ANVSA
7,940 Tribal Tracts,
Tribal BG, CDP,
BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

Nikolai Village
Ninilchik Village
Nisqually Indian Tribe of the
Nisqually Reservation

Nikolai ANVSA
Ninilchik ANVSA
Nisqually Reservation

7070
7080
2460

100
13,264
588

47 ANVSA
7,007 ANVSA
178 CDP, BDP

Seattle
Seattle
Seattle

Nome Eskimo Community
Nondalton Village
Nooksack Indian Tribe
Noorvik Native Community
Northern Cheyenne Tribe of the
Northern Cheyenne Indian
Reservation

Nome
Nondalton ANVSA
Nooksack Reservation
Noorvik ANVSA
Northern Cheyenne Reservation

7095
7100
2475
7110
2490

221
0
634
4,470

ANVSA
120 ANVSA
0 CDP, BDP
157 ANVSA
1,328 Tribal Tracts,
Tribal BG, CDP,
BDP

Seattle
Seattle
Seattle
Seattle
Denver

Northfork Rancheria of Mono
Indians

North Fork Rancheria

2495

9

2 CDP, BDP

Northway Village
Northwestern Band of Shoshone
Nation (Washakie)

Northway ANVSA
Northwestern Shoshone
Reservation

7115
2505

107
0

39 ANVSA
0 CDP, BDP

Seattle
Denver

Nottawaseppi Huron Band of the
Potawatomi

Huron Potawatomi Reservation 1550

11

7 CDP, BDP

Detroit

Nulato Village
Nunakauyarmiut Tribe
Oglala Sioux Tribe of the Pine
Ridge Reservation

Nulato ANVSA
Toksook Bay ANVSA
Pine Ridge Reservation

7130
7625
2810

336
532
14,068

119 ANVSA
Seattle
110 ANVSA
Seattle
3,572 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Ohkay Owingeh

Ohkay Owingeh

2510

6,748

2,554 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

59 ANVSA
Seattle
75 ANVSA
Seattle
59,498 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Los Angeles

28

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Olsonville, Incorporated

Kanakanak (Knugank /
Olsonville)

6787

Omaha Tribe

Omaha Reservation

2550

5,194

1,837 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Oneida Nation
Oneida Tribe of Indians

Oneida (NY) Reservation
Oneida (WI) Reservation

2555
2560

26
21,321

20 CDP, BDP
Boston
7,559 Tribal Tracts,
Chicago
Tribal BG, CDP,
BDP

Onondaga Nation

Onondaga Reservation

2570

1,473

311 Tribal Block,
CDP, BDP

Organized Village of Grayling
Organized Village of Kake
Organized Village of Kasaan
Organized Village of Kwethluk
Organized Village of Saxman
Orutsararmuit Native Village
Osage Nation

Grayling ANVSA
Kake ANVSA
Kasaan ANVSA
Kwethluk ANVSA
Saxman ANVSA
Bethel ANVSA
Osage Reservation

6550
6670
6705
6835
7420
6205
2595

194
710
39
713
431
5,471
44,437

63 ANVSA
288 ANVSA
39 ANVSA
199 ANVSA
146 ANVSA
1,990 ANVSA
18,826 Tribal Tracts,
Tribal BG, CDP,
BDP

7175
5760
5770
2625
1970

61
778
6,204
270
212

20 ANVSA
323 AITS
2,764 AITS
84 CDP, BDP
100 CDP, BDP

Paiute-Shoshone Tribe of the Fallon Fallon Paiute-Shoshone Colony 1070
Reservation and Colony

123

51 CDP, BDP

Denver

Paiute-Shoshone Tribe of the Fallon Fallon Paiute-Shoshone
Reservation and Colony
Reservation

1075

620

256 CDP, BDP

Denver

Pala Band of Luiseno Mission
Indians of the Pala Reservation

Pala Reservation

2635

1,573

408 Tribal Block,
CDP, BDP

Los Angeles

Pamunkey Indian Tribe
Pascua Yaqui Tribe

Pamunkey (state) Reservation
Pascua Yaqui Reservation

9260
2680

58
3,315

36 State Res.
Charlotte
785 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Paskenta Band of Nomlaki Indians
Passamaquoddy Tribe - Indian
Township Reservation

Paskenta Rancheria
Indian Township Reservation

2685
1575

0
676

0 CDP, BDP
261 CDP, BDP

Seattle
Boston

Passamaquoddy Tribe - Indian
Township Reservation

Passamaquoddy Trust Land

2695

0

0 CDP, BDP

Boston

Passamaquoddy Tribe - Pleasant
Point Reservation

Passamaquoddy Trust Land

2695

0

0 CDP, BDP

Boston

Passamaquoddy Tribe - Pleasant
Point Reservation

Pleasant Point Reservation

2850

640

256 CDP, BDP

Boston

Paucatuck Eastern Pequot Indians

Paucatuck Eastern Pequot (state) 9280
Reservation

26

19 State Res.

Boston

Oscarville Traditional Village
Oscarville ANVSA
Otoe-Missouria Tribe of Indians
Otoe-Missouria OTSA
Ottawa Tribe
Ottawa OTSA
Paiute Indian Tribe
Paiute (UT) Reservation
Paiute-Shoshone Indians of the Lone Lone Pine Reservation
Pine Community of the Lone Pine
Reservation

ANVSA

Regional
Census
Center
Seattle

Boston
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Kansas City

Seattle
Kansas City
Kansas City
Denver
Los Angeles

29

Tribe Name

Paugussett Indian Nation
Pauloff Harbor Village
Pauma Band of Luiseno Mission
Indians of the Pauma & Yuima
Reservation

Area Name

Golden Hill (state) Reservation
Pauloff Harbor
Pauma and Yuima Reservation

Census
Census
Area
2000
Code Population
9100
7195
2715

Pawnee Nation
Pawnee OTSA
Pechanga Band of Luiseno Mission Pechanga Reservation
Indians of the Pechanga Reservation
Pedro Bay Village
Penobscot Tribe
Peoria Tribe of Indians
Person County Indians (Sappony)

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

186

0 State Res.
ANVSA
53 CDP, BDP

Boston
Seattle
Los Angeles

5780
2745

16,509
467

7,407 AITS
163 CDP, BDP

Kansas City
Los Angeles

7205
2760
5795
9760

50
562
4,840
1,919

44 ANVSA
263 CDP, BDP
2,051 AITS
811 SDTSA

Seattle
Boston
Kansas City
Charlotte

Petersburg Indian Association
Petersburg
Picayune Rancheria of Chukchansi Picayune Rancheria
Indians

7220
2775

20

ANVSA
16 CDP, BDP

Seattle
Los Angeles

Pilot Station Traditional Village
Pinoleville Pomo Nation
Pit River Tribe
Pit River Tribe
Pit River Tribe
Pit River Tribe
Pit River Tribe
Pit River Tribe
Pit River Tribe
Platinum Traditional Village
Poarch Band of Creek Indians
Point Possession, Incorporated
Pokagon Band of Potawatomi
Indians

Pilot Station ANVSA
Pinoleville Rancheria
Montgomery Creek Rancheria
Big Bend Rancheria
Lookout Rancheria
Pit River Trust Land
Roaring Creek Rancheria
XL Ranch Rancheria
Likely Rancheria
Platinum ANVSA
Poarch Creek Reservation
Point Possession
Pokagon Reservation

7230
2820
2330
0215
1980
2835
3185
4680
1955
7245
2865
7257
2890

550
136
5
0
7
0
9
14
0
41
156

Ponca Tribe of Indians
Ponca Tribe of Nebraska
Poospatuck Indian Nation
Port Gamble Indian Community of
the Port Gamble Reservation

Ponca OTSA
Ponca (NE) Trust Land
Poospatuck (state) Reservation
Port Gamble Reservation

Portage Creek Village
Potter Valley Tribe
Powhatan-Renape
Prairie Band of Potawatomi Nation

Portage Creek ANVSA
Tribal Area Placeholder
Rankokus (state) Reservation
Prairie Band Potawatomi
Reservation

Prairie Island Indian Community

Pedro Bay ANVSA
Penobscot Reservation
Peoria OTSA
Indians of Person County
SDAISA

0

Census
2000
Housing
Units

0

126 ANVSA
42 CDP, BDP
2 CDP, BDP
0 CDP, BDP
5 CDP, BDP
0 CDP, BDP
5 CDP, BDP
13 CDP, BDP
0 CDP, BDP
26 ANVSA
75 CDP, BDP
ANVSA
0 CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Atlanta
Seattle
Detroit

5800
2900
9300
2910

2,284
0
283
699

904 AITS
0 CDP, BDP
104 State Res.
226 CDP, BDP

Kansas City
Denver
New York
Seattle

7260
0000
9330
2980

36
0
0
1,238

22 ANVSA
0 TDSA
0 State Res.
428 Tribal Block,
CDP, BDP

Seattle
Seattle
Philadelphia
Kansas City

Prairie Island Indian Community 2985

177

57 CDP, BDP

Kansas City

152

67 ANVSA

Seattle

Pribilof Islands Aleut Communities St. George ANVSA
of St. Paul & St. George (St.
George)

7340

30

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Pribilof Islands Aleut Communities St. Paul ANVSA
of St. Paul & St. George (St. Paul)

7390

532

Pueblo of Acoma

Acoma Pueblo

0010

2,802

Pueblo of Cochiti

Pueblo de Cochiti

0680

1,502

Pueblo of Isleta

Isleta Pueblo

1625

3,166

Pueblo of Jemez

Jemez Pueblo

1685

1,958

Pueblo of Laguna

Laguna Pueblo

1840

3,815

Pueblo of Nambe

Nambe Pueblo

2400

1,764

735 Tribal Block,
CDP, BDP

Denver

Pueblo of Picuris

Picuris Pueblo

2785

1,801

883 Tribal Block,
CDP, BDP

Denver

Pueblo of Pojoaque

Pueblo of Pojoaque

2990

2,712

1,179 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of San Felipe

San Felipe Pueblo

3400

3,185

738 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of San Ildefonso

San Ildefonso Pueblo

3415

1,524

626 Tribal Block,
CDP, BDP

Pueblo of Sandia

Sandia Pueblo

3370

4,414

1,622 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of Santa Ana
Pueblo of Santa Clara

Santa Ana Pueblo
Santa Clara Pueblo

3480
3495

487
10,658

197 CDP, BDP
Denver
4,435 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of Santo Domingo

Santo Domingo Pueblo

3585

3,166

601 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of Taos

Taos Pueblo

4140

4,484

2,488 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Pueblo of Tesuque
Pueblo of Zia

Tesuque Pueblo
4170
Zia Pueblo and Off-Reservation 4770
Trust Land

806
646

Puyallup Tribe of the Puyallup
Reservation

Puyallup Reservation

3000

41,335

214 ANVSA

Regional
Census
Center
Seattle

1,004 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
625 Tribal Block,
CDP, BDP

Denver

1,204 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
504 Tribal Block,
CDP, BDP

Denver

1,238 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

327 CDP, BDP
189 CDP, BDP

Denver

Denver
Denver

16,385 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

31

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Pyramid Lake Paiute Tribe of the
Pyramid Lake Reservation

Pyramid Lake Reservation

3010

1,734

Qagan Tayagungin Tribe of Sand
Point Village

Sand Point ANVSA

7410

952

Qawalangin Tribe of Unalaska
Unalaska ANVSA
Quapaw Tribe of Indians
Quapaw OTSA
Quartz Valley Indian Community of Quartz Valley Reservation
the Quartz Valley Reservation

7695
5810
3020

4,283
7,455
126

Quechan Tribe of the Fort Yuma
Indian Reservation

Fort Yuma Reservation

1280

2,376

Quileute Tribe of the Quileute
Reservation

Quileute Reservation

3030

371

Quinault Tribe of the Quinault
Reservation

Quinault Reservation

3040

1,370

Ramapough Lenape Indian Nation Ramapough SDAISA
Ramona Band or Village of Cahuilla Ramona Village
Mission Indians

9850
3070

Rampart Village
Red Cliff Band of Lake Superior
Chippewa Indians

Rampart ANVSA
Red Cliff Reservation

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

687 Tribal Block,
CDP, BDP

Denver

282 ANVSA

Seattle

988 ANVSA
3,119 AITS
58 CDP, BDP

Seattle
Kansas City
Seattle

962 Tribal Tracts,
Los Angeles
Tribal BG, CDP,
BDP
128 CDP, BDP

Seattle

487 Tribal Block,
CDP, BDP

Seattle

892
0

262 SDTSA
0 CDP, BDP

New York
Los Angeles

7300
3085

45
1,078

46 ANVSA
429 CDP, BDP

Seattle
Chicago

Red Lake Band of Chippewa Indians Red Lake Reservation
of the Red Lake Reservation

3100

5,162

Redding Rancheria
Redding Rancheria
Redwood Valley Rancheria of Pomo Redwood Valley Rancheria
Indians
Reservation

3095
3115

45
263

Reno-Sparks Indian Colony
Resighini Rancheria
Rincon Band of Luiseno Mission
Indians of the Rincon Reservation

Reno-Sparks Colony
Resighini Rancheria
Rincon Reservation

3130
3145
3165

881
36
1,495

Robinson Rancheria of Pomo
Indians

Robinson Rancheria

3195

138

Rosebud Sioux Tribe of the Rosebud Rosebud Reservation
Indian Reservation

3235

9,050

Round Valley Indian Tribes of the
Round Valley Reservation

3250

82

31 CDP, BDP

Seattle

Rumsey Indian Rancheria of Wintun Rumsey Rancheria
Indians

3265

36

11 CDP, BDP

Seattle

Sac & Fox Nation of Missouri in
Kansas and Nebraska

3285

217

79 CDP, BDP

Kansas City

Sac & Fox Nation, Oklahoma
Sac and Fox OTSA
Sac & Fox Tribe of the Mississippi Sac and Fox/Meskwaki
in Iowa
Reservation

5820
3280

55,690
761

24,684 AITS
267 CDP, BDP

Kansas City
Kansas City

Saginaw Chippewa Indian Tribe

1610

25,822

10,574 Tribal Tracts,
Detroit
Tribal BG, CDP,
BDP

Round Valley Reservation

Sac and Fox Reservation

Isabella Reservation

1,419 Tribal Tracts,
Kansas City
Tribal BG, CDP,
BDP
17 CDP, BDP
87 CDP, BDP
282 CDP, BDP
6 CDP, BDP
385 Tribal Block,
CDP, BDP
39 CDP, BDP

Seattle
Seattle
Denver
Seattle
Los Angeles
Seattle

2,766 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

32

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Saint Regis Mohawk Tribe

St. Regis Mohawk Reservation

3320

2,699

977 Tribal Tracts,
Boston
Tribal BG, CDP,
BDP

Salt River Pima-Maricopa Indian
Community of the Salt River
Reservation

Salt River Reservation

3340

6,405

2,526 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Samish Indian Tribe
Samish TDSA
San Carlos Apache Tribe of the San San Carlos Reservation
Carlos Reservation

8750
3355

33,265
9,385

18,901 TDSA
Seattle
2,497 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

San Manuel Band of Serrano
San Manuel Reservation
Mission Indians of the San Manuel
Reservation

3445

74

27 CDP, BDP

Los Angeles

San Pasqual Band of Diegueno
Mission Indians

3460

752

228 CDP, BDP

Los Angeles

Santa Rosa Band of Cahuilla Indians Santa Rosa Reservation

3525

65

25 CDP, BDP

Los Angeles

Santa Rosa Indian Community of
the Santa Rosa Rancheria

Santa Rosa Rancheria

3520

517

125 CDP, BDP

Los Angeles

Santa Ynez Band of Chumash
Mission Indians of the Santa Ynez
Reservation

Santa Ynez Reservation

3540

122

42 CDP, BDP

Los Angeles

Santa Ysabel Band of Diegueno
Santa Ysabel Reservation
Mission Indians of the Santa Ysabel
Reservation

3550

250

102 CDP, BDP

Los Angeles

Santee Sioux Nation
Santee Reservation
Sauk-Suiattle Indian Tribe
Sauk-Suiattle Reservation
Sault Ste. Marie Tribe of Chippewa Sault Ste. Marie Reservation
Indians

3565
3625
3635

878
45
354

368 CDP, BDP
16 CDP, BDP
116 CDP, BDP

Denver
Seattle
Detroit

Schaghticoke (state) Reservation 9350

9

4 State Res.

Boston

0 TDSA

Seattle

Schaghticoke Tribe

San Pasqual Reservation

Scotts Valley Band of Pomo Indians Tribal Area Placeholder

0000

0

Seldovia Village Tribe
Seminole Nation
Seminole Tribe
Seminole Tribe
Seminole Tribe
Seminole Tribe
Seminole Tribe
Seminole Tribe
Seminole Tribe
Seminole Tribe

Seldovia ANVSA
Seminole OTSA
Immokalee Reservation
Tampa Reservation
Big Cypress Reservation
Brighton Reservation
Coconut Creek Trust Land
Fort Pierce Reservation
Seminole Trust Land
Hollywood Reservation

7435
5830
1555
4130
0225
0360
0690
1260
3665
1475

430
22,792
175
0
142
566
0
2
0
2,051

Seneca Nation

Oil Springs Reservation

2535

11

391 ANVSA
10,255 AITS
62 CDP, BDP
0 CDP, BDP
55 CDP, BDP
216 CDP, BDP
0 CDP, BDP
1 CDP, BDP
0 CDP, BDP
1,498 Tribal Tracts,
Tribal BG, CDP,
BDP
20 CDP, BDP

Seattle
Kansas City
Atlanta
Atlanta
Atlanta
Atlanta
Atlanta
Atlanta
Atlanta
Atlanta

Boston

33

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Seneca Nation

Cattaraugus Reservation

0540

2,412

901 Tribal Tracts,
Boston
Tribal BG, CDP,
BDP

Seneca Nation

Allegany Reservation

0080

6,804

3,035 Tribal Tracts,
Boston
Tribal BG, CDP,
BDP

Seneca-Cayuga Tribe
Shageluk Native Village
Shakopee Mdewakanton Sioux
Community

Seneca-Cayuga OTSA
Shageluk ANVSA
Shakopee Mdewakanton Sioux
Community

5835
7440
3680

3,997
129
266

2,874 AITS
52 ANVSA
97 CDP, BDP

Sherwood Valley Rancheria of
Pomo Indians

Sherwood Valley Rancheria

3735

179

49 CDP, BDP

Seattle

Shingle Springs Band of Miwok
Shingle Springs Rancheria
Indians, Shingle Springs Rancheria
(Verona Tract)

3750

57

16 CDP, BDP

Seattle

Shinnecock Indian Nation
Shinnecock (state) Reservation
Shoalwater Bay Tribe of the
Shoalwater Bay Reservation
Shoalwater Bay Indian Reservation

9370
3780

504
69

194 State Res.
33 CDP, BDP

Shoshone Tribe of the Wind River
Reservation

Wind River Reservation

4610

23,245

9,369 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Shoshone-Bannock Tribes of the
Fort Hall Reservation

Fort Hall Reservation

1185

5,760

2,010 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

Shoshone-Paiute Tribes of the Duck Duck Valley Reservation
Valley Reservation

0965

1,265

Sisseton-Wahpeton Oyate of the
Lake Traverse Reservation

Lake Traverse Reservation

1860

10,408

Sitka Tribe of Alaska
Skagway Village
Skokomish Indian Tribe of the
Skokomish Reservation

Sitka
Skagway
Skokomish Reservation

7475
7485
3825

Skull Valley Band of Goshute
Indians

Skull Valley Reservation

Smith River Rancheria
Smith River Rancheria
Snoqualmie Tribe
Snoqualmie Reservation
Soboba Band of Luiseno Indians of Soboba Reservation
the Soboba Reservation

457 Tribal Block,
CDP, BDP

Kansas City
Seattle
Kansas City

New York
Seattle

Denver

5,184 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

730

ANVSA
ANVSA
279 CDP, BDP

Seattle
Seattle
Seattle

3840

31

11 CDP, BDP

Denver

3855
3860
3870

62
0
522

21 CDP, BDP
0 CDP, BDP
173 CDP, BDP

Seattle
Seattle
Los Angeles

Sokaogon Chippewa Community of Sokaogon Chippewa Community 3885
Chippewa Indians

298

113 CDP, BDP

Chicago

South Naknek Village
Southern Ute Indian Tribe of the
Southern Ute Reservation

South Naknek ANVSA
Southern Ute Reservation

7505
3925

137
11,159

137 ANVSA
Seattle
4,796 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Spirit Lake Tribe

Spirit Lake Reservation

3935

4,435

1,534 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

34

Tribe Name

Spokane Tribe of the Spokane
Reservation

Area Name

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

3940

2,004

Squaxin Island Tribe of the Squaxin Squaxin Island Reservation
Island Reservation

3955

0

St. Croix Chippewa Indians
St. Croix Reservation
Standing Rock Sioux Tribe of North Standing Rock Reservation
& South Dakota

3305
3970

481
8,250

158 CDP, BDP
Chicago
2,762 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Star Musckogee Creek SDAISA 9880

7,331

3,508 SDTSA

Stebbins Community Association
Stebbins ANVSA
7510
Stillaguamish Tribe
Stillaguamish Reservation
4000
Stockbridge-Munsee Community of Stockbridge Munsee Community 4015
Mohican Indians

547
102
1,527

Star Clan of Muscogee Creeks

Spokane Reservation

Census
Census
Area
2000
Code Population

Seattle

0 CDP, BDP

Seattle

134 ANVSA
31 CDP, BDP
676 Tribal Block,
CDP, BDP

Atlanta
Seattle
Seattle
Chicago

Summit Lake Paiute Tribe
Summit Lake Reservation
Sun'aq Tribe of Kodiak
Kodiak (Shoonaq' Tribe)
Suquamish Indian Tribe of the Port Port Madison Reservation
Madison Reservation

4045
6795
2925

6,536

Susanville Indian Rancheria
Swinomish Indians of the
Swinomish Reservation

Susanville Rancheria
Swinomish Reservation

4060
4075

298
2,664

Sycuan Band of the Kumeyaay
Nation

Sycuan Reservation

4090

33

14 CDP, BDP

Los Angeles

Table Mountain Rancheria
Takotna Village
Tanalian, Incorporated
Telida Village
Te-Moak Tribe of Western
Shoshone Indians (Battle Mountain
Band)

Table Mountain Rancheria
Takotna ANVSA
Port Alsworth
Telida ANVSA
Battle Mountain Reservation

4110
7530
7263
7565
0165

11
50
3
124

4 CDP, BDP
49 ANVSA
ANVSA
8 ANVSA
63 CDP, BDP

Los Angeles
Seattle
Seattle
Seattle
Denver

Te-Moak Tribe of Western
Shoshone Indians (Elko Band)

Elko Colony

1005

729

257 CDP, BDP

Denver

Te-Moak Tribe of Western
South Fork Reservation
Shoshone Indians (South Fork Band)

3930

83

42 CDP, BDP

Denver

Te-Moak Tribe of Western
Shoshone Indians (Wells Band)

Wells Colony

4580

54

24 CDP, BDP

Denver

Three Affiliated Tribes of the Fort
Berthold Reservation

Fort Berthold Reservation

1160

5,915

2,881 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Tohono O'odham Nation

Tohono O'odham Reservation

4200

10,483

3,492 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Tonawanda Band of Seneca Indians Tonawanda Reservation

4225

543

Tonkawa Tribe of Indians

5860

4,119

Tonkawa OTSA

15

701 Tribal Block,
CDP, BDP

15 CDP, BDP
Denver
ANVSA
Seattle
2,884 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
95 CDP, BDP
Seattle
1,302 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP

197 CDP, BDP
1,786 AITS

Boston
Kansas City

35

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Tonto Apache Tribe
Torres Martinez Desert Cahuilla
Indians

Tonto Apache Reservation
Torres-Martinez Reservation

4235
4255

132
4,146

Traditional Village of Togiak
Tulalip Tribes of the Tulalip
Reservation

Togiak ANVSA
Tulalip Reservation

7605
4290

809
9,246

Tule River Indian Tribe of the Tule Tule River Reservation
River Reservation

4300

566

179 CDP, BDP

Tuluksak Native Community
Tuluksak ANVSA
Tunica-Biloxi Indian Tribe
Tunica-Biloxi Reservation
Tuolumne Band of Me-Wuk Indians Tuolumne Rancheria
of the Tuolumne Rancheria

7630
4315
4330

428
89
165

93 ANVSA
34 CDP, BDP
66 CDP, BDP

Turtle Mountain Band of Chippewa Turtle Mountain Reservation
Indians

4345

5,815

Tuscarora Nation
Twenty-Nine Palms Band of
Mission Indians

Tuscarora Reservation
4360
Twenty-Nine Palms Reservation 4375

1,138
0

Twin Hills Village
Uganik Natives, Incorporated
Ugashik Village
Umkumiute Native Village
Unga Corporation
United Auburn Indian Community
United Houma Nation
Upper Sioux Community
Upper Skagit Indian Tribe
Ute Indian Tribe of the Uintah &
Ouray Reservation

Twin Hills ANVSA
Uganik
Ugashik ANVSA
Umkumiute
Unga
Auburn Rancheria
United Houma Nation SDAISA
Upper Sioux Reservation
Upper Skagit Reservation
Uintah and Ouray Reservation

7650
7660
7665
7685
7705
0120
9960
4445
4455
4390

0
839,880
57
238
19,182

Ute Mountain Tribe of the Ute
Mountain Reservation

Ute Mountain Reservation

4470

1,687

Utu Utu Gwaitu Paiute Tribe of the Benton Paiute Reservation
Benton Paiute Reservation

0185

50

Uyak, Incorporated
Village of Alakanuk
Village of Anaktuvuk Pass
Village of Aniak
Village of Atmautluak
Village of Bill Moore's Slough
Village of Chefornak
Village of Clarks Point
Village of Crooked Creek
Village of Dot Lake
Village of Iliamna

7715
6035
6080
6105
6160
6225
6275
6360
6390
6415
6625

Uyak
Alakanuk ANVSA
Anaktuvuk Pass ANVSA
Aniak ANVSA
Atmautluak ANVSA
Bill Moore's ANVSA
Chefornak ANVSA
Clark's Point ANVSA
Crooked Creek ANVSA
Dot Lake ANVSA
Iliamna ANVSA

69
11

652
282
572
294
0
394
75
107
38
102

Regional
Census
Center

38 CDP, BDP
Denver
933 Tribal Tracts,
Los Angeles
Tribal BG, CDP,
BDP
221 ANVSA
Seattle
3,638 Tribal Tracts,
Seattle
Tribal BG, CDP,
BDP
Los Angeles
Seattle
Dallas
Seattle

1,911 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
398 CDP, BDP
0 CDP, BDP
33 ANVSA
ANVSA
35 ANVSA
ANVSA
ANVSA
0 CDP, BDP
337,007 SDTSA
31 CDP, BDP
76 CDP, BDP
8,700 Tribal Tracts,
Tribal BG, CDP,
BDP

Boston
Los Angeles
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Dallas
Kansas City
Seattle
Denver

570 Tribal Block,
CDP, BDP

Denver

30 CDP, BDP

Seattle

ANVSA
160 ANVSA
101 ANVSA
203 ANVSA
64 ANVSA
0 ANVSA
82 ANVSA
51 ANVSA
46 ANVSA
25 ANVSA
58 ANVSA

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

36

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Village of Kalskag
Village of Kaltag
Village of Kotlik
Village of Lower Kalskag
Village of Ohogamiut
Village of Old Harbor
Village of Red Devil
Village of Salamatoff
Village of Sleetmute
Village of Solomon
Village of Stony River
Village of Wainwright
Waccamaw Siouan Tribe
Walker River Paiute Tribe of the
Walker River Reservation

Kalskag ANVSA
Kaltag ANVSA
Kotlik ANVSA
Lower Kalskag ANVSA
Ohogamiut ANVSA
Old Harbor ANVSA
Red Devil ANVSA
Salamatof ANVSA
Sleetmute ANVSA
Solomon ANVSA
Stony River ANVSA
Wainwright ANVSA
Waccamaw Siouan SDAISA
Walker River Reservation

6685
6690
6815
6890
7145
7150
7305
7400
7495
7500
7525
7735
9970
4515

230
230
591
267
0
237
48
954
100
4
61
546
2,329
853

66 ANVSA
78 ANVSA
139 ANVSA
79 ANVSA
4 ANVSA
111 ANVSA
22 ANVSA
282 ANVSA
51 ANVSA
4 ANVSA
25 ANVSA
179 ANVSA
891 SDTSA
339 CDP, BDP

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Charlotte
Denver

Wampanoag Tribe of Gay Head
Washoe Tribe
Washoe Tribe (Carson Colony)
Washoe Tribe (Dresslerville
Colony)

Wampanoag-Aquinnah
Washoe Ranches
Carson Colony
Dresslerville Colony

4530
4560
0510
0940

0
0
286
315

0 CDP, BDP
0 CDP, BDP
105 CDP, BDP
116 CDP, BDP

Boston
Denver
Denver
Denver

Washoe Tribe (Stewart Community) Stewart Community

3980

196

62 CDP, BDP

Denver

Washoe Tribe (Woodfords
Community)

Woodfords Community

4665

219

61 CDP, BDP

Denver

White Mountain Apache Tribe of
the Fort Apache Reservation

Fort Apache Reservation

1140

12,429

3,532 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

Wichita and Affiliated Tribes
(Wichita, Keechi, Waco &
Tawakonie)

Caddo-Wichita-Delaware OTSA 5540

14,638

6,897 AITS

Winnebago Tribe

Winnebago Reservation

4625

2,588

Winnemucca Indian Colony
Wiyot Tribe
Wrangell Cooperative Association
Wyandotte Nation
Yakutat Tlingit Tribe
Yankton Sioux Tribe

Winnemucca Colony
Table Bluff Reservation
Wrangell
Wyandotte OTSA
Yakutat ANVSA
Yankton Reservation

4635
4095
7755
5890
7765
4700

62
81
1,678
680
6,500

Yavapai-Apache Nation of the
Camp Verde Indian Reservation

Yavapai-Apache Nation
Reservation

4708

743

197 CDP, BDP

Denver

Yavapai-Prescott Tribe of the
Yavapai Reservation

Yavapai-Prescott Reservation

4710

182

60 CDP, BDP

Denver

Kansas City

875 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP
21 CDP, BDP
30 CDP, BDP
ANVSA
741 AITS
385 ANVSA
2,581 Tribal Tracts,
Tribal BG, CDP,
BDP

Denver
Seattle
Seattle
Kansas City
Seattle
Denver

37

Tribe Name

Area Name

Census
Census
Area
2000
Code Population

Census
2000
Housing
Units

2010 Census
Areas Eligible
for Delineation

Regional
Census
Center

Yerington Paiute Tribe of the
Yerington Colony & Campbell
Ranch

Yerington Colony

4725

139

54 CDP, BDP

Denver

Yerington Paiute Tribe of the
Yerington Colony & Campbell
Ranch

Campbell Ranch

0440

446

80 CDP, BDP

Denver

Yomba Shoshone Tribe of the
Yomba Reservation

Yomba Reservation

4740

96

36 CDP, BDP

Denver

Ysleta Del Sur Pueblo
Yupiit of Andreafski
Yurok Tribe of the Yurok
Reservation

Ysleta Del Sur Pueblo
Andreafsky ANVSA
Yurok Reservation

4755
6095
4760

421
127
1,103

116 CDP, BDP
59 ANVSA
604 Tribal Block,
CDP, BDP

Dallas
Seattle
Seattle

4785

7,758

Zuni Tribe of the Zuni Reservation Zuni Reservation

2,107 Tribal Tracts,
Denver
Tribal BG, CDP,
BDP

38

Appendix B – Procedures for accessing population and housing unit
data from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

39

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

40

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the
first data set listed which is “Census 2000 Summary File 1.” You may want to scroll
through the other data sets to see what other information is available for your future
reference.

41

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example we will access tribal block group data, but you can also
access data for reservations, off-reservation trust lands, tracts, blocks and many other
geographic areas.

42

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1”
that you are looking for. Remember that you may select multiple data types.

6. After clicking “Show Result” you will now see the data you have requested.

43

Appendix C - Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail: charlotte.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

44

2010 Census Tribal Statistical Areas Program

Guidelines for Delineating
Oklahoma Tribal Statistical Areas

Version 1
January 2008

1. Introduction......................................................................................................................... 1
2. Background on OTSA Tribal Statistical Areas................................................................ 3
2.1.1 OTSAs...................................................................................................................... 3
2.1.2 Off Reservation Trust Lands.................................................................................... 4
2.1.3 Joint Use Areas ........................................................................................................ 4
2.1.4 Tribal Subdivisions .................................................................................................. 4
2.1.5 Census Designated Places........................................................................................ 5
2.2 Tribes Eligible to Delineate OTSAs............................................................................. 6
2.3 The Boundary and Annexation Survey ...................................................................... 6
2.4 Schedule ......................................................................................................................... 6
2.5 Program Materials........................................................................................................ 7
2.6 Important Information on Features............................................................................ 8
2.6.1 Acceptable Features for use as boundaries .............................................................. 8
2.6.2 Boundary Feature Updates....................................................................................... 9
2.7 Feature Extension Criteria........................................................................................... 9
3. Criteria and Guidelines for OTSAs, tribal subdivisions on OTSAs and CDPs .......... 10
3.1 The OTSA criteria are: .............................................................................................. 10
3.2 Guidelines for delineating OTSAs are: ..................................................................... 10
3.3 Guidelines for delineating tribal subdivisions within OTSAs are:......................... 11
3.4 The census designated place criteria are: ................................................................. 11
3.5 Guidelines for delineating census designated places are:........................................ 11
4. Procedures ......................................................................................................................... 12
4.1 Review of Statistical Areas......................................................................................... 12
4.2 Annotation of maps: ................................................................................................... 12
4.3 Transmitting completed submissions and Census Bureau review ......................... 13
4.4 Verification .................................................................................................................. 14
Appendix A – Oklahoma tribal statistical areas eligible for delineation........................... 1
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder.............................................................................................................. 1
Appendix C - Regional Census Center’s Contact Information .......................................... 6

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people and
the economy. The U.S. Constitution mandates that a census be taken every 10 years in order
to reapportion the House of Representatives. The data gathered by the decennial census and
other Census Bureau programs are used for several other purposes, including the allocation
and distribution of funds to state, local and tribal governments. Census information shapes
important policy decisions that in turn shape the nation’s social and economic conditions.
While best known for the decennial census, the Census Bureau conducts numerous surveys
and censuses that measure changing individual and household demographics and the entire
economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need. Many
tribal communities use census information to attract new business and plan for growth. In
fact, many tribes and tribal organizations use census data to plan new facilities and programs
for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has developed the Tribal
Statistical Areas Program (TSAP) to collect updates to the inventory and boundaries of
American Indian and Alaska Native statistical geographic areas. Participation in the TSAP is
voluntary, however if your tribe chooses not to participate, the Census Bureau may revise the
boundary of an existing area or delineate a new area in accordance with published criteria
and guidelines. The TSAP includes the following statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts (TCTs) and tribal block groups (TBGs) on American Indian
reservations (AIRs)/ off-reservation trust lands (ORTLs)
census designated places (CDPs)

The Census Bureau will tabulate statistical data from the 2010 Census for each entity type
listed above, and will continue to use these areas to provide data from the American
Community Survey (ACS) through the coming decade. Meaningful statistical data from the
2010 Census and ACS provide tribes and other data users with a tool to help them make
informed decisions and plan for community services. More information about the
background and components of these geographic areas can be found in the Federal Register
notice Vol. 73, No. 221 / Friday, November 14, 2008, page 67470. This notice can also be
accessed from our TSAP webpage:
http://www.census.gov/geo/www/tsap2010/tsap2010.html
These guidelines explain the criteria and complete instructions for using paper maps to
review the Census Bureau’s Census 2000 OTSA boundaries and delineate tribal subdivisions
and CDPs within OTSAs. The topics covered are:

ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Background on OTSA Boundaries, Tribal Subdivisions on OTSAs and CDPs
Tribes Eligible to Delineate OTSAs, Tribal Subdivisions on OTSAs and CDPs
Schedule
Required Materials
OTSA, Tribal Subdivision on OTSA and CDP Criteria
Procedures for Annotating Maps
Procedures for Transmitting Completed Submissions
Census Bureau Submission Review
Verification

Statistical data will be tabulated for all people living within the boundaries of their
geographic areas, and also for all tribal members regardless of where they reside in the state
or nation. Each individual, whether or not he or she is located on a tribal area, will have the
same opportunity to identify their tribal affiliation. While data tabulated for well defined
OTSAs will provide a rich source of statistical and demographic information for your tribe, it
is not necessary for an individual to be living within the boundary of the OTSA to be counted
as part of the tribe. Representation of American Indian statistical boundaries in Census
Bureau products is solely for the purpose of data tabulation and presentation, and does not
convey or confer any rights to land ownership, governmental authority, or jurisdictional
status.
Federally recognized tribes in Oklahoma wishing to update OTSAs and/or delineate OTSA
tribal subdivisions or CDPs will have the option of using paper maps or Census Bureauprovided Geographic Information System (GIS) data, tools, shapefiles, and an ESRI®
ArcGIS® extension specific to this program. Participants who choose to submit changes
using the digital method must have ArcGIS 9.2 or 9.3. These guidelines provide
instructions for to the use of paper maps. There are separate guidelines for the use of the
ESRI extension which are found on the data disc supplied by the Census Bureau.
The TSAP extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides a
suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management features of
the extension. In addition to the inherent functionality of the ArcGIS software, the
extension’s unique editing tools consist of geographic area assignment, block boundary
definition, tribal tract/tribal block group type attribution, as well as line editing and polygon
split/merge functions. The option of using either the TSAP extension or the paper maps to
submit changes is at the complete discretion of each tribe as neither is preferred over the
other by the Census Bureau. However, depending on the number anticipated updates and/or
their complexity, you might consider using the TSAP extension which offers you the ability
to view population density within American Indian statistical areas and allow you to more
clearly add or remove area or adjust boundaries. If you are interested in using a GIS
application to submit your boundaries and you have ArcGIS 9.2 or 9.3 software, but did not
receive the ArcGIS extension software or digital data files along with your materials, please

2

contact the Census Bureau’s Kansas City RCC. 1 You may also contact RCC staff to ask
other questions or arrange for training.
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is used
to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical tribal
entities for use in tabulating and publishing data from the 2010 Census, the American
Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours per
respondent, including time for reviewing instructions, assembling materials, organizing and
reviewing the information, and reporting any needed changes. We anticipate that an
estimated 650 participants will respond. Remaining entities may be worked by Census
Bureau regional staff. For larger areas or areas with many changes, however, the respondent
burden may be 180 hours or longer to complete. Please send comments regarding this
burden estimate or any other aspect of this collection of information, including suggestions
for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 0607-0795”
as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background on OTSA Tribal Statistical Areas
2.1.1 OTSAs
OTSAs are statistical areas identified and delineated by the Census Bureau and federally
recognized tribes based in Oklahoma that had a former American Indian Reservation (AIR)
in Oklahoma. OTSAs are intended to represent the former AIRs that existed in the Indian
and Oklahoma territories prior to Oklahoma statehood in 1907. They provide comparable
1

See Appendix C for RCC contact information.

3

geographic entities for analyzing data over time, and a way to obtain data comparable to that
provided to federally recognized tribes that currently have an AIR. Because all former AIRs
in Oklahoma were delineated for Census 2000, the Census Bureau does not expect any new
OTSAs for the 2010 Census. As part of the TSAP, the Census Bureau is providing your tribe
with the opportunity to review the boundary and name of the Census 2000 OTSA. In
addition, your tribe may opt to identify or revise tribal subdivisions and census designated
places within the Census 2000 OTSA.
2.1.2 Off Reservation Trust Lands
The Census Bureau is aware that federally recognized tribes in Oklahoma have trust lands
throughout the state. As part of the TSAP, a tribe may choose to have the Census Bureau
tabulate data for its ORTL for the 2010 Census. This can be implemented if the tribe can
supply an acceptable Geographic Information System file or map(s) and the required
supporting legal documentation for the Census Bureau to use to record the ORTL accurately.
If a tribe chooses to submit their ORTL to the Census Bureau, the tribe’s ORTL will be
excluded from the OTSA. The trust land areas will then become part of the universe of
legally defined entities updated and maintained through the Census Bureau’s annual
Boundary and Annexation Survey (BAS). Contact your RCC for more information on
reporting ORTLs and the BAS (See section 2.3).
2.1.3 Joint Use Areas
For previous censuses, the Census Bureau allowed the boundaries of OTSAs to deviate
somewhat from the corresponding former AIR boundaries when requested by a tribe and
supported by available demographic data. Such deviations affect the delineation and
identification of other tribes’ OTSAs, resulting in area being associated with multiple
OTSAs. These areas with multiple relationships were defined as separate geographic entities
and identified as “joint use area OTSAs” for Census 2000. In response to comments received
from data users, especially with regard to federal laws and programs requiring the use of the
former AIR boundaries rather than OTSA boundaries, the Census Bureau would like TSAP
participants to workto dissolve the existing OTSA joint use areas. If tribes can not come to
agreement on how to eliminate these areas, we will allow the existing Census 2000 Joint Use
Areas to remain, but will not approve any new ones for 2000. Four joint use area OTSAs
were created for Census 2000:
ƒ
ƒ
ƒ
ƒ

Kiowa-Comanche-Apache-Ft. Sill Apache-Caddo-Wichita-Delaware
Creek-Seminole
Kaw-Ponca
Miami-Peoria.

2.1.4 Tribal Subdivisions
Tribal subdivisions are units of self government and/or administration within an AIR and/or
ORTL for a federally recognized tribe or within an OTSA, that serve social, cultural, and/or
legal purposes for the tribal government. Tribal subdivisions delineated within an AIR or
ORTL are considered “legal geographic entities” by the Census Bureau and, thus, are
specifically termed “legal tribal subdivisions.” These are delineated or updated through the
annual BAS (See section 2.3). Tribal subdivisions delineated within OTSAs are considered
4

‘‘statistical geographic entities’’ by the Census Bureau and are specifically termed
‘‘statistical tribal subdivisions’’ because the larger OTSA is also considered a statistical
geographic entity. They are delineated or updated with the OTSAs through the TSAP. If
delineated, OTSA tribal subdivisions should completely cover all of an OTSA. Separate,
discrete communities whose boundaries encompass a concentration of population and
housing should be identified as a CDP rather than a tribal subdivision (see section 2.1.5).
The Census Bureau tabulates data for only one level of tribal subdivision within an AIR,
ORTL, or OTSA. Tribes that have multiple hierarchical levels of administrative units (for
example, water districts that nest within councilmen districts) should submit the unit with the
smallest geographic area (the water districts using our example) so that their data can be
aggregated if desired for the larger geographic area. The Census Bureau will identify each
tribal subdivision in its data products with the name and administrative unit type (chapter,
district, etc.) submitted by the defining tribal government. The name of each tribal
subdivision must reflect its name, as cited in recent tribal legal documentation and/or used by
the tribal government for administrative purposes.
2.1.5 Census Designated Places
CDPs are statistical geographic areas representing closely settled, unincorporated
communities, which are locally recognized and identified by name. They are the statistical
equivalents of incorporated places, with the primary differences being the lack of both a
legally defined boundary and an active, functioning governmental structure, chartered by the
state and administered by elected officials. CDPs encompass a concentration of population,
housing, and commercial structures that are clearly identifiable by a single name, but are not
within an incorporated place. The primary goal of CDPs is to map a boundary for and
provide meaningful statistics for well-known, unincorporated localities. A CDP generally
consists of a contiguous cluster of census blocks comprising a single piece of territory and
containing a mix of residential and commercial uses similar to that of an incorporated place
of similar size. Some CDPs, however, may be predominantly residential; such places should
represent recognizably distinct, locally known communities, but not typical suburban
subdivisions. A CDP may not be located, either partially or entirely, within an incorporated
place or another CDP.
CDPs are delineated through both the TSAP and the Participant Statistical Areas Program
(PSAP) for the 2010 Census. Federally recognized tribes with AIRs, ORTLs, or OTSAs may
update or delineate new CDPs within the boundary of their reservation, trust land, or OTSA
through the TSAP. Tribes that would like to delineate CDPs for communities completely off
their legal or statistical area should work with the PSAP primary participants for the areas in
which they are interested. Contact the Kansas City RCC (See Appendix C) for more
information.

5

2.2 Tribes Eligible to Delineate OTSAs
Federally recognized tribes based in Oklahoma that had a former AIR in Oklahoma are
invited to review their 2000 OTSA boundary and update or delineate tribal subdivisions
within the OTSA boundary. These tribes are also eligible to delineate CDPs. Federal
recognition of an American Indian tribe specifically means that the tribe is recognized by and
eligible to receive services from the Bureau of Indian Affairs (BIA). BIA recognition is
determined by inclusion of a tribe on the BIA’s list of recognized tribes or by addenda to the
list as published by the BIA. If for any reason, you believe you should not be updating an
OTSA or OTSA tribal subdivision and should be delineating or updating another type of
American Indian Area (or if you have a federally recognized reservation or off-reservation
trust lands), please contact the Kansas City RCC. If the OTSA official declines or defers
participation, the Census Bureau will use the Census 2000 boundaries, possibly modifying it
to meet 2010 OTSA criteria, and will not likely define any tribal subdivisions or CDPs within
the OTSA.
2.3 The Boundary and Annexation Survey
The Boundary and Annexation Survey (BAS) is an annual Census Bureau survey of legal
geographic entities that includes federal AIRs, ORTLs, and any associated tribal
subdivisions. Whereas the TSAP provides the process for reviewing and updating those
AIAs that are statistical geographic entities (TCTs, TBGs, and CDPs), the BAS provides the
process for reviewing and updating AIAs that are legal federal geographic entities, such as
the reservation itself, tribal subdivisions and ORTLs. Its purpose is to determine, solely for
data collection and tabulation by the Census Bureau, the complete and current inventory and
the correct names, legal descriptions, official status, and official, legal boundaries of the legal
geographic entities with governmental authority over certain areas within the United States,
as of January 1 of the survey year. The BAS also collects specific information to document
the legal actions that established a boundary or imposed a boundary change. In support of
the government-to-government relationship with federally recognized American Indian
tribes, the Census Bureau works directly with tribal officials on the BAS. Through the BAS,
the Census Bureau also accepts updates to features such as roads or rivers, and address range
break information at the boundaries. If you wish to update boundaries for you reservation,
off-reservation trust lands or legal tribal subdivisions, you should do so through the BAS.
For more information about the BAS, contact your RCC or see the Census Bureau's website
at http://www.census.gov/geo/www/bas/bashome.html. The BAS Respondent
Guide for federally recognized tribes is available at:
http://www.census.gov/geo/www/bas/bas09/bas09_mat_aia.html
2.4 Schedule
In October 2008, the Census Bureau mailed formal invitation letters to tribal officials of each
eligible OTSA. These guidelines accompany the paper maps required to complete the work.
Tribes will have 120 days from the date they receive these materials to review and submit
their geographic statistical area delineations or updates to the RCC. In late 2009, after the
Census Bureau has reviewed and incorporated your delineations into our geographic
database, you will receive new maps or digital files so that you can verify that we have
6

inserted your boundaries correctly. If you have questions regarding your delineation or
submission, assistance will be available from geographers at the Kansas City RCC.
2.5 Program Materials
The paper map types you receive will vary depending on the size and mapping complexity of
your OTSA. An OTSA that is smaller in land area may only receive a few index and parent
maps. OTSAs with a larger land area may receive an index map, a series of parent maps, and
a number of inset maps. An index map shows the complete OTSA with gridlines defining
specific areas shown on each parent map. A parent map shows a detailed version of a single
grid box from the index map and an inset map shows finer details of areas within the parent
map where the feature network is too dense to represent clearly at the map scale of the parent
sheet. You can think of the inset map as a “blow-up” of a specific area.

Figure 1: Example of Index, Parent and Inset maps

Figure 2: TSAP map symbology

7

Figure 2 shows all the boundaries that may be shown on your map and how they will be
symbolized. The Census Bureau requests that participants use a pencil with purple lead to
annotate OTSA tribal subdivisions and a red pencil to delineate CDP boundaries on the paper
maps provided. Since OTSAs are based on the historical former reservation boundary, the
boundaries should not change from what was used in Census 2000. If you think there is a
problem with those boundaries contact the Kansas City RCC.
2.6 Important Information on Features
2.6.1 Acceptable Features for use as boundaries
Statistical area boundaries should follow specified legal or administrative boundaries that do
not change greatly over time, or permanent, visible features, such as roads, perennial streams,
railroads, and high-tension power lines. Permanent visible features should be easily locatable
in the field by Census Bureau staff without ambiguity. The acceptable visible boundary
features are
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (main)
carline, streetcar track, monorail, other mass transit rail
interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county highway,
secondary and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
fencelines

Natural topographic features include the crests of well-defined mountain ridges; the rims or
bases of sharply defined escarpments, cliffs, or bluffs; the position of dry ravines or arroyos;
as well as other features as long as the features are not also mimicked by another visible
feature, have no housing in the vicinity, and are easily located on the ground.
Data user and Census Bureau experience has shown that some features make better
boundaries than others, and the same type of feature can make an excellent boundary in one
place and a poor one in another. Rivers, major canals, lakes, and other bodies of water often
8

make good statistical area boundaries because they generally limit access from one area to
another and rarely change relative location. Other features that limit access between areas,
such as interstate and other major highways, railroad tracks, and the ridges of mountain
ranges, also make good statistical area boundaries. In some instances, however, such a
feature unifies a community, for example, a lake forming the core of a recreational housing
development or a through street forming the spine of a subdivision. In these circumstances,
the statistical area boundary should include the entire area of the lake or both sides of a
unifying street to better encompass similar community patterns.
In general, when delineating boundaries in bodies of water represented as polygons and
having area (lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow a
line bisecting the water body rather than following a shoreline. Whenever possible, use an
existing line in water (for example, a county line in the middle of a river) rather than adding a
new line.
2.6.2 Boundary Feature Updates
The Census Bureau has spent the last six years enhancing the spatial accuracy of the roads in
our database system. The local files used during this project were required to have an overall
average accuracy of 7.6 meters with some files having better accuracy.
Although much of the street network is vastly improved, as you work with our maps you may
notice that in some counties the street and boundary features look distorted. A line that
should be straight may have a noticeable kink or pointed shape. The Census Bureau is
working to correct these problems, therefore if you need to use a feature that is distorted,
follow the guidelines in section 4.2.
The Census Bureau is now moving forward with our 2010 Census field canvassing and
collection activities. This means that we are no longer processing realignments to our street
network. What is critical for the success of the 2010 Census data tabulation is the location of
roads relative to the tabulation entity boundary. As long as the road is within the correct
entity, the population and housing will be properly reported. The guidelines in section 4.2
also explain what feature updates are acceptable as part of the TSAP.
The Census Bureau staff will contact you if they require more information or have questions
about feature updates submitted as part of our 2010 TSAP.
2.7 Feature Extension Criteria
If you want to use an existing feature that doesn’t form a closed polygon, you may add a
short line to connect the features and close the polygon. The Census Bureau refers to these
lines as feature extensions and several requirements pertain. To avoid creating ambiguous
Census block boundaries, we require that feature extensions:
ƒ Are no longer than 300 feet;
ƒ Are straight lines from the end of a road and intersecting a non-road feature (These
include all hydrographic features, pipelines, powerlines, and railroads.);
ƒ Do not intersect a cul-de-sac.

9

3. Criteria and Guidelines for OTSAs, tribal subdivisions on OTSAs and
CDPs
All American Indian Areas (AIAs) must follow a standard set of criteria that support a shared
purpose of providing a meaningful and relevant geographic framework for tabulating data for
the Census. It is the responsibility of the Census Bureau to ensure that geographic entity
criteria can achieve the goal of providing meaningful, relevant, and reliable statistical data,
and that the final criteria for geographic entities are met. While aware that there are
secondary uses of geographic entities and the data tabulated for them, the Census Bureau will
not modify their boundaries or attributes specifically to meet these secondary uses, including
those of other government agencies. If a change is made to a geographic entity to meet one
specific purpose, it may be detrimental for other programs that also use these entities.
The Census Bureau will use the following criteria and guidelines for the 2010 Census.
Criteria are rules that must be followed by all officials delineating statistical AIAs for the
2010 Census, while guidelines are the Census Bureau’s suggested approach for improving
the relevance and utility of statistical AIAs. Because OTSA boundaries are based on the
historical boundaries of former reservations, they should not change from the boundaries
used in the 2000 Census. If you feel the 2000 boundaries are not correct, please contact the
Kansas City RCC.
3.1 The OTSA criteria are:
1. An OTSA must contain some American Indian population and housing.
2. An OTSA may not include more water area than land area.
3. OTSAs must be located completely within the current boundaries of the state of
Oklahoma.
4. OTSAs must follow the last legal boundaries established for their former AIR.
5. An OTSA may not completely surround another legal or statistical area at the same level
of the geographic hierarchy.
6. The name for each OTSA is determined by the tribe or tribes (in conjunction with the
Census Bureau) that are responsible for delineating each OTSA, and must be clearly
distinguishable from the name of any other OTSA. The Census Bureau will revise any
name submitted for an OTSA if the name does not reflect one or more of the following
conditions:
a. The tribe or tribes associated with the former AIR represented by the OTSA;
b. Tribes that have historically resided within the area of the OTSA;
c. Tribes that have significant population currently residing within the OTSA;
and/or
d. The name(s) of the tribe(s) commonly associated with the area encompassed
by the OTSA.
3.2 Guidelines for delineating OTSAs are:
1. To the extent possible, OTSA boundaries identified for the 2010 Census should be the
same as those delineated for Census 2000.
2. Tribes should strive to eliminate overlapping OTSA boundaries that resulted in the
Census 2000 joint use area OTSAs.
3. Tribes may delineate tribal subdivisions within their own OTSAs.
10

4. Tribes may delineate CDPs representing unincorporated communities located within their
own OTSAs.
3.3 Guidelines for delineating tribal subdivisions within OTSAs are:
1. OTSA tribal subdivisions should represent units of self-government or administration
within an AIR or ORTL for a federally recognized tribe.
2. OTSA tribal subdivisions are intended to completely cover all of an OTSA.
3. The name of each tribal subdivision must reflect the name cited in recent tribal legal
documentation and/or used by the tribal government for administrative purposes.
4. If an OTSA consists of multiple, noncontiguous parts, the tribal subdivisions within them
will be noncontiguous.

3.4 The census designated place criteria are:
1. CDPs cannot be coextensive with an entire OTSA, AIR, or any other AIA.
2. CDPs may extend off OTSAs.
3. A CDP may not have the same name as an adjacent or nearby incorporated place.
4. A CDP may be located in more than one county but must not cross state boundaries.
5. A CDP may not be located, either partially or entirely, within an incorporated place or
another CDP.
3.5 Guidelines for delineating census designated places are:
1. A CDP constitutes a single, closely settled center of population that is named. To the
extent possible, individual unincorporated communities should be identified as separate
CDPs.
2. A CDP is defined to provide data for a single named locality, therefore the Census
Bureau does not encourage delineating CDPs that comprise a combination of places or
are identified by hyphenated names. For example, CDPs such as Poplar-Cotton Center
and Downieville-Lawson-Dumont are no longer acceptable. Prior to Census 2000
communities were sometimes combined as a single CDP in order to comply with the
Census Bureau minimum population requirements. The Census Bureau’s elimination of
population threshold criteria has made such combinations unnecessary.
3. Multiple communities may only be combined to form a single CDP when the identities of
these communities have become so intertwined that the communities are commonly
perceived and referenced as a single place.
4. Multiple communities also may be defined as a single CDP when there is no
distinguishable or suitable feature in the landscape that can be used as a boundary
between the communities, even if the two communities still have separate identities.
5. There is no minimum population or housing unit thresholds for defining CDPs; however,
a CDP must contain some population or housing units or both. Participants submitting
boundaries for places with less than ten housing units may be asked to provide additional
information attesting to the existence of the CDP.
6. CDP boundaries should follow the features, outlined in section 2.5. CDP boundaries may
follow other nonvisible features in instances where reliance upon visible features will
result in over bounding of the CDP and the intent is to include housing units on both

11

sides of a road or street feature. Such nonvisible lines might include parcel boundaries
and public land survey system lines; national, state, or local park boundaries.
7. The CDP name should be one that is recognized and used in daily communication by the
residents of the community.
8. A CDP should have population during at least one entire season of the year, and have a
higher housing unit and population density than surrounding areas.
If you need to define a CDP that is outside of your OTSA boundary, please contact the
Kansas City RCC. Both population and housing unit data can be found by accessing
American FactFinder on the Census Bureau’s internet website. Directions for obtaining this
data can be found in Appendix B.

4. Procedures
4.1 Review of Statistical Areas
The Census Bureau suggests the following procedures for reviewing and delineating OTSAs,
tribal subdivisions within OTSAs and CDPs.
1. Compare your source materials with the Census Bureau’s maps.
2. If you are satisfied with the OTSA name and how the OTSA boundary is currently
portrayed on the Census Bureau’s maps and you do not wish to update or delineate any
tribal subdivisions within your OTSAs nor do you want to delineate or revise any CDPs,
fill out and sign the form attached to the cover letter that came with your materials
indicating “no change.” Return the form to the RCC using the postage paid envelope
provided.
3. If you believe the OTSA boundary or name needs to be changed or corrected, contact the
Kansas City RCC to discuss your recommended change.
4.2 Annotation of maps:
1. If you need to update or delineate new OTSAs, tribal subdivisions on OTSAs or CDPs,
use a pencil with purple lead to plot revised OTSA and OTSA tribal subdivision
boundaries and a pencil with red lead to plot CDP boundaries on the Census Bureau’s
map.
a. Please do not add street or other features unless you are adding a feature that
forms the boundary of your OTSA tribal subdivision or CDP. The Census
Bureau cannot accept new road features at this time. If you must add a road
or other feature in order to delineate a boundary, please use a black lead pencil
to add and label this feature, then use the purple or red pencil to highlight the
feature as a boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your boundary using that
feature, please draw your boundary (using the purple or red pencil) following
the problematic feature and contact the Kansas City RCC to describe the
location and nature of the problem.

12

c. Please remember to adjust your OTSA tribal subdivision or CDP boundary to
follow the acceptable features described under the “Acceptable Boundary
Features” section.
4. Add any new features first in black and plot your tribal subdivision and/or CDP
boundaries adjacent to the black lead pencil line.
5. Review the name of the Census 2000 OTSA, tribal subdivision, or CDP. If the name is
still appropriate for the OTSA, make no annotation. If the name requires revision, cross
out the old name and clearly label the new name in purple (for tribal subdivisions) or red
(for CDPs) within the boundary of the OTSA. The Census Bureau will evaluate the
submitted name of each OTSA to ensure that the name is clearly distinguishable from the
name of any other OTSA.
Example

Figure 3: In this example, a new CDP has been delineated on an existing OTSA.
4.3 Transmitting completed submissions and Census Bureau review
13

Please return all maps to the RCC in the same tube/box/envelope you received it in and be
sure to use the mailing label provided. The Census Bureau RCC geographic staff will verify
that the submitted OTSAs are complete, meet all criteria and other requirements and, where
the criteria have not been met, a valid justification is provided.
The Census Bureau will provide feedback to the participant on their submission, and if
necessary provide additional guidance on the criteria and guidelines usage. The Census
Bureau will contact your tribe with any questions or concerns regarding the submission. The
Census Bureau reserves the right to modify, create, or reject any boundary or attribute as
needed to meet the final program criteria and guidelines, or to maintain geographic
relationships before the tabulation geography is finalized for the 2010 Census.
4.4 Verification
If you return your submissions within 120 days, the Census Bureau will provide you with a
new map which your tribe can use to verify that the Census Bureau staff inserted the
boundary of the OTSA correctly. The verification map will be provided in late 2009. At that
time it would be possible for tribes to make minor boundary changes or add features that still
may be missing from our maps.

14

OMB No. 0607-0795: Approval Expires 03/31/09

Appendix A – Oklahoma tribal statistical areas eligible for delineation
Tribe Name

Area Name

Census
Area
Code

Census
2000
Population

Census
2000
Housing
Units

2010 Census Areas
Eligible for
Delineation

Regional
Census
Center

24,684

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City

6,897

OTSA Tribal Sub.,
CDP

Kansas
City

Seneca-Cayuga Tribe

Seneca-Cayuga OTSA

5835

3,997

2,874

Otoe-Missouria Tribe of Indians

Otoe-Missouria OTSA

5760

778

323

Ottawa Tribe

Ottawa OTSA

5770

6,204

2,764

Pawnee Nation

Pawnee OTSA

5780

16,509

7,407

Peoria Tribe of Indians

Peoria OTSA

5795

4,840

2,051

Ponca Tribe of Indians

Ponca OTSA

5800

2,284

904

Quapaw Tribe of Indians

Quapaw OTSA

5810

7,455

3,119

Seminole Nation

Seminole OTSA

5830

22,792

10,255

Modoc Tribe

Modoc OTSA

5740

228

79

Tonkawa Tribe of Indians

Tonkawa OTSA

5860

4,119

1,786

Wyandotte Nation

5890

1,678

741

Apache Tribe

Wyandotte OTSA
Kiowa-Comanche-Apache-Fort Sill
Apache OTSA

5720

193,260

81,174

Sac & Fox Nation, Oklahoma

Sac and Fox OTSA

5820

55,690

Wichita and Affiliated Tribes
(Wichita, Keechi, Waco &
Tawakonie)

Caddo-Wichita-Delaware OTSA

5540

14,638

Fort Sill Apache Tribe

Kiowa-Comanche-Apache-Fort Sill
Apache OTSA

5720

193,260

81,174

Delaware Nation

Caddo-Wichita-Delaware OTSA

5540

14,638

6,897

Miami Tribe

Miami OTSA

5730

271

103

Cherokee Nation

Cherokee OTSA

5550

462,327

204,270

Cheyenne and Arapahoe Tribes

Cheyenne-Arapaho OTSA

5560

157,869

66,836

Chickasaw Nation

Chickasaw OTSA

5580

277,416

127,634

Choctaw Nation
Absentee-Shawnee Tribe of
Indians

Choctaw OTSA
Citizen Potawatomi NationAbsentee Shawnee OTSA
Kiowa-Comanche-Apache-Fort Sill
Apache OTSA

5590

224,472

101,877

5600

106,624

41,192

5720

193,260

81,174

Comanche Nation
Caddo Nation

5540

14,638

6,897

5600

106,624

41,192

Kiowa Indian Tribe

Caddo-Wichita-Delaware OTSA
Citizen Potawatomi NationAbsentee Shawnee OTSA
Kiowa-Comanche-Apache-Fort Sill
Apache OTSA

5720

193,260

81,174

Kickapoo Tribe of Oklahoma

Kickapoo OTSA

5700

18,544

7,130

Kaw Nation

Kaw OTSA

5690

6,123

2,759

Iowa Tribe of Oklahoma

Iowa OTSA

5670

6,148

2,536

Eastern Shawnee Tribe

Eastern Shawnee OTSA

5640

661

278

Muscogee (Creek) Nation

Creek OTSA

5620

704,565

306,727

Citizen Potawatomi Nation

OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP
OTSA Tribal Sub.,
CDP

Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City
Kansas
City

2

OMB No. 0607-0795: Approval Expires 03/31/09

Appendix B – Procedures for accessing population and housing unit data
from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

2

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the first
data set listed which is “Census 2000 Summary File 1.” You may want to scroll through the
other data sets to see what other information is available for your future reference.

3

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example we will access tribal block group data but you can also
access data for reservations, off-reservation trust lands, tracts, blocks and many other
geographic areas.

4

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1” that
you are looking for. Remember that you may select multiple data types.

6. After clicking “Show Result” you will now see the data you have requested.

5

Appendix C - Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail: charlotte.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

6

2010 Census Tribal Statistical Areas Program

Guidelines for Delineating
Alaska Native Village Statistical Areas

Version 1
January 2008

1. Introduction................................................................................................................... 3
2. Background on ANVSAs.............................................................................................. 5
2.1 Purpose of an ANVSAs........................................................................................... 5
2.2 Villages Eligible to Delineate ANVSAs ................................................................. 6
2.3 Schedule ................................................................................................................... 7
2.4 Program Materials.................................................................................................. 7
2.5 Important Information on Features...................................................................... 8
2.5.1 Acceptable features for use as ANVSA boundaries .......................................... 8
2.5.2 Boundary Feature Updates............................................................................... 10
2.6 Feature Extension Criteria................................................................................... 10
3. Criteria......................................................................................................................... 11
3.1 All Alaska Native Village statistical areas must follow these criteria:............. 11
3.2 All Alaska Native Village statistical areas should follow these guidelines: ..... 11
4. Procedures ................................................................................................................... 13
4.1 Annotation of Maps .............................................................................................. 13
4.1.1 Suggested procedures for reviewing and revising an existing ANVSA: ........ 13
4.1.2 Suggested procedures for delineating a new ANVSA:.................................... 13
4.2 Transmitting completed ANVSA submissions and Census Bureau review .... 14
4.3 Verification ............................................................................................................ 15
Appendix A – Alaska Native statistical areas eligible for delineation........................ 16
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder...................................................................................................... 28
Appendix C - Regional Census Center’s Contact Information .................................. 33

2

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people
and the economy. The U.S. Constitution mandates that a census be taken every 10 years
in order to reapportion the House of Representatives. The data gathered by the decennial
census and other Census Bureau programs are used for several other purposes, including
the allocation and distribution of funds to state, local and tribal governments. Census
information shapes important policy decisions that in turn shape the nation’s social and
economic conditions. While best known for the decennial census, the Census Bureau
conducts numerous surveys and censuses that measure changing individual and
household demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need.
Many tribal communities use census information to attract new business and plan for
growth. In fact, many tribes and tribal organizations use census data to plan new
facilities and programs for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has developed the Tribal
Statistical Areas Program (TSAP) to collect updates to the inventory and boundaries of
American Indian and Alaska Native statistical geographic areas. Participation in the
TSAP is voluntary; however, if your village chooses not to participate, the Census
Bureau may update the boundary of an existing area or delineate a new area in
accordance with published criteria and guidelines. TSAP includes the following
statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts (TCTs) and tribal block groups (TBGs) on American Indian
reservations (AIRs)/ off-reservation trust lands (ORTLs)
census designated places (CDPs)

The Census Bureau will tabulate statistical data from the 2010 Census for each of the
entities listed above, and will continue to use these areas to provide data from the
American Community Survey (ACS). Through the coming decade, meaningful statistical
data from the 2010 Census and ACS can provide villages and other data users with a tool
to help make informed decisions and plan for community services. More information
about the background and components of these geographic areas can be found in the
Federal Register notices Vol. 73, No. 221 / Friday, November 14, 2008, page 67470 and
Vol. 73, No. 214 / Tuesday, November 4, 2008, page 65572. These notices can also be
accessed from our TSAP webpage:
http://www.census.gov/geo/www/tsap2010/tsap2010.html.

3

These guidelines contain the criteria and instructions for delineating ANVSAs and cover
the following topics:
ƒ Background on ANVSAs
ƒ Villages eligible to delineate ANVSAs
ƒ Schedule
ƒ Required materials
ƒ ANVSA criteria
ƒ Procedures for annotating maps
ƒ Procedures for transmitting completed submissions
ƒ Census Bureau submission review
ƒ Verification
Tribes wishing to delineate ANVSAs will have the option of using paper maps or Census
Bureau-provided Geographic Information System (GIS) data, tools, shapefiles, and an
ESRI® extension specific to this program. Participants who chose to submit changes
using the digital method must have ArcGIS® 9.2 or 9.3. These guidelines provide
instructions for submitting ANVSAs using paper maps. There are separate
guidelines for use of the ESRI extension to delineate ANVSAs. These are found in
the data disc supplied by the Census Bureau.
The TSAP Extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides
a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management
features of the extension. In addition to the inherent functionality of the ArcGIS
software, the extension’s unique editing tools consist of geographic area assignment, as
well as line editing and polygon split/merge functions. The option of using either the
TSAP extension or the paper maps to submit changes is at the complete discretion of
each tribe as neither is preferred over the other by the Census Bureau. However,
depending on the number anticipated updates and/or their complexity, you might consider
using the TSAP extension which offers you the ability to view population density within
American Indian statistical areas and allow you to more clearly add or remove area or
adjust boundaries.
If you are interested in using a GIS application to submit your boundaries and you have
ArcGIS 9.2 or 9.3 software, but did not receive the ArcGIS extension software or digital
data files along with your materials, please contact the Seattle Regional Census Center
(RCC). You may also contact RCC staff to ask other questions or arrange for training.
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is
used to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical

4

tribal entities for use in tabulating and publishing data from the 2010 Census, the
American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours
per respondent, including time for reviewing instructions, assembling materials,
organizing and reviewing the information, and reporting any needed changes. We
anticipate that an estimated 650 participants will respond. Remaining entities may be
worked by Census Bureau regional staff. For larger areas or areas with many changes,
however, the respondent burden may be 180 hours or longer to complete. Please send
comments regarding this burden estimate or any other aspect of this collection of
information, including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 06070795” as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background on ANVSAs
2.1 Purpose of an ANVSAs
ANVSAs are defined so that the Census Bureau can produce statistical data for each
Alaska Native village (ANV). ANVSAs are statistical geographic entities representing
permanent and/or seasonal residences of Alaska Natives who are members of or receive
governmental services from the defining ANV, and we are located within the region and
vicinity of the ANV’s historic and/or traditional location. ANVSAs are intended to
represent the relatively densely settled portion of each ANV and should include only an
area where Alaska Natives, especially members of the defining ANV, represent a
substantial proportion of the population during at least one season of the year. ANVSAs
should not contain large areas that are primarily unpopulated or that do not include
concentrations of Alaska Natives. An ANVSA should include housing, cultural and
commercial structures. ANVSAs are not necessarily meant to portray traditional lands,
and their depiction on Census Bureau products is not intended to convey any rights to
land ownership, governmental authority, or jurisdictional status.

5

Boundaries for Alaska Native Village statistical areas (ANVSAs) were first determined
for the 1990 Census of Population and Housing. The 1990 ANVSAs were then reviewed
and if needed, revised prior to Census 2000. As part of the 2010 Census TSAP, Alaska
Native village (ANV) officials will again have the opportunity to review and confirm or
if needed to update the boundaries of their existing ANVSAs or if appropriate delineate
new ANVSAs. If the ANV official declines or defers participation, or does not respond
to the Census Bureau invitation to participate, we will request that the associated village
or group corporation work with us to define the ANVSA. If the village or group
corporation is also unable or unwilling to define the ANVSA, the Census Bureau will
work with the Alaska Native Regional Corporation (ANRC) non-profit association in
whose region the ANV is located (see Appendix A for a list showing ANV to ANRC
relationships). If the Census Bureau receives no reply from any of these entities, the
Census Bureau may delineate or revise the ANVSA, to meet the criteria outlined in this
document. In some cases, an ANV official may elect not to delineate an ANVSA if it
will not provide meaningful, relevant, or reliable statistical data. This would be
appropriate if the member population now resides in other places or has been completely
subsumed by non-member and/or non-Native populations.
The Census Bureau will tabulate statistical data for all people living within the
boundaries of an ANVSA (including non-village members), and also for all village
members regardless of where they reside in the state or nation. Each household
completing the Census questionnaire has the opportunity to identify the race of each
person living in the house. For each person who identifies their race as American Indian
or Alaska Native, they can then list their village as the enrolled or principle tribe. While
data tabulated for a well defined ANVSA will provide a rich source of statistical and
demographic information about an ANV, it is not necessary for an individual to be living
within the boundary of the ANVSA to be counted as part of the village.
2.2 Villages Eligible to Delineate ANVSAs
Any ANV that is recognized by or eligible to receive services from the Bureau of Indian
Affairs (BIA) or that is recognized under the Alaska Native Claims Settlement Act
(ANCSA) as either a Native village or Native group may delineate an ANVSA. BIA
recognition is determined by inclusion of an ANV on the BIA’s list of recognized tribes
or by addenda to the list as published by the BIA. ANVSA recognition is determined by
inclusion on the Bureau of Land Management’s (BLM’s) list of ANCSA recognized
Native villages and Native groups. There are no population requirements for defining an
ANVSA. A list of ANVs that are eligible to delineate ANVSAs has been included in
Appendix A. The following three tribes in Alaska recognized by the BIA would not be
eligible to be represented by ANVSAs because they are not ANVs, are large regional
tribal associations, or have a legally defined American Indian Reservation: Central
Council of the Tlingit and Haida Indian Tribes, Inupiat Community of the Arctic Slope,
and Metlakatla Indian Community Annette Island Reserve. Also, the former Tetlin
TDSA is now an ANVSA and the Kamatak TDSA has been removed.

6

2.3 Schedule
In October 2008, the Census Bureau mailed formal invitation letters to village officials of
each eligible ANV. These guidelines accompany the paper maps required to complete
the work. Participants have 120 calendar days from the date they receive these materials
to review existing boundaries or delineate new ANVSA boundaries and must submit their
revisions or new boundary definitions to the Census Bureau’s Seattle RCC 1 within that
time. In fall 2009, after the Census Bureau has reviewed and incorporated your
delineations into our geographic database, you will receive new maps or digital files so
that you can verify that we have inserted your boundaries correctly. If you have
questions regarding your delineation or submission, assistance will be available from
geographers at the Seattle RCC.
2.4 Program Materials
If a village has a Census 2000 ANVSA delineation, the Seattle RCC is providing:
ƒ A map depicting the Census 2000 ANVSA area boundary with a one-mile
fringe area.
ƒ A map showing a point location of the ANV and a 50 mile radius area around
the point.
ƒ A map of the ANRC in which the ANV is located.
If a village did not have a Census 2000 ANVSA, the Seattle RCC will provide:
ƒ A map showing the latitude and longitude coordinate location of the ANV and
a 50 mile radius around that point.
ƒ A map of the ANRC in which the ANV is located.
The point locations provided on the maps represent each eligible ANV, as determined by
the Census Bureau. Each point location has been verified using the ANRC boundaries,
the USGS Geographic Names Information System (GNIS) point locations, USGS
topographic maps, location information from previous censuses, BLM Core Townships,
ANCSA 14(c) survey plats, location information from the State of Alaska, and Native
allotment boundaries. The latitude and longitude coordinates listed for an ANV provide
the starting point for delineation of that ANVSA. Each ANVSA must primarily include
land immediately surrounding the corresponding point locations, but may include
additional territory according to the other final program criteria and guidelines.
All ANV point location maps and ANRC maps will be a single map sheet. If you had a
Census 2000 ANVSA delineation, the ANVSA area map types you receive will depend
on the size and complexity of your ANVSA. An ANVSA that is smaller in land area may
only receive a single map sheet. ANVSAs with a large land area may receive an index
map, a series of parent maps and a number of inset maps. An index map shows the
complete ANVSA with gridlines defining specific areas shown on the parent map. A
parent map shows a detailed version of a single grid box from the index map and an inset
map shows finer details of areas within the parent map where the feature network is too
dense to clearly represent at the map scale of the parent sheet. You can think of the inset
1

See Attachment E for contact information for the Regional Census Centers

7

map as a “blow up” of a specific area. ANRC maps are provided as a reference map.
ANVSA updates and revisions should be annotated on the ANVSA parent or inset maps.

Figure 1: Example of Index, Parent and Inset maps

Figure 2: This image shows all the boundaries that may appear on your ANVSA maps
and how they are symbolized.
If you would like to use Census 2000 data, such as total population or housing units, in
the delineation of your ANVSA, you may contact the Seattle RCC or go to American
FactFinder on the Census Bureau website (http://www.census.gov/). Detailed
instructions for using American FactFinder can be found in Appendix D.
2.5 Important Information on Features
2.5.1 Acceptable features for use as ANVSA boundaries

8

ANVSA boundaries should follow specified legal or administrative boundaries that do
not change greatly over time. Examples of these legal or administrative census areas
boundaries are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

American Indian reservation
Off-reservation trust land
Tribal subdivision
County
County subdivision
Boroughs
Incorporated places
Alaska Native Regional Corporations

Statistical area boundaries may also follow permanent, visible features, such as roads,
perennial streams, railroads, and high-tension power lines. Permanent visible features
should be easily locatable in the field by Census Bureau staff without ambiguity. The
acceptable visible boundary features are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (main)
carline, streetcar track, monorail, other mass transit rail
interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county
highway, secondary and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
fencelines

Natural topographic features include the crests of well-defined mountain ridges; the rims
or bases of sharply defined escarpments, cliffs, or bluffs; the position of dry ravines or
arroyos; as well as other features as long as the features are not also mimicked by another
visible feature, have no housing in the vicinity, and are easily located on the ground.

9

Data user and Census Bureau experience has shown that some features make better
boundaries than others, and the same type of feature can make an excellent boundary in
one place and a poor one in another. Rivers, major canals, lakes, and other bodies of
water often make good statistical area boundaries because they generally limit access
from one area to another and rarely change relative location. Other features that limit
access between areas, such as interstate and other major highways, railroad tracks, and
the ridges of mountain ranges, also make good statistical area boundaries. In some
instances, however, such a feature unifies a community, for example, a lake forming the
core of a recreational housing development or a through street forming the spine of a
subdivision. In these circumstances, the statistical area boundary should include the
entire area of the lake or both sides of a unifying street to better encompass similar
community patterns.
In general, when delineating boundaries in bodies of water represented as polygons and
having area (lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow
a line bisecting the water body rather than following a shoreline. If possible, use an
existing line in water (for example, a city limit in the middle of a river) rather than adding
a new line.
Officials delineating ANVSAs may only add non-visible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and
ridgelines are not available and they aid in an ANVSA meeting other specified
delineation criteria and/or guidelines.
2.5.2 Boundary Feature Updates
The Census Bureau has spent the last six years enhancing the spatial accuracy of the
roads in our database system. The local files used during this project were required to
have an overall average accuracy of 7.6 meters while some files had better accuracy.
Although much of the street network is vastly improved, as you work with our maps you
may notice that in some counties the street and boundary features look distorted. A line
that should be straight may have a noticeable kink or pointed shape. The Census Bureau
is working to correct these problems. If you can not correctly delineate the boundary for
an entity you are updating because the feature you need to follow is incorrectly located,
mislabeled or distorted in the Census Bureau’s file, we request that you fix that feature.
In addition, we request that you report the problem area to the Seattle RCC by sending
information describing the incorrect feature and the specific entity boundary affected.
What is critical for the success of the 2010 Census data tabulation is the location of roads
relative to the tabulation entity boundary such as a city, county or ANVSA. As long as
the road is within the correct entity, the population and housing will be properly reported.
If roads are missing from our map, we ask that you add each missing road and provide
the name of the road on your ANVSA map.
2.6 Feature Extension Criteria

10

If you want to use an existing feature that doesn’t form a closed polygon, you may add a
short line to connect the features and close the polygon. The Census Bureau refers to
these lines as feature extensions and several requirements pertain. To avoid creating
ambiguous Census block boundaries, we require that feature extensions:
ƒ Are no longer than 300 feet;
ƒ Are straight lines from the end of a road and intersecting a non-road feature
(These include all hydrographic features, pipelines, powerlines, and railroads.);
ƒ Do not intersect a cul-de-sac.

3. Criteria
Participants defining American Indian and Alaska Native areas must follow a standard set
of criteria that support a shared purpose of providing a meaningful and relevant
geographic framework for tabulating data for the Census. It is the responsibility of the
Census Bureau to ensure that geographic entity criteria can achieve this goal and that the
final criteria for geographic entities are met. While aware that there are secondary uses
of geographic entities and the data tabulated for them, the Census Bureau will not modify
their boundaries or attributes specifically to meet these secondary uses, including those of
other government agencies. If a change is made to a geographic entity to meet one
specific purpose, it may be detrimental for other programs that also use these entities.
The Census Bureau will use the following criteria and guidelines to help ensure that the
ANVSAs delineated for the 2010 Census support the intended purpose of the program,
provide useful and meaningful data for the village they represent, and enhance the ability
for data users to make more meaningful comparisons between data.
Criteria are those rules and conditions that must be met when defining an ANVSA entity;
guidelines are procedures and measures suggested by the Census Bureau to enhance the
utility of ANVSAs for presentation and analysis of statistical data.
3.1 All Alaska Native Village statistical areas must follow these criteria:
1. ANVSAs delineated for the 2010 Census shall not overlap.
2. An ANVSA shall not completely surround the location of another ANV.
3. All portions of an ANVSA must be located within fifty miles of the ANV’s point
location.
4. An ANVSA shall not include more water area than land area. Large expanses of
water area should be included only to maintain contiguity, to provide a generalized
version of the shoreline, or if the water area is completely surrounded by land area
included in the ANVSA.
5. The name for an ANV must match the name corresponding to the ANV point location
in Appendix A. Name changes will only be considered if submitted in writing and
signed by the highest elected official of the ANV.
3.2 All Alaska Native Village statistical areas should follow these guidelines:
1. The population within an ANVSA should be majority Alaska Native and of that
population, the majority should be members of the population served by the
11

2. ANVSAs should be located in areas of historical and traditional significance and
include land that is locally recognized as being associated with the village or group.
In addition each ANVSA should include land area that contains structures such as
tribal headquarters, meeting areas, cultural or spiritual landmarks, service centers
and/or tribally owned stores.
3. An ANVSA should not extend beyond the regional boundary of the ANRC in which
the ANV is located.
4. An ANVSA should not exceed 325 square miles in area. Based on review of
ANVSA boundaries from previous censuses as well as other information about ANVs
and ANVSAs, the Census Bureau suggests this size as sufficient to encompass the
Alaska Native population and housing associated with each respective ANV, but not
so extensive that large amounts of non-Native population and housing are included.
5. An ANVSA should not contain large areas without housing or population.
Specifically, an ANVSA should have a housing unit density of at least three housing
units per square mile.
6. An ANVSA should be contiguous; that is, an ANVSA should form a single area with
all territory located within a continuous boundary. This makes identification of the
extent of the ANVSA easier for residents and data users, and also provides for a
clearer representation of the ANVSA’s boundaries on maps. An ANVSA, however,
may be defined with multiple noncontiguous pieces if doing so helps avoid inclusion
of population and housing not associated with the ANV.
7. An ANVSA’s boundary shall follow visible, physical features, such as rivers,
streams, shorelines, roads, trails, and ridgelines.
8. Officials delineating ANVSAs may use nonvisible lines as an ANVSA boundary only
if acceptable boundary features are not available. For example, an ANVSA boundary
may follow the nonvisible, legally defined boundaries of ANRCs, boroughs, or cities
(See section 2.5.1).
9. If the ANVSA boundary follows a governmental unit boundary, the Census Bureau
will adjust the ANVSA boundary to continue to follow that boundary should it
change due to correction, annexation or detachment.
10. When visible features listed in section 2.5.1 are not available for selection as an
ANVSA boundary, the Census Bureau, at its discretion, may approve other
nonstandard and potentially nonvisible features such as the boundaries of local and
state parks and forests, cemeteries other special land-use properties and short straightline extensions of visible features or other lines-of-sight.

12

4. Procedures
4.1 Annotation of Maps
4.1.1 Suggested procedures for reviewing and revising an existing ANVSA:
1. Compare your source materials with the Census Bureau’s maps.
2. If you are satisfied with how the ANVSA boundary is currently portrayed on the
Census Bureau’s maps, fill out and sign the form attached to the cover letter that
came with your materials indicating there is “no change” to the boundary. Return the
form to the RCC using the postage paid envelope provided.
3. If you need to change the ANVSA boundary, cross out the old boundary with an “X”
using a pencil with red lead. Mark the ends of the deletion with red hatch marks (//).
4. Using a pencil with purple lead, plot the revised boundaries on the Census Bureau’s
map.
5. If you must add a road or other feature, please use a black pencil to add and label this
feature. If the feature is also an ANVSA boundary, then use the red lead pencil to
highlight the feature as such.
6. If a feature is incorrectly located, mislabeled or distorted on the Census Bureau’s
maps so that you cannot correctly delineate your ANVSA boundary using that
feature, please draw your boundary (using the purple lead pencil) following the
problematic feature and contact the Seattle RCC to describe the location and nature
of the problem.
7. Remember to adjust your ANVSA boundary to follow the criteria described in
Section 3 as well as the acceptable features described under section 2.5.1.
8. Review the name of the 2000 ANVSA. The name must match the name
corresponding to the ANV point location in Appendix A. If the name is still
appropriate for the ANVSA, make no annotation. If the name requires revision, cross
out the old name and clearly label the new name in purple within the boundary of the
ANVSA. If there is a name change to something other than the name shown in
Appendix A, you must submit a written request signed by the highest elected official
of the ANV.
4.1.2 Suggested procedures for delineating a new ANVSA:
1. If you do not wish to delineate an ANVSA, fill out and sign the form attached to the
cover letter that came with your materials, indicating you do not wish to participate.
2. Compare your source materials with the Census Bureau’s map(s).
3. Using a pencil with red lead, plot the boundary on the Census Bureau’s map(s).
4. If a feature that is not on the census map(s) is required as the boundary of the
ANVSA, use a black lead pencil to add and label the new feature and the red pencil to
highlight the feature as an ANVSA boundary.
5. Ensure that the ANVSA boundary follows the criteria outlined in Section 3 as well as
the acceptable features described in the section 2.5.1.
6. If a feature is incorrectly located, mislabeled or distorted on the Census Bureau’s
maps so that you cannot correctly delineate your ANVSA boundary using that
13

feature, please draw your boundary (using the red lead pencil) following the
problematic feature and contact the Seattle RCC to describe the location and nature
of the problem.
7. Please label the name of your new ANVSA with red pencil within the boundary of
the ANVSA. The name should reflect the name associated with the ANV point
location found in Appendix A. If you wish to use a name that varies from the name
in Appendix A, you must submit a written request signed by the chairperson, chief or
president of the ANV.

Figure 3: This is an example of a new ANVSA delineated based on the provided ANV
point location.
4.2 Transmitting completed ANVSA submissions and Census Bureau review
Please return all maps to the Seattle RCC in the same tube/box/envelope you received it
in and be sure to use the mailing label provided.
The Seattle RCC will provide acknowledgment that it received the ANVSA revisions and
delineations. RCC geographers will review the ANVSA plans and contact the delineating
official if there are any questions or if the delineation does not comply with the program
criteria as described in this document. The Census Bureau reserves the right to modify,
create or reject any boundary or attribute as needed to meet final program criteria and
guidelines, or to maintain geographic relationships before the tabulation geography is
finalized for the 2010 Census.

14

4.3 Verification
If you return your submissions within 120 days of receiving the maps and other materials,
the Census Bureau will provide you with a new map, which you can use to verify that the
Census Bureau staff inserted the boundary of the ANVSA correctly. The verification
map will be provided in late 2009. At that time it would be possible for tribes to make
minor boundary changes to correct any differences from your submission that were not
previously discussed with you.

15

Appendix A – Alaska Native statistical areas eligible for delineation
Tribe Name

Eklutna Native Village
Chilkoot Indian
Association
Chilkat Indian Village
Chignik Lake Village
Native Village of Chignik
Lagoon
Chignik Bay Tribal
Council
Chickaloon Native
Village
Chevak Native Village
Native Village of Chanega
Village of Chefornak
Chalkyitsik Village
Caswell Native
Association, Incorporated
Kian Tree Corporation
Native Village of
Cantwell
Native Village of
Chuathbaluk

Area Name

Census
Area
Code

Regional
Census
Center

Eklutna ANVSA

6450

Seattle

Chilkoot ANVSA

6315

Seattle

Chilkat ANVSA
Chignik Lake
ANVSA
Chignik Lagoon
ANVSA

6310

Seattle

6305

Seattle

6300

Chignik ANVSA
Chickaloon
ANVSA
Chevak ANVSA

Alaska Native
Village Name

Eklutna
(Anchorage)
Chilkoot
(Haines)
Chilkat
(Klukwan)

Alaska Native
Regional
Corporation
Name

Point
Location:
Latitude

Point
Location:
Longitude

Census
2000
Population

Census
2000
Housing
Units

Cook Inlet

61.4606405

-149.3612981

394

141

Sealaska

59.2239572

-135.4459756

338

186

Sealaska

59.399702

-135.8964089

139

85

Bristol Bay

56.2496142

-158.7521999

145

50

Seattle

Chignik Lake
Chignik
Lagoon

Bristol Bay

56.3084393

-158.5302391

103

68

6295

Seattle

Chignik

Bristol Bay

56.3037403

-158.4129046

79

80

6290
6285

Seattle
Seattle

Cook Inlet
Calista

61.8001927
61.5285278

-148.4916137
-165.5807499

16,918
765

6,393
190

6280

Seattle

Chickaloon
Chevak
Chenega
(Chenega Bay)

Chugach

60.0663707

-148.012387

86

27

Chenega ANVSA
Chefornak
ANVSA
Chalkyitsik
ANVSA

6275

Seattle

Chefornak

Calista

60.1538056

-164.2723052

394

82

6265

Seattle

Chalkyitsik

Doyon

66.6534092

-143.7285785

83

62

Caswell

6260

Seattle

Cook Inlet

62.0046861

-149.9478739

0

0

Canyon Village
Cantwell
ANVSA
Chuathbaluk
ANVSA

6257

Seattle

Caswell
Canyon
Village

Doyon

67.15484

-142.0878206

0

0

6255

Seattle

Cantwell

Ahtna

63.3920921

-148.9104556

222

177

6335

Seattle

Chuathbaluk

Calista

61.5774142

-159.2481461

119

43

16

Organized Village of
Saxman

Saxman ANVSA
Stevens Village
ANVSA

7420

Seattle

7520

Shageluk Native Village

Stebbins ANVSA
South Naknek
ANVSA
Solomon
ANVSA
Sleetmute
ANVSA
Skagway
Sitka
Shungnak
ANVSA
Shishmaref
ANVSA
Shaktoolik
ANVSA
Shageluk
ANVSA

Seldovia Village Tribe
Native Village of Port
Graham
Native Village of
Scammon Bay
Native Village of
Tanacross
Native Village of
Savoonga

Seldovia ANVSA
Port Graham
ANVSA
Scammon Bay
ANVSA
Tanacross
ANVSA
Savoonga
ANVSA

Qagan Tayagungin Tribe
of Sand Point Village

Sand Point
ANVSA

Native Village of Stevens
Stebbins Community
Association
South Naknek Village
Village of Solomon
Village of Sleetmute
Skagway Village
Sitka Tribe of Alaska
Native Village of
Shungnak
Native Village of
Shishmaref
Native Village of
Shaktoolik

Sealaska

55.3220786

-131.6002963

431

146

Seattle

Saxman
Stevens
Village

Doyon

66.0054606

-149.1038725

87

43

7510

Seattle

Stebbins

Bering Straits

63.5208272

-162.2819964

547

134

7505

Seattle

South Naknek

Bristol Bay

58.7123478

-157.0026423

137

137

7500

Seattle

Solomon

Bering Straits

64.5596601

-164.4487838

4

4

7495
7485
7475

Seattle
Seattle
Seattle

Sleetmute
Skagway
Sitka

Calista
Sealaska
Sealaska

61.6962336
59.4583395
57.0543416

-157.1689024
-135.3119224
-135.3425771

100
0
0

51
0
0

7470

Seattle

Shungnak

NANA

66.887306

-157.1426196

256

64

7465

Seattle

Shishmaref

Bering Straits

66.2564123

-166.0666291

562

148

7450

Seattle

Shaktoolik

Bering Straits

64.3494735

-161.1845472

230

66

7440

Seattle

Doyon

62.6555754

-159.5226837

129

52

7435

Seattle

Shageluk
Seldovia
(Seldovia
Village)

Cook Inlet

59.4389826

-151.7122604

430

391

7265

Seattle

Port Graham

Chugach

59.3481439

-151.83529

171

82

7425

Seattle

Scammon Bay

Calista

61.8417

-165.5818139

465

114

7535

Seattle

Tanacross

Doyon

63.3761711

-143.3565211

140

53

7415

Seattle

Bering Straits

63.6959165

-170.4639566

643

160

7410

Seattle

Savoonga
Sand Point
(Qagun
Tayagungin
Tribe)

Aleut

55.3458213

-160.4905342

952

282

17

Village of Salamatoff
Pribilof Islands Aleut
Communities of St. Paul
& St. George (St. Paul)
Native Village of Saint
Michael
Pribilof Islands Aleut
Communities of St. Paul
& St. George (St. George)
Iqurmuit Traditional
Council
Native Village of Ruby
Chinik Eskimo
Community
Native Village of
Diomede
Village of Iliamna
Igiugig Village
Hydaburg Cooperative
Association
Huslia Village
Hughes Village
Native Village of Hooper
Bay
Hoonah Indian
Association
Holy Cross Village
Healy Lake Village
Native Village of
Hamilton
Gulkana Village
Native Village of
Kwinhagak

Salamatof
ANVSA

7400

Seattle

Salamatof

Cook Inlet

60.615375

-151.3194369

954

282

57.127394

-170.2727324

532

214

St. Paul ANVSA
St. Michael
ANVSA

7390

Seattle

Saint Paul

Aleut

7375

Seattle

Saint Michael

Bering Straits

63.4783536

-162.038351

368

93

St. George
ANVSA

7340

Seattle

Aleut

56.6044126

-169.5519435

152

67

Russian Mission
ANVSA
Ruby ANVSA

7315
7310

Seattle
Seattle

Calista
Doyon

61.7853706
64.7370784

-161.3286859
-155.472947

296
188

81
107

Golovin ANVSA

6540

Seattle

Bering Straits

64.5443153

-163.0287302

144

54

Inalik ANVSA
Iliamna ANVSA
Igiugig ANVSA
Hydaburg
ANVSA
Huslia ANVSA
Hughes ANVSA
Hooper Bay
ANVSA

6630
6625
6620

Seattle
Seattle
Seattle

Saint George
Iqurmuit
(Russian
Mission)
Ruby
Chinik
(Golovin)
Inalik
(Diomede)
Iliamna
Igiugig

Bering Straits
Bristol Bay
Bristol Bay

65.7546776
59.7567965
59.3266025

-168.937034
-154.9110837
-155.8927205

146
102
53

47
58
20

6615
6610
6605

Seattle
Seattle
Seattle

Hydaburg
Huslia
Hughes

Sealaska
Doyon
Doyon

55.2066677
65.7026276
66.0455433

-132.8201169
-156.3892174
-154.2557494

382
293
78

154
111
39

6595

Seattle

Hooper Bay

Calista

61.5293908

-166.0977978

1,014

239

6590

Seattle

Hoonah

Sealaska

58.1099855

-135.4345509

860

348

6585

Seattle

Holy Cross

Doyon

62.1985193

-159.7737538

227

81

6575

Seattle

Healy Lake

Doyon

63.9872308

-144.6998325

37

21

6570
6560

Seattle
Seattle

Calista
Ahtna

62.8896468
62.2633915

-163.8597707
-145.3655587

0
164

0
74

6845

Seattle

Hamilton
Gulkana
Kwinhagak
(Quinhagak)

Calista

59.7524618

-161.9054612

555

153

Hoonah ANVSA
Holy Cross
ANVSA
Healy Lake
ANVSA
Hamilton
ANVSA
Gulkana ANVSA
Kwinhagak
ANVSA

18

Native Village of
Goodnews Bay
Organized Village of
Kake
Gold Creek-Susitna
Association, Incorporated
Native Village of
Georgetown

Goodnews Bay
ANVSA

6545

Seattle

Goodnews
Bay

Calista

59.1233725

-161.5863711

230

87

Kake ANVSA

6670

Seattle

Kake

Sealaska

56.9774822

-133.9450634

710

288

Gold Creek
Georgetown
ANVSA

6537

Seattle

Gold Creek

Cook Inlet

62.75667

-149.69389

0

0

6535

Seattle

Georgetown

Calista

61.8979091

-157.6727421

3

4

Native Village of Gambell
Galena Village
Native Village of Gakona
Native Village of Fort
Yukon
Native Village of False
Pass

Gambell ANVSA
Galena ANVSA
Gakona ANVSA
Fort Yukon
ANVSA
False Pass
ANVSA

6530
6525
6520

Seattle
Seattle
Seattle

Gambell
Galena
Gakona

Bering Straits
Doyon
Ahtna

63.7621144
64.7426745
62.3004045

-171.702207
-156.8851662
-145.3119166

649
675
84

187
259
39

6515

Seattle

Fort Yukon

Doyon

66.5626991

-145.2496728

595

317

6500

Seattle

Aleut

54.8519613

-163.412128

64

40

Native Village of Eyak

Eyak ANVSA
Evansville
ANVSA
Emmonak
ANVSA
Elim
Ekwok ANVSA
Grayling
ANVSA
Kipnuk ANVSA
Kwigillingok
ANVSA
Kwethluk
ANVSA
Koyukuk
ANVSA
Koyuk ANVSA
Kotzebue
ANVSA
Kotlik ANVSA

6495

Seattle

Chugach

60.526294

-145.6351157

168

65

6490

Seattle

False Pass
Eyak
(Cordova)
Evansville
(Bettles)

Doyon

66.927233

-151.5099561

71

66

6480
6470
6460

Seattle
Seattle
Seattle

Emmonak
Elim
Ekwok

Calista
Bering Straits
Bristol Bay

62.7786549
64.616495
59.351935

-164.5453798
-162.2575681
-157.4865969

767
0
130

218
0
56

6550
6750

Seattle
Seattle

Grayling
Kipnuk

Doyon
Calista

62.9061128
59.9342781

-160.0688723
-164.0375868

194
644

63
154

6840

Seattle

Kwigillingok

Calista

59.8693714

-163.1647332

338

78

6835

Seattle

Kwethluk

Calista

60.8101309

-161.4381234

713

199

6830
6825

Seattle
Seattle

Koyukuk
Koyuk

Doyon
Bering Straits

64.8818268
64.9311897

-157.7031427
-161.1628455

101
297

55
95

6820
6815

Seattle
Seattle

Kotzebue
Kotlik

NANA
Calista

66.8988065
63.032498

-162.5874263
-163.5499514

3,082
591

1,007
139

Evansville Village
Emmonak Village
Native Village of Elim
Ekwok Village
Organized Village of
Grayling
Native Village of Kipnuk
Native Village of
Kwigillingok
Organized Village of
Kwethluk
Koyukuk Native Village
Native Village of Koyuk
Native Village of
Kotzebue
Village of Kotlik

19

Native Village of
Kongiganak
Kokhanok Village

Sun'aq Tribe of Kodiak
Native Village of Kobuk

Olsonville, Incorporated
Knik Tribe
Ivanoff Bay Village
Native Village of Kivalina
Kaguyak Village
King Salmon Tribe
Agdaagux Tribe of King
Cove
Native Village of Kiana
Ketchikan Indian
Corporation

Kongiganak
ANVSA
Kokhanok
ANVSA

6810

Seattle

Kongiganak

Calista

59.9532731

-162.8951327

359

90

6800

Seattle

Bristol Bay

59.4374439

-154.7681714

174

59

6795
6790

Seattle
Seattle

Koniag
NANA

57.8008507
66.9252171

-152.3885025
-156.8887759

0
109

0
45

6787
6785

Seattle
Seattle

Kokhanok
Kodiak
(Shoonaq'
Tribe)
Kobuk
Kanakanak
(Knugank /
Olsonville)
Knik

Bristol Bay
Cook Inlet

59.0046325
61.4946614

-158.5372637
-149.6821811

0
31,969

0
16,333

6650
6755
6660
6740

Seattle
Seattle
Seattle
Seattle

Bristol Bay
NANA
Koniag
Bristol Bay

55.903292
67.7295203
56.868931
58.7090295

-159.4836055
-164.5386059
-153.7955164
-156.7311507

22
377
0
0

12
80
0
0

King Cove
ANVSA
Kiana ANVSA

6735
6730

Seattle
Seattle

Ivanof Bay
Kivalina
Kaguyak
King Salmon
King Cove
(Agdaagux
Tribe)
Kiana

Aleut
NANA

55.0629282
66.9716847

-162.3028896
-160.4309426

792
388

207
133

Ketchikan

6725

Seattle

Sealaska

55.3420894

-131.6444895

0

0

6720

Seattle

Ketchikan
Kenai
(Kenaitze
Indian Tribe)

Cook Inlet

60.5521284

-151.2613885

29,320

14,124

6710

Seattle

Kasigluk

Calista

60.887316

-162.5138906

543

110

Kasaan
Karluk
Kanatak
Kaltag
Kalskag
(Upper
Kalskag)

Sealaska
Koniag
Koniag
Doyon

55.5418886
57.5571678
57.5727792
64.3259494

-132.4017381
-154.4393132
-156.0431783
-158.7301853

39
27
10,252
230

39
24
3,997
78

Calista

61.5400011

-160.3214855

230

66

Kodiak
(Shoonaq' Tribe)
Kobuk ANVSA
Kanakanak
(Knugank /
Olsonville)
Knik ANVSA
Ivanof Bay
ANVSA
Kivalina ANVSA
Kaguyak
King Salmon

Kenaitze
ANVSA
Kasigluk
ANVSA

Kenaitze Indian Tribe
Kasigluk Traditional
Elders Council
Organized Village of
Kasaan
Native Village of Karluk
Native Village of Kanatak
Village of Kaltag

Kasaan ANVSA
Karluk ANVSA
Kanatak
Kaltag ANVSA

6705
6700
6695
6690

Seattle
Seattle
Seattle
Seattle

Village of Kalskag

Kalskag ANVSA

6685

Seattle

20

Kaktovik Village
Egegik Village
Klawock Cooperative
Association
Yupiit of Andreafski
Native Village of Ekuk
Village of Bill Moore's
Slough
Orutsararmuit Native
Village
Native Village of
Belkofski
Beaver Village
Native Village of Barrow
Inupiat Traditional
Government
Ayakulik, Incorporated
Atqasuk Village
Village of Atmautluak
Native Village of Atka
Native Village of Venetie
Tribal Government
(Arctic Village)
Anvik Village
Native Village of Brevig
Mission
Angoon Community
Association
Native Village of
Buckland
Village of Anaktuvuk
Pass
Native Village of Ambler

Kaktovik
ANVSA
Egegik ANVSA
Klawock
ANVSA
Andreafsky
ANVSA
Ekuk ANVSA
Bill Moore's
ANVSA
Bethel ANVSA
Belkofski
ANVSA
Beaver ANVSA

Barrow ANVSA
Ayakulik
Atqasuk ANVSA
Atmautluak
ANVSA
Atka ANVSA
Arctic Village
ANVSA
Anvik ANVSA
Brevig Mission
ANVSA
Angoon ANVSA
Buckland
ANVSA
Anaktuvuk Pass
ANVSA
Ambler ANVSA

6680
6445

Seattle
Seattle

Kaktovik
Egegik

Arctic Slope
Bristol Bay

70.1324111
58.2173441

-143.6113046
-157.3535623

293
116

95
286

6765

Seattle

Sealaska

6095
6455

Seattle
Seattle

Klawock
Andreafsky
(St. Mary's)
Ekuk

55.552629

-133.0947795

854

368

Calista
Bristol Bay

62.0476191
58.8035099

-163.1933921
-158.5533853

127
2

59
73

6225

Seattle

Calista

62.9448676

-163.7766666

0

0

Seattle

Bill Moore's
Orutsararmuit
(Bethel)

6205

Calista

60.7968375

-161.7730197

5,471

1,990

6195
6190

Seattle
Seattle

Belkofski
Beaver

Aleut
Doyon

55.0865176
66.3628034

-162.0423148
-147.4025507

0
84

4
54

6175
6170
6165

Seattle
Seattle
Seattle

Barrow
Ayakulik
Atqasuk

Arctic Slope
Koniag
Arctic Slope

71.2909063
57.1949295
70.4736266

-156.7811223
-154.5072442
-157.4135247

4,581
0
228

1,620
0
60

6160
6150

Seattle
Seattle

Atmautluak
Atka

Calista
Aleut

60.8590583
52.2105764

-162.2794732
-174.2095218

294
92

64
41

6140
6125

Seattle
Seattle

Doyon
Doyon

68.1242576
62.65154

-145.5283348
-160.1965315

152
104

67
49

6240

Seattle

Arctic Village
Anvik
Brevig
Mission

Bering Straits

65.3350407

-166.4885137

276

76

6100

Seattle

Angoon

Sealaska

57.4975419

-134.5823806

572

221

6250

Seattle

NANA

65.976712

-161.1246103

406

89

6080
6075

Seattle
Seattle

Buckland
Anaktuvuk
Pass
Ambler

68.1479512
67.0873951

-151.7285614
-157.8670731

282
309

101
98

Arctic Slope
NANA

21

Allakaket Village
Algaaciq Native Village
Alexander Creek,
Incorporated
Native Village of
Aleknagik
Alatna Village
Village of Alakanuk
Native Village of Akutan
Akiak Native Community
Akiachak Native
Community
Native Village of Akhiok
Native Village of Afognak
Village of Aniak
Cheesh-Na Tribe
Craig Community
Association
Native Village of Eek
Native Village of Eagle
Douglas Indian
Association

Village of Dot Lake
Curyung Tribal Council
Native Village of Deering
Village of Crooked Creek
Native Village of Council

Allakaket
ANVSA
Algaacig
ANVSA

Doyon

66.5596513

-152.6506408

133

68

Calista

62.0534167

-163.1768811

373

127

Seattle

Allakaket
Algaaciq (St.
Mary's)
Alexander
Creek
(Susitna)

Cook Inlet

61.4217936

-150.5999329

0

0

6045
6040

Seattle
Seattle

Aleknagik
Alatna

Bristol Bay
Doyon

59.278885
66.5636177

-158.6188518
-152.756306

221
35

107
17

6035
6030
6025

Seattle
Seattle
Seattle

Alakanuk
Akutan
Akiak

Calista
Aleut
Calista

62.6797024
54.1383602
60.911928

-164.6612268
-165.7808952
-161.2222287

652
713
309

160
38
76

6020
6015
6005
6105

Seattle
Seattle
Seattle
Seattle

Calista
Koniag
Koniag
Calista

60.9026297
56.94556
58.0221236
61.5750236

-161.4276407
-154.17028
-152.7652264
-159.5486861

585
80
0
572

189
34
0
203

6325

Seattle

Akiachak
Akhiok
Afognak
Aniak
Cheesh-Na
(Chistochina)

Ahtna

62.5717828

-144.6541704

75

39

Craig ANVSA
Eek ANVSA

6385
6440

Seattle
Seattle

Sealaska
Calista

55.4870391
60.2170012

-133.1253201
-162.0247336

1,725
280

737
83

Eagle ANVSA
Douglass
ANVSA

6430

Seattle

Doyon

64.7807903

-141.1112818

77

57

6420

Seattle

Sealaska

58.2781154

-134.3992073

5,297

2,372

6415

Seattle

Doyon

63.6502637

-144.0354243

38

25

6405
6400

Seattle
Seattle

Bristol Bay
NANA

59.0487208
66.078021

-158.4669939
-162.7283017

2,466
136

1,000
61

6390
6380

Seattle
Seattle

Craig
Eek
Eagle (Eagle
Village)
Douglas
(Juneau)
Dot Lake
(Dot Lake
Village)
Curyung
(Dillingham)
Deering
Crooked
Creek
Council

Calista
Bering Straits

61.8719565
64.895

-158.1123526
-163.67639

137
0

46
40

Alexander Creek
(Susitna)
Aleknagik
ANVSA
Alatna ANVSA
Alakanuk
ANVSA
Akutan ANVSA
Akiak ANVSA
Akiachak
ANVSA
Akhiok ANVSA
Afognak
Aniak ANVSA
Chistochina
ANVSA

Dot Lake
ANVSA
Dillingham
ANVSA
Deering ANVSA
Crooked Creek
ANVSA
Council ANVSA

6070

Seattle

6065

Seattle

6055

22

Village of Clarks Point
Circle Native Community
Chuloonawick Native
Village
Birch Creek Tribe
Native Village of Chitina
Village of Red Devil
Rampart Village
Native Village of Port
Lions
Native Village of Port
Heiden
Native Village of Selawik
Ugashik Village
Native Village of Kluti
Kaah
Minchumina Natives
Incorporated
Yakutat Tlingit Tribe
Wrangell Cooperative
Association
Native Village of White
Mountain
Native Village of Wales
Village of Wainwright
Native Village of Venetie
Tribal Government
(Venetie Village)
Uyak, Incorporated
Unga Corporation

Clark's Point
ANVSA
Circle ANVSA
Chulloonawick
ANVSA
Birch Creek
ANVSA
Chitina ANVSA
Red Devil
ANVSA
Rampart ANVSA
Port Lions
ANVSA
Port Heiden
ANVSA
Selawik ANVSA
Ugashik ANVSA
Copper Center
ANVSA
Lake
Minchumina
Yakutat ANVSA

6360
6350

Seattle
Seattle

Bristol Bay
Doyon

Seattle

Clark's Point
Circle
Chulloonawic
k

58.8330083
65.8260731

-158.5471213
-144.0723417

75
100

51
42

6340

Calista

62.950411

-164.1627576

0

1

6235
6330

Seattle
Seattle

Birch Creek
Chitina

Doyon
Ahtna

66.2590355
61.524029

-145.8190168
-144.4412094

28
106

22
41

7305
7300

Seattle
Seattle

Red Devil
Rampart

Calista
Doyon

61.7834473
65.5094443

-157.3387411
-150.1453142

48
45

22
46

7275

Seattle

Port Lions

Koniag

57.8658671

-152.8893955

256

106

7270
7430
7665

Seattle
Seattle
Seattle

Bristol Bay
NANA
Bristol Bay

56.9325614
66.5983985
57.5027418

-158.6249699
-160.0162004
-157.3887491

119
772
11

56
188
35

6365

Seattle

Ahtna

61.9769598

-145.3297294

492

218

6850
7765

Seattle
Seattle

Port Heiden
Selawik
Ugashik
Kluti Kaah
(Copper
Center)
Lake
Minchumina
Yakutat

Doyon
Sealaska

63.8829979
59.5542784

-152.3122074
-139.7435343

0
680

0
385

Sealaska

56.4752443

-132.3791325

0

0

Bering Straits
Bering Straits

64.6805456
65.6082056

-163.4042118
-168.0960055

203
152

75
59

Wrangell
White Mountain
ANVSA
Wales ANVSA
Wainwright
ANVSA

7755

Seattle

7745
7740

Seattle
Seattle

Wrangell
White
Mountain
Wales

7735

Seattle

Wainwright

Arctic Slope

70.6447815

-160.0201934

546

179

Venetie
Uyak
Unga

7725
7715
7705

Seattle
Seattle
Seattle

Venetie
Uyak
Unga

Doyon
Koniag
Aleut

67.0177722
57.6335601
55.1840915

-146.4148666
-154.007795
-160.5050438

0
0
0

0
0
0

23

Qawalangin Tribe of
Unalaska
Native Village of
Unalakleet
Village of Stony River
King Island Native
Community
Takotna Village
Uganik Natives,
Incorporated
Native Village of Tyonek
Twin Hills Village
Native Village of
Tununak
Native Village of
Tuntutuliak
Tuluksak Native
Community
Traditional Village of
Togiak
Native Village of Teller
Telida Village
Native Village of Tazlina
Native Village of Tatitlek
Native Village of Tanana
Native Village of Tetlin
Umkumiute Native
Village
Native Village of Minto
Native Village of Nelson
Lagoon
Newtok Village

Unalaska
ANVSA
Unalakleet
ANVSA
Stony River
ANVSA
Ukivok (King
Island)
Takotna ANVSA

7695

Seattle

Unalaska
(Qawalangin
Tribe)

7690

Seattle

Unalakleet

Bering Straits

63.8776565

-160.79136

747

242

7525

Seattle

Calista

61.7891481

-156.589835

61

25

7675
7530

Seattle
Seattle

Stony River
Ukivok (King
Island)
Takotna

Bering Straits
Doyon

64.9642527
62.972292

-168.0718043
-156.0870195

0
50

0
49

7660
7655

Seattle
Seattle

Uganik
Tyonek

Koniag
Cook Inlet

57.7565056
61.0716285

-153.4046297
-151.1494465

0
193

0
90

7650

Seattle

Twin Hills

Bristol Bay

59.0773756

-160.2835707

69

33

7645

Seattle

Tununak

Calista

60.5827236

-165.2588303

325

93

Aleut

53.8745625

-166.5337448

4,283

988

Uganik
Tyonek ANVSA
Twin Hills
ANVSA
Tununak
ANVSA
Tuntutuliak
ANVSA
Tuluksak
ANVSA

7640

Seattle

Tuntutuliak

Calista

60.3423989

-162.6695799

370

97

7630

Seattle

Tuluksak

Calista

61.1019806

-160.9629755

428

93

Togiak ANVSA
Teller ANVSA
Telida ANVSA
Tazlina ANVSA
Tatitlek ANVSA
Tanana ANVSA
Tetlin ANVSA

7605
7570
7565
7560
7555
7540
7580

Seattle
Seattle
Seattle
Seattle
Seattle
Seattle
Seattle

Togiak
Teller
Telida
Tazlina
Tatitlek
Tanana
Tetlin

Bristol Bay
Bering Straits
Doyon
Ahtna
Chugach
Doyon
Doyon

59.06194
65.261291
63.3839856
62.0588695
60.8663962
65.1715657
63.1350512

-160.37639
-166.3627828
-153.2785017
-145.4284212
-146.6779418
-152.0762703
-142.5238796

809
268
3
339
107
308
124

221
87
8
173
57
166
66

Umkumiute
Minto ANVSA
Nelson Lagoon
ANVSA
Newtok ANVSA

7685
6965

Seattle
Seattle

Calista
Doyon

60.4996523
65.150411

-165.1988597
-149.349708

0
258

0
99

7025
7055

Seattle
Seattle

Umkumiute
Minto
Nelson
Lagoon
Newtok

Aleut
Calista

56.0006152
60.9376751

-161.206974
-164.6307421

83
321

33
67

24

New Koliganek Village
Council
Newhalen Village
Nenana Native
Association

Lesnoi Village
Native Village of
Napaskiak
Native Village of
Napakiak
Native Village of
Napaimute
Native Village of
Nanwalek
Naknek Native Village
Nagamut, Limited
Nikolai Village
Montana Creek Native
Association, Incorporated
Native Village of
Nightmute
Mentasta Traditional
Council
Native Village of
Mekoryuk
Native Village of Mary's
Igloo
Native Village of
Marshall
Manokotak Village
Manley Hot Springs
Village

Seattle

New
Koliganek
(Koliganek)

Bristol Bay

59.72861

-157.28444

182

77

7035

Seattle

Newhalen

Bristol Bay

59.723835

-154.8923946

160

51

7030

Seattle

Doyon

64.5609632

-149.0874579

402

210

6860

Seattle

Nenana
Lesnoi
(Woody
Island)

Koniag

57.7778517

-152.3350845

0

0

7020

Seattle

Napaskiak

Calista

60.706026

-161.7633667

390

95

7010

Seattle

Napakiak

Calista

60.6905612

-161.9789784

353

101

7005

Seattle

Napaimute

Calista

61.5414325

-158.6738827

0

16

6995
6990
6985
7070

Seattle
Seattle
Seattle
Seattle

Chugach
Bristol Bay
Calista
Doyon

59.3520867
58.7329799
61.01944
63.0127602

-151.9119024
-156.9868784
-157.67444
-154.3814348

177
678
0
100

54
455
0
47

6970

Seattle

Nanwalek
Naknek
Nagamut
Nikolai
Montana
Creek

Cook Inlet

62.0686031

-150.0650363

0

0

7065

Seattle

Nightmute

Calista

60.4788125

-164.7216172

208

54

6945

Seattle

Mentasta Lake

Ahtna

62.9329779

-143.7700394

125

68

6935

Seattle

Mekoryuk

Calista

60.3891594

-166.1942792

210

96

6915

Seattle

Mary's Igloo

Bering Straits

65.1488994

-165.0677585

0

5

6910

Seattle

Marshall

Calista

61.8794301

-162.0878085

349

104

6905

Seattle

Bristol Bay

58.9724274

-158.9981386

399

106

6900

Seattle

Manokotak
Manley Hot
Springs

Doyon

65.0088256

-150.6107477

72

105

New Koliganek
ANVSA
Newhalen
ANVSA

7040

Nenana ANVSA
Lesnoi (Woody
Island)
Napaskiak
ANVSA
Napakiak
ANVSA
Napaimute
ANVSA
Nanwalek
ANVSA
Naknek ANVSA
Nagamut
Nikolai ANVSA
Montana Creek
Nightmute
ANVSA
Mentasta Lake
ANVSA
Mekoryuk
ANVSA
Mary's Igloo
ANVSA
Marshall
ANVSA
Manokotak
ANVSA
Manley Hot
Springs ANVSA

25

Levelock Village
Native Village of Larsen
Bay

McGrath
ANVSA
Lower Kalskag
ANVSA
Lime Village
ANVSA
Levelock
ANVSA
Larsen Bay
ANVSA

Nunakauyarmiut Tribe
Tanalian, Incorporated

Toksook Bay
ANVSA
Port Alsworth

McGrath Native Village
Village of Lower Kalskag
Lime Village

Asa'carsarmiut Tribe
Pilot Station Traditional
Village
Native Village of Nikolski
Native Village of Paimiut
New Stuyahok Village
Pedro Bay Village
Native Village of
Perryville
Oscarville Traditional
Village
Native Village of Pilot
Point
Native Village of
Ouzinkie
Native Village of Pitka's
Point
Platinum Traditional
Village

Mountain Village
ANVSA
Pilot Station
ANVSA
Nikolski ANVSA
Paimiut ANVSA
New Stuyahok
ANVSA
Pedro Bay
ANVSA
Perryville
ANVSA
Oscarville
ANVSA
Pilot Point
ANVSA
Ouzinkie
ANVSA
Pitkas Point
ANVSA
Platinum
ANVSA

6895

Seattle

Doyon

62.9488245

-155.575891

401

213

Seattle

McGrath
Lower
Kalskag

6890

Calista

61.5125106

-160.3642285

267

79

6875

Seattle

Lime Village

Calista

61.3539737

-155.4378285

6

24

6865

Seattle

Levelock

Bristol Bay

59.1116702

-156.8612549

122

50

6855

Seattle

Koniag

57.5351177

-153.9874373

115

70

7625
7263

Seattle
Seattle

Calista
Cook Inlet

60.5337752
60.2016214

-165.1036627
-154.322332

532
0

110
0

6975

Seattle

Larsen Bay
Nunakauyarmi
ut (Toksook
Bay)
Port Alsworth
Asa'carsarmiut
(Mountain
Village)

Calista

62.0905945

-163.7278598

755

211

7230
7075
7185

Seattle
Seattle
Seattle

Pilot Station
Nikolski
Paimiut

Calista
Aleut
Calista

61.9375015
52.9400839
61.7029942

-162.8824583
-168.8615003
-165.8200534

550
39
2

126
28
1

7050

Seattle

New Stuyahok

Bristol Bay

59.4518085

-157.3207794

471

107

7205

Seattle

Pedro Bay

Bristol Bay

59.7768286

-154.1483802

50

44

7215

Seattle

Perryville

Bristol Bay

55.9139846

-159.1632767

107

45

7175

Seattle

Oscarville

Calista

60.7236478

-161.775834

61

20

7225

Seattle

Pilot Point

Bristol Bay

57.5545282

-157.575306

100

60

7180

Seattle

Ouzinkie

Koniag

57.9237326

-152.5002138

225

86

7235

Seattle

Pitkas Point

Calista

62.0345494

-163.2826137

125

42

7245

Seattle

Platinum

Calista

59.0094965

-161.8236582

41

26

26

Native Village of Point
Hope
Native Village of Point
Lay
Point Possession,
Incorporated
Portage Creek Village
Petersburg Indian
Association
Native Village of Nuiqsut
Ninilchik Village
Native Village of Noatak
Nome Eskimo
Community
Nondalton Village
Pauloff Harbor Village

Northway Village
Village of Old Harbor
Nulato Village
Native Village of Nunam
Iqua
Native Village of
Nunapitchuk
Village of Ohogamiut
Noorvik Native
Community

Point Hope
ANVSA
Point Lay
ANVSA
Point Possession
Portage Creek
ANVSA
Petersburg
Nuiqsut ANVSA
Ninilchik
ANVSA
Noatak ANVSA
Nome
Nondalton
ANVSA
Pauloff Harbor
Northway
ANVSA
Old Harbor
ANVSA
Nulato ANVSA

7250

Seattle

Point Hope

Arctic Slope

68.3485799

-166.7693181

757

215

7255

Seattle

Arctic Slope

69.7426654

-163.0081627

247

67

7257

Seattle

Point Lay
Point
Possession

Cook Inlet

61.0307945

-150.4110377

0

0

7260

Seattle

Portage Creek

Bristol Bay

58.9072773

-157.7174301

36

22

7220
7125

Seattle
Seattle

Petersburg
Nuiqsut

Sealaska
Arctic Slope

56.8112667
70.2166008

-132.9512425
-150.9999733

0
433

0
126

7080
7085

Seattle
Seattle

Ninilchik
Noatak

Cook Inlet
NANA

60.0299672
67.5716105

-151.6936161
-162.9676294

13,264
428

7,007
106

7095

Seattle

Nome

Bering Straits

64.4999264

-165.3939641

0

0

7100
7195

Seattle
Seattle

Bristol Bay
Aleut

59.9634006
54.4576992

-154.8564289
-162.7071458

221
0

120
0

7115

Seattle

Nondalton
Pauloff Harbor
Northway
(Northway
Village)

Doyon

62.98222

-141.95167

107

39

7150
7130

Seattle
Seattle

Koniag
Doyon

57.2104162
64.724638

-153.303112
-158.1066292

237
336

111
119

7133

Seattle

Old Harbor
Nulato
Nunam Iqua
(Sheldon
Point)

Calista

62.5298955

-164.8525142

164

45

Nunam Iqua
ANVSA
Nunapitchuk
ANVSA
Ohogamiut
ANVSA

7135

Seattle

Nunapitchuk

Calista

60.8967946

-162.4522001

466

120

7145

Seattle

Ohogamiut

Calista

61.5703795

-161.8648259

0

4

Noorvik ANVSA

7110

Seattle

Noorvik

NANA

66.8344824

-161.0439804

634

157

27

Appendix B – Procedures for accessing population and housing unit
data from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

28

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

29

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the
first data set listed which is “Census 2000 Summary File 1.” You may want to scroll
through the other data sets to see what other information is available for your future
reference.

30

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example we will access tribal block group data, but you can also
access data for reservations, off-reservation trust lands, tracts, blocks and many other
geographic areas.

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1”
that you are looking for. Remember that you may select multiple data types.

31

6. After clicking “Show Result” you will now see the data you have requested.

32

Appendix C - Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail: charlotte.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

33

2010 Census Tribal Statistical Areas Program

Guidelines for Delineating
State Designated Tribal Statistical Areas

Version 1
January 2008

1. Introduction................................................................................................................... 3
2. Background on SDTSAs and the TSAP...................................................................... 5
2.1 Purpose of SDTSAs................................................................................................. 5
2.2 Eligibility.................................................................................................................. 6
2.3 Schedule ................................................................................................................... 6
2.4 Program Materials.................................................................................................. 6
2.5 Important Information on Features...................................................................... 8
2.5.1 Acceptable Features for Use as SDTSA Boundaries......................................... 8
2.5.2 Boundary Feature Updates................................................................................. 9
2.5.3 Guidelines for Updating Features .................................................................... 10
2.6 Feature Extension Criteria................................................................................... 10
3. Criteria......................................................................................................................... 10
3.1 All State Designated Tribal Statistical Areas must follow these criteria:........ 11
3.2 All State Designated Tribal Statistical Areas should follow these guidelines: 11
3.3 Things to consider when delineating SDTSAs ................................................... 12
4. Procedures ................................................................................................................... 12
4.1.1 The following procedures are suggested for reviewing and revising an existing
SDTSA (SDAISA):................................................................................................... 13
4.1.2 The Census Bureau suggests the following procedures for delineating a new
SDTSA:..................................................................................................................... 13
4.2 Transmitting completed submissions and Census Bureau review ................... 15
4.3 Verification ............................................................................................................ 15
Appendix A – State designated tribal statistical areas eligible for delineation......... 16
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder...................................................................................................... 18
Appendix C - Regional Census Center’s Contact Information .................................. 23

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people
and the economy. The U.S. Constitution mandates that a census be taken every 10 years
in order to reapportion the House of Representatives. The data gathered by the decennial
census and other Census Bureau programs are used for several other purposes, including
the allocation and distribution of funds to state, local and tribal governments. Census
information shapes important policy decisions that in turn shape the nation’s social and
economic conditions. While best known for the decennial census, the Census Bureau
conducts numerous surveys and censuses that measure changing individual and
household demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need.
Many tribal communities use census information to attract new business and plan for
growth. In fact, many tribes and tribal organizations use census data to plan new
facilities and programs for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has developed the Tribal
Statistical Areas Program (TSAP) to collect updates to the inventory and boundaries of
American Indian and Alaska Native statistical geographic areas. Participation in the
TSAP is voluntary. If you choose not to participate, the Census Bureau may revise the
boundary of an existing area or delineate a new area in accordance with published criteria
and guidelines. The TSAP includes the following statistical areas:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Alaska Native village statistical areas (ANVSAs)
Oklahoma tribal statistical areas (OTSAs) and tribal subdivisions on OTSAs
state designated tribal statistical areas (SDTSAs)
tribal designated statistical areas (TDSAs)
tribal census tracts (TCTs) and tribal block groups (TBGs) on American Indian
reservations (AIRs)/ off-reservation trust lands (ORTLs)
census designated places (CDPs)

The Census Bureau will tabulate statistical data from the 2010 Census for each entity
type listed above, and will continue to use these areas to provide data from the American
Community Survey (ACS) through the coming decade. Meaningful statistical data from
the 2010 Census and ACS provide tribes and other data users with a tool to help them
make informed decisions and plan for community services. More information about the
background and components of these geographic areas can be found in the Federal
Register notice Vol. 73, No. 221 / Friday, November 14, 2008, page 67470. This notice
can also be accessed from our TSAP webpage at
http://www.census.gov/geo/www/tsap2010/tsap2010.html.
These guidelines explain the criteria and complete instructions for delineating SDTSAs
using paper maps. The subjects covered are:
ƒ
ƒ

Background on the TSAP and SDTSAs
Tribes Eligible to Delineate SDTSAs

ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

Schedule
Required Materials
SDTSA Criteria
Procedures for Annotating Maps
Procedures for Transmitting Completed Submissions
Census Bureau Submission Review
Verification

Those state liaisons wishing to delineate SDTSAs for eligible tribes in their states will
have the option of using paper maps or Census Bureau-provided Geographic Information
System (GIS) data, tools, shapefiles, and ESRI® ArcGIS® extension specific to this
program. Participants who choose to submit changes using the digital method must have
ArcGIS 9.2 or 9.3. These guidelines refer mainly to the use of paper maps.
The TSAP Extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides
a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management
features of the extension. In addition to the inherent functionality of the ArcGIS
software, the extension’s unique editing tools consist of geographic area assignment, as
well as line editing and polygon split/merge functions. The option of using either the
TSAP extension or the paper maps to submit changes is at the complete discretion of
each tribe as neither is preferred over the other by the Census Bureau. However,
depending on the number anticipated updates and/or their complexity, you might consider
using the TSAP extension which offers you the ability to view population density within
American Indian statistical areas and allow you to more clearly add or remove area or
adjust boundaries. If you are interested in using a GIS application to submit your
boundaries and you have ArcGIS 9.2 or 9.3 software, but did not receive the ArcGIS
extension software or digital data files along with your materials, please contact the
Census Bureau Regional Census Center 1 (RCC). You may also contact RCC staff to ask
other questions or arrange for training.
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is
used to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical
tribal entities for use in tabulating and publishing data from the 2010 Census, the
American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours
per respondent, including time for reviewing instructions, assembling materials,
organizing and reviewing the information, and reporting any needed changes. We
anticipate that an estimated 650 participants will respond. Remaining entities may be
1

See Appendix C for RCC contact information

worked by Census Bureau regional staff. For larger areas or areas with many changes,
however, the respondent burden may be 180 hours or longer to complete. Please send
comments regarding this burden estimate or any other aspect of this collection of
information, including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 06070795” as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background on SDTSAs and the TSAP
2.1 Purpose of SDTSAs
In an effort to improve the presentation of data for state recognized American Indian
tribes that did not have a reservation, boundaries for statistical areas associated with these
tribes were first introduced for the 1990 Census of Population and Housing, and then
revised during Census 2000. In Census 2000 these statistical areas were known as State
Designated American Indian Statistical Areas (SDAISAs). For the 2010 Census, they are
known as State Designated Tribal Statistical Areas (SDTSAs).
Prior to 1990, data were only tabulated for federal and state recognized reservations and
off-reservation trust lands, legal tribal subdivisions and the Historic Areas of Oklahoma
(now called OTSAs). As part of the 2010 Census, TSAP state liaisons representing state
recognized tribes will again have the opportunity to review and update the boundaries of
existing SDTSAs (SDAISAs) or delineate new SDTSAs.
SDTSAs are statistical American Indian Areas (AIAs) identified for state recognized
tribes that are not federally recognized and do not have an American Indian reservation
(AIR) or off-reservation trust lands (ORTLs). The Census Bureau works with a state
liaison appointed by each state governor to delineate these areas. SDTSAs may not cross
state lines and are limited to the state in which the respective tribe is officially
recognized. SDTSAs provide state recognized tribes without reservations statistical data
for a geographic area that encompasses a substantial concentration of tribal members.
SDTSAs are intended to provide comparable geographic entities for analyzing data over
time and to provide a way to obtain data comparable to that provided for tribes of a

similar size that have reservations or off-reservation trust lands in the same region and/or
state. The definition of a SDTSA may not necessarily include all tribal members; nor is it
intended to depict land ownership, represent an area over which a tribe has any form of
governmental authority or jurisdiction, or represent all of the traditional or historical
areas associated with the tribe, including areas used for subsistence activities.
Representation of statistical American Indian Area (AIA) boundaries in Census Bureau
products is solely for the purpose of data tabulation and presentation. Likewise,
representation of SDTSA boundaries in Census Bureau products does not convey or
confer any rights to land ownership, government authority, or jurisdictional status.
Statistical data will be tabulated for all people living within the boundaries of a SDTSA
(including non-tribe members), and also for all tribal members regardless of where they
reside in the state or nation. Each individual, whether or not he or she is located on a
tribal area, will have the same opportunity to identify their tribal affiliation. While data
tabulated for a well defined SDTSA will provide a rich source of statistical and
demographic information for the SDTSA, it is not necessary for an individual to be living
within the boundary of the SDTSA to be counted as part of a tribe. Both population and
housing unit data can be found by accessing American FactFinder on the Census
Bureau’s internet website. Directions for obtaining this data can be found in Appendix B.
2.2 Eligibility
As the TSAP state liaison appointed by your governor, you have been asked to work with
your state recognized tribes that do not have a reservation or off-reservation trust lands to
update or delineate SDTSAs. Qualifying tribes must be recognized by a formal state
recognition process. The specifics of this process vary from state to state. If for any
reason, you believe the tribe or tribes in your state should not be delineating a SDTSA
and should be delineating or updating another type of American Indian Area, please
contact your local RCC. A list of RCC contacts is available in Attachment C. If you
decline or defer participation, the Census Bureau will use 2000 SDTSA boundaries,
which will possibly be modified to reflect 2010 criteria. If no SDTSA was present in
2000, the Census Bureau will most likely not delineate one for 2010 without your
participation.
2.3 Schedule
In fall 2008, the Census Bureau mailed formal invitation letters to TSAP state liaisons for
each eligible SDTSA. These guidelines and accompanying paper maps required to
complete the work are scheduled to arrive in January 2009. State liaisons will have 120
days from the date they receive these materials to complete a review and submit their
geographic statistical area delineations or updates to the RCC. In the fall of 2009, after
the Census Bureau has reviewed and incorporated your delineations into our geographic
database, you will receive new maps or digital files so that you can verify that we have
inserted your boundaries correctly. If you have questions regarding your delineation or
submission, assistance will be available from geographers at your RCC. We strongly
encourage you to work closely with the tribes in your state throughout this process.
2.4 Program Materials

The paper map types you receive will depend on the size and mapping complexity of the
SDTSA. An SDTSA that is smaller in land area may only receive a single map sheet. A
SDTSA with a large land area may receive an index map, a series of parent maps, and a
number of inset maps. An index map shows the complete SDTSA with gridlines defining
specific areas shown on each parent map sheet. A parent map shows a detailed version of
a single grid box from the index map, and an inset map shows finer details of any areas
within the parent map where the feature network is too dense to represent clearly at the
map scale of the parent sheet. You can think of the inset map as a “blow-up” of a
specific area.

Figure 1: Example of index, parent and inset maps
If a tribe has a Census 2000 SDTSA (SDAISA) delineation, your RCC will provide a
map depicting the Census 2000 SDTSA boundary with a one-mile fringe area. If your
updates include area outside of this fringe area, please contact your RCC for maps
depicting this additional area. If a tribe did not have a Census 2000 SDTSA, your RCC
will provide county maps for the area in which the SDTSA might be delineated. If a
SDTSA should be delineated in counties for which you did not receive maps, please
contact the RCC and they will provide you with the county maps you need. Figure 2
shows entity boundaries that are shown on your maps and how they are symbolized.

Figure 2: Tribal areas symbology
The Census Bureau requests that participants use a pencil with red lead to annotate
SDTSA boundaries on the paper map provided. Procedures for annotating the maps are
detailed in section 4.
2.5 Important Information on Features
2.5.1 Acceptable Features for Use as SDTSA Boundaries
SDTSA boundaries should follow specified legal or administrative boundaries that do not
change greatly over time, or permanent, visible features, such as roads, perennial streams,
railroads, and high-tension power lines. Permanent visible features should be easily
locatable in the field by Census Bureau staff without ambiguity. The acceptable visible
boundary features are:
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

levee
dam
stream/river (perennial)
canal, ditch or aqueduct (perennial)
pier/dock
runway/taxiway
pipeline (above ground)
powerline (above ground, high-tension)
aerial tramway/ski lift
natural topographic features
cliff/escarpment
perennial shoreline
railroad features (main)
carline, streetcar track, monorail, other mass transit rail

ƒ
ƒ
ƒ
ƒ
ƒ
ƒ

interstate highway or primary road with limited access
primary road without limited access, US highway, state highway or county
highway, secondary and connecting roads
local neighborhood road, rural road, city street
service drive (usually along a limited access highway)
alley
fencelines

Natural topographic features include the crests of well-defined mountain ridges; the rims
or bases of sharply defined escarpments, cliffs, or bluffs; the position of dry ravines or
arroyos; as well as other features as long as the features are not also mimicked by another
visible feature, have no housing in the vicinity, and are easily located on the ground.
Data user and Census Bureau experience has shown that some features make better
boundaries than others, and the same type of feature can make an excellent boundary in
one place and a poor one in another. Rivers, major canals, lakes, and other bodies of
water often make good statistical area boundaries because they generally limit access
from one area to another and rarely change relative location. Other features that limit
access between areas, such as interstate and other major highways, railroad tracks, and
the ridges of mountain ranges, also make good statistical area boundaries. In some
instances, however, such a feature unifies a community, for example, a lake forming the
core of a recreational housing development or a through street forming the spine of a
subdivision. In these circumstances, the statistical area boundary should include the entire
area of the lake or both sides of a unifying street to better encompass similar community
patterns.
In general, when delineating boundaries in bodies of water represented as polygons and
having area (lakes, reservoirs, bays, oceans, and wide rivers), the boundary should follow
a line bisecting the water body rather than following a shoreline. If possible, use an
existing line in water (for example, a city limit in the middle of a river) rather than adding
a new line.
Officials delineating TDSAs may only add non-visible lines as a boundary if other
acceptable boundary features such as roads, rivers, streams, shorelines, trails and
ridgelines, are not available and they aid in a TDSA meeting other specific delineations
criteria and/or guidelines. The Census Bureau staff will contact you if they require more
information or have questions about feature updates submitted as part of the 2010 TSAP.
2.5.2 Boundary Feature Updates
The Census Bureau has spent the last six years enhancing the spatial accuracy of the
roads in our database system. The local files used during this project were required to
have an overall average accuracy of 7.6 meters while some files had better accuracy.
Although much of the street network is vastly improved, as you work with our maps you
may notice that in some counties the street and boundary features look distorted. A line
that should be straight may have a noticeable kink or pointed shape. The Census Bureau

is working to correct these problems, and if you need to use a feature that is distorted in
our maps follow the guidelines below.
The Census Bureau is also now moving forward with our 2010 Census field canvassing
and collection activities. This means that we are no longer processing realignments to
our street network. What is critical for the success of the 2010 Census data tabulation is
the location of roads relative to the tabulation entity boundary. As long as the road is
within the correct entity, the population and housing will be properly reported. The
guidelines below also explain what updates are acceptable as part of the TSAP.
It is critical that participants understand that the 2010 TSAP is are not intended for street
feature updates except where a boundary follows a road (or other visible feature such as a
stream) and the road is not reflected in our file. For this reason the Census Bureau can
not accept street (or other) feature updates that do not follow the guidelines below:
2.5.3 Guidelines for Updating Features
1. If a road is missing and it forms the boundary for the area you are defining, add
the road and provide the name.
2. If you can not correctly delineate the boundary for an entity you are updating
because the feature you need to follow is incorrectly located, mislabeled or
distorted in the Census Bureau’s file, we request that you fix that feature only. In
addition, we request that you report the problem area to the Census Bureau
(through your RCC) by sending information describing the incorrect feature and
the specific entity boundary affected.
3. Do not add streets that are missing for an entire housing development (add only
streets that are needed to form a boundary). We will be adding new or missing
streets during our address canvassing operation which will occur in the spring and
early summer of 2009. The Census Bureau will provide verification materials to
each participant that returns their submission in the correct format and within the
allotted 120 days that will show the results of address canvassing. If these streets
are still missing at that time, we will accept these as adds.
2.6 Feature Extension Criteria
If you want to use an existing feature that doesn’t form a closed polygon, you may add a
short line to connect the features and close the polygon. The Census Bureau refers to
these lines as feature extensions and several requirements pertain. To avoid creating
ambiguous Census block boundaries, we require that feature extensions:
ƒ Are no longer than 300 feet;
ƒ Are straight lines from the end of a road and intersecting a non-road feature
(These include all hydrographic features, pipelines, powerlines, and railroads.);
ƒ Do not intersect a cul-de-sac.

3. Criteria
All American Indian Areas (AIAs) must follow a standard set of criteria that support a
shared purpose of providing a meaningful and relevant geographic framework for
tabulating data for the Census. It is the responsibility of the Census Bureau to ensure that
geographic entity criteria can achieve the goal of providing meaningful, relevant, and

reliable statistical data, and that the final criteria for geographic entities are met. While
aware that there are secondary uses of geographic entities and the data tabulated for them,
the Census Bureau will not modify their boundaries or attributes specifically to meet
these secondary uses, including those of other government agencies. If a change is made
to a geographic entity to meet one specific purpose, it may be detrimental for other
programs that also use these entities.
The Census Bureau will use the following criteria and guidelines to help ensure that the
SDTSAs delineated for the 2010 Census meet their definition, support the intended
purpose of the program, provide useful and meaningful data for the tribe they represent,
and enhance the ability for data users to make more meaningful comparisons between
data.
Criteria are rules that must be followed by all officials delineating statistical AIAs for the
2010 Census, while guidelines are suggestions for improving the relevance and utility of
statistical AIAs.
3.1 All State Designated Tribal Statistical Areas must follow these criteria:
1. A SDTSA must contain some American Indian population and housing.
2. A SDTSA may not overlap with any other AIA, at the same level of the geographic
hierarchy.
3. A SDTSA may not completely surround another legal or statistical AIA at the same
level of the geographic hierarchy.
4. A SDTSA may not include more water area than land area.
5. Officials delineating SDTSAs may only add nonvisible lines such as corporate limits
as a boundary if other acceptable boundary features such as roads, rivers, streams,
shorelines, trails and ridgelines, are not available and they aid in a SDTSA meeting
other specific, delineation criteria and/or guidelines.
6. The Census Bureau will evaluate the submitted name of a SDTSA to ensure that the
name is clearly distinguishable from the name of any other legal or statistical AIA.
7. SDTSAs may not include military areas.
8. An SDTSA for a specific tribe may be delineated in a state only if the tribe is
officially recognized by the state.
9. The name for each SDTSA is determined by the tribe or tribes (in conjunction with
the Census Bureau, and the state liaison for SDTSAs) that are responsible for its
delineation. The name of a SDTSA must reflect one or more of the following
conditions: The tribe that has the largest population currently residing within the
SDTSA; and/or the name of the tribe most commonly associated with the area
encompassed by the SDTSA.

3.2 All State Designated Tribal Statistical Areas should follow these guidelines:
1. SDTSAs should be comparable in area to the AIRs and/or ORTLs of other tribes with
similar numbers of members in the same state and/or region.

2. American Indians should constitute a large proportion of the population within a
SDTSA, and of the American Indian population, the majority should be members of
the delineating tribe.
3. A minimum population of at least 1,200 individuals or 480 housing units is suggested
to help enhance reliability and availability of sample-based data.
4. SDTSAs should include area where there is structured and organized tribal activity,
including tribal headquarters, tribal service centers, meeting areas and buildings,
ceremonial grounds, tribally owned commercial locations, etc.
5. SDTSAs should not contain large areas without housing or population. A housing
unit density of at least three housing units per square mile is suggested.
6. SDTSAs should be contiguous.
7. Water area should be included only to maintain contiguity, to provide a generalized
version of the shoreline, or if the water area is completely surrounded by land area
included in the SDTSA.
8. SDTSA boundaries should follow visible, physical features, such as rivers, streams,
shorelines, roads, and ridgelines.
9. SDTSA boundaries may follow the non visible, legally defined boundaries of AIRs,
ORTLs, states, counties, or incorporated places.
3.3 Things to consider when delineating SDTSAs
Since SDTSAs also will be used to tabulate and present period estimates from the ACS,
defining officials should consider that, as a general rule, period estimates of demographic
characteristics for geographic entities with small populations will be subject to higher
variances than comparable estimates for geographic entities with larger populations. In
addition, the Census Bureau’s disclosure rules may have the effect of restricting the
availability and amount of data for geographic entities with small populations. The more
closely a SDTSA’s boundary relates to the distribution of tribal members and American
Indians receiving governmental services from the tribe, and does not include large
numbers of people and households not affiliated with the tribe, the more likely that data
presented for the SDTSA will accurately reflect the characteristics of the intended tribal
population.
Although eligible, in a few cases a tribe may elect not to delineate a SDTSA if it will not
provide meaningful, relevant, or reliable statistical data because the member population
now resides in numerous other locations or has been completely subsumed by nonmember and/or non-American Indian populations. In such instances, defining a SDTSA
will not improve the presentation of statistical data relating to tribal members. These
tribes may still be able to receive meaningful, relevant, and reliable statistical data for
their tribal membership at higher levels of census geography through the characteristic of
tribal affiliation.

4. Procedures
The Census Bureau strongly encourages TSAP state liaisons to work closely with tribal
officials when delineating SDTSAs.

4.1.1 The following procedures are suggested for reviewing and revising an existing
SDTSA (SDAISA):
1. Compare your source materials with the Census Bureau’s maps.
2. If you are satisfied with how the 2000 SDTSA (SDAISA) boundary is currently
portrayed on the Census Bureau’s maps, fill out and sign the form attached to the
cover letter that came with your materials indicating there is “no change” to the
boundary. Return the form to the RCC using the postage paid envelope provided.
3. If you need to change the SDTSA boundary, cross out the old boundary with an “X”
using a pencil with red lead. Mark the ends of the deletion with red hatch marks (//).
4. Using a pencil with red lead, plot the revised boundaries on the Census Bureau’s map.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your SDTSA. The Census Bureau will not
accept new road features at this time unless the road or other feature is
necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature. Then use the red lead pencil to highlight
the feature as an SDTSA boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your SDTSA
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact your RCC to
describe the location and nature of the problem.
5. Please remember to adjust your SDTSA boundary to follow the acceptable features
described in section 2.5.
6. Review the name of the 2000 SDTSA (SDAISA). If the name is still appropriate for
the SDTSA, make no annotation. If the name requires revision, cross out the old
name and clearly label the new name in red within the boundary of the SDTSA.
Make sure the name follows the criteria described earlier. If there is a name change
for any reason, you must submit a written request signed by the chairperson, chief or
president of the SDTSA.
4.1.2 The Census Bureau suggests the following procedures for delineating a new
SDTSA:
1. If you do not wish to delineate an SDTSA for a tribe, fill out and sign the form
attached to the cover letter that came with your materials indicating you do not wish
to delineate an area.
2. Compare your source materials with the Census Bureau’s map(s).
3. Using a pencil with red lead, plot the boundary on the Census Bureau’s map(s).
4. If a feature that is not on the census map(s) is required as the boundary of the
SDTSA, use a black lead pencil to add and label the new feature and the red pencil to
highlight the feature as an SDTSA boundary.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your SDTSA. The Census Bureau will not
accept new road features at this time unless the road or other feature is
necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature. Then use the red lead pencil to highlight
the feature as an SDTSA boundary.

b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your SDTSA
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact the your RCC to
describe the location and nature of the problem.
5. Ensure that the SDTSA boundary follows the acceptable features described in section
2.5.
6. Clearly label the name of the new SDTSA in red within the boundary of the SDTSA.
Examples:

Figure 1: Area is being removed from the SDTSA shown in white.

Figure 2: Area is being added to the SDTSA shown in white.
4.2 Transmitting completed submissions and Census Bureau review
Please return all maps to the RCC in the same tube/box/envelope you received it in and
be sure to use the mailing label provided.
The Census Bureau RCC geographic staff will verify that the submitted SDTSAs are
complete, meet all criteria and other requirements and, where the criteria have not been
met, a valid justification is provided. The Census Bureau will provide feedback to the
participant on their submission and if necessary provide additional guidance on the
criteria and guideline usage. The Census Bureau will contact you with any questions or
concerns regarding this submission. The Census Bureau reserves the right to modify,
create, or reject any boundary or attribute as needed to meet the final program criteria and
guidelines or to maintain geographic relationships before the tabulation geography is
finalized for the 2010 Census.
4.3 Verification
If you return your submission with 120 days of receiving the maps and other materials,
the Census Bureau will provide you with a new map, which you can use to verify that the
Census Bureau staff inserted the boundary of the SDTSA correctly. The verification map
will be provided in late 2009. At that time it would be possible for tribes to make minor
boundary changes or add features that still may be missing from our maps.

Appendix A – State designated tribal statistical areas eligible for delineation
Tribe Name

Waccamaw Indian People
Santee Indian Organization
Choctaw Apache Tribe
Pee Dee Indian Nation of Upper South
Carolina
Nansemond Indian Tribe
Pee Dee Tribe
Rappahannock Tribe
Upper Mattaponi Indian Tribe
Echota Cherokee Tribe
Little Shell Tribe of Chippewa Indians
Point-Au-Chen Tribe
United Houma Nation
Clifton Choctaw Tribe
Adai Caddo Tribe
Monacan Indian Nation
Beaver Creek Indians
Occaneechi Band of Saponi Nation
Four Winds Tribe
Cherokee Tribe of Northeast Alabama
Ramapough Lenape Indian Nation
Chickahominy Indians Eastern
Division
Nanticoke Lenni-Lenape Indians
Nanticoke Indian Tribe

Area Name

Census
Area
Code

Census 2000
Population

Census 2000
Housing Units

2010 Census Areas
Eligible for
Delineation

Regional
Census
Center

Tribal Area Placeholder
Tribal Area Placeholder
Apache Choctaw SDAISA
Tribal Area Placeholder

0
0
9515
0

0
0
23,459
0

0
0
13,671
0

SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Dallas
Charlotte

Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Echota Cherokee SDAISA
Tribal Area Placeholder
Tribal Area Placeholder
United Houma Nation SDAISA
Clifton Choctaw SDAISA
Adais Caddo SDAISA
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Four Winds Cherokee SDAISA
Cherokee Tribe of Northeast
Alabama SDAISA
Ramapough SDAISA
Eastern Chickahominy SDAISA

0
0
0
0
9680
0000
0
9960
9630
9510
0
0
0
9720
9560

0
0
0
0
65,068
0
0
839,880
476
39,080
0
0
0
79,657
173

0
0
0
0
26,997
0
0
337,007
205
16,890
0
0
0
34,316
92

SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Charlotte
Charlotte
Atlanta
Denver
Dallas
Dallas
Dallas
Dallas
Charlotte
Charlotte
Charlotte
Dallas
Atlanta

9850
9675

892
104

262
42

SDTSA
SDTSA

Philadelphia
Charlotte

9835

12,316

2,959

SDTSA

Philadelphia

9830

22,683

17,594

SDTSA

Philadelphia

Nanticoke Lenni Lenape
SDAISA
Nanticoke Indian Tribe SDAISA

Haliwa-Saponi Tribe
Chickahominy Indian Tribe
Biloxi-Chitimacha
Confederation/Bayou LaFourche Band
Coharie Tribe
Piqua Shawnee Tribe
MaChis Lower Creek Tribe
Star Clan of Muscogee Creeks
Meherrin Tribe
Waccamaw Siouan Tribe
Cherokees of Southeast Alabama
United Cherokee Ani-Yun-Wiya
Nation
Lumbee Tribe
Person County Indians (Sappony)
Pamunkey Indian Tribe
Lower Muscogee Creek Tribe
MOWA Band of Choctaw Indians
Mattaponi Indian Tribe
Shinnecock Indian Nation
Paugussett Indian Nation
Powhatan-Renape
Hassanamisco Band of the Nipmuc
Nation
Paucatuck Eastern Pequot Indians
Schaghticoke Tribe
Poospatuck Indian Nation

Haliwa-Saponi SDAISA
Chickahominy SDAISA
Tribal Area Placeholder

9745
9580
0

8,272
3,313
0

3,384
1,311
0

SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Dallas

Coharie SDAISA
Tribal Area Placeholder
MaChis Lower Creek SDAISA
Star Musckogee Creek SDAISA
Meherrin SDAISA
Waccamaw Siouan SDAISA
Cherokees of Southeast Alabama
SDAISA
Tribal Area Placeholder

9635
0
9820
9880
9825
9970
9550

123,761
0
24,198
7,331
7,867
2,329
120,294

54,248
0
11,048
3,508
3,419
891
55,734

SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Atlanta
Atlanta
Atlanta
Charlotte
Charlotte
Atlanta

0

0

0

SDTSA

Atlanta

Lumbee SDAISA
Indians of Person County
SDAISA
Pamunkey (state) Reservation
Tama (state) Reservation
MOWA Choctaw (state)
Reservation
Mattaponi (state) Reservation
Shinnecock (state) Reservation
Golden Hill (state) Reservation
Rankokus (state) Reservation
Hassanamisco (state)
Reservation
Paucatuck Eastern Pequot (state)
Reservation
Schaghticoke (state) Reservation
Poospatuck (state) Reservation

9815
9760

474,100
1,919

184,305
811

SDTSA
SDTSA

Charlotte
Charlotte

9260
9400
9240

58
57
124

36
21
37

State Res.
State Res.
State Res.

Charlotte
Atlanta
Atlanta

9230
9370
9100
9330
9150

58
504
0
0
2

28
194
0
0
1

State Res.
State Res.
State Res.
State Res.
State Res.

Charlotte
New York
Boston
Philadelphia
Boston

9280

26

19

State Res.

Boston

9350
9300

9
283

4
104

State Res.
State Res.

Boston
New York

Appendix B – Procedures for accessing population and housing unit
data from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the
first data set listed which is “Census 2000 Summary File 1.” You may want to scroll
through the other data sets to see what other information is available for your future
reference.

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example, we will access tribal block group data, but you can also
access data for reservations, off-reservation trust lands, tracts, blocks, and many other
geographic areas.

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1”
that you are looking for. Remember that you may select multiple data types.

6. After clicking “Show Result” you will now see the data you have requested.

Appendix C - Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail: charlotte.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

2010 Census Tribal Statistical Areas Program

Guidelines for Updating State Reservations

Version 1
January 2008

1. Introduction................................................................................................................... 1
2. Background on the State Reservation Program ........................................................ 3
2.1 Eligibility.................................................................................................................. 3
2.2 Schedule ................................................................................................................... 4
2.3 Program Materials.................................................................................................. 4
2.4 Boundary Feature Updates .................................................................................... 5
3. Criteria........................................................................................................................... 6
4. Procedures ..................................................................................................................... 7
4.1 Annotating Maps..................................................................................................... 7
4.1.1 Suggested procedures for reviewing and revising an existing state AIR: ......... 7
4.1.2 Suggested procedures for delineating a new state AIR: .................................... 7
4.2 Transmitting completed submissions and Census Bureau review ..................... 9
4.3 Verification .............................................................................................................. 9
Appendix A – American Indian and Alaska Native Tribe Areas Eligible for
Delineation ......................................................................................................................... 1
Appendix B – Procedures for accessing population and housing unit data from
American FactFinder........................................................................................................ 1
Appendix C - Regional Census Center’s Contact Information .................................... 6

OMB No. 0607-0795: Approval Expires 03/31/09

1. Introduction
The U.S. Census Bureau is the premier source of information about the American people
and the economy. The U.S. Constitution mandates that a census be taken every 10 years
in order to reapportion the House of Representatives. The data gathered by the decennial
census and other Census Bureau programs are used for several other purposes, including
the allocation and distribution of funds to state, local and tribal governments. Census
information shapes important policy decisions that helps shape the nation’s social and
economic conditions. While best known for the decennial census, the Census Bureau
conducts numerous surveys and censuses that measure changing individual and
household demographics and the entire economic condition of the nation.
Census data help tribal elders and leaders understand what their communities need.
Many tribal communities use census information to attract new business and plan for
growth. In fact, many tribes and tribal organizations use the census data to plan new
facilities and programs for the communities they serve.
In preparation for the 2010 Census, the U.S. Census Bureau has developed the State
Reservation Program (SRP). The SRP provides an opportunity for state officials, working
with state-recognized tribes that have a state American Indian reservation (AIR) to
review and, as needed, update the boundaries and names for American Indian
Reservations (AIRs) for state-recognized American Indian tribes. State recognized tribes
that do not have an AIR are eligible to delineate a state designated tribal statistical area
(SDTSA) as part of our Tribal Statistical Area Program (TSAP). The TSAP also
provides opportunities for federally recognized tribes to delineate other statistical areas as
appropriate. Because the Census Bureau works with a single state appointed liaison to
review and update the state recognized reservations and to delineate state designated
tribal statistical areas, TSAP and the SRP are conducted in tandem.
The Census Bureau will tabulate statistical data from the 2010 Census for state AIRs, and
all TSAP entities, and will continue to use these areas to provide data from the American
Community Survey (ACS) through the coming decade. Meaningful statistical data from
the 2010 Census and ACS provide tribes and other data users with a tool to help them
make informed decisions and plan for community services. More information about the
background and components of these geographic areas can be found in the Federal
Register notice Vol. 73, No. 221 / Friday, November 14, 2008, page 67470. This notice
can also be accessed from our TSAP webpage at:
http://www.census.gov/geo/www/tsap2010/tsap2010.html
These guidelines explain the background, criteria and complete instructions for updating
and delineating state AIRs using paper maps. The topics covered are:
ƒ
ƒ
ƒ
ƒ

Background on the State Reservation Program
Tribes Eligible to Delineate State AIRs
Schedule
Required Materials

ƒ
ƒ
ƒ
ƒ
ƒ

State AIR Criteria
Procedures for Annotating Maps
Procedures for Transmitting Completed Submissions
Census Bureau Submission Review
Verification

Those wishing to participate in the SRP will have the option of updating or delineating
their state AIRs using paper maps or Census Bureau-provided Geographic Information
System (GIS) data, tools, shapefiles, and ESRI® extension specific to this program.
Participants who choose to submit changes using the digital method must have ArcGIS®
9.2 or 9.3. These guidelines provide instructions for the use of paper maps. There
are separate guidelines for the use of the ESRI extension which can be found on the data
disc.
The TSAP Extension, developed by the Census Bureau for ESRI’s ArcMap 9.2, provides
a suite of GIS data management and editing tools/commands designed for participants to
identify, delineate, and review statistical areas. Project inception, quality control, data
submission, and workflow administration are all included in the data management
features of the extension. In addition to the inherent functionality of the ArcGIS
software, the extension’s unique editing tools consist of geographic area assignment,
block boundary definition, tribal tract/tribal block group type attribution, as well as line
editing and polygon split/merge functions. The option of using either the TSAP
extension or the paper maps to submit changes is at the complete discretion of each tribe
as neither is preferred over the other by the Census Bureau. However, depending on the
number anticipated updates and/or their complexity, you might consider using the TSAP
extension which offers you the ability to view population density within American Indian
statistical areas and allow you to more clearly add or remove area or adjust boundaries.
If you are interested in using this GIS application to submit your boundaries and you
have ArcGIS 9.2 or 9.3 software, but did not receive the ArcGIS extension software or
digital data files along with your materials, please contact your RCC 1 . You may also
contact the RCC staff to ask other questions or to arrange for training.
Disclosures to Respondents
The Geography Division manages programs to continuously update features, boundaries,
addresses, and geographic entities in the Master Address File / Topologically Integrated
Geographic Encoding and Referencing System (MAF/TIGER) database (MTdb) that is
used to support programs and to conduct the census and surveys. The TSAP program was
developed to give tribes the opportunity to review and update, if necessary, statistical
tribal entities for use in tabulating and publishing data from the 2010 Census, the
American Community Survey, and other surveys.
Public reporting burden for this collection of information is estimated to average 48 hours
per respondent, including time for reviewing instructions, assembling materials,
organizing and reviewing the information, and reporting any needed changes. We
anticipate that an estimated 650 participants will respond. Remaining entities may be
1

RCC contact information can be found in Appendix C

2

worked by Census Bureau regional staff. For larger areas or areas with many changes,
however, the respondent burden may be 180 hours or longer to complete. Please send
comments regarding this burden estimate or any other aspect of this collection of
information, including suggestions for reducing this burden to:
Paperwork Project
0607-0795
U.S. Census Bureau
4600 Silver Hill Road
Room 3K138
Washington, D.C. 20233
You may e-mail comments to Paperwork@census.gov. Use “Paperwork Project 06070795” as the subject.
Responses to this survey are voluntary. The authority for conducting these activities is
covered under the legal authority of Title 13 U.S.C. Sections 141 and 193.
No agency may conduct and no person may be required to respond to a collection of
information unless it displays a valid Office of Management and Budget (OMB) approval
number. The OMB approval number for this information collection is 0607-0795.

2. Background on the State Reservation Program
The 1890 Census was the first in which American Indian data were collected and
presented for individual AIRs. The Census Bureau began to report data systematically
for a variety of American Indian Areas (AIAs) starting in 1980, when it identified and
presented data for a more complete inventory of AIRs. The Census worked with the
Bureau of Indian Affairs to identify boundaries for AIRs of federally recognized tribes,
and with state government officials to identify boundaries for state recognized AIRs, by
obtaining maps depicting their legally established boundaries.
The SRP occurs once before each decennial census, and is a survey of state AIRs for
those states with state-recognized tribes that are not also federally recognized. Its purpose
is to determine, solely for data collection and tabulation by the Census Bureau, the
complete and current inventory and the correct attributes (names, legal descriptions,
official status) and official, legal boundaries of the state AIRs in each state. Through the
State Reservation Program, the Census Bureau also accepts additions and updates to
features such as roads or rivers that serve as a boundary for the state AIR, as well as
address range break information at the boundaries.
As part of the 2010 Census, state officials will again have the opportunity to review and
update the boundaries of their existing state AIRs or to provide boundaries and other
attribute information for newly recognized state AIRs. If the state AIR official declines
or defers participation, the Census Bureau will use 2000 state AIR boundaries, to tabulate
2010 Census data.
2.1 Eligibility
3

In order to delineate a state AIR for the 2010 Census the tribe associated with the AIR
first must be state recognized. While the Bureau of Indian Affairs (BIA) serves as a
single source for determining which American Indian tribes are federally recognized,
state recognition varies by state. Some states have unique laws that recognize specific
tribes while other states have established a formal process by which tribes apply for state
recognition. State AIRs and their legal boundaries are established pursuant to state law.
Prior to the decennial census and before implementing the state reservation program, the
Census Bureau sends a letter to the governor of each state requesting a list of any staterecognized tribes that are not also federally recognized, and requesting appointment of a
liaison to work with the state recognized tribes and the Census Bureau on geographic
programs. State recognition of a tribe is determined by each respective state government
and conveyed to the Census Bureau by the governor’s appointed liaison. The Census
Bureau will work with the state’s liaison to ascertain a tribe’s status if contacted directly
by a tribe who is claiming state recognition but has not been included on the state’s list of
recognized tribes.
As the liaison for both the SRP and the TSAP, the Census Bureau will work with you to
determine which tribes are eligible for delineating a SDTSA. The list of eligible staterecognized tribes for each individual state will change if new tribes are recognized and
reported to the Census Bureau by that state’s liaison on or before January 1, 2010. The
current list is provided in Appendix A.
2.2 Schedule
In October 2008, the Census Bureau mailed formal invitation letters to state liaisons.
These guidelines and accompanying paper maps required to complete the work are
scheduled to arrive in January 2009. The state liaison will have 120 days from the date
they receive SRP materials to complete a review and submit state AIR delineations or
updates to the RCC. In late 2009, after the Census Bureau has reviewed and incorporated
your delineations into our geographic database, you will receive new maps or digital files
so that you can verify that we have inserted your boundaries correctly. If you have
questions regarding your delineation or submission, assistance will be available from
geographers at your RCC. The Census Bureau strongly encourages you to work with
tribal officials throughout this process.
2.3 Program Materials
If a state has a Census 2000 state AIR(s), the Census Bureau’s RCC will provide maps
depicting the Census 2000 boundary for each state AIR within a one-mile fringe area. If
your updates include area outside of the fringe area, please contact your RCC for
additional maps. If one or more of your state recognized tribes did not have a state AIR
delineated for 2000, but they do have a legally defined reservation that you want to
provide boundaries for 2010, the RCC will work with you to provide map coverage.
County-based maps will be used for this purpose.
The paper map types you receive will depend on the size and mapping complexity of
your state AIR. A state AIR that is smaller in land area may only receive a parent map
4

sheet. State AIRs with large land area may receive an index map, a series of parent maps,
and a number of inset maps. An index map shows the complete state AIR with gridlines
defining specific areas shown on each parent map. A parent map shows a detailed
version of a single grid box from the index map, and an inset map shows finer details of
any areas within the parent map where the feature network is too dense to represent
clearly at the map scale of the parent sheet. You can think of the inset map as a “blowup” of a specific area.

Figure 1: Example of index, parent and inset maps

Figure 2: Tribal areas symbology on maps
The Census Bureau requests that participants use a pencil with red lead to annotate state
AIR boundaries on the paper maps provided. Procedures for annotating the paper maps
are detailed in section 4.
2.4 Boundary Feature Updates

5

The Census Bureau has spent the last six years enhancing the spatial accuracy of the
roads in our database system. The local files used during this project were required to
have an overall average accuracy of 7.6 meters with some files having better accuracy.
Although much of the street network is vastly improved, as you work with our maps you
may notice that in some counties the street and boundary features look distorted. A line
that should be straight may have a noticeable kink or pointed shape. The Census Bureau
is working to correct these problems, and if you need to use a feature that is distorted in
our maps follow the guidelines below.
The Census Bureau is also now moving forward with our 2010 Census field canvassing
and collection activities. This means that we are no longer processing realignments to
our street network. What is critical for the success of the 2010 Census data tabulation is
the location of roads relative to the tabulation entity boundary. As long as the road is
within the correct entity, the population and housing will be properly reported. The
guidelines below explain what updates are acceptable as part of the SRP.
It is critical that participants understand that the SRP is not intended for street feature
updates except where a boundary follows a road (or other visible feature such as a
stream) and the road is not reflected in our file. For this reason the Census Bureau can
not accept street (or other) feature updates that do not follow the guidelines below:
2.4.1 Guidelines for Updating Features
1. If a road is missing and it forms the boundary for the area you are defining, add
the road and provide the name.
2. If you can not correctly delineate the boundary for an entity you are updating
because the feature you need to follow is incorrectly located, mislabeled or
distorted in the Census Bureau’s file, we request that you fix that feature only. In
addition, we request that you report the problem area to the Census Bureau
(through your RCC).
3. Do not add streets that are missing for an entire housing development (add only
streets that are needed to form a boundary). We will be adding new or missing
streets during our address canvassing operation which will occur in the spring and
early summer of 2009. The Census Bureau will provide verification materials to
each participant that returns their submission in the correct format and within the
allotted 120 days that will show the results of address canvassing. If these streets
are still missing at that time, we will accept these as adds.

3. Criteria
State AIR boundaries and names should be reported to the Census Bureau as they exist in
the legislation or treaty under which they were established. By definition, state AIR
boundaries cannot cross state lines unless the AIR and tribe is separately recognized in
each state. State AIRs may not include territory within federally recognized AIRs or off
reservation trust lands. Acceptance of boundary changes to state AIRs requires clear
legal documentation supporting any, and all, changes involving these boundaries. The
Census Bureau will identify each state AIR with the name submitted by the state liaison

6

providing the boundary for the area. For this reason, the state AIR name should reflect
the specific tribal name cited in the legal records establishing the state AIR.

4. Procedures
4.1 Annotating Maps
The Census Bureau strongly encourages SRP state liaisons to work closely with tribal
officials to review state AIRs.
4.1.1 Suggested procedures for reviewing and revising an existing state AIR:
1. Compare your source materials with the Census Bureau’s maps.
2. If you are satisfied with how the state AIR boundary is currently portrayed on the
Census Bureau’s maps, fill out and sign the form attached to the cover letter that
came with your materials indicating there is “no change” to the boundary. Return the
form to the RCC using the postage paid envelope provided.
3. If you need to change the state AIR boundary, cross out the old boundary with an “X”
using a pencil with red lead. Mark the ends of the deletion with red hatch marks (//).
4. Using a pencil with red lead, plot the revised boundaries on the Census Bureau’s map.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your state AIR. The Census Bureau will not
accept new road features at this time unless the road or other feature is
necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature. Then use the red lead pencil to highlight
the feature as a state AIR boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your state AIR
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact your RCC to
describe the location and nature of the problem.
5. On the paper map, “delete” any incorrect boundaries by drawing “X”s along the
boundary using the appropriate colored pencil.
6. Review the name of the 2000 state AIR. If the name is still appropriate for the state
AIR, make no annotation. If the name requires revision, cross out the old name and
clearly label the new name in red within the boundary of the state AIR.
4.1.2 Suggested procedures for delineating a new state AIR:
1. Compare your source materials with the Census Bureau’s map(s).
2. Using a pencil with red lead, plot the boundary on the Census Bureau’s map(s).
3. If a feature that is not on the census map(s) is required as the boundary of the state
AIR, use a black lead pencil to add and label the new feature and the red pencil to
highlight the feature as a state AIR boundary.
a. Please do not add street or other features unless you are adding a feature
that forms the boundary of your state AIR. The Census Bureau will not
accept new road features at this time unless the road or other feature is
7

necessary in order to delineate a boundary. Please use a pencil with black
lead to add and label this feature. Then use the red lead pencil to highlight
the feature as a state AIR boundary.
b. If a feature is incorrectly located, mislabeled or distorted on the Census
Bureau’s maps so that you cannot correctly delineate your state AIR
boundary using that feature, please draw your boundary (using the red lead
pencil) following the problematic feature and contact your RCC to
describe the location and nature of the problem.
4. Clearly label the name of the new State AIR in red within the boundary of the AIR.

Figure 3: In this example, area is being added to an existing State AIR.

8

Figure 4: In this example, area is being removed from the State AIR.
Acceptance of state AIR boundary changes to state AIRs requires clear legal
documentation supporting any and all changes involving these boundaries.
4.2 Transmitting completed submissions and Census Bureau review
Please return all maps and copies of relevant documentation describing the State AIR
boundary location in the same tube/box/envelope you received it in and be sure to use the
mailing label provided. The Census Bureau RCC geographic staff will verify that the
submitted state AIRs are complete, and that all legal documentation is provided. The
Census Bureau will contact you with any questions or concerns regarding your
submission.
4.3 Verification
If you return your submission within 120 days of receiving the maps and other materials,
the Census Bureau will provide you with a new map, which you can use to verify that the
Census Bureau staff inserted the boundary of the State AIR correctly. The verification
map will be provided in late 2009. At that time it would be possible for tribes to make
minor boundary corrections if necessary.

9

OMB No. 0607-0795: Approval Expires 03/31/09

Appendix A – American Indian and Alaska Native Tribe Areas Eligible for Delineation
Tribe Name

Waccamaw Indian People
Santee Indian Organization
Choctaw Apache Tribe
Pee Dee Indian Nation of Upper South
Carolina
Nansemond Indian Tribe
Pee Dee Tribe
Rappahannock Tribe
Upper Mattaponi Indian Tribe
Echota Cherokee Tribe
Little Shell Tribe of Chippewa Indians
Point-Au-Chen Tribe
United Houma Nation
Clifton Choctaw Tribe
Adai Caddo Tribe
Monacan Indian Nation
Beaver Creek Indians
Occaneechi Band of Saponi Nation
Four Winds Tribe
Cherokee Tribe of Northeast Alabama
Ramapough Lenape Indian Nation
Chickahominy Indians Eastern
Division
Nanticoke Lenni-Lenape Indians
Nanticoke Indian Tribe

Area Name

Census
Area
Code

Census 2000
Population

Census 2000
Housing Units

2010 Census Areas
Eligible for
Delineation

Regional
Census
Center

Tribal Area Placeholder
Tribal Area Placeholder
Apache Choctaw SDAISA
Tribal Area Placeholder

0
0
9515
0

0
0
23,459
0

0
0
13,671
0

SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Dallas
Charlotte

Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Echota Cherokee SDAISA
Tribal Area Placeholder
Tribal Area Placeholder
United Houma Nation SDAISA
Clifton Choctaw SDAISA
Adais Caddo SDAISA
Tribal Area Placeholder
Tribal Area Placeholder
Tribal Area Placeholder
Four Winds Cherokee SDAISA
Cherokee Tribe of Northeast
Alabama SDAISA
Ramapough SDAISA
Eastern Chickahominy SDAISA

0
0
0
0
9680
0000
0
9960
9630
9510
0
0
0
9720
9560

0
0
0
0
65,068
0
0
839,880
476
39,080
0
0
0
79,657
173

0
0
0
0
26,997
0
0
337,007
205
16,890
0
0
0
34,316
92

SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Charlotte
Charlotte
Atlanta
Denver
Dallas
Dallas
Dallas
Dallas
Charlotte
Charlotte
Charlotte
Dallas
Atlanta

9850
9675

892
104

262
42

SDTSA
SDTSA

Philadelphia
Charlotte

9835

12,316

2,959

SDTSA

Philadelphia

9830

22,683

17,594

SDTSA

Philadelphia

Nanticoke Lenni Lenape
SDAISA
Nanticoke Indian Tribe SDAISA

Haliwa-Saponi Tribe
Chickahominy Indian Tribe
Biloxi-Chitimacha
Confederation/Bayou LaFourche Band
Coharie Tribe
Piqua Shawnee Tribe
MaChis Lower Creek Tribe
Star Clan of Muscogee Creeks
Meherrin Tribe
Waccamaw Siouan Tribe
Cherokees of Southeast Alabama
United Cherokee Ani-Yun-Wiya
Nation
Lumbee Tribe
Person County Indians (Sappony)
Pamunkey Indian Tribe
Lower Muscogee Creek Tribe
MOWA Band of Choctaw Indians
Mattaponi Indian Tribe
Shinnecock Indian Nation
Paugussett Indian Nation
Powhatan-Renape
Hassanamisco Band of the Nipmuc
Nation
Paucatuck Eastern Pequot Indians
Schaghticoke Tribe
Poospatuck Indian Nation

Haliwa-Saponi SDAISA
Chickahominy SDAISA
Tribal Area Placeholder

9745
9580
0

8,272
3,313
0

3,384
1,311
0

SDTSA
SDTSA
SDTSA

Charlotte
Charlotte
Dallas

Coharie SDAISA
Tribal Area Placeholder
MaChis Lower Creek SDAISA
Star Musckogee Creek SDAISA
Meherrin SDAISA
Waccamaw Siouan SDAISA
Cherokees of Southeast Alabama
SDAISA
Tribal Area Placeholder

9635
0
9820
9880
9825
9970
9550

123,761
0
24,198
7,331
7,867
2,329
120,294

54,248
0
11,048
3,508
3,419
891
55,734

SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA
SDTSA

Charlotte
Atlanta
Atlanta
Atlanta
Charlotte
Charlotte
Atlanta

0

0

0

SDTSA

Atlanta

Lumbee SDAISA
Indians of Person County
SDAISA
Pamunkey (state) Reservation
Tama (state) Reservation
MOWA Choctaw (state)
Reservation
Mattaponi (state) Reservation
Shinnecock (state) Reservation
Golden Hill (state) Reservation
Rankokus (state) Reservation
Hassanamisco (state)
Reservation
Paucatuck Eastern Pequot (state)
Reservation
Schaghticoke (state) Reservation
Poospatuck (state) Reservation

9815
9760

474,100
1,919

184,305
811

SDTSA
SDTSA

Charlotte
Charlotte

9260
9400
9240

58
57
124

36
21
37

State Res.
State Res.
State Res.

Charlotte
Atlanta
Atlanta

9230
9370
9100
9330
9150

58
504
0
0
2

28
194
0
0
1

State Res.
State Res.
State Res.
State Res.
State Res.

Charlotte
New York
Boston
Philadelphia
Boston

9280

26

19

State Res.

Boston

9350
9300

9
283

4
104

State Res.
State Res.

Boston
New York

2

OMB No. 0607-0795: Approval Expires 03/31/09

Appendix B – Procedures for accessing population and housing unit
data from American FactFinder
1. Starting at the U.S. Census Bureau internet homepage, click on “American FactFinder”
within the list along the left side of the screen.

2. On the next page, you will see another list on the left side on the screen. Hover your
mouse over “Data Sets” and then click on “Decennial Census” in the menu that pops up.

2

3. On the next screen, you will have the option of choosing between several different data
sets along with a small description of what each one contains. In this example, we will
access tribal block group data. For block group population data, you should select the
first data set listed which is “Census 2000 Summary File 1.” You may want to scroll
through the other data sets to see what other information is available for your future
reference.

3

4. To extract data, you will now select a number of parameters to identify your area of
interest. Again, in this example we will access tribal block group data, but you can also
access data for reservations, off-reservation trust lands, tracts, blocks, an many other
geographic areas.

4

5. Finally, you will select the specific type of data within “Census 2000 Summary File 1”
that you are looking for. Remember that you may select multiple data types.

6. After clicking “Show Result” you will now see the data you have requested.

5

Appendix C - Regional Census Center’s Contact Information
Atlanta RCC: Geography
285 Peachtree Center Avenue NE
Marquis II Tower, Suite 1000
Atlanta, GA 30303-1230
Phone: (404) 332-2711
Fax: (404) 332-2787
E-mail: atlanta.geography@census.gov

Detroit RCC: Geography
300 River Place Drive, Suite 2950
Detroit, MI 48207
Phone: (313) 396-5002
Fax: (313) 567-2119
E-mail: detroit.geography@census.gov

Boston RCC: Geography
One Beacon Street, 7th Floor
Boston, MA 02108-3107
Phone: (617) 223-3600
Fax: (617) 223-3675
E-mail: boston.geography@census.gov

Kansas City RCC: Geography
2001 NE 46th Street, Suite LL100
Kansas City, MO 64116-2051
Phone: (816) 994-2020
Fax: (816) 994-2033
E-mail:
kansas.city.geography@census.gov

Charlotte RCC: Geography
3701 Arco Corporate Drive, Suite 250
Charlotte, NC 28273
Phone: (704) 936-4200
Fax: (704) 936-4225
E-mail: charlotte.geography@census.gov

Los Angeles RCC: Geography
9301 Corbin Avenue, Suite 1000
Northridge, CA 91324-2406
Phone: (818) 717-6701
Fax: (818) 717-6778
E-mail:
los.angeles.geography@census.gov

Chicago RCC: Geography
500 West Madison Street, Suite 1600
Chicago, IL 60661-4555
Phone: (312) 454-2705
Fax: (312) 448-1510
E-mail: chicago.geography@census.gov

New York RCC: Geography
330 West 34th street, 13th Floor
New York, NY 10001-2406
Phone: (212) 971-8800
Fax: (212) 971-8990
E-mail:
new.york.rcc.geography@census.gov

Dallas RCC: Geography
2777 N Stemmons Freeway, Suite 200
Dallas, TX 75207-2514
Phone: (214) 267-6920
Fax: (214) 267-6970
E-mail: dallas.geography@census.gov

Philadelphia RCC: Geography
1234 Market Street, Suite 340
Philadelphia, PA 19107-3780
Phone: (215) 717-1000
Fax: (215) 253-8001
E-mail:
philadelphia.geography@census.gov

Denver RCC: Geography
6950 W Jefferson Avenue, Suite 250
Lakewood, CO 80235-2032
Phone: (720) 475-3600
Fax: (720) 962-4606
E-mail:
denver.rcc.geography@census.gov

Seattle RCC: Geography
19820 North Creek Parkway N, Suite
100
Bothell, WA 98011
Phone: (425) 908-3010
Fax: (425) 908-3020
E-mail: seattle.geography@census.gov

6