bom_streets_pdx
Category	Transportation - Streets
Feature Dataset Name	STAND-ALONE
Item Name	BOM_STREETS_PDX
Database Type	SDE
Originator	City of Portland
Bureau	Bureau of Technology Services - Corporate GIS
Publication Date	01/01/1990
Abstract	Segments from the Regional Streets Centerline Network that are used for specific operations and analysis by the City of Portland Bureau of Maintenance. The dataset includes segments that are maintained in the Centerline Maintenance environment but are not transferred to the Regional Streets Network.  It contains planned and other non-typical orprimary street types.  This dataset does not create a connected street network and does not include the data fields and structure necessary for performing routing operations.
Purpose	Allows City of Portland Bureau of Maintenance employees to have access to segments they need to perform analysis and map their operations.
Supplemental Information
Last Dataset Update	01/22/2025 17:20
Last Source Update	01/22/2025 04:44
Maintenance/Update Frequency	Weekly
Extent	Clackamas County, Multnomah County, and Washington County, Oregon
Data Type	Vector
Shape Type	Poly Line
Feature Count	7305
Horizontal Position Accuracy
Horizontal Position Accuracy Link	Taxlots
Progress	Complete
North Bounding Coordinate	779837.610892385
South Bounding Coordinate	471315.520669296
East Bounding Coordinate	7890317.77001312
West Bounding Coordinate	7471413.0593832
Theme Keyword(s)	Streets, Centerline, BOM
Theme Keyword Thesaurus	None
Place Keyword(s)	Portland, Multnomah County, Washington County, Clackamas County, Oregon
Place Keyword Thesaurus	None
Access Constraints	Available for Public Use
Use Constraints	These data are distributed under the terms of the City of Portland Data Distribution Policy. Care was taken in the creation of this data but it is provided "as is". The City of Portland cannot accept any responsibility for errors, omissions, or positional accuracy.
Source Dataset Type	File Geodatabase
Output Geodatabase	EGH_Public
Distribution	Grid: State plane coordinate system 1983(91). Units: International feet Datum: North American Datum of 1983/1991 (HPGN) Liability: The information in this file was derived from digital databases on the City of Portland GIS. Care was taken in the creation of this file. The City cannot accept any responsibility for errors, omissions, or positional accuracy. There are no warranties, expressed or implied. Format: Shapefile or File Geodatabase Feature Class - Data will be provided via City of Portland FTP Site. Online Resource: http://portlandmaps.com/opendata Online Instructions: City of Portland Public/Open Data is distributed via the PortlandMaps Open Data Site - http://portlandmaps.com/opendata. Data not available on the PortlandMaps Open Data site can be requested by contacting the City of Portland CGIS Group - maps@portlandoregon.gov Transfer Size: varies SPCS Zone Identifier: 5076
Contact(s) Add
File(s) Add Add File File Description Cancel Add File
Images	52060.png 53.36Kb X
Lineage Add
01/01/1988	Acquired street linework and annotation from Oregon Department of Transportation. This was digitized from 7 1/2 minutes USGS quad sheets.
01/01/1991	Replaced linework with newly digitized line work which "fell within" the street rights-of-way from the tax lot layer. Attributes were transfered from the U.S. Census Bureau TIGER file. Street names and address ranges were updated using paper maps collected from the three counties. Thomas Brothers Mapping was the primary contractor.
01/01/1991	The dataset was originally created by modifying the 1990 TIGER Census Centerline dataset to match the Oregon Department of Transporation (ODOT) maps.
04/01/1998	We deleted types 1600, 1900, 2100, 2200, 3100, 3210, 3220. Streets are no longer shown on the Clark County side of the river. Contact Clark County for detailed street information.
07/01/1998	This layer was reprojected to the NAD83/91 projection (also known as HPGN) as part of a conversion of all RLIS map layers.
07/15/2001	Projection information (.prj file), compatible with ArcGIS 8.1, was added to the layer.
10/31/2001	Add XML metadata compatible with ArcCatalog 8.1
10/31/2002	QC street name, addresse, city and zipcodes using E-911 CAD materials for Clackamas County (complete 20020901) and Washington County (complete 20021031).
10/24/2003	Hillsboro streets positional accuracy was improved. Streets were snapped to local planimetric data with a +/- 1' tolerance. The City of Hillsboro now maintains their subarea and supplies the data to Metro on a weekly basis.
01/01/2004	The City of Portland receives updates of the Regional Street Network on a quarterly basis. These updates are written to the regional dataset to update the segments that are not maitained by the City of Portland.
04/07/2020	The City of Portland maintains and updates the segments in and around the City of Portland (there is approximately a 1mi buffer around the City of Portland that is maintained by the City) on a weekly basis.

Attribute Tables & Domains

