Boundary and Annexation Survey (BAS)
Supplemental Information for Digital Updates

I.  Requirements

1.	The user must be prompted to verify and make updates (if necessary) to the Boundary and Annexation Survey (BAS) and 		Highest Elected Official (HEO) contact information via the BAS form prior to starting map editing.

2.	The user must be able to easily view the spreadsheet which is populated by the popup boxes (or similar solution) in 		rules 8-10.

3.	User must be able to add or delete area from an entity by creating new features and selecting existing features to 		comprise a polygon.  

4.	When a participant creates a polygon, they must be able to add data via a popup box (or similar solution) to the 		form.  In addition, a polygon ID will be auto-generated each time the edits are saved by the user.  This polygon ID 		will link the information filled in the pop-up box (or similar solution) to a record in the BAS form and in the 		polygon attribute table.  The polygon ID must be auto-populated into the polygons attribute table as well as into 		the form.  The field name for ID in the attribute table will be ID.  If a participant creates multiple polygons 		prior to saving, all polygons will be saved with the same ID.  The participant must enter at least one polygon per 	ID.

5.	The county participant must select the entity type they are editing before they create a change polygon. A dropdown 		menu must be available for them to choose County, MCD, or Place.  Once they have selected the entity type they must 		be able to select the target entity from a drop down menu and the type of change they would like to make (see number 		35 for a list of types of change).  The list of entities must be only of entities which are in the entity type that 		they chose.  The types of change list must include (new entity) as an option for both Minor Civil Division (MCD) 		and Place, but not when the user selects County.  This is because Counties may report new places and MCDs that are 		newly incorporated.  They must then be able to create a change polygon and populate attribute data into a popup box 		(or similar solution) (see number 10 for the attribute data required for each entity type).  

6.	If the person is an MCD or Place level participant, the map must be zoomed to the extent of the MCD/Place.  The 		participant must be able to add or delete area.  The participant will NOT be allowed to add a new entity.

7.	If the person is a tribal participant, the map must be zoomed to the extent of the Tribal area.  The participant must 
	be allowed to add or delete area from anywhere on the map.  The participant must also be able to add tribal 			subdivisions within existing or new boundaries.  The participant must be asked the entity type, target entity, and 		change action type before creating a change polygon.  After the change polygon is created the participant must be 		asked to populate a popup box (or similar solution) with the attribute data.  The entity type dropdown list must 		include Reservation/Off-Reservation Trust Land and Tribal Subdivision.  The types of change are listed in number 		33.

8.	If county participant selects New Entity, a popup box (or similar solution)  must ask questions to obtain the 		following information:

Column in Form	Number of Characters	Character Type	Allowed Values	Required	
Form_ID		4			Integer				Auto-filled	
Entity Name	30			Text				Y		
Entity Type	20			Text				Auto-filled by the target layer that is chosen
Effective Date				Date				Y

9.	If a tribal participant selects New Entity for tribal subdivision, a popup box (or similar solution) must ask 	questions to obtain the following information

Column in Form		Number of characters	Character Type	Allowed Values	Required

Form_ID			4			Integer				Auto-filled

Tribal Subdivision Name	30			Text				Y

Status (Type)		1			Text		A  Active
								I  Inactive	Y

Effective Date		Date							Y

10.	A popup box (or similar solution) must ask questions to obtain the following information.  This information must be 	populated into the form.

Column in Form	Number of 	Character Type	Required    	Non-Tribal	Non-Tribal 	Tribal	Tribal 					Characters			    				Allowed Values		Allowed Values

Form_ID		4		Integer		Auto-filled		X	X	

Entity Name	Auto fill	text		Auto-filled		X	X	

Type of Change	1 		text		Auto-filled		X	A, B, C, D, 	X	A, B, C, D, F, E, O
										E, F, O

Authorization 	1		text		Y (if Type of 		X	O, L, R, S, X	X	A, C, D, N, X
type						Change is A or D)
						Editable, but not 
						required if 
						Change type is 
						F or C	

Authorization 	120		Text		Y (if Type of 		X			X
number						Change is A or D 
						and state does 
						not equal Georgia)  
						Editable, but not 
						required if Change 
						type is F or C	

Effective Date			Date		Y (if Type of 		X			X
						Change is A or D)
						Editable, but not 
						required if Change 
						type is F or C		

Boundary 	3		Text		Y (if Type of 		X	In, Out		X	In, Out
correction					Change equals B)

County where 	120		Text		Auto-filled		X			X	
change occurred

MCD where 	120		Text		Editable but not 	X
change occurred					required (not 
						required for tribal
						submissions)				

Type of Land 	1		Text		Y (required only for 	X				R, T
Added						tribal submissions 
						that are not 
						Boundary corrections)			

Area		10, 1 		Double		Y (if state equals 	X			X
		decimal 			Georgia and Change 
		places				Type equals A or D) 
						Editable but not 
						required for other states		

11.	User must be able to create a change polygon which crosses into another entitys territory.  If this occurs the user 		must be notified of the fact that they are annexing a portion of an adjacent entity.  The user must confirm that this 	is what they intend to do.  The user must also be notified that this change will not be finalized until it is 			confirmed by the adjacent entity.

12.	User must be able to click on all polygons and view the attribute information.

13.	User must be able to add a linear feature.
a.	User is given the option to start and end the feature at an intersection or at the end of a linear feature (point), 		on a liner feature (line), or in space.  
b.	The user must be able to add curve points in between start and end points.
c.	User must choose a classification (listed in Section V) via a popup window (or similar solution).
d.	User is allowed to name the feature with acceptable types, prefixes, and types via a popup window (or similar 			solution).  Provide a means for the user to select unnamed for unnamed features so that the user does not type 		unnamed.

14.	User must be able to delete features (existing segments) 
a.	User is able to delete existing segments.
b.	If feature is a block boundary, the visible feature may be deleted but the block boundary will remain.

15.	The user must be able to add nodes to a line to split a feature.
a.	When a node is added, the existing feature should be split and attributes (names, addresses, classification code) 		should be duplicated on both sides.  
b.	User must be able to modify the lines and their names and classifications separately.

16.	User must be able to add, edit, and delete primary names of linear features.

17.	User must NOT be able to add, edit, or delete alternative names.

18.	User must be able to copy the name and classification from an existing line, digitize a new line with these 			attributes, and delete the original line.

19.	User must be able to edit the classification of a feature (see classification list in Section V).

20.	User must be able to click on all features and view attribute information (all names, classification code, left 		geography 2-cell, right geography 2-cell).

21.	User must be able to undo their last action.

22.	Please use a different color for each of the different change types for polygons (A, B, C, D, F, and O). Boundary 		corrections (add area) and boundary corrections (remove area) must be shaded in separate colors.

23.	Prior to data being submitted to the Census Bureau the program must ask the user if all map edits and forms are 		completed and finalized.

24.	The pop-up boxes (or similar solution) referred to throughout the instructions will populate the BAS forms based on a 	unique form ID that is auto-generated by the program each time the user saves their edits.  This ID will serve to 		link together the change polygons, the change polygon attribute table and the BAS form.  

25.	The participant must be able to view and edit data in the BAS form at any time, through either popup boxes (or 			similar solution) or the form.

26.	When the participant submits their form it should contain all the information that was entered into the form through 		either the form review and popup boxes (or similar solution).

27.	If the entity deletes a polygon, which they have added during their edit session, do not create a add polygon or 		delete polygon in the change layer returned to the Census Bureau. 

28.	The all lines shapefile that is returned to the Census Bureau must contain all lines that have been added, deleted, 		or edited by the participant, including boundary lines.

29.	If the entity adds a line then splits the do not change the code to SL.  It should remain AL for add line.

30.	The participants submission must include a change polygon shapefile which has a form ID (auto-generated after each 		save edits) associated with each change polygon.

31.	The participants submission must also include the whole entity boundary, including entity name and entity codes for 		each entity submitted.  (e.g. when a county submits for its entities, all MCDs and places must have whole entity 		polygons which include entity name and entity codes.)

32.	If the participants submit address break information the shapefile must include address break information which is 		associated to the appropriate TLIDs and sent back to the Census Bureau with the address ranges in the appropriates 		four fields (Right-to, Left-to, Right-from, Left-from) in the all lines attribute table.  If the entity does not 		key-in address information, please leave these fields as null.

33.	The participant must be allowed to add, delete, or rename area landmarks.  Please return all previously provided 		attribute information along with change type information.

34.	The user must be required to choose a boundary change type from a list before creating a change polygon.  The 			boundary change types selection are:
a.	Addition or Annexation
b.	Boundary Correction (add area)
c.	Boundary Correction (remove area)
d.	Geographic Corridor
e.	Deletion or Deannexation
f.	New Entity or Tribal Subdivision
g.	Geographic Offset
h.	Other

35.	The corresponding code, as stated in Section II, must be populated in the Type of Change field of the table.  For 		Boundary Correction (add area) and Boundary Correction (remove area) polygons, populate the Type of Change field with 	B. Populate the Relate field with In if Boundary Correction (add area) is chosen or with Out if Boundary 			Correction (remove area) is chosen. 

36.	A tribal subdivision boundary must not be able to cross an American Indian / Alaska Native / Native Hawaiian (AIANNH) 	boundary.

37.	During verification, the user must be able to edit lines in the attribution spreadsheet.  They must not be able to 		add a new record at that time.

38.	The participant type can be identified by looking at the first digit of the BAS Entity ID Code in the setup file.  
	Entity Code	Entity Type
	1		Place
	2		County
	3		MCD
	4		American Indian Areas

39.	The Census Bureau will provide data files for BAS forms named the following:
a.	<Entity ID>_MAIN.dat
b.	<Entity ID>_NAMES.dat
c.	<Entity ID>_CHANGES.dat
d.	<Entity ID>_ST_FIPS.dat
e.	<Entity ID>_TRIBALSUBDIVISION.dat

40.	On the AIA form: if an annexation crosses into multiple counties, populate the COUNTY_NAME field with all counties 		which the annexation exists in.

41.	Entity Code explanations:
a.	Place -- 10100031205
i.	First Digit -- Entity Type (place)
ii.	2nd and 3rd digits -- State code
iii.	4th  6th digits -- Always 000 for Places
iv.	7th  11th digits -- Place FIPS code
b.	County -- 20115200000
i.	1st digit -- Entity Type (County)
ii.	2nd  3rd digits -- State code
iii.	4th  6th digits -- County code
iv.	7th  11th digits -- Always 00000 for Counties
c.	Minor civil division -- 30115233457
i.	1st digit -- Entity Type (MCD)
ii.	2nd  3rd digits -- state code
iii.	4th  6th digits -- county code
iv.	7th  11th digits -- MCD FIPS code
d.	American Indian area -- 49900024300
i.	1st digit -- Entity Type (AIA)
ii.	2nd  3rd digits -- Always 99 for AIAs
iii.	4th  6th digits -- Always 000 for AIAs
iv.	7th  10th digits -- AIA Code
v.	11th digit -- Always 0 for AIAs

42.	Output change shapefile naming conventions:
Participant		Changes being submitted		Shapefile name
All			All Lines			<Geographic Program Name>_<BASID>_LN_Changes.shp
All			Area Landmark			<Geographic Program Name>_<BASID>_Alndk_Changes.shp
All			Point Landmark			<Geographic Program Name>_<BASID>_Plndk_Changes.shp
All			Hydrography Area		<Geographic Program Name>_<BASID>_HydroA_Changes.shp
Place			Place				<Geographic Program Name>_<BASID>_changes.shp
County Subdivision	County Subdivision		<Geographic Program Name>_<BASID>_changes.shp
County			Place				<Geographic Program Name>_<BASID>_changes_incplace.shp
County			County Subdivision		<Geographic Program Name>_<BASID>_changes_cousub.shp
County			County				<Geographic Program Name>_<BASID>_changes.shp
AIANNH			AIANNH				<Geographic Program Name>_<BASID>_changes.shp
AIANNH			Tribal Subdivision		<Geographic Program Name>_<BASID>_changes_tribalsub.shp
Consolidated City	Consolidated City		<Geographic Program Name>_<BASID>_changes.shp
ANRC			ANRC				<Geographic Program Name>_<BASID>_changes.shp

43.	Output whole entity shapefile naming conventions:
Participant		Whole entity type	Shapefile name
Place			Place			<Geographic Program Name>_<BASID>_WholeEntity.shp
County Subdivision	County Subdivision	<Geographic Program Name>_<BASID>_ WholeEntity.shp
County			Place			<Geographic Program Name>_<BASID>_ WholeEntity_incplace.shp
County			County Subdivision	<Geographic Program Name>_<BASID>_ WholeEntity_cousub.shp
County			County			<Geographic Program Name>_<BASID>_ WholeEntity.shp
AIANNH			AIANNH			<Geographic Program Name>_<BASID>_ WholeEntity.shp
AIANNH			Tribal Subdivision	<Geographic Program Name>_<BASID>_ WholeEntity_tribalsub.shp
Consolidated City	Consolidated City	<Geographic Program Name>_<BASID>_WholeEntity.shp
ANRC			ANRC			<Geographic Program Name>_<BASID>_WholeEntity.shp

44.	Zip file naming conventions:
Participant		Zip File
Place			<Geographic Program Name>_<BASID>_return.zip
County Subdivision	<Geographic Program Name>_<BASID>_return.zip
County			<Geographic Program Name>_<BASID>_ return.zip
Consolidated City	<Geographic Program Name>_<BASID>_ return.zip
ANRC			<Geographic Program Name>_<BASID>_ return.zip
AIANNH			<Geographic Program Name>_<BASID>_ return.zip
Consolidated City	<Geographic Program Name>_<BASID>_ return.zip
ANRC			<Geographic Program Name>_<BASID>_ return.zip

45.	Each time a participant submits, changes please add the version number to the zip file.
	Ex. BAS08_10100012345_return_v3.zip

46.	Excluding shapefiles, all files that are extracted must be named <Geographic Program Name>_<parent file 			name>_return. 
	Ex. BAS08_22714100000_Names_return.dat

47.	Please output the data returned from the file previously named BASForm.asc in a dBASE file so that it may be easily 		joined to a shapefile in a GIS.  This file can be named <Geographic Program Name>_<BASID>_Form.dbf.  The file 			originally named ParticipantInfo.txt should be named as <Geographic Program. Name>_<BASID>_ParticipantInfo.txt

48.	Please follow the table below in labeling the BAS Changes:
Change Type		Label						Caveat

Addition/Annexation, 	<Target Entity Name>, <Change Type>, 		If the change does not have an Authorization
Deletion/Deannexation	<Authorization Number>, <Effective Date>	Number disregard the requirement for the 											Authorization Number.
Boundary Correction	<Target Entity Name>, <Change Type>, computer 
			generated sequential number unique to change 
			type	

Geographic Corridor 	<Target Entity Name>, <Change Type>, 		If the change does not have an Authorization
			<Authorization Number>, <Effective Date>, 	Number or Effective Date, assign
			computer generated sequential number unique to 	a computer generated sequential number.
			change type, if applicable
	  
Geographic Offset	<Target Entity Name>, <Change Type>, computer 
			generated sequential number unique to change 
			type	

New Entity 		<New Entity Name or New Tribal Subdivision 	If the change does not have an Authorization 
			Name>, <Change Type>, <Authorization Number>, 	Number, disregard the request for the
			<Effective Date>				Authorization Number. 

Other			<Target Entity Name>, <Change Type>, computer 
			generated sequential number unique to change 
			type	

49.	User must be able to print or save maps and forms by clicking on an easily identifiable icon.

50.	User must be able to save data and reenter the program at a later date to complete the updates.

51.	The table below describes the change types that must be available in the dropdown menu when a target layer is chosen.  	See rule 34 for additional information about boundary corrections. 
Target layer		Available Change Types
Place			A, B, C, D, E, F, O
County Subdivision	A, B, D, E, F
County			A, B, D
Tribal Subdivision	A, B, C, D, E, F, O
AIANNH			A, B, C, D, E, F, O

52.	A County Subdivision boundary must not be able to cross a County boundary.

53.	A disclaimer must be at the bottom of the screen stating All boundary changes are subject to U.S. Census Bureau 		processing prior to being incorporated into the MAF/TIGER database.

54.	The participants must be able to work on their file and submit to the Census Bureau as a whole entity  (i.e., 		entities that are in multiple counties must be able to be worked on and submitted to the Census Bureau as one 			complete entity).

55.	The following fields are required in the Setup File table:
Element				Example Value		Valid Value 		Required 	Comments
							(Type& max size)	(Y/N)
Geographic Program Name		BAS08			alphanumeric (10)	Y	 

Participant's Entity Name	Autauga County		alphanumeric (60)	Y	 

Participant's Entity Code	CO01001			alphanumeric (11)	Y	 

Core County codes for data	01001			alphanumeric (1000)	Y	 

Fringe County codes for data	01021, 01047, 		alphanumeric (1000)	Y
				01051, 01085, 	 
				01102

Minimum Latitude Coordinate	28.0042			numeric decimal		Y	 

Maximum Latitude Coordinate	30.317			numeric decimal		Y	 

Minimum Longitude Coordinate	-101.7748		numeric decimal		Y	 

Maximum Longitude Coordinate	-98.7659		numeric decimal		Y	 

CFCC/MTFCC flag			CFCC			alpha (5)		Y		Values will always be either 													"CFCC" or "MTFCC"

Username			BAS08			alphanumeric (10)	Y		Values will always be the													name of the geographic 												program

First Name			John			alpha (20)		Y	 

Last Name			Smith			alpha (30)		Y	 

Title				GIS Planner		alphanumeric (45)	N	 

Department Name			Information Technology	alphanumeric (60)	N	 

Mailing Address			8903 Presidential 	alphanumeric (40)	Y
				Parkway	 

City				Upper Marlboro		alphanumeric (40)	Y	 

State				MD			alpha (2)		Y	 

Zip Code			20772			alpha (5)		Y	 

Zip+4				9099			alpha (4)		N	 

Phone Area Code			301			numeric (3)		N	 

Phone Exchange			763			numeric (3)		N	 

Phone Last4			8630			numeric (4)		N	 

Phone Extension			9			numeric (4)		N	 

FAX Area Code			301			numeric (3)		N	 

FAX Exchange			763			numeric (3)		N	 

FAX Last4			4710			numeric (4)		N	 

E-mail Address			john.smith@local.gov	alphanumeric (100)	N	 

Entity ID			20603700000		numeric (11)		Y	 

Table Review File Included Flag	Y			alpha (1)		Y		Values will always be "Y" or 												"N"

Boundary Text			Boundaries as of 	alphanumeric(40)	Y	 
				January 1, 2006

II.	Coding Explanations

Type of Geographic Area Changes
Code	Explanation
A	Addition or Annexation 
B	Boundary Correction
C	Geographic Corridor
D	Deletion or Deannexation
E	New Entity, Tribal Subdivision, or Landmark
F	Geographic Offset
O	Other

Authorization Types
Code	Explanation
A	Act of Congress, Statute, or Federal Law
C	Federal Court Decision
D	Deed Placing Land into Trust
L	Local Law
N	Federal Register Notice or Notice Published in a Local Newspaper by the Federal Government
O	Ordinance
R	Resolution
S	State Level Action
X	Other Type

Type of Land Added or Deleted
Code	Explanation
R	Reservation
T	Off-Reservation Trust Land

III.  Feature Classifications (Must be the same as the early submission from LUCA)
1.	Road Features
a.	Interstate Highway or Primary road with limited access
b.	Primary Road without limited access, US Highway, State Highway, or County Highway
c.	Secondary and connecting roads
d.	Local Neighborhood Road, Rural Road, or City Street
e.	Vehicular Trail (4WD)
f.	Ramp
g.	Service Drive usually along a limited access highway
h.	Walkway/Pedestrian Trail
i.	Stairway
j.	Alley
k.	Private Road for service vehicles (logging, oil fields, ranches, etc)
l.	Private Driveway
m.	Airport or Airfield

2.	Water Features
a.	Stream/River
b.	Braided Stream
c.	Canal, Ditch, or Aqueduct

3.	Railroads
a.	Railroad Feature (Main, Spur, or Yard)
b.	Carline, Streetcar Tract, Monorail, Other Mass Transit Rail
c.	Cog Rail Line, Incline Rail Line, Tram

4.	Miscellaneous Features
a.	Non-visible Boundary
b.	Pipeline
c.	Power Transmission Line
d.	Fence Line
e.	Ridge Line
f.	Aerial Tramway/ Ski Lift
g.	Airport or Airfield
h.	Property/Parcel Line
i.	Ferry Crossing

Type of Linear Feature Changes
Change Type Code	Description
AL			Add Line
DL			Delete Line
CA			Change Attributes (Applies to Address Breaks, Change Name, and Change Feature Class Code)
SL			Split Line
RL			Replace Line

IV. Area and Point Landmarks Business Rules

1.	If the participant selects Area Landmark as the target layer they must be able to select the following change types:
	Boundary Correction (add area)
	Boundary Correction (remove area)
	New Landmark
	Deletion or Deannexation
	Change Name

2.	If the participant selects Point Landmark as the target layer them must be able to select the following change types: 
	New Landmark
	Deletion 
	Change Name

3.	If a participant selects to change the name or add a new area or point landmark, a name must be entered into the 		fullname field.

4.	The participant must be able to add a new area or point landmark by selecting New Landmark and selecting the faces or 	adding points.

5.	The participant must be able to delete an area or point landmark by selecting Deletion or Deannexation (area 		landmarks) or Deletion (point landmarks).

6.	The corresponding code, as stated in Section V, must be populated in the chng_type field of the table.  

7.	For area landmarks, Boundary Correction (add area) and Boundary Correction (remove area) polygons, populate the 		chng_type field with B.  Populate the Relate field in the shapefile with In if Boundary Correction (add area) is 		chosen or with Out if Boundary Correction (remove area) is chosen. 

8.	The participant must have the same update functionality for these change types as it does with other layers.

9.	Area hydrography can be edited in the same manner as area landmarks (including same chng_types).

V.  Coding Explanations for Area and Point Landmarks

Type of Change for Area Landmarks / Hydrography Area
Code	Explanation
B	Boundary Correction
D	Deletion or Deannexation
E	New Landmark
G	Change Name

Type of Changes for Point Landmarks
Code	Explanation
D	Deletion 
E	New Landmark
G	Change Name