BBSPV_GUPSWeb_ParticipantGuide_Final

Status: Original and derived artifacts are available for this document.

Download: docx | pdf | html

Instructions for Participating in the Block Boundary Suggestion Project Verification Using the Web Version of the Geographic Update Partnership Software 

January 2027

This page intentionally left blank.
Table of Contents
Introduction	ix
SECTION 1.	Block Boundary Suggestion Project Overview	1
SECTION 2.	Suggested Workflow	3
2.1	Linear Feature Review	3
2.2	Area Landmark Review	5
2.3	Legal Boundary Updates	5
2.4	Linear Feature Extension Review	6
2.5	Prototype Block Review	6
2.5.1	Block Size Review	7
2.5.2	Block Shape Review	7
2.6	Block Boundary Suggestion Flagging	8
2.6.1	Block Boundary Criteria	9
2.6.2	Assigning a “Must Hold” Flag	9
2.6.3	Assigning a “Do Not Hold” Flag	10
2.7	Block Area Grouping Delineation	10
2.8	Block Boundary Review and Verification	10
2.9	Potential Small Block Check	10
2.10	Boundary Review	11
2.11	Submitting Updates to the Census Bureau	11
SECTION 3.	Getting Started	12
3.1	Getting Started with GUPS Web	12
3.1.1	Accessing GUPS Web	12
3.1.2	Logging into GUPS Web	12
3.1.3	GUPS Web User Access Roles	13
3.1.3.1	Project Owner	13
3.1.3.2	Project Collaborator	13
3.1.3.3	Project Reviewer	14
3.1.3.4	Project Viewer	14
3.2	GUPS Web Dashboard	14
3.2.1	Map Management	15
3.2.2	Recent Projects	15
3.2.3	Opening a Project	15
3.2.4	User Management Module	16
3.2.4.1	Invite Users	16
3.2.4.2	Manage Users	18
3.3	GUPS Web Tools	19
3.3.1	GUPS Web Navigation Bar	20
3.3.2	Quick Tools	22
3.3.3	Tools	23
3.3.3.1	View Tools	23
3.3.3.2	Imagery Tools	25
3.3.3.3	Selection Tools	26
3.3.3.4	Edit Tools	27
3.3.3.5	Review Tools	28
3.3.4	Layer Legend	29
3.3.4.1	Manual BBSP Change Layers	31
3.3.4.2	Attribute Table Tools	31
3.3.5	Import/Export Tools	33
3.3.6	Project Management Tool	34
3.3.7	Notification Button	35
3.3.8	User Count Button	35
SECTION 4.	BBSP Update Activities in GUPS Web	36
4.1	Linear Feature Review	36
4.1.1	Adding a Linear Feature	37
4.1.2	Deleting a Linear Feature	38
4.1.3	Restoring a Deleted Linear Feature	39
4.1.4	Modifying Attributes of a Linear Feature	40
4.1.5	Splitting a Linear Feature	40
4.2	Area Landmark Review	41
4.2.1	Modify Area Feature Tool	41
4.2.2	Boundary Correction by Adding Area to Area Landmark	43
4.2.3	Boundary Correction by Removing Area from an Area Landmark	45
4.2.4	Creating a New Area Landmark	47
4.2.5	Deleting an Area Landmark	48
4.2.6	Modifying the Attributes of an Area Landmark	49
4.3	Legal Changes	50
4.3.1	Creating Legal Changes with the Modify Area Feature Tool	50
4.3.2	Adding Area through Legal Changes (Annexation)	52
4.3.3	Removing Area through Legal Changes (Deannexation)	54
4.3.4	Boundary Correction by Adding Area to a Legal Entity	56
4.3.5	Boundary Correction by Removing Area from a Legal Entity	58
4.3.6	Adding a New Legal Entity	59
4.3.7	Deleting a Legal Entity	61
4.3.8	Modifying the Attributes of a Legal Entity	63
4.4	Linear Feature Extension Review	64
4.4.1	Verify Linear Feature Extension Tool	65
4.5	Prototype Block Review	66
4.5.1	Block Size Review	66
4.5.2	Block Shape Review	67
4.6	Block Boundary Suggestion Flagging	67
4.6.1	Block Boundary Criteria	68
4.6.2	“Must Hold” Flags	71
4.6.2.1	Assigning “Must Hold” Flags	72
4.6.3	“Do Not Hold” Flags	73
4.6.3.1	Assigning “Do Not Hold” Flags	73
4.6.4	Removing a “Must Hold” or “Do Not Hold” Flag	74
4.6.5	Digitizing a New Linear Feature Extension	74
4.7	Block Area Grouping Delineation	75
4.7.1	Creating a Block Area Grouping	75
4.7.2	Deleting a Block Area Grouping	75
4.8	Block Boundary Review	76
4.8.1	Performing Verification	77
4.9	Potential Small Block Check	78
4.10	Boundary Review	79
4.11	Submitting Updates to the Census Bureau	80
4.11.1	Export Tools	81
4.11.1.1	Submit to Census	81
4.11.1.2	Submit for Review	83
4.11.1.3	Download Project Files	83
4.11.1.4	Export Map	84
Appendix A	Partnership Shapefile Names and Layouts	A-1
Appendix B	MTFCC Descriptions	B-1


List of tables
Table 1: 2030 Census Planned Tabulation Block Boundaries by MAF/TIGER Feature Class Code (MTFCC)	1
Table 2: MTFCCs for Linear Feature Review	4
Table 3: Block Size Indicator Values	7
Table 4: Description of Block Boundary Flagging Fields	8
Table 5: GUPS Web User Access Roles	13
Table 6: How to Invite a User to GUPS Web Project	17
Table 7: How to Utilize the Manage Users Interface	19
Table 8: GUPS Web Navigation Bar	20
Table 9: Quick Tools	22
Table 10: View Tools	24
Table 11: Imagery Tools	25
Table 12: Selection Tools	26
Table 13: Edit Tools	27
Table 14: Review Tools	29
Table 15: Attribute Table Tools	32
Table 16: How to Search the Attribute Table	33
Table 17: Import/Export Tools	34
Table 18: How to Add a Linear Feature	37
Table 19: How to Delete a Linear Feature	38
Table 20: How to Restore a Deleted Linear Feature	39
Table 21: How to Modify a Linear Feature	40
Table 22: How to Split a Linear Feature	41
Table 23: How to Add Area to an Area Landmark	44
Table 24: How to Remove Area from an Area Landmark	46
Table 25: How to Create a New Area Landmark	47
Table 26: How to Delete an Area Landmark	48
Table 27: How to Modify an Area Landmark	50
Table 28 How to Perform an Annexation	52
Table 29: How to Perform a Deannexation	55
Table 30: How to Add Area to a Incorporated Place or MCD	56
Table 31: How to Remove Area from an Incorporated Place	58
Table 32: How to Add a New Incorporated Place or MCD	60
Table 33: How to Delete An Incorporated Place	62
Table 34: How to Modify the Attributes of an Incorporated Place or MCD	64
Table 35: How to Review Linear Feature Extensions	65
Table 36: Block Size Indicator Values	66
Table 37: Description of Block Boundary Flagging Fields	67
Table 38: Block Boundary Flagging Symbology	68
Table 39: How to Apply a "Must Hold" Flag	72
Table 40: How to Apply a "Do Not Hold" Flag	73
Table 41: How to Remove a "Must Hold" or "Do Not Hold" Flag	74
Table 42: How to Add a Linear Feature Extension	74
Table 43: How to Create a Block Area Grouping	75
Table 44: How to Delete a Block Area Grouping	76
Table 45: How to Review Block Boundary Flags	77
Table 46: How to Perform Verification	78
Table 47: How to Review Potential Small Block Output	79
Table 48: How to Review Boundary Changes	80
Table 49: How to Submit a Project to Census	82
Table 50: How to Download Project Files	83
Table 51: How to Export a Map	85

List of Figures
Figure 1: Suggested Workflow	3
Figure 2: Workflow for Accessing GUPS Web	12
Figure 3: GUPS Web Dashboard Button	14
Figure 4: GUPS Web Dashboard Interface	14
Figure 5: Example of Access Denied Message	15
Figure 6: Example of a New Project Opened in GUPS Web (Map View)	16
Figure 7: User Management Module Button	16
Figure 8: Invite Users Interface (County-Level)	17
Figure 9: Invite Users Interface (State-Level)	18
Figure 10: Manage Users Interface	18
Figure 11: GUPS Web Map View with Tools Identified	20
Figure 12: Quick Tools Button	22
Figure 13: Tools Button	23
Figure 14: View Tools Option	23
Figure 15: Imagery Tools Option	25
Figure 16: Selection Tools Option	26
Figure 17: Edit Tools Option	27
Figure 18: Review Tools Option	28
Figure 19: Layer Legend Button	29
Figure 20: Layer Legend Interface	30
Figure 21: Import/Export Button	33
Figure 22: Import/Export Interface	34
Figure 23: Project Management Button	34
Figure 24: Delete Project Button	35
Figure 25: Notification Button	35
Figure 26: User Count Button	35
Figure 27: Add Linear Feature Button	37
Figure 28: Add Linear Feature Dialog Window	37
Figure 29: Delete/Restore Linear Feature Button	38
Figure 30: "Must Hold" Delete Warning	39
Figure 31: Delete Linear Feature Warning	39
Figure 32: Modify Linear Feature Button	40
Figure 33: Modify Linear Feature Interface	40
Figure 34: Split Linear Feature Button	40
Figure 35: Modify Area Feature Tool Button	41
Figure 36: Modify Area Feature Interface	42
Figure 37: Modify Area Feature Button	43
Figure 38: Modify Area Feature Tool Boundary Correction- Add Area Interface	44
Figure 39: Modify Area Feature Tool Boundary Correction- Remove Area Interface	45
Figure 40: Modify Area Feature Tool New Area Landmark Interface	47
Figure 41: Modify Area Feature Tool Delete Area Landmark Interface	48
Figure 42: Modify Area Feature Tool Modify Attributes Interface	49
Figure 43: Modify Area Feature Tool Interface with Legal Fields	51
Figure 44: Modify Area Feature Tool Annexation Interface	52
Figure 45: Modify Area Feature Tool Deannexation Interface	54
Figure 46: Modify Area Feature Legal Update Boundary Correction-Add Area Interface	56
Figure 47: Modify Area Feature Legal Update Boundary Correction-Remove Area Interface	58
Figure 48: Add a New Legal Entity Interface	59
Figure 49: Delete a Legal Entity Interface	61
Figure 50: Modify Attributes of a Legal Entity Interface	63
Figure 51:Verify Linear Feature Extension Tool Button	65
Figure 52: Verify Linear Feature Extension Tool Interface	65
Figure 53: Feature Flagging Tool Button	72
Figure 54: Feature Flagging Tool Interface	72
Figure 55: Add Linear Feature Extension Button	74
Figure 56: Create Block Area Grouping Button	75
Figure 57: Delete Block Area Grouping Button	75
Figure 58: Block Boundary Review Button	76
Figure 59: Block Boundary Review Interface	76
Figure 60: Block Boundary Review Interface Verification Filter Options	78
Figure 61: Potential Small Block Check Button	79
Figure 62: Potential Small Block Check Interface	79
Figure 63: Boundary Review Button	79
Figure 64: Boundary Review Selection Interface	80
Figure 65: Boundary Review Tool Interface	80
Figure 66: Import/Export Button	81
Figure 67: Submit to Census Interface	82
Figure 68: Download Project Files Interface	83
Figure 69: Export Map Interface	84


Introduction
Public Law (P.L.) 94-171 stipulates that the U.S. Census Bureau work in a nonpartisan manner with the states to identify and provide the small-area population counts necessary for legislative redistricting. The Census Bureau is required to provide these counts within one year of Census Day, to the governor and the officers or public bodies responsible for redistricting in each state. For the 2030 Census, the Census Bureau must deliver the counts by April 1, 2031.
The Redistricting & Voting rights Data Office (RVDO) implements the requirements of P.L. 94-171 through the Redistricting Data Program (RDP) which is organized into five phases for the 2030 Census:
	Phase 1: Block Boundary Suggestion Project (BBSP) 
	Phase 2: Voting District Project (VTDP)
	Phase 3: Delivery of the 2030 Redistricting Data 
Phase 4: Collection of Post-2030 Census Congressional and State Legislative District Plans 
Phase 5: Review of the 2030 Census Redistricting Data Program and Recommendations for the 2040 Census
This document pertains to the second cycle of Phase 1: Block Boundary Suggestion Project (BBSP) called Block Boundary Suggestion Project Verification (BBSPV) of the RDP. Through the BBSP, nonpartisan liaisons designated by the governors and legislative leadership in each state, the District of Columbia, and the Commonwealth of Puerto Rico, can influence the delineation of the 2030 Census tabulation blocks (i.e., blocks). 
Participants influence block delineation by suggesting linear features (e.g., roads, rivers, railroads, property lines) or edges to be held or not held as block boundaries. The Census Bureau refers to this as suggesting block boundaries, or setting or flagging ‘Must Hold’ or ‘Do Not Hold’ on the features. Participants can also influence block boundaries by adding and deleting linear features or edges, and by suggesting updates to boundaries for other census geographies including incorporated places, minor civil divisions (MCDs), counties, and area landmarks, all of which are potential block boundaries.
    • SECTION 1 of the document provides the conceptual overview of the planned 2030 Census tabulation block boundaries. 
    • SECTION 2 of the document contains the suggested workflow, update activities including verification, and quality control activities.
    • SECTION 3 of the document contains instructions for getting started with the GUPS Web application. 
    • SECTION 4 of the document contains details on performing BBSP Update Activities and how to submit files to the Census Bureau via GUPS Web.

    SECTION 1. Block Boundary Suggestion Project Overview