X bom_streets_pdx
Table Description
Table Jurisdiction
Column Sort	Column Name	Column Alias	Column Type	Column Size	Domain Value(s)	Column Description Add
1	LENGTH	LENGTH	Numeric	8	Add	X Software Calculated length of the street segment.
1	LOCALID	Segment ID	Integer	4	Add	X The Jurisdiction Specific Identification Number for the segment. This ID is used to coordinate editing the dataset with other regional jurisdictions.
1	ZERO	Leading Zero Indicator	Integer	2	Add	X Indicates whether the addresses along the segment begin with a zero (i.e.: 0321 SW Main St.).
1	PREFIX	Street Name Prefix	String	2	Add	X The Street Name Prefix for the segment (i.e.: N, NE, NW, S, SE, SW).
1	STREETNAME	Street Name	String	50	Add	X The recorded name of the street segment.
1	FTYPE	Street Name Type	String	4	Add	X Street segment feature type (i.e.: Ave, Blvd, St, etc.).
1	DIRECTION	Travel Direction	Integer	2	Add	X Direction of traffic travel on the street segment (if not bi-directional).
1	LEFTADD1	Left Side From Address	Integer	4	Add	X Beginning value of the address range on the left side of the street segment.
1	LEFTADD2	Left Side To Address	Integer	4	Add	X Ending value of the address range on the left side of the street segment.
1	RGTADD1	Right Side From Address	Integer	4	Add	X Beginning value of the address range on the right side of the street segment.
1	RGTADD2	Right Side To Address	Integer	4	Add	X Ending value of the address range on the right side of the street segment.
1	LEFTZIP	Left Side Zip Code	String	5	Add	X The Zip Code value to the left side of the street segment.
1	RIGHTZIP	Right Side Zip Code	String	5	Add	X The Zip Code value to the right side of the street segment.
1	TYPE	Transport Type	Integer	4	Add 1600 Alley X 1780 Private Planned X 1900 Unimproved Rights-of-Way X 1970 Virtual Streets with Addresses (streets added to account for anomaly addresses; NOT REAL) X 1980 Unimproved Rights-of-Way with Addresses X 1990 Vacated Rights-of-Way with no Address Range X 1995 Vacated Rights-of-Way with Address Range X 2000 Unimproved Rights-of-Way used for Local Access (improved to some substandard level) X 4000 Miscellaneous X	X Street Classification.
1	LCOUNTY	Left Side County Name	String	5	Add	X The County Name to the left side of the street segment.
1	RCOUNTY	Right Side County Name	String	5	Add	X The County Name to the right side of the street segment.
1	LCITY	Left Side City Name	String	25	Add	X The City Name to the left side of the street segment.
1	RCITY	Right Side City Name	String	25	Add	X The City Name to the right side of the street segment.
1	SUFFIX	Street Name Suffix	String	2	Add	X Suffix value to be included in the name of a street segment. Usually used on highway and interstate segments to indicate the direction of traffic flow.
1	FULL_NAME	Full Street Name	String	65	Add	X A combination of the "Prefix", "StreetName", "FType" and "Suffix" values to produce a full name for the street segment.
1	SIDE	Side Label	Integer	2	Add	X Address Side. Indicates whether addresses are found on both sides of the street segment, one side of the street segment or neither side of the street segment.
1	SOURCE	Segment Data Source	String	1	Add	X The original source document for the street segment.
1	CFCC	Census Feature Class Code (CFCC)	String	3	Add	X The Census Feature Class Code value for the street segment.
1	SUBAREA	Data Maintenance Sub Area	String	1	Add	X The jurisdiction responsible for maintenance of the street segment.
1	STRUC_TYPE	Structure Type	Integer	4	Add	X The basic type of structure related to the street segment.
1	LEFT_JUR	Left Side Jurisdiction Name	String	30	Add	X The jurisdication to the left of the street segment.
1	RIGHT_JUR	Right Side Jurisdiction Name	String	30	Add	X The jurisdiction name to the right of the street segment. Street segment side is determined by moving along the segment in the direction of address value increase.
1	PRI_NM_ID	Primary Street Name ID	Integer	4	Add	X The primary street name id to tie the name of the street segment to the address database.
1	LFT_NM_ID	Left Side Street Name ID	Integer	4	Add	X The street name id to the left side of the street segment. to tie the name of the street segment to the address database. Street segment side is determined by moving along the segment in the direction of address value increase.
1	RGT_NM_ID	Right Side Street Name ID	Numeric	8	Add	X The street name id to the right side of the street segment. to tie the name of the street segment to the address database. Street segment side is determined by moving along the segment in the direction of address value increase.
1	BTM_SEG_ID	BTM Segment ID	Numeric	8	Add	X The identification number used for the street segment in the Bureau of Transportation Management.
1	PDX_F_NODE	Portland From Node ID	Integer	4	Add	X The Portland ID for the node at the beginning of the street segment. Street segment side begining and end corresponds to the lowest and highest value of the address along the segment respectively.
1	PDX_T_NODE	Portland To Node ID	Integer	4	Add	X The Portland ID for the node at the end of the street segment. Street segment side begining and end corresponds to the lowest and highest value of the address along the segment respectively.
1	F_ZLEV	From Z Level	Integer	2	Add	X
1	T_ZLEV	To Z Level	Integer	2	Add	X