Block boundaries primarily follow visible features, such as roads and rivers, as well as any edges that bound legal, administrative, or statistical geographic areas or selected area landmarks stored in the Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). Census blocks nest within all other tabulated census geographic entities and are the smallest tabulation geography published by the decennial census.
Table 1: 2030 Census Planned Tabulation Block Boundaries by MAF/TIGER Feature Class Code (MTFCC) lists the feature and boundary types currently planned as 2030 Census block boundaries. If state participants flag these features as a “Do Not Hold” (i.e., request that the feature or boundary type not become a 2030 block boundary), the Census Bureau may not accept the “Do Not Hold” suggestion.
Table 1: 2030 Census Planned Tabulation Block Boundaries by MAF/TIGER Feature Class Code (MTFCC)
MTFCC
Description
MTFCC
Description
G2120
Hawaiian  
G5200
Congressional District
G2130
Alaska Native Village Statistical Area
G5210
State Legislative District (Upper Chamber)
G2140
Oklahoma Tribal Statistical Area
G5220
State Legislative District (Lower Chamber)
G2150
State-designated Tribal Statistical Area
G5240
Voting District
G2160
Tribal Designated Statistical Area
G5400
Elementary School District
G2170
American Indian Joint Use Area
G5410
Secondary School District
G2200
Alaska Native Regional Corporation
G5420
Unified School District
G2300
Tribal Subdivision
G6330
Urban Growth Area
G2400
Tribal Census Tract
G6500
Military Installation
G2410
Tribal Block Group
K2181
National Park Service Land
G4000
State or State Equivalent
K2182
National Forest or Other Federal Land
G4020
County or County Equivalent
K2540
University or College
G4040
County Subdivision
K1235
Juvenile Institution
G4060
Sub-Minor Civil Divisions
K1236
Local Jail or Detention Center
G4110
Incorporated Place

K1237
Federal Penitentiary, State Prison, or Prison Farm
G4120
Consolidated City
K1238
Other Correctional Institution
G5020
Census Tract
S1100
Primary Road
G5035
Block Area Grouping
S1200
Secondary Road
While primary and secondary roads (i.e., MTFCCs S1100 and S1200) are planned block boundaries, other linear features, such as local roads, alleys, railroads, and perennial water, may or may not qualify as block boundaries based on the established criteria. These features can be flagged as “Must Hold” or “Do Not Hold” block boundaries.
Participants can determine whether a feature is a planned block boundary by the feature’s value in the Census Block Boundary Flag (CBBFLG) field in the attribute table of the Edges shapefile. A CBBFLG value of “4” indicates the feature is a planned 2030 block boundary, while a CBBFLG value of “9” indicates the feature is ineligible as a 2030 block boundary. A CBBFLG value of “1” indicates the feature was flagged as a “Must Hold” and a CBBFLG value of “2” indicates the feature was flagged a “Do Not Hold” during the delineation cycle of BBSP conducted in 2026. When the CBBFLG field is null, its status has not yet been determined. This indicates that it is a good candidate for a “Must Hold” or a “Do Not Hold” flag.

    SECTION 2. Suggested Workflow
Figure 1 depicts the suggested workflow for reviewing and updating Census Bureau data for the BBSP and BBSP Verification. This section outlines the activities associated with each of the workflow process boxes. 
Work is performed at a county level and should be submitted to the Census Bureau on a flow basis, as each county is completed. Submitting work on a flow basis permits the RVDO and the Census Bureau to review the files early in the process, provide feedback as necessary, and facilitate file processing. 

Figure 1: Suggested Workflow
Note:	The review process may be different for each state. The number in parentheses refers to the section where the action is described.
        2.1 Linear Feature Review
Review the Census Bureau’s linear features (edges shapefile) to determine whether there are features that need to be added or deleted. Pay particular attention to any areas that have experienced population growth, and where there may be new housing or subdivisions not reflected in the Census Bureau’s geospatial data. 

Table 2: MTFCCs for Linear Feature Review
MTFCC
Description
MTFCC
Description
C3024
Levee
L4165
Ferry Crossing
C3027
Dam
P0001
Nonvisible Legal/Statistical Boundary
H3010
Stream/River
P0002
Perennial Shoreline
H3013
Braided Stream
P0003
Intermittent Shoreline
H3020
Canal, Ditch, or Aqueduct
P0004
Other non-visible bounding edge (e.g., Census water boundary, boundary of area feature)
K2432
Pier/Dock
S1100
Primary Road
K2459
Runway/Taxiway
S1200
Secondary Road
L4010
Pipeline
S1400
Local Neighborhood Road, Rural Road, City Street
L4020
Power Line
S1500
Vehicular Trail (4WD)
L4110
Fence Line
S1630
Ramp
L4121
Ridge Line
S1640
Service Drive usually along a limited access highway
L4125
Cliff/Escarpment
S1730
Alley
L4130
Point-to-Point Line
S1740
Private Road for service vehicles (logging, oil fields, ranches, etc.)
L4140
Property/Parcel Line
S1820
Bike Path or Trail
R1011 
Railroad Feature (Main, Spur, or Yard)
R1051
Carline, Streetcar Track, Monorail, Other Mass Transit Rail
R1052
Cog Rail Line, Incline Rail Line, Tram


The basic groupings of the MTFCCs are as follows:
    • S-class = Roads.
    • R-class = Railroads.*
    • P-class = Nonvisible Features.*
    • L-class, K-class, and C-class = Other Linear Features. *
    • H-class = Hydrography.*
The Census Bureau will also accept attribute updates (name and classification code) for MTFCCs in the S-class (roads). Added road features (except for highway ramps) require a feature name. If a road feature does not have a name but is still needed, use the name “BBSP Road”. Your update will be reviewed and adjudicated by Census staff during processing. 
*These types of linear features should only be added if desired as a block boundary and therefore must have a “Must Hold” flag assigned to them when submitted to the Census Bureau.
Note: 	Please be aware that the Census Bureau will not process the wholesale spatial realignment of features merely to conform to an alternate spatial accuracy. If a feature is in the incorrect location in the Census Bureau’s feature network, mark the feature for deletion and then add it in the correct location. Take this action only if most of the realigned feature is more than 7.6 meters from the existing feature or interferes (is topologically incorrect) with relationships to other features.
        2.2 Area Landmark Review
The Census Bureau accepts updates to area landmarks (e.g., prison areas, state parks, and cemeteries) as part of the BBSP. Allowable updates include:
    • Boundary corrections (adding and removing area).
    • Creating a new area landmark.
    • Removing an area landmark.
    • Changing or adding a name of an area landmark.
    • Changing or updating the MTFCC of an area landmark.
If the state plans to reallocate prisoners during redistricting, consider reviewing the existing area landmarks with MTFCCs K1235, K1236, K1237, and K1238, which represent areas with potential prison populations, or create new landmarks for those types of areas.
To report updates to water area features, such as lakes or reservoirs, please contact the RVDO at 301-763-4039 or at <[email protected]>.
        2.3 Legal Boundary Updates
Participants may provide legal boundary updates (annexations, deannexations, incorporations and disincorporations), along with their supporting documentation, and boundary corrections. The Census Bureau will assume the responsibility for reconciling the updates with the appropriate governments as part of the Boundary and Annexation Survey (BAS).
Participants may submit legal boundary updates for counties, MCDs, and incorporated places. Although legal documentation (effective date, authorization type, and documentation number) is not required for boundary updates submitted through the BBSP, the Census Bureau strongly encourages the submission of documentation to expedite our ability to reconcile and process any legal updates reported. Annexations and deannexations without supporting documentation should be submitted as boundary corrections. To report a new county, MCD, or incorporated place without supporting documentation or to delete an existing MCD or county, please call the RVDO at 301-763-4039 or at <[email protected]>.
Note:	The Census Bureau cannot guarantee these updates will be made, as we may first have to adjudicate and receive concurrence for the updates from the official BAS contact.
        2.4 Linear Feature Extension Review
All block boundary suggestions are contingent upon the lines intersecting to form a closed polygon at the time the Census Bureau creates blocks. As a result, all block boundary “Must Hold” flags when combined with the features identified as planned holds, should form a closed polygon.
For the 2020 Census, BBSP participants could place a “Must Hold” flag on an existing feature that did not form a closed a polygon. To do this, the participant also added a feature extension to close the polygon and create a potential new block. Those 2020 feature extensions are included in the 2030 BBSP files for review and update.
The Census Bureau requests that participants review the 2020 linear feature extensions to determine if they are still needed. Please be aware that to hold an old 2020 feature extension as a 2030 block boundary, participants must take an action to again classify that extension as a “Must Hold” suggestion, as described in section 4.6.2.
During the linear feature extension review, participants may:
    • Hold the old 2020 linear feature extension as a 2030 block boundary suggestion along with the feature from which the extension originates. If possible, when applying a “Must Hold” to a feature extension, review the extension against cadastral data or imagery to ensure it is in the most appropriate location. 
    • Flag the old 2020 feature extension as a "Do Not Hold". Some linear features cannot be deleted from the MTS. By flagging the old 2020 linear feature extension as a "Do Not Hold", it will help the Census Bureau ensure the feature extension no longer serves as a block boundary. 
    • Ignore the 2020 linear feature extension. If no action is taken on a 2020 linear feature extension, the Census Bureau may delete the old extension or if kept, decide whether to hold the extension and the feature associated with it as a 2030 block boundary or not.
        2.5 Prototype Block Review
The prototype block shapefile shows what the planned 2030 blocks would look like if created using the geography as it exists at this time, which include any previously submitted and accepted “Must Hold” or “Do Not Hold” flags. The prototype block shapefile is a useful tool for participants to review their potential block geography and then use the “Must Hold” and “Do Not Hold” flags to make targeted updates. The prototype blocks for BBSPV will be different than the prototype block shapefiles provided for BBSP and will reflect the updates made during BBSP as well as other geographic update programs (e.g., Boundary and Annexation Survey).

            2.5.1 Block Size Review
In the prototype block shapefile, the Census Bureau assigned a block size indicator (BLKZIND field) to each block based on the range of the estimated number of housing units in the prototype block. These values can be used to identify both potentially small population blocks and large population blocks to split or merge using the “Must Hold” and “Do Not Hold” flags.
Note:	Although discrete numbers have been established to assign each block a size value, the actual number of housing units in a block is approximate.
Block size indicators range from “A” through “I”, with “A” blocks having the most housing units and “I” having the least. Prototype blocks estimated to contain no housing units are assigned an indicator letter of “Z.”
Table 3: Block Size Indicator Values
Indicator
Approximate Number of Housing Units
A
Greater than 2,000
B
1,600-1,999
C
1,200-1,599
D
1,000-1,199
E
700-999
F
480-699
G
400-479
H
240-399
I
1-239
Z
Potential “0” housing unit block

            2.5.2 Block Shape Review
In the prototype block shapefile, the Census Bureau also calculated a shape index (SHAPEIDX) using a simple area to perimeter ratio method. The shape index value will be between 0 and 1. The closer the value to 1, the more compact the block. The closer the value to 0 the less compact the block. These values can be used to help identify less compact blocks to see if their shape would interfere with the ability to conduct redistricting (e.g. long sinuous water bodies). Then, the “Must Hold” and “Do Not Hold” flags can be used to remedy this if it is an issue.
        2.6 Block Boundary Suggestion Flagging
BBSP participants can assign BBSP flags to features--suggest they be held or not held as block boundaries--in the BBSP_2030 field of the edges shapefile. Using established criteria for delineating tabulation blocks, the Census Bureau has identified features already planned as 2030 block boundaries, which have a CBBFLG value of “4” in the edges shapefile. Refer to Table 1 for the complete planned feature list. The planned block boundaries may change if the criteria change, or if a feature’s attributes are updated through other Census programs. 
The Census Bureau has identified features that are ineligible to be 2030 block boundaries with a CBBFLG value of “9” in the edges shapefile. There are also features with no block boundary status assigned (CBBFLG value is null). Participants are not required to assign a BBSP flag (e.g., “Must Hold” or “Do Not Hold”) to every feature in the file, nor should they.
Table 4: Description of Block Boundary Flagging Fields
Values
Description
BBSPFLG=1
2020 Participant Identified “Must Hold” Block Boundary.
BBSPFLG=2
2020 Participant Identified ”Do Not Hold” Block Boundary.
BBSPFLG=4
2020 Census Identified Planned Block Boundary.
BBSPFLG=9
2020 Census Identified Ineligible Block Boundary.
BBSP_2030=1
2030 Participant Identified “Must Hold” Block Boundary.
BBSP_2030=2
2030 Participant Identified “Do Not Hold” Block Boundary.
BBSP_2030=0
2030 Participant Identified “Must Hold” or “Do Not Hold” flag set during the initial BBSP Submission, now set for removal.
CBBFLG=1
2030 Participant Identified “Must Hold” Block Boundary (Populated by Census Bureau during processing of initial BBSP submission and corresponds to the value from the BBSP_2030 field when the Must Hold was applied and submitted.)
CBBFLG=2
2030 Participant Identified “Do Not Hold” Block Boundary (Populated by Census Bureau during processing of initial BBSP submission and corresponds to value from the BBSP_2030 field when the Do Not Hold was applied and submitted.)
CBBFLG=3
2030 Census Applied “Must Hold” Block Boundary.
CBBFLG=4
2030 Census Identified Planned Block Boundary.
CBBFLG=5
2030 Census Applied “Do Not Hold” Block Boundary.
CBBFLG=9
2030 Census Identified Ineligible Block Boundary.

            2.6.1 Block Boundary Criteria
All BBSP participant-provided 2030 Census “Must Holds,” i.e., BBSP_2030 = 1 or CBBFLG=1, combined with existing features and other planned block boundaries, must form closed polygons.
2030 Census planned block boundaries, i.e., CBBFLG = 4, are an indication of what the Census Bureau plans to use as a 2030 Census block boundary if they were defined today. The planned block boundaries may change if the criteria changes, or if the feature attributes are updated through other Census programs.
BBSP participant-provided 2030 Census “Do Not Holds”, i.e., BBSP_2030 = 2, will not be honored if the line they are placed on needs to be held for other purposes. For example, if a “Do Not Hold” flag was placed on an incorporated place boundary, the “Do Not Hold” flag would not be honored.
            2.6.2 Assigning a “Must Hold” Flag
Participants may assign a “Must Hold” flag to features to suggest them as 2030 block boundaries. Candidates for assigning a “Must Hold” flag are:
    • Newly added features.
    • Features not currently planned as block boundaries.
    • To ensure features planned as 2030 block boundaries are held should the Census Bureau change their “planned” status. 
Participants may wish to assign a “Must Hold” flag to features that are planned 2030 block boundaries in case the block definition criteria or feature classification codes change between when BBSP occurs and when the Census Bureau creates the 2030 Census blocks. Assigning a “Must Hold” flag to a planned block boundary feature will increase the likelihood that the feature will become a 2030 block boundary.
Be aware that assigning a “Must Hold” flag to a feature that is ineligible to be a block boundary or assigning a “Do Not Hold” flag to a feature that is planned to be a 2030 block boundary does not ensure that the Census Bureau will honor the request. The Census Bureau will re-evaluate the feature’s status based on the participant’s suggestion.
All “Must Hold” flags are contingent upon the features intersecting to form a closed polygon at the time the Census Bureau creates the 2030 blocks. 
To hold a feature as a 2030 block boundary when the feature does not form a closed polygon, add a feature extension to close the polygon. Feature extensions must meet the following criteria:
    • Extensions, combined with other features and planned holds, must form a closed polygon.
    • Extensions must be no longer than 300 feet. (If an extension needs to be longer than 300 feet, participants must provide justification.)
    • Extensions must be a straight line originating from the end of a road feature.
    • Extensions must terminate on a non-road feature, except for highways (i.e., extensions may terminate on highways – MTFCC S1100).
            2.6.3 Assigning a “Do Not Hold” Flag
Participants may assign “Do Not Hold” flags to features that they do not want to become 2030 block boundaries. Potential candidates for assigning a “Do Not Hold” flag may include:
    • Private roads, trails, and unimproved roads.
    • Hydrographic features with no area, shown as a single-line feature, such as streams or creeks.
    • Any feature creating unnecessary blocks, such as highway ramps, traffic circles, or cul-de-sacs shown as open circles or “lollipops” in the Census geospatial files, and similar features.
Be aware that assigning a “Do Not Hold” flag to a feature that is a 2030 planned block boundary may not be honored if that boundary is needed to meet other Census criteria or program needs. For example, if a “Do Not Hold” flag is placed on an incorporated place boundary, the “Do Not Hold” will not be honored.
        2.7 Block Area Grouping Delineation
During the 2030 Census block creation, the Census Bureau will automatically group islands to form a single block if they have no road features and the islands fall within a 5-kilometer radius. Participants may also choose to group specific islands to create a single 2030 Census block, called a Block Area Grouping (BAG). The criteria for creating a BAG are as follows:
    • BAG must consist of two or more islands.
    • BAG perimeter must be entirely over water.
    • BAGs cannot overlap.
    • BAGs cannot cross the boundary of other tabulation geographies, such as county or incorporated place boundaries.
BAG delineation is optional, and most appropriate for states with hydrographic areas that contain many islands.
        2.8 Block Boundary Review and Verification
Block boundary suggestions must be reviewed at least once before submitting updates to the Census Bureau. The Block Boundary Review Tool allows participants to systematically navigate to features on the map, by 2030 “Most Hold” and “Do Not Hold” flags, for review and further update if desired. 
Linear features flagged as a “Must Hold” or “Do Not Hold” in the initial BBSP phase can be verified during the block boundary review process. 
        2.9 Potential Small Block Check
The Potential Small Block Check reviews the edges within the project and returns a list of potential small blocks that exist in the project based on the planned and suggested block boundaries. 
All small blocks under 3,000 square meters are identified and listed. Within this list of potential small blocks: 
    • Type “ - “: Small blocks under 3,000 square meters that are created by the planned block boundaries and do not include “Must Hold” flags. 
    • Type A: Small blocks of 500 square meters or less that have one or more bounding edges where a "Must Hold" flag is involved. 
    • Type B: Small blocks of 500.1 square meters to 3,000 square meters that have one or more bounding edges where a "Must Hold" flag is involved. 
If the small blocks are unwanted or unintentional, they can be adjusted through Block Boundary Suggestion Flagging (i.e., remove the “Must Hold” flag from a bounding edge or apply a “Do Not Hold” flag). Potential small blocks must be reviewed at least once before submitting updates to the Census Bureau.
        2.10 Boundary Review
The Boundary Review Tool allows updates to area landmarks and legal entities (incorporated places and MCDs) to be viewed. Records can be selected to navigate from update to update. In addition, legal information for annexations and deannexations can be added via the Boundary Review Tool. 
        2.11 Submitting Updates to the Census Bureau
The Census Bureau conducts the RDP activities through the official liaison appointed by the governor and legislative leadership of the state. The official liaisons are responsible for making BBSP updates and submitting the projects to the Census Bureau. However, the official liaisons have two options for designating technical liaisons to assist them in making BBSP updates on behalf of the state.
    • Option 1. Official liaisons can formally designate technical liaisons who are able to perform geographic updates and submit completed updates to the Census Bureau on their behalf. Official liaisons should reach out to the RVDO at 301-763-4039 or <[email protected]> to make technical liaison designations.
    • Option 2. Official liaisons can delegate work to designees who perform the updates and submit the updates back to the official liaison. The official liaison will submit the work to the Census Bureau if they approve the work. If the official liaison determines that BBSP work completed by a designee requires changes or additional work, it is the official liaison's responsibility to decide whether to make the changes or return the project to their designee for further updates.
The liaison responsible for submitting updates to the Census Bureau should submit completed, county-level files on a flow basis to the Census Bureau directly through GUPS Web. Do not hold files to submit all at once. Submit files as they are completed, especially at the beginning of the update period, so that the Census Bureau can provide feedback if there are errors, omissions, or other concerns.
    SECTION 3. Getting Started
        3.1 Getting Started with GUPS Web
GUPS Web is a user-friendly geographic information system (GIS) that is customized for each of the Census Bureau’s geographic partnership programs. GUPS Web features a BBSP Verification module which offers tools specific to the BBSP, allowing participants to create a standardized submission. All participants regardless of their participation level during BBSP will use the BBSP Verification module for any new updates. 
Standardized submissions allow the Census Bureau to easily process returned BBSPV files and update the MTS. GUPS Web also allows project sharing, collaboration, and the ability to receive feedback from RVDO staff before submitting the project to the Census Bureau.
            3.1.1 Accessing GUPS Web
This section goes into further detail on accessing GUPS web, but a general workflow for accessing GUPS Web is shown in Figure 2.

Figure 2: Workflow for Accessing GUPS Web
Ahead of the start of BBSPV, all counties within a state will be assigned to the official redistricting liaison(s). The liaisons will then receive an email prompting them to create a GUPS Web account. Only new users will have to register for an account.  If the user already has a GUPS Web account, they will not need to re-register and can log into the GUPS Web application once they receive the invitation.  
Upon logging in to GUPS Web, the liaison(s) will be able to access all the counties within the state and assign work to technical liaisons and other stakeholders as described in section 3.2.4.
            3.1.2 Logging into GUPS Web
Once the GUPS Web account has been created, participants can navigate to the GUPS Web Login page <https://gupsweb.geo.census.gov/>, select the Login button. The participant will then be re-directed to another GUPS page where the participant will be prompted to enter their credentials--registered email and password--used to set up the account. After selecting Sign in, the participant will be logged into GUPS Web and directed to the GUPS Dashboard page; see section 3.2.

            3.1.3 GUPS Web User Access Roles 
For BBSP, when a project is created, there is only one version of the project. It may be shared with other users by assigning them a user access role.
There are four access roles, each with different permissions, within the GUPS Web environment: 
    • Project Owner
    • Project Collaborator
    • Project Reviewer
    • Project Viewer 
Table 5: GUPS Web User Access Roles
User Role
Assign/Revoke
Access
Edit Projects
Delete Projects
Submit to Census
Read-Only Access
Project Owner
X
X
X
X

Project Collaborator

X
X
X

Project Reviewer

X



Project Viewer




X
                3.1.3.1 Project Owner 
Official redistricting liaisons will be automatically assigned the role of project owner for all counties in their state. As shown in Table 5, project owners can perform BBSPV updates, delete projects, and submit projects to the Census Bureau. Additionally, project owners can assign or revoke project owner, project collaborator, project reviewer, and project viewer access roles to other participants. Project owners can also download a Project Status Report for all counties within their state. 
Even though the official redistricting liaison will automatically be assigned the project owner role by the RVDO at the start of BBSPV, there can be multiple project owners for a county project. If a project owner assigns another participant (i.e., technical liaison) the project owner role, that new project owner now has all the same permissions as the official redistricting liaison.
                3.1.3.2 Project Collaborator 
Project collaborators are invited to projects by project owners and can make BBSP updates, submit projects to the Census Bureau, and delete projects to which they are assigned.
If a project owner wants a technical liaison to be able to make edits and submit to the Census Bureau without being able to assign or revoke access roles for other participants, the technical liaison should be assigned the project collaborator role.
                3.1.3.3 Project Reviewer
Project reviewers are invited to projects by project owners and/or collaborators and can make BBSP updates for the project owner or project collaborators to submit to Census. 
                3.1.3.4 Project Viewer
Project Viewers can only view data from specific projects assigned to them. 
        3.2 GUPS Web Dashboard
The GUPS Web Dashboard is the page displayed when participants log into GUPS Web. From the dashboard, participants can perform user management, view recent projects, and open projects. The dashboard button, see Figure 3, is displayed in GUPS Web no matter what actions the participant is performing, allowing participants to return to the dashboard. 

Figure 3: GUPS Web Dashboard Button


Figure 4: GUPS Web Dashboard Interface

            3.2.1 Map Management
Map Management, labeled as A in Figure 4, allows participants to open new or existing projects by selecting the state and then the county. Project owners can also download a Project Status Report within the Map Management window (not pictured) for the status of their counties in GUPS Web. 
If the participant does not have access to the project, they will not be able to open the project; see Figure 5. If an official redistricting liaison cannot access a county within their state, contact the RVDO at 301-763-4039 or at <[email protected]>. 

Figure 5: Example of Access Denied Message
            3.2.2 Recent Projects
Recent Projects, labeled as B in Figure 4, shows the participants a list of their 10 most recent projects, where they are assigned either project owner, project collaborator, or project viewer access. Additional information for the project is provided, including: 
    • The last date/time the project was opened by any participant.
    • The status of the project:
        ◦ New: No updates have been made in the project. 
        ◦ In Progress: Updates have been made:
        ◦ Ready for Review: Project has been submitted to the Census Bureau. 
    • The ability to open the project. 
            3.2.3 Opening a Project
Once a project has been opened from the Map Management or Recent Projects interface, the project will display at the county level (for new projects) or at the last location saved from an earlier session. This is shown in Figure 6 and referred to as the map view in this document. The rest of Section 3 details the tools and actions that are available in the GUPS Web map view.

Figure 6: Example of a New Project Opened in GUPS Web (Map View)
            3.2.4 User Management Module
At the start of BBSP, the RVDO will assign the project owner role to the official redistricting liaisons for all the counties in their state. It is up to the liaison to invite additional participants to GUPS Web as fellow project owners, project collaborators, or project viewers.  
                3.2.4.1 Invite Users
Only participants with a project owner access role can assign counties within their state to another project owner, project collaborator, project reviewer, or project viewer. The Invite Users interface is accessed by clicking on the User Management button, labeled as C in Figure 4 in the top right corner of the dashboard, and then selecting Invite Users from the dropdown. Participants must be invited to access the project. 

Figure 7: User Management Module Button

Table 6: How to Invite a User to GUPS Web Project
Step
Description
Step 1
To invite users, click on the User Management icon, see Figure 7, and select Invite Users.
Step 2
Under Program on the left side of the screen, select Block Boundary Suggestion Project Verification. 
Step 3
Select user role:
    • Project Owner
    • Project Collaborator
    • Project Reviewer
    • Project Viewer
Step 4
In the personal message part of the screen, the user role will automatically be updated.  
Step 5
Select the State either by entering the FIPS Code (e.g., 42) or Name (e.g., Pennsylvania). 
Step 6
Once the state is selected, work can be assigned by selecting individual counties using the County ID/Name field or by checking the Select All box to select all the counties within the state that are currently assigned to the project owner. This prevents assigning counties that the project owner may not have access to. In the personal message section, the counties that are being assigned are populated automatically within the message.
Step 7
Enter the email address for the invited participant in the Invite Users field. 
Step 8
Make any updates to the email text. 
Step 9
Click Invite to send or Cancel to cancel. 
Figure 8 shows an example where three (out of 67) counties were assigned to the new project owner. The current project owner was only assigned those three counties and selected Select All for the County ID/Name.

Figure 8: Invite Users Interface (County-Level)
Figure 9 shows an example where all 55 counties in state of West Virginia were assigned to a new project owner. 

Figure 9: Invite Users Interface (State-Level)
                3.2.4.2 Manage Users
The Manage Users Tool allows project owners to manage new or existing users based on their projects. The Manage Users interface is accessed through the User Management button labeled as C in Figure 4 in the top right corner of the dashboard by selecting Manage Users.

Figure 10: Manage Users Interface


Table 7: How to Utilize the Manage Users Interface
Step
Description
Step 1
To manage users, click on the User Management button, see Figure 7, and select Manage Users.
Step 2
Select Block Boundary Suggestion Project. 
Step 3
Select how to Search By:
    • State Code: search by FIPS code for the state and county.
    • State Name: search by name for the state and county.
    • User email address: search by the user email address.
Note: the example in Figure 10 was based on a user email address search.
Step 4
Searching by State Code or Name, the following fields are displayed:
    • Date added: the date the county project was created. 
    • Email address: the email address of the user(s) assigned to the project.
    • Last active: the last time the project was opened by the participant. For new projects, it will show the time the project was created.
    • Role: Shows if the participant is a project owner, project collaborator, project reviewer, or project viewer. Also allows project owners to switch the user to a different role. 
    • Actions: Allows project owners to remove users.
Step 5
Searching by user email address, the following fields are displayed:
    • Date added: the date the county project was created.
    • Last active: the last time the project was opened.
    • Project ID: FIPS code of the state and county. 
    • Project Name: Name of the county and state.
    • Role: Shows if the participant is a project owner, project collaborator, project reviewer, or project viewer. Also allows project owners to switch the user to a different access role.
    • Actions: Allows project owners to remove participants. 
Step 6
Below the Manage Users Interface, there is an “Add User” and “Remove User” button. These allow project owners to select multiple projects from the Interface to add or remove users from. 
        3.3 GUPS Web Tools
This section describes the tools available in GUPS Web for project viewing and editing. All the tools are accessible from the dashboard, described in section 3.2, and in the map view as shown in Figure 11 with the tools identified.  


Figure 11: GUPS Web Map View with Tools Identified
            3.3.1 GUPS Web Navigation Bar
On the left of the dashboard screen, there is the GUPS Web Navigation Bar (displayed vertically). The buttons are described below. 
Table 8: GUPS Web Navigation Bar
Tool
Icon
Description
Quick Tools

Quick Tools are functions that are used often to navigate the map. The menu includes Add/Remove Esri Imagery and Save and Refresh. This tool is activated when a project is opened; see section 3.3.2.
Tools

Tools include the View, Imagery, Selection, Edit, and Review Tools. This tool is activated when a project is opened; see section 3.3.3.
Layer Legend

Layer Legend depicts the layers in the map view. This tool is activated when a project is opened; see section 3.3.4.
Import/Export

Import/Export allows the user to import a reference shapefile, export a map as a pdf, jpg, or png, and submit to the Census Bureau for review. This tool is activated when a project is opened; see section 3.3.5.
Layer Search

This tool is not currently active for BBSP. Attribute tables can be used for search within the layers; see section 3.3.4.2.
Help Center

The Help Center is available for participants to obtain more information on GUPS Web, the supported programs, FAQs, and project tools. It is recommended to visit the BBSP Program Management Page for specific BBSP Guidance. <https://www.census.gov/programs-surveys/decennial-census/about/rdo/program-management.html>. 
Project Management

The Project Management tool allows project owners and project collaborators to delete projects not intended for submission to the Census Bureau; see section 3.3.6.
Dashboard

Return to the GUPS Web Dashboard; see section 3.2.
Log Out

Log out of GUPS Web. 
Expand Navbar

Expands the navigation toolbar which houses the tools described in this table. 
Version Number

Display current version number of GUPS Web.  
On Screen Pan and Zoom Tools 

Allows users to access the tools described below. 
Pan Map

Shift the map in the map view without changing the map scale.
Zoom In

Display the map view at a larger scale.
Zoom Out

Display the map view at a smaller scale.
Zoom Full

Zoom the map view to the full extent of the county.
Zoom Last

Zoom the map view to the previous map extent.
Zoom Next

Zoom the map view forward to the next map extent.

Note: 	For Quick Tools, Tools, Layer Legend, and Import/Export Tools clicking the button will expand the toolbar to show the tools and then clicking on the button again will collapse the tools.
            3.3.2 Quick Tools
The Quick Tools are functions that are used often to navigate the map. The menu includes the following actions:

Figure 12: Quick Tools Button
Table 9: Quick Tools
Tool
Icon
Description
Add Esri Imagery

Display or remove satellite imagery on the map.
Save and Refresh

Save current edits and refresh the map view. 


            3.3.3 Tools
There are five sets of tools within GUPS Web to assist participants with performing their BBSP updates. These tools include View, Imagery, Selection, Edit, and Review. To access the tools, click on the Tools button shown in Figure 13. The navigation bar will expand to show the tools listed below. 

Figure 13: Tools Button
                3.3.3.1 View Tools 

Figure 14: View Tools Option
View Tools include the options to pan and zoom in and out of the map, identify features, measure distances, create bookmarks and add or remove a dynamic scale bar. 
Click on the arrow next to View Tools to show the list of actions within the tool; see Figure 14.
The menu includes the following actions described in Table 10: View Tools. 


Table 10: View Tools
Tool
Description

Shift the map in the map view without changing the map scale.

Identify the selected geographic feature.

Provide options to measure linear distance and area on the map.

Zoom the map view to the full extent of the county.

Zoom the map view to the rows selected in the attribute table.

Zoom the map view to the extent of the active layer.

View the current scale of the map view. 

Create, view, or delete bookmarks within the project. Bookmarks can be private to the user or shared between all users within the project. 
                3.3.3.2 Imagery Tools

Figure 15: Imagery Tools Option
Imagery Tools provides the option of adding and removing Esri imagery or opening Google Maps or Bing Maps to view the selected location.
Click on the arrow next to Imagery Tools to show the list of actions within the tool; see Figure 15.
The menu includes the following actions described in Table 11.
Table 11: Imagery Tools
Tool
Description

Display the selected map location in Google Maps in a separate browser tab after clicking on the map. 

Display the selected map location in Bing Maps in a separate browser tab after clicking on the map.

Display satellite imagery in the map view. 

Remove satellite imagery from the map view. 
                3.3.3.3 Selection Tools

Figure 16: Selection Tools Option
Selection Tools allow the participant to select features in the active layer using a variety of selection types, including Select Features, Select by Polygon, and Select Freehand, as well as Deselect All.
Click on the arrow next to Selection Tools to show the list of actions within the tool; see Figure 16. 
The menu includes the following actions described in Table 12. 
Table 12: Selection Tools
Tool
Description

Left click on a single feature to select it or left click and drag to select multiple features.

Draw a polygon around features to select them. 

Draw a freehand shape around features to select them. 

Clear the selected features. 
                3.3.3.4 Edit Tools

Figure 17: Edit Tools Option
Edit Tools allow participants to make updates to their project. Edit tools are unique across participant programs. 
Click on the arrow next to Edit Tools to show the list of actions within the tool; see Figure 17. The menu includes the following actions described in Table 13. 
Table 13: Edit Tools
Tool
Description

Create and edit area landmarks and legal entities; see section 4.2 and section 4.3. 

Add a new linear feature; see section 4.1.1.

Delete a linear feature or restore a deleted linear feature; see section 4.1.2 and 4.1.3.

Split a linear feature from one segment to two segments; see section 4.1.5.

Edit attributes of a selected linear feature; see section 4.1.4.

Assign or remove a “Must Hold” or “Do Not Hold” flag to a linear feature; see section 4.6.

Add a 2030 linear feature extension to create a closed polygon for a suggested 2030 block; see section 4.6.5. 

Create a Block Area Grouping over water; see section 4.7.1.

Delete a Block Area Grouping; see section 4.7.2

                3.3.3.5 Review Tools

Figure 18: Review Tools Option
Review tools allow participants to perform different reviews for their updates within a project. Types of reviews are specific to participant programs. 
Click on the arrow next to Review Tools to show the list of actions within the tool; see Figure 18.
The menu includes the following actions described in Table 14. 

Table 14: Review Tools
Tool
Description

Perform a systematic review of any area landmark or legal entity updates made in the project; see section 4.10.

Perform a systematic review of linear features with block boundary suggestion flags sorted by BBSP category (Must Hold, Do Not Hold, NULL) ; see section 4.8. This tool is also used for performing verification; see section 4.8.1.

Perform a systematic review of 2020 linear feature extensions (if present) and take an action for 2030 (i.e., assign a “Must Hold” or “Do Not Hold” flag or Ignore); see section 4.4.1.

Perform a systematic review of small blocks (less than 3,000 square meters) that exist in the project based on the planned and suggested block boundaries; see section 4.9.

            3.3.4 Layer Legend
The Layer Legend depicts the layers in the map view.  It can be opened by clicking the Layer Legend button shown in Figure 19. 

Figure 19: Layer Legend Button
Layers have been pre-styled and arranged for optimal use. The layers and their labels appear at varying scales depending on the layer. Layers can also be manually turned off and on depending on the geography that needs to be viewed. Use the arrows next to the layers to reveal or hide sub-layers for group layers.
Participants can select the pin icon at the top of the Layer Legend to keep the Legend open while using other Tools. 

Figure 20: Layer Legend Interface
Note: 	For BBSP, the edges layer has an extensive sub-menu detailing the symbology showing planned and ineligible block boundaries as well as participant indicated “Must Hold” and “Do Not Hold” flags. It is not shown in this screenshot due to the size, but it is recommended to expand the edges sub-menu while making BBSP updates. 
The order in which the layers appear determines the order that the layers display in the Map View. The layers at the top of the Layer Legend display on top of the layers that appear below them. To manage the order of layers, select and drag the layer to the desired position in the layer legend. Some layers may be blocked from view due to layers being drawn on top of them; this can be resolved by turning layers off and on. 
Right-clicking on a layer reveals additional functions:
    • Open Attribute Table: Open an attribute table.
    • Zoom to Layer: Zoom to the full extent of the layer.
    • Zoom to Selection: Zoom to selected features.
    • Properties: Open layer properties.
    • Hide Labels: Hide and show labels.
    • Load Default Style: Revert to the default style (symbology).

Participants can use the Properties function to adjust the symbology of the selected layer by selecting Properties and then Symbology. Selecting “Categorized” symbology over the default “Rule - Based” symbology allows participants to use unique colors to symbolize unique values. Examples where this might be helpful include symbolizing each incorporated place in the county a different color. Participants can use Load Default Style to restore the default symbology. 

Note:	Participants may want to turn some layers off to better view their area of update if those layers are not relevant to the review. 
                3.3.4.1 Manual BBSP Change Layers
At the bottom of the Layers Legend, there is a layer called “Manual BBSP Changes” and it includes three sub-layers; see Figure 20.
    • bbsp27_<ssccc>_changes_place (shows place changes)
    • bbsp27_<ssccc>_changes_mcd (shows MCD changes)
    • bbsp27_<ssccc>_changes_arealm (shows area landmark changes)
These layers are present in every project even if there are no changes for these geographies. When there are changes for these layers, participants can view the change polygons in the map view and the change attributes in the attribute table of the shapefiles listed above. These layers also populate the Boundary Review Interface; see section 4.10.
                3.3.4.2 Attribute Table Tools
Attribute tables can be opened from the Layer Legend by selecting the layer, right clicking it, and selecting Open Attribute Table. Attribute tables in GUPS Web have built in functionality for sorting and filtering records. Participants can also select records within the attribute table and zoom to their location in the map view. Participants can choose to show all the records within the table, show all records that are currently visible in the map view, or show selected records. 




Table 15: Attribute Table Tools
Tool
Icon
Description
Show Features

Choose which records in the attribute table to display: Show All, Show Features Visible on Map, or Show Selected Features. 
Filter

Click on the Filter button to apply filters as described.
Filter Options

Once filter is selected, filter options allow the participant to tailor their filters for their search.
Sort

Sort the records within the column.
Sort Ascending

Indicates that the column is sorted in ascending order.
Sort Descending

Indicates that the column is sorted in descending order.
Zoom to Selection

Zoom to the selected feature(s) in the map view.
Deselect All

Clear all selected records.
Clear Filters

Clear applied filters. 


Table 16: How to Search the Attribute Table
Step
Description
Step 1
Open the attribute table from the Layer Legend. 
Step 2
Use the Filter or Sort functions to identify and view the feature(s). 
Step 2a
To use the Filter option: Choose if the filter should “match all” records or “match any” records (this is only needed if there is more than one rule applied within the filter). Type in the search phrase. Then choose from the following: Starts With, Contains, Not Contains, Ends with, Equals, or Not Equals. 
Example: If the participant is searching for Ardmore Boulevard, they should click on the Filter button for the FULLNAME column, leave the default Match All, select Starts With, and type in the search phrase of Ardmore. By using only Ardmore, the participant will find records that may include Blvd and Boulevard, but the participant would not find West Ardmore, as that starts with “West.”
Step 4
To use the Sort option: Click on the Sort button. It will sort the features in ascending order (from A-Z). Click on the Sort button again to sort the features in descending order (from Z-A). Use Ctrl to sort on another field within the attribute table. 
Step 5
Once the results are shown within the table, select a single record and double click on the record to zoom to the feature. Select multiple records by holding down the shift key while clicking on all the records Use the Zoom to Selection tool to zoom to the extent that includes all the selected records. Use the Deselect All button clears the selected features.  
Step 6
Use the Clear Filters button to remove the filters.

            3.3.5 Import/Export Tools
The Import/Export Tool, see Figure 21, allows the participant to import a reference shapefile, export a map as a pdf, jpg, or png, and submit the project to the Census Bureau for review. 
Click on the arrow next to Import Tools or Export Tools to show the list of actions within the tool; see Figure 22.

Figure 21: Import/Export Button


Figure 22: Import/Export Interface
The menu includes the following actions described in Table 17. 
Table 17: Import/Export Tools
Tool
Description

Import a shapefile to use as reference for the project. Importing a reference file does not create any updates in the project.

Begin the submission to Census process. Located under Export Tools; see section 4.11.1.1.

Download a copy of the project file. Located under Export Tools; see section 4.11.1.3.

Export a map of the area displayed in the map view. Located under Export Tools; see section 4.11.1.4.

            3.3.6 Project Management Tool

Figure 23: Project Management Button
The Project Management Tool, see Figure 23, is a part of the GUPS Web Navigation Bar, described in section 3.3.1. This tool allows project owners and project collaborators to delete projects that they have access to; see Figure 24.
If a project was deleted and needs to be restored, please contact the RVDO at [email protected] or 301-763-4039. 

Figure 24: Delete Project Button
Note: 	Deleting projects will delete the project, and all edits that were made, for all participants (project owners, project collaborators, project reviewers, and project viewers) who have access to the project.
            3.3.7 Notification Button

Figure 25: Notification Button
The notification button is on the top right of the map view; see Figure 25. It shows the current number of notifications. Participants can click on the button to view any notifications for participants. Notifications can include messages about scheduled and unscheduled downtimes or upcoming deadlines. Notifications can also be viewed on the dashboard when participants log in. 
            3.3.8 User Count Button

Figure 26: User Count Button
The user count button is in the top right of the map view; see Figure 26, It shows the current number of users in the project. If the participant clicks the icon, it will display the name(s) of the current user(s) in the project.
    SECTION 4. BBSP Update Activities in GUPS Web
Section 4 details the process for making specific BBSP updates and verifying updates made in initial BBSP. The tools described in this section are within the Edit Tools menu in GUPS Web. Most of the sections describing updates will include an image of the button used to initiate the action, an image of the action (with certain aspects highlighted if applicable), and a table of steps.
        4.1 Linear Feature Review
Review the Census Bureau’s linear features (edges shapefile) to determine whether there are features that need to be added or deleted. Pay particular attention to any areas that have experienced population growth, and where there may be new housing or subdivisions not reflected in the Census Bureau’s geospatial data. 
Refer to Table 1 for a complete list of MTFCCs for linear features.  
The basic groupings of the MTFCCs are as follows:
    • S-class = Roads.
    • R-class = Railroads.*
    • P-class = Nonvisible Features.*
    • L-class, K-class, and C-class = Other Linear Features. *
    • H-class = Hydrography.*
The Census Bureau will also accept attribute updates (name and classification code) for MTFCCs in the S-class (roads). Added road features (except for highway ramps) require a feature name. If a road feature does not have a name but is still needed, use the name “BBSP Road”. Your update will be reviewed and adjudicated by Census staff during processing. 
*These types of linear features should only be added if desired as a block boundary and therefore must have a “Must Hold” flag assigned to them when submitted to the Census Bureau.
Note: 	Please be aware that the Census Bureau will not process the wholesale spatial realignment of features merely to conform to an alternate spatial accuracy. If a feature is in the incorrect location in the Census Bureau’s feature network, mark the feature for deletion and then add it in the correct location. Take this action only if most of the realigned feature is more than 7.6 meters from the existing feature or interferes (is topologically incorrect) with relationships to other features.

            4.1.1 Adding a Linear Feature

Figure 27: Add Linear Feature Button


Figure 28: Add Linear Feature Dialog Window 

Table 18: How to Add a Linear Feature
Step
Description
Step 1
Select the Add Linear Feature button; see Figure 27. This is found under Edit Tools described in section 3.3.3.4.
Step 2
To digitize the linear feature, left-click the mouse at the starting point of the line and continue to left-click the mouse at each vertex (shape point) of the line. When the new line is completed, right-click the mouse. The Add Linear Feature dialog window will open; see Figure 28. 
Step 3
Select the MTFCC and enter the Name of the linear feature if it is a road. Just enter the MTFCC if it is a non-road feature.  If a road feature does not have a name but is still needed, use the name “BBSP Road”. Your update will be reviewed and adjudicated by Census staff during processing. 
Use the following drop downs as appropriate:
    • Predirectional (if the name of the road is preceded with a direction e.g., N. Main St.).
    • Prefix (if the street type is before the name, e.g., State Rd 46.).
    • Suffix (if the street type is after the Name, e.g., First Ave).
    • Postdirectional (if the road name has a direction after it, e.g., Main St. S).
Step 4
If the new linear feature is a “Must Hold”, use the check box to flag the new linear feature. 
Note: All linear features other than road features should only be added to be used as block boundaries and must be flagged with a “Must Hold.” 
If a non-road feature is added and “Flag as Must Hold” is not selected, an error will appear prompting the participant to either flag the feature as a “Must Hold” or cancel the action. 
Step 5
Click on Commit to save the linear feature or select Cancel to cancel.
Step 6
The newly digitized linear feature appears on the map with its corresponding symbology.
Note:	When adding new linear features, imagery should be turned on within GUPS Web. 
            4.1.2 Deleting a Linear Feature

Figure 29: Delete/Restore Linear Feature Button

Table 19: How to Delete a Linear Feature
Step
Description
Step 1
Select the Delete/Restore Linear Feature button; see Figure 29. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature to delete or left click and drag to select multiple features to delete at the same time. The edge(s) will be highlighted once selected.   
Step 3
Right click to delete the selected linear feature. 
If the linear feature selected for deletion has a “Must Hold” flag, a popup will appear “Warning: One or more of the linear features that you have selected for deletion has been flagged as a Must Hold. This action cannot be undone.” To continue with the deletion, click OK. To cancel the deletion, click Cancel. Figure 30 shows this popup.
Step 4
An additional popup will appear reminding the participant that “Note that the features are marked for deletion in GUPS Web, however they may not be deleted from the MAF/TIGER System. If your goal is to ensure that the edge is not used as a block boundary, flag the edge(s) as a Do Not Hold.” This message can be turned off for the session by selecting “Do no show this message again.” Click Cancel to cancel the action or Click OK to continue with the delete action. Figure 31 shows this popup.
Step 5
If the linear feature existed in the shapefiles, the deleted line appears with a red line symbology to show it has been marked for deletion. (Note: you may need to turn on the Deleted Linear Feature symbology from the Edges layer.) If the linear feature was newly added and then deleted, it is completely removed from the map view and cannot be restored.

Note:	If the goal is to ensure that the edge is not used as a block boundary, refer to section 4.6.3.1 on flagging the edges as “Do Not Hold” rather than using the delete function. 


Figure 30: "Must Hold" Delete Warning


Figure 31: Delete Linear Feature Warning
            4.1.3 Restoring a Deleted Linear Feature
Only existing linear features can be restored. Newly added linear features that were deleted cannot be restored. 
Table 20: How to Restore a Deleted Linear Feature
Step
Description
Step 1
Select Delete/Restore Linear Feature button; see Figure 29. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the deleted linear feature to restore. 
Step 3
Right click to confirm the selected linear feature. 
Step 4
The red symbology will be removed from the linear feature.
Note:	If a linear feature was added and then deleted, it cannot be restored. 
            4.1.4 Modifying Attributes of a Linear Feature

Figure 32: Modify Linear Feature Button


Figure 33: Modify Linear Feature Interface

Table 21: How to Modify a Linear Feature
Step
Description
Step 1
Select Modify Linear Feature button; see Figure 32. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature to modify or left click and drag to select multiple features to modify at the same time. The edge(s) will be highlighted once selected.   
Selecting multiple edges is helpful if the linear feature is made up of several edges with the same Full Name and MTFCC. If the selected linear feature does not have matching Full Names and MTFCCs, they cannot be edited at the same time. 
Step 3
Right click to confirm the selected linear feature. 
Step 4
Update the MTFCC and/or Full Name; see Figure 33. If the linear feature is being modified from a road to a non-road feature, the Name will be removed from the feature.
Step 5
Click Update to perform the modification or Cancel to cancel the modification. 
            4.1.5 Splitting a Linear Feature

Figure 34: Split Linear Feature Button

Table 22: How to Split a Linear Feature
Step
Description
Step 1
Select Split Linear Feature button; see Figure 34. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature where the split should occur. There is no confirmation screen.
Step 3
The linear feature has been split.

        4.2 Area Landmark Review
The Census Bureau accepts updates to area landmarks (such as prison areas, state parks, and cemeteries) as part of the BBSP through the Modify Area Feature Tool. Allowable updates include:
    • Boundary corrections (adding and removing area).
    • Creating a new area landmark.
    • Removing an area landmark.
    • Changing or adding a name to an area landmark.
    • Changing/updating the MTFCC of an area landmark.
If the state plans to reallocate prisoners during redistricting, consider reviewing the existing area landmarks with MTFCCs K1235, K1236, K1237, and K1238, which represent areas with potential prison populations, or create new ones for those types of areas.
            4.2.1 Modify Area Feature Tool
Updates to area landmarks and legal entities are made using the Modify Area Feature Tool. 

Figure 35: Modify Area Feature Tool Button


Figure 36: Modify Area Feature Interface
    • Geography (A) allows the participant to select the area features to create, delete or modify. These include Incorporated Places, Area Landmarks, and MCDs.
    • Action (B) allows the participant to select what action to perform on the area feature selected. The actions available will vary depending on the geography selected, but they include:
        ◦ Annexation allows the participant to create annexations by adding area to the incorporated place or MCD. Documentation is required to process the update; see section 4.3.2. 
        ◦ Deannexation allows the participant to create deannexations by removing area from the incorporated place.  Documentation is required to process the update; see section 4.3.3.
        ◦ New: allows the participant to create a new area landmark (see section 4.2.4), incorporated place, or MCD. Documentation is required to process the insertion of new Incorporated Places or MCDs; see section 4.3.6.
        ◦ Boundary Correction-Add Area allows the participant to create boundary corrections by adding area to the area landmark (see section 4.2.2), incorporated place or MCD; see section 4.3.4.
        ◦ Boundary Correction-Remove Area: allows the participant to create boundary corrections by removing area from the area landmark (see section 4.2.3), incorporated place or MCD; see section 4.3.5.
        ◦ Delete: allows the participant to delete an area landmark (see section 4.2.5) or incorporated place. Documentation is required to process the deletion for Incorporated Places or MCDs; see section 4.3.7.
        ◦ Modify Attributes allows the participant to modify the attributes of an area landmark (see section 4.2.6. For incorporated places or MCD see section 4.3.8.)
    • Target Geography (C) allows the participant to select a geography to update using the map. It is helpful to use this tool when the geography is in the map view and the scale should remain the same. 
    • Draw Polygon (D) allows the participant to manually draw a boundary update or new entity. 
    • Reset Polygon (E) allows the participant to remove the unsaved change polygon. 
    • Comments (F) allows the participant to include comments for specific actions. Comments are not required. 
    • Commit (G) saves the update. 
    • Cancel (H) cancels the update. 
Note:	When updating area landmarks, places, and MCDs participants do not need to digitize separate linear features to represent the boundaries of the area landmark. The change polygon that is drawn using the Draw Polygon Tool will represent the boundary and the Census Bureau will digitize the boundary edges accordingly. 
            4.2.2 Boundary Correction by Adding Area to Area Landmark

Figure 37: Modify Area Feature Button


Figure 38: Modify Area Feature Tool Boundary Correction- Add Area Interface

Table 23: How to Add Area to an Area Landmark
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 38, select Area Landmark as the Geography.
Step 3
Select Boundary Correction - Add Area as the Action.
Step 4
Click on the area landmark record from the list or use Select Target Geography to select the area landmark from the map to add area to. Note: when the selected area landmark is selected from the list GUPS Web zooms to area landmark’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Once the area landmark is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be added to the area landmark. Note these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match. 
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line. 
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Click Commit to save or Cancel to cancel. 
            4.2.3 Boundary Correction by Removing Area from an Area Landmark

Figure 39: Modify Area Feature Tool Boundary Correction- Remove Area Interface


Table 24: How to Remove Area from an Area Landmark
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 39, select Area Landmark as the Geography
Step 3
Select Boundary Correction - Remove Area as the Action.
Step 4
Click on the area landmark record from the list or use Target Geography to select the area landmark from the map to remove area from. Note: when the area landmark is selected from the list, GUPS Web zooms to the area landmark’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Once the area landmark is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be removed from the area landmark. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match. 
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line. 
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Click Commit to save or Cancel to cancel.
            4.2.4 Creating a New Area Landmark

Figure 40: Modify Area Feature Tool New Area Landmark Interface

Table 25: How to Create a New Area Landmark
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 40, select Area Landmark as the Geography
Step 3
Select New as the Action.
Step 4
Use Draw Polygon to manually draw a polygon reflecting the boundaries of the new area landmark. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match. 
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 5
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 6
Select the MTFCC Code.
Step 7
Enter the Name.
Step 8
Click Commit to save or Cancel to cancel.
            4.2.5 Deleting an Area Landmark

Figure 41: Modify Area Feature Tool Delete Area Landmark Interface

Table 26: How to Delete an Area Landmark
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 41, select Area Landmark as the Geography.
Step 3
Select Delete as the Action.
Step 4
Click on the area landmark record from the list or use Target Geography to select the area landmark from the map to delete.  
Step 5
Click Commit to save or Cancel to cancel.
            4.2.6 Modifying the Attributes of an Area Landmark


Figure 42: Modify Area Feature Tool Modify Attributes Interface


Table 27: How to Modify an Area Landmark
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 42, select Area Landmark as the Geography.
Step 3
Select Modify Attributes as the Action.
Step 4
Click on the area landmark record from the list or use Target Geography to select the area landmark from the map to modify.  
Step 5
Edit the MTFCC and/or Name.
Step 6
Click Commit to save or Cancel to cancel.
        4.3 Legal Changes
Participants may provide legal boundary updates (annexations, deannexations, incorporations and disincorporations), along with their supporting documentation, or boundary corrections. The Census Bureau will assume the responsibility for reconciling the updates with the appropriate governments as part of the Boundary and Annexation Survey (BAS).
Participants may submit legal boundary updates for MCDs and incorporated places. Although legal documentation (effective date, authorization type, and documentation number) is not required for boundary updates submitted through the BBSP, the Census Bureau strongly encourages the submission of documentation to expedite our ability to reconcile and process any legal updates reported. Annexations and deannexations without supporting documentation should be submitted as boundary corrections. To report a new county, MCD, or incorporated place (without documentation) or to delete an existing MCD, incorporated place or county (without documentation), please call the RVDO at 301-763-4039 or at <[email protected]>.
Note:	The Census Bureau cannot guarantee these updates will be made, as we must adjudicate and receive concurrence for the updates from the official BAS contact.
            4.3.1 Creating Legal Changes with the Modify Area Feature Tool
When performing annexations and deannexations, the Modify Area Feature Tool will include the following fields in addition to the fields described in section 4.2.

Figure 43: Modify Area Feature Tool Interface with Legal Fields
These fields include:
    • Attachment (A) allows the participant to upload the relevant documentation for the annexation, deannexation, new, or delete action.  
    • Document Number (B) allows the participant to enter the ordinance or other legal documentation number authorizing the annexation, deannexation, new, or delete action.  
    • Authorization Type (C) allows the participant to select the type of document that approved the annexation, deannexation, new, or delete action such as ordinance, resolution, or state law. 
    • Effective Date (D) allows the participant to enter or select the date that the annexation, deannexation, new, or delete action becomes effective.  
Note:	When making changes to places and MCDs, participants do not need to digitize separate linear features to represent the boundaries of the area landmark. The change polygon that is drawn using Draw Polygon will represent the boundary and the Census Bureau will digitize the boundary edges accordingly.
            4.3.2 Adding Area through Legal Changes (Annexation)

Figure 44: Modify Area Feature Tool Annexation Interface

Table 28 How to Perform an Annexation
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 44, select Incorporated Place or MCD as the Geography.
Step 3
Select Annexation as the Action.
Step 4
Click on the Place/MCD record from the list or use Target Geography to select the Place/MCD from the map to add area to. 
Note: when the selected Incorporated Place or MCD is selected from the list GUPS Web zooms to the Incorporated Place or MCD’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent. 
Step 5
Once the Place/MCD is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be annexed. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match.
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
tep 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Upload an attachment of the document (optional) and enter the legal information into the Document Number, Authorization Type, and Effective Date fields to activate the commit button. If this documentation is unavailable, refer to section 4.3.4 and provide this as a Boundary Correction- Add Area. 
Step 8
Click Commit to save or Cancel to cancel.


            4.3.3 Removing Area through Legal Changes (Deannexation)

Figure 45: Modify Area Feature Tool Deannexation Interface


Table 29: How to Perform a Deannexation
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 45, select Incorporated Place as the Geography. This functionality is not available for MCDs. 
Step 3
Select Deannexation as the Action.
Step 4
Click on the Place record from the list or use Target Geography to select the Place from the map to remove area from. 
Note: when the selected Incorporated Place is selected from the list GUPS Web zooms to the Incorporated Place’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Once the Place is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be deannexed. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match.
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Upload an attachment of the document (optional) and enter the legal information into the Document Number, Authorization Type, and Effective Date fields to activate the commit button. If this documentation is unavailable, refer to section 4.3.5 and provide this as a Boundary Correction- Remove Area.
Step 8
Click Commit to save or Cancel to cancel.


            4.3.4 Boundary Correction by Adding Area to a Legal Entity

Figure 46: Modify Area Feature Legal Update Boundary Correction-Add Area Interface

Table 30: How to Add Area to a Incorporated Place or MCD
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 46 select Incorporated Place or MCD as the Geography. 
Step 3
Select Boundary Correction - Add Area as the Action.
Step 4
Click on the Place/MCD record from the list or use Target Geography to select the Place/MCD from the map to add area to.
Note: when the selected Incorporated Place or MCD is selected from the list GUPS Web zooms to the Incorporated Place or MCD’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Once the Place/MCD is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be added. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match.
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Click Commit to save or Cancel to cancel.
            4.3.5 Boundary Correction by Removing Area from a Legal Entity

Figure 47: Modify Area Feature Legal Update Boundary Correction-Remove Area Interface

Table 31: How to Remove Area from an Incorporated Place
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 47 select Incorporated Place as the Geography. This functionality is not available for MCDs. 
Step 3
Select Boundary Correction - Remove Area as the Action.
Step 4
Click on the Place record from the list or use Target Geography to select the Place/MCD from the map to add area to. Note: when the selected Incorporated Place is selected from the list GUPS Web zooms to the Incorporated Place’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Once the Place is selected, use Draw Polygon to manually draw a polygon reflecting the area that should be removed. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match.
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 6
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 7
Click Commit to save or Cancel to cancel.

            4.3.6 Adding a New Legal Entity

Figure 48: Add a New Legal Entity Interface

Table 32: How to Add a New Incorporated Place or MCD
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 48, select Incorporated Place or MCD as the Geography. 
Step 3
Select New as the Action.
Step 4
Use Draw Polygon to manually draw a polygon reflecting boundaries of the new Place/MCD. Note, these polygons will not automatically align with the linear features in the project. Please digitize them carefully to reflect the update but they do not need to exactly match.
Start drawing with a single left or right click at starting point. GUPS Web will display a single blue point and line.
    • With a single click, add one vertex (shape point) at a time to create the shape of the polygon.
    • Use the ‘d’ key to delete the previous drawn vertex.
    • The new polygon may overlap an existing boundary to avoid gaps or holes.
    • End drawing with a single click at the starting point of the polygon.
Step 5
To end drawing without saving, hold the shift key and left click or select Reset Polygon.
Step 6
Enter the Name.
Step 7
Select the Legal and Statistical Area Description (LSAD).
Step 8
Upload an attachment of the document (optional) and enter the legal information into the Document Number, Authorization Type, and Effective Date fields to activate the commit button. If this documentation is unavailable, reach out to the RVDO at 301-763-4039 or at [email protected].
Step 9
Click Commit or Cancel to cancel. 


            4.3.7 Deleting a Legal Entity

Figure 49: Delete a Legal Entity Interface


Table 33: How to Delete An Incorporated Place
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
On the Modify Area Feature Interface; see Figure 49, select Incorporated Place as the Geography. This functionality is not available for MCDs. 
Step 3
Select Delete as the Action.
Step 4
Click on the place record from the list or use Target Geography to select the incorporated place from the map to delete. 
Step 5
Upload an attachment of the document (optional) and enter the legal information into the Document Number, Authorization Type, and Effective Date fields to activate the commit button. If this documentation is unavailable, reach out to the RVDO at 301-763-4039 or at [email protected].
Step 6
Click Commit to save or Cancel to cancel.

Note:	If the deleted incorporated place crosses a county boundary, it must be deleted in both counties separately. After making the change in the working county, return to Map Management, select the other county as the working county, and proceed to delete the entity in this county as well. If the deleted entity crosses more than one county boundary, complete the deletion in each county affected.

            4.3.8 Modifying the Attributes of a Legal Entity

Figure 50: Modify Attributes of a Legal Entity Interface

Table 34: How to Modify the Attributes of an Incorporated Place or MCD
Step
Description
Step 1
Select Modify Area Feature button; see Figure 37. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Select Place or MCD as the Geography.
Step 3
Select Modify Attributes as the Action.
Step 4
Click on the Incorporated Place or MCD record from the list or use Target Geography to select the the Place/MCD whose attributes will change from the map. Note: when the selected Incorporated Place or MCD is selected from the list GUPS Web zooms to the Incorporated Place’s full extent. Using the Select Target Area Tool will select the entity without zooming to the full extent.
Step 5
Edit the Name, select the LSAD value, upload an attachment of any documentation available, enter the Document Number, select the authorization type, and add an Effective Date.  If this documentation is unavailable, reach out to the RVDO at 301-763-4039 or at [email protected].
Step 6
Click Commit to save or Cancel to cancel.
        4.4 Linear Feature Extension Review
All block boundary suggestions are contingent upon the lines intersecting to form a closed polygon at the time the Census Bureau creates blocks. As a result, all block boundary “Must Hold” suggestions, when combined with the features identified as planned holds, should form a closed polygon.
For the 2020 Census, BBSP participants could place a “Must Hold” flag on an existing feature that did not form a closed a polygon. To do this, the participant also added a feature extension to close the polygon and create a potential new block. Those 2020 feature extensions are included in the 2030 BBSP files for review and update. It is important to note that most counties do not have linear feature extensions to review. 
The Census Bureau requests that participants review the 2020 linear feature extensions to determine if they are still needed. Please be aware that to hold an old 2020 feature extension as a 2030 block boundary, participants must take an action to again classify that extension as a “Must Hold” suggestion.
During the feature extension review, participants may:
    • Hold the old 2020 linear feature extension as a 2030 block boundary suggestion along with the feature from which the extension originates. If possible, when applying a Must Hold to a feature extension, review the extension against cadastral data or imagery to ensure it is in the most appropriate location. 
    • Flag the old 2020 feature extension as a "Do Not Hold" as some linear features cannot be deleted from the MTS. Flagging the old 2020 linear feature extension as a "Do Not Hold" will help the Census Bureau ensure the feature extension no longer serves as a block boundary. 
    • Ignore the 2020 linear feature extension. If no action is taken on a 2020 linear feature extension, the Census Bureau may delete the old extension or if kept, decide whether to hold the extension and the feature associated with it as a 2030 block boundary or not.
            4.4.1 Verify Linear Feature Extension Tool
Some counties have linear feature extensions inserted in previous BBSP cycles. These extensions should be reviewed, and the edges should either be flagged as a “Must Hold”, “Do Not Hold”, or left as is. 

Figure 51:Verify Linear Feature Extension Tool Button

Figure 52: Verify Linear Feature Extension Tool Interface

Table 35: How to Review Linear Feature Extensions
Step
Description
Step 1
Open the Review Verify Linear Feature Extension Tool; see  Figure 51. This is found under Review Tools described in section 3.3.3.5.
Step 2
All 2020 linear feature extensions are displayed in the interface. Not all counties have linear feature extensions for review. 
Step 3
Click on a row to select the feature and zoom to it on the map.
Step 4
There are several tools to sort through the Linear Feature Extension Review process; see Figure 52: 
    • Arrows will navigate up and down through the list of records (A).
    • Hide will remove selected records from the table for the session (B).
    • All records can be selected with the Select All button (C).
Step 5
Review that this edge has the appropriate block boundary flag assigned to it. 
    • Must Hold Flag will assign a “Must Hold” flag to the edge (D).
    • Do Not Hold Flag will assign a “Do Not Hold” flag to the edge (E).
    • Ignore the extension by not assigning either flag to it. 
        4.5 Prototype Block Review
The prototype block shapefile shows what the planned 2030 blocks would look like if created using the geography as it exists at this time, which include any previously submitted and accepted “Must Hold” or “Do Not Hold” flags. The prototype block shapefile is a useful tool for participants to review their potential block geography and then use the “Must Hold” and “Do Not Hold” flags to make targeted updates. The prototype blocks for BBSPV will be different than the prototype block shapefiles provided for BBSP and will reflect the updates made during BBSP as well as other geographic update programs (e.g., Boundary and Annexation Survey).
Note:	The prototype blocks are included in the Layer Legend (see section 3.3.4) and need to be turned on for review within the project. There is no specific tool. 
            4.5.1 Block Size Review
In the prototype block shapefile, the Census Bureau assigned a block size indicator (BLKZIND field) to each block based on the range of the estimated number of housing units in the prototype block. These values can be used to identify both potentially small population blocks or large population blocks to split or merge using the “Must Hold” and “Do Not Hold” flags.
Note:	Although discrete numbers have been established to assign each block a size value, the actual number of housing units in a block is approximate.
Blk size indicators range from “A” through “I”, with “A” blocks having the most housing units and “I” having the least. Prototype blocks estimated to contain no housing units are assigned an indicator letter of “Z.”
Table 36: Block Size Indicator Values
Indicator
Approximate Number of Housing Units
A
Greater than 2,000
B
1,600-1,999
C
1,200-1,599
D
1,000-1,199
E
700-999
F
480-699
G
400-479
H
240-399
I
1-239
Z
Potential “0” housing unit block

            4.5.2 Block Shape Review
In the prototype block shapefile, the Census Bureau also calculated a shape index (SHAPEIDX) using a simple area to perimeter ratio method. The shape index value will be between 0 and 1. The closer the value to 1, the more compact the block. The closer the value to 0 the less compact the block. These values can be used to help identify less compact blocks to see if their shape would interfere with the ability to conduct redistricting (e.g. long sinuous water bodies). Then, the “Must Hold” and “Do Not Hold” flags can be used to remedy this if it is an issue.
        4.6 Block Boundary Suggestion Flagging
BBSP participants can assign BBSP flags to features, suggesting they be held or not held as block boundaries, in the BBSP_2030 field of the edges shapefile. Using established criteria for delineating tabulation blocks, the Census Bureau has identified features already planned as 2030 block boundaries, which have a CBBFLG value of “4” in the edges shapefile. Refer to Table 1 for the complete planned feature list. The planned block boundaries may change if the criteria change, or if a feature’s attributes are updated through other Census programs.
The Census Bureau has also identified features that are ineligible to be 2030 block boundaries with a CBBFLG value of “9” in the edges shapefile. There are also features with no block boundary status assigned (CBBFLG value is null). Participants are not required to assign a BBSP flag (e.g., “Must Hold” or “Do Not Hold”) to every feature in the file, nor should they.
The CBBFLG field also shows block boundary statuses set by participants during initial BBSP in 2026. A CBBFLG of “1” indicates the participant wanted the feature held as a block boundary, while a CBBFLG value of “2” indicates the participant wanted the feature set as a “do not hold.”

Table 37: Description of Block Boundary Flagging Fields
Values
Description
BBSPFLG=1
2020 Participant Identified “Must Hold” Block Boundary.
BBSPFLG=2
2020 Participant Identified ” Do Not Hold” Block Boundary.
BBSPFLG=4
2020 Census Identified Planned Block Boundary.
BBSPFLG=9
2020 Census Identified Ineligible Block Boundary.
BBSP_2030=1
2030 Participant Identified “Must Hold” Block Boundary.
BBSP_2030=2
2030 Participant Identified “Do Not Hold” Block Boundary.
BBSP_2030=0
2030 Participant Identified “Must Hold” or “Do Not Hold” flag set during the initial BBSP Submission, now set for removal.
CBBFLG=1
2030 Participant Identified “Must Hold” Block Boundary (Populated by Census Bureau during processing of initial BBSP submission and corresponds to the value from the BBSP_2030 field when the Must Hold was applied and submitted.)
CBBFLG=2
2030 Participant Identified “Do Not Hold” Block Boundary (Populated by Census Bureau during processing of initial BBSP submission and corresponds to value from the BBSP_2030 field when the Do Not Hold was applied and submitted.)
CBBFLG=3
2030 Census Applied “Must Hold” Block Boundary.
CBBFLG=4
2030 Census Identified Planned Block Boundary.
CBBFLG=5
2030 Census Applied “Do Not Hold” Block Boundary.
CBBFLG=9
2030 Census Identified Ineligible Block Boundary.
            4.6.1 Block Boundary Criteria
All BBSP participant-provided 2030 Census “Must Holds,” i.e., BBSP_2030 = 1, combined with existing features and other identified or planned block boundaries, must form closed polygons.
2030 Census planned block boundaries, i.e., CBBFLG = 4, are an indication of what the Census Bureau plans to use as a 2030 Census block boundary if they were defined today. The planned block boundaries may change if the criteria change, or if the feature attributes are updated through other Census programs.
BBSP participant-provided 2030 Census “Do Not Hold” flags, i.e., BBSP_2030 = 2, will not be honored if the line they are placed on needs to be held for other purposes. For example, if a “Do Not Hold” flag was placed on an incorporated place boundary, the “Do Not Hold” flag would not be honored.
Table 38: Block Boundary Flagging Symbology
Value
Symbology
Description
Planned Block Boundaries
CBBFLG=4

Edges that are planned block boundaries have a blue halo symbology. 
Ineligible Block Boundaries
CBBFLG=9

Edges that are ineligible block boundaries have a red halo symbology. 
“Must Hold”
BBSP_2030=1 


Edges that are flagged as a “Must Hold” that were neither planned nor ineligible block boundaries have a dark blue line. 
“Do Not Hold”
BBSP_2030=2


Edges that are flagged as a “Do Not Hold” that were neither planned nor ineligible block boundaries have a dark red line.
Previously Flagged “Must Hold”
CBBFLG=1
Or
Census Applied “Must Hold” 
CBBFLG=3

Edges flagged as a “Must Hold” during BBSP have a blue line. 
Previously Flagged “Do Not Hold”
CBBFLG=2
Or
Census Applied “Do Not Hold” 
CBBFLG=5

Edges flagged as a “Do Not Hold” during BBSP have a red line.
NULL

Edges that have no block boundary flags vary between roads and invisible edges (dark brown) and hydro features (blue). 
CD/SLD Block Split
CBBFLG=S

For Reference Only: Edges that have been flagged as a CD/SLD Block Split have a green/gray halo symbology. 

            4.6.2 “Must Hold” Flags
Participants may assign a “Must Hold” flag to features to suggest them as 2030 block boundaries. Candidates for assigning a “Must Hold” flag are:
    • Newly added features.
    • Features not currently planned as block boundaries.
    • To ensure features planned as 2030 block boundaries are held should the Census Bureau change their “planned” status. 
Participants may wish to assign a “Must Hold” flag to features that are planned 2030 block boundaries in case the block definition criteria or feature classification codes change between when BBSP occurs and when the Census Bureau creates the 2030 Census blocks. Assigning a “Must Hold” to a planned block boundary feature will increase the likelihood that the feature will become a 2030 block boundary.
Be aware that assigning a “Must Hold” flag to a feature that is ineligible to be a block boundary or assigning a “Do Not Hold” flag to a feature that is planned to be a 2030 block boundary does not ensure that the Census Bureau will honor the request. The Census Bureau will re-evaluate the feature’s status based on the participant’s suggestion.
All “Must Hold” flags are contingent upon the features intersecting to form a closed polygon at the time the Census Bureau creates the 2030 blocks. 
To hold a feature as a 2030 block boundary when the feature does not form a closed polygon, add a feature extension to close the polygon. Feature extensions must meet the following criteria:
    • Extensions, combined with other features and planned holds, must form a closed polygon.
    • Extensions must be no longer than 300 feet. (If an extension needs to be longer than 300 feet, participants must provide justification.)
    • Extensions must be a straight line originating from the end of a road feature.
    • Extensions must terminate on a non-road feature, except for highways (i.e., extensions may terminate on highways – MTFCC S1100).
                4.6.2.1 Assigning “Must Hold” Flags

Figure 53: Feature Flagging Tool Button


Figure 54: Feature Flagging Tool Interface

Table 39: How to Apply a "Must Hold" Flag
Step
Description
Step 1
Click the Feature Flagging Tool button; see Figure 53. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature or left click and drag to select multiple linear features. 
Step 3
Right click to start editing. 
Step 4
The Feature Flagging Tool Interface opens; see Figure 54. Select the Action (flag) to apply to the linear feature: Must Hold. 
Step 5
Click on Update to save or Cancel to cancel. The symbology will update.
Note:	If the participant is performing boundary corrections, annexations, or deannexations to legal entities, do not flag the new boundaries with a “Must Hold” flag. The BAS team may adjudicate the updates with the BAS contact and apply the updates in a different manner than how they were submitted. However, the new legal boundaries will automatically be held as 2030 block boundaries. 
            4.6.3 “Do Not Hold” Flags
Participants may assign “Do Not Hold” flags to features that they do not want to become 2030 block boundaries. Potential candidates for assigning a “Do Not Hold” flag may include:
    • Private roads, trails, and unimproved roads.
    • Hydrographic features with no area, shown as a single-line feature, such as streams or creeks.
    • Any feature creating unnecessary blocks, such as highway ramps, traffic circles, or cul-de-sacs shown as open circles or “lollipops” in the Census geospatial files, and similar features.
Be aware that assigning a “Do Not Hold” flag to a feature that is a 2030 planned block boundary may not be honored if that boundary is needed to meet other Census criteria or program needs. For example, if a “Do Not Hold” flag is placed on an incorporated place boundary, the “Do Not Hold” will not be honored.
                4.6.3.1 Assigning “Do Not Hold” Flags
Table 40: How to Apply a "Do Not Hold" Flag
Step
Description
Step 1
Click the Feature Flagging Tool button; see Figure 53. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature or left click and drag to select multiple linear features. 
Step 3
Right click to start editing. 
Step 4
The Feature Flagging Tool Interface opens; see Figure 54. Select the Action (flag) to apply to the linear feature: Do Not Hold.
Step 5
Click on Update to save or Cancel to cancel. The symbology will update.
Note:	If the participant is performing boundary corrections, annexations, or deannexations to legal entities, do not flag the previous boundaries with “Do Not Hold” flags. The BAS team may adjudicate the updates with the BAS contact and apply the updates in a different manner than how they were submitted. 


            4.6.4 Removing a “Must Hold” or “Do Not Hold” Flag
Table 41: How to Remove a "Must Hold" or "Do Not Hold" Flag
Step
Description
Step 1
Click the Feature Flagging Tool button; see Figure 53. This is found under Edit Tools described in section 3.3.3.4.
Step 2
Left click on the linear feature or left click and drag to select multiple linear features. 
Step 3
Right click to start editing. 
Step 4
The Feature Flagging Tool Interface opens; see Figure 54. Select the Action (flag) to apply to the linear feature: NULL.
Step 5
Click on Update to save or Cancel to cancel. The symbology will update.
Note:	Figure 54 shows CD/SLD Split as an option for in the Feature Flagging Tool. This should only be applied when creating block splits during Phase 4 - Collection of Post-2020 Census Congressional and State Legislative District Plans and is not part of the BBSP update process.
            4.6.5 Digitizing a New Linear Feature Extension
To hold a feature as a 2030 block boundary when the feature does not form a closed polygon, add a feature extension to close the polygon. 

Figure 55: Add Linear Feature Extension Button
Table 42: How to Add a Linear Feature Extension
Step
Description
Step 1
Select Add Linear Feature Extension button; see Figure 55. This is found under Edit Tools described in section 3.3.3.4.
Step 2
To digitize the linear feature extension, left-click on the location where the linear feature ends to draw the linear feature extension and right-click to end the extension.
    • Extensions, combined with other features and planned holds, must form a closed polygon.
    • Extensions must be no longer than 300 feet (If an extension needs to be longer than 300 feet, participants must provide justification).
    • Extensions must be a straight line originating from the end of a road feature.
    • Extensions must terminate on a non-road feature, except for highways (i.e., extensions may terminate on highways – MTFCC S1100).
Step 3
If the linear feature extension is over 300 feet long, a justification for the length must be entered.  
Step 4
The linear feature extension will be shown and automatically flagged with a “Must Hold” flag.  
        4.7 Block Area Grouping Delineation
During the 2030 Census block creation, the Census Bureau will automatically group islands to form a single block if they have no road features and the islands fall within a 5-kilometer radius. Participants may also choose to group specific islands to create a single 2030 Census block, called a Block Area Grouping (BAG). The criteria for creating a BAG are as follows:
    • BAG must consist of two or more islands.
    • BAG perimeter must be entirely over water.
    • BAGs cannot overlap.
    • BAGs cannot cross the boundary of other geographies, such as county or incorporated place boundaries.
BAG delineation is optional, and most appropriate for states with hydrographic areas that contain many islands.
            4.7.1 Creating a Block Area Grouping

Figure 56: Create Block Area Grouping Button

Table 43: How to Create a Block Area Grouping
Step
Description
Step 1
Turn on the Block Area Grouping layer in the Layer Legend. 
Step 2
Select Create Block Area Grouping button; see Figure 56. This is found under Edit Tools described in section 3.3.3.4.
Step 3
Digitize the BAG polygon by left clicking to begin drawing the BAG and continue to left click at each vertex (shape point) of the line. Press 'd' to delete previous vertices.
Step 4
Left click on the starting point of the BAG to close the BAG.
Step 5
Right click to complete the polygon. It will turn blue when it is completed. 
 Step 6
The Block Area Grouping confirmation dialog box opens and click OK to save the BAG or Cancel to cancel the action. 
            4.7.2 Deleting a Block Area Grouping

Figure 57: Delete Block Area Grouping Button

Table 44: How to Delete a Block Area Grouping
Step
Description
Step 1
Turn on the Block Area Grouping layer in the Layer Legend.
Step 2
Select the Delete Block Area Grouping button; see Figure 57. This is found under Edit Tools described in section 3.3.3.4.
Step 3
Left click on the BAG to delete.
Step 4
Right click to complete the selection.
 Step 5
The Block Area Grouping confirmation dialog box opens. Click OK to delete the BAG or Cancel to cancel the action. 

        4.8 Block Boundary Review 
The Block Boundary Review Tool allows participants to systematically navigate to features on the map by 2030 “Must Hold” and “Do Not Hold” flags for review and further update if desired. Block boundary suggestions must be reviewed at least once before submitting updates to the Census Bureau.
Linear features flagged as a “Must Hold” or “Do Not Hold” in the initial BBSP phase can be verified during the block boundary review process. 

Figure 58: Block Boundary Review Button


Figure 59: Block Boundary Review Interface

Table 45: How to Review Block Boundary Flags
Step
Description
Step 1
Click on the Block Boundary Review button; see Figure 58. This is found under Review Tools described in section 3.3.3.5.
Step 2
All block boundary updates are displayed in the Block Boundary Review Table.
Step 3
Click on a row to select the feature and zoom to it on the map.
Step 4
There are several tools to sort through the Block Boundary Review table; see Figure 59.
    • Arrows will navigate up and down through the list of records (A).
    • Filter by Flags allows the participant to view specific flag types (B).
    • Hide will remove selected records from the table for the session (C).
    • All records can be selected with the Select All button (D).
Step 5
Review to confirm that edges have the appropriate block boundary flag assigned to it. 
    • Must Hold Flag will assign a “Must Hold” to the edge (E).
    • Do Not Hold Flag will assign a “Do Not Hold” to the edge (F).
    • Split will assign a Split to the edge (G). 
    • NULL will remove any “Must Hold”, “Do Not Hold”, or Split flag from the edge (H).
Step 6
If the flag is correct, no further action is needed.
Note:	Split flags are assigned during Phase 4 - Collection of the Post 2020 Census Congressional and State Legislative Plans. This option should not be added or removed during the BBSP update process.
            4.8.1 Performing Verification
 Linear features flagged as a “Must Hold” or “Do Not Hold” in the initial BBSP phase can be verified during the block boundary review process. 
During BBSP, any edges that were flagged as “Must Hold” were assigned a value of BBSP_2030=1 and any edges flagged with a “Do Not Hold” were assigned a value of BBSP_2030=2. During processing at Census, the BBSP_2030 was converted to the CBBFLG field and the BBSP_2030 field was cleared. 
All previously flagged edges can be displayed and updated using the Block Boundary Review Table. Verification updates allow for “Must Hold” or “Do Not Hold” flags to either be removed or replaced. Participants do not need to re-flag their edges with the same flag (e.g. do not select all of the current edges with a “Must Hold” flag in the CBBFLG field and flag them with “Must Hold” flags again.)
Any updates to the flags during BBSP Verification will be written to the BBSP_2030 field and the CBBFLG field will be updated with those changes during Census processing. 

Figure 60: Block Boundary Review Interface Verification Filter Options
Table 46: How to Perform Verification
Step
Description
Step 1
Click on the Block Boundary Review button; see Figure 59. This is found under Review Tools described in section 3.3.3.5.
Step 2
Select “Filter by Flags” to select “Previously Flagged Must Hold” and/or “Previously Flagged Do Not Hold,” see Figure 60.
Step 3
Click on a row to select the feature and zoom to it on the map.
Step 4
Verification updates (optional) include the following actions:
    • To remove a previously flagged "Must Hold" or "Do Not Hold," use the NULL action within the Block Boundary Review Module. The BBSP_2030 field will be updated with a value of '0.'  
    • To replace a previously flagged "Must Hold" or "Do Not Hold," use the appropriate action within the Block Boundary Review Module. The BBSP_2030 field will be updated with either a ‘1’ for a “Must Hold” flag or a ‘2’ for “Do Not Hold” flag.
Participants do not need to re-flag their edges with the same flag (e.g. select all the current edges with a  “Must Hold” flag and flag them with “Must Hold” flags again.
        4.9 Potential Small Block Check
The Potential Small Block Check reviews the edges within the project and returns a list of potential small blocks that exist in the project based on the planned and suggested block boundaries. 
All small blocks under 3,000 square meters are identified and listed. Within this list of potential small blocks: 
    • Type “ - “: Small blocks under 3,000 square meters that are created by the planned block boundaries and do not include “Must Hold” flags. 
    • Type A: Small blocks of 500 square meters or less that have one or more bounding edges where a "Must Hold" flag is involved. 
    • Type B: Small blocks of 500.1 square meters to 3,000 square meters that have one or more bounding edges where a "Must Hold" flag is involved. 
If the small blocks are unwanted or unintentional, they can be adjusted through Block Boundary Suggestion Flagging (i.e., remove the “Must Hold” flag from a bounding edge or apply a “Do Not Hold” flag). Potential small blocks must be reviewed at least once before submitting updates to the Census Bureau.

Figure 61: Potential Small Block Check Button


Figure 62: Potential Small Block Check Interface
Table 47: How to Review Potential Small Block Output
Step
Description
Step 1
Click on the Potential Small Block Check button; see Figure 61. This is found under Review Tools described in section 3.3.3.5.
Step 2
Click on a row to select the feature and zoom to it on the map. Filter and sort are available. 
Step 3
If potential small blocks can be adjusted by applying or removing “Must Hold” or “Do Not Hold” flags, the participant should open the Feature Flagging Tool (under Edit Tools; see section 4.6) and apply the correct flags. 
Step 4
It is recommended to run the check several times while editing the project. 
        4.10 Boundary Review
The Boundary Review Tool allows updates to area landmarks and legal entities (Incorporated Places and MCDs) to be viewed. Records can be clicked on to navigate from update to update. In addition, legal information can be added via the Boundary Review interface.   

Figure 63: Boundary Review Button


Figure 64: Boundary Review Selection Interface


Figure 65: Boundary Review Tool Interface

Table 48: How to Review Boundary Changes
Step
Description
Step 1
Click on the Boundary Review button; see Figure 63. This is found under Review Tools described in section 3.3.3.5.
Step 2
Select which layer to view; see Figure 64. Only layers with changes will be available to select. 
Step 3
Click on a row to select the feature and zoom to it on the map.
Step 4
If spatial edits need to be made use Modify Area Feature Tool (see section 4.2 and 4.3) to apply the edits. Legal Information can be updated by clicking on the Add Legal Information button within the Review table. 

        4.11 Submitting Updates to the Census Bureau
The Census Bureau conducts the RDP activities through the official liaison appointed by the governor and legislative leadership of the state. The official liaisons are responsible for making BBSP updates and submitting the projects to the Census Bureau. However, the official liaisons have two options for designating technical liaisons to assist them in making BBSP updates on behalf of the state.
• Option 1. Official liaisons can formally designate technical liaisons who are able to perform geographic updates and submit completed updates to the Census Bureau on their behalf. Official liaisons should reach out to the RVDO at 301-763-4039 or <[email protected]> to make technical liaison designations.
• Option 2. Official liaisons can delegate work to designees who perform the updates and submit the updates back to the official liaison. The official liaison will submit the work to the Census Bureau if they approve the work. If the official liaison determines that BBSP work completed by a designee requires changes or additional work, it is the official liaison's responsibility to decide whether to make the changes or return the project to their designee for further updates.
The liaison responsible for submitting updates to the Census Bureau should submit completed, county-level files on a flow basis to the Census Bureau directly through GUPS Web. Do not hold files to submit all at once. Submit files as they are completed, especially at the beginning of the update period, so that the Census Bureau can provide feedback if there are errors, omissions, or other concerns.
            4.11.1 Export Tools
                4.11.1.1 Submit to Census
Projects can be directly submitted to the Census Bureau from GUPS Web, bypassing the Secure Web Incoming Module (SWIM). Project owners and collaborators can submit projects. This option will only be visible for Project Owners and Project Collaborators. 

Figure 66: Import/Export Button

Figure 67: Submit to Census Interface

Table 49: How to Submit a Project to Census
Step
Description
Step 1
While in the project that should be submitted, click the Import/Export button on the GUPS Web Navigation Bar; see Figure 66.
Step 2
Expand Export Tools and then select Submit to Census; see Figure 67.
Step 3
Select Submit. 
Step 4
The project has been submitted to the Census Bureau. If the project needs to be recalled, reach out to the RVDO at 301-763-4039 or at [email protected]. 
Note: Please alert the RVDO to any technical liaisons (project owners and project collaborators) who are approved to submit projects to the Census Bureau to ensure the correct submission processing.  

                4.11.1.2 Submit for Review
Projects completed by Project Reviewers can be directly submitted to Project Owners and Collaborators for their review. The steps for submitting a project for review mirror the steps in Table 49 replacing the “Submit to Census” option.
                4.11.1.3 Download Project Files
The Download Project Files tool allows users to download a copy of the current project submission for their records. 

Figure 68: Download Project Files Interface

Table 50: How to Download Project Files
Step
Description
Step 1
Click the Import/Export button on the GUPS Web Navigation Bar; see Figure 66. 
Step 2
Expand Export Tools and then select Download Project Files; see Figure 68.
Step 3
Select Download. 
Step 4
Click Confirm to continue the download or Cancel to cancel. 


                4.11.1.4 Export Map
This allows participants to export a map (in pdf, png, or jpeg form) of a specific area. 

Figure 69: Export Map Interface
Table 51: How to Export a Map
Step
Description
Step 1
Click the Import/Export button on the GUPS Web Navigation Bar; see Figure 66.
Step 2
Expand Export Tools and then select Export Map; see Figure 69.
Step 3
Enter following fields:
    • Map Title
    • Map Subtitle
Select the following fields:
    • Page Orientation (Portrait, Landscape)
    • Desired Page Size (Letter 8.5X11, Large 11X17)
    • Export File Format (.PDF, .PNG, .JPEG)
Step 4
Click Save to export the map or Cancel to cancel. 


    Appendix A Partnership Shapefile Names and Layouts
Partnership Shapefiles reflect the legal boundaries and names for all governments, as reported through the previous year’s BAS. Participants can access the partnership shapefiles from two locations: 
    • Download the partnership shapefiles from the Geography Partnership website at:
        ◦ <www.census.gov/geographies/mapping-files/time-series/geo/partnership.html> 
    • Download the partnership shapefiles from the FTP site at:
        ◦ <https://www2.census.gov/geo/pvs/>
Census Bureau files are in GCS NAD83 format and can be projected into any local coordinate system/project. Most GIS software packages will allow users to transform file coordinate systems and projections.
Partnership shapefile technical documentation is available at: <https://www.census.gov/programs-surveys/geography/technical-documentation/complete-technical-documentation/partnership-shapefiles.html>


    Appendix B MTFCC Descriptions
The MTFCC is a 5-digit code assigned by the Census Bureau to classify and describe geographic objects or features. A full list of MTFCC codes and descriptions can be found at <www.census.gov/library/reference/code-lists/mt-feature-class-codes.html>.