Metadata: Streets

Streets

Category Transportation - Streets
Feature Dataset Name STAND-ALONE
Item Name STREETS_PDX
Database Type SDE
Originator City of Portland
Bureau Bureau of Technology Services - Corporate GIS
Publication Date 01/01/1990
Abstract Street centerline network for the City of Portland, Multnomah County, Clark County and Washington County. This dataset does not yet include the data fields and structure necessary for performing routing operations.
Purpose Provides a base for addressing, street maintenance planning and tracking for street segments in the City of Portland. Displays the transportation infrastructure for the region including the City of Portland.
Supplemental Information
Last Dataset Update 09/15/2021 17:10
Last Source Update 09/15/2021 04:59
Maintenance/Update Frequency Weekly
Extent Clackamas County, Multnomah County, and Washington County, Oregon
Data Type Vector
Shape Type Poly Line
Feature Count 109345
Horizontal Position Accuracy
Horizontal Position Accuracy Link Taxlots
Progress Complete
North Bounding Coordinate 790525.591535434
South Bounding Coordinate 430310.380905509
East Bounding Coordinate 7905234.73392388
West Bounding Coordinate 7435953.38943569
Theme Keyword(s) Streets, Centerline
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
Paul Cone
503-823-4071
Paul.Cone@portlandoregon.gov
1120 SW Fifth Avenue, Suite #1111
Portland, OR 97204

City of Portland - BTS/CGIS
503 823-5198
503 823-9176
CGIS@portlandoregon.gov
File(s)
Add
Images
52057.png 71.75Kb 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.

Web Services

Service Description Feature Access Layer
BES_Layers Referecne layers as used by various BES web content Dynamic Streets
BES_PH Layers for Portland Harbor web map Dynamic Street Names
Parks_Protect_The_Best_Basemap Parks PTB Basemap Cached All Streets
Parks_Protect_The_Best_Basemap Parks PTB Basemap Cached Arterials
Basemap_Color Color basemap for the City of Portland, Oregon Cached Streets
Basemap_Color_Complete Color basemap for the City of Portland, Oregon Cached Streets
Basemap_Color_Complete_Aerial Color basemap for the City of Portland, Oregon Cached Streets
Basemap_Gray_Complete Gray basemap for the City of Portland, Oregon Cached Streets
BDS_Layers Map layers used to facilatate the permitting process Dynamic Centerline
Parks_PTB_Basemap Parks PTB Basemap Cached All Streets
Parks_PTB_Basemap Parks PTB Basemap Cached Arterials
Street_Tree_Inventory_Basemap_Overlays Cached Streets
Urban_Forestry_Park_Tree_Inventory_Basemap_Overlays PP&R Urban Forestry Park Tree Inventory Basemap Overlays Cached Streets
Add

Attribute Tables & Domains

X
streets_pdx
Table Description Regional Street Network Line Attributes.
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
0 No Leading Zero X
1 Contains Leading Zero. X
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
E East X
N North X
NE NorthEast X
NW NorthWest X
SE Southeast X
SW Southwest X
S South X
W West X
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
1 Two-way street X
2 One-way street, range increases with centerline direction X
3 One-way street, range increases against centerline direction X
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 LEFT_JUR Left Side Jurisdiction Name String 30
Add
X
The jurisdication to the left of the street segment.
1 TYPE Transport Type Integer 4
Add
1110 Freeway X
1120 Ramps, Interchanges (one Freeway to another) X
1121 On-Ramp or Slip Road Linkage (used to enter a Freeway or lower class road) X
1122 Off-Ramp or Slip Road Linkage (used to exit a Freeway or lower class road) X
1123 On/Off-Ramp or Slip Road Linkage (used to enter or exit a Freeway or lower class road) X
1200 Highway X
1221 On-Ramp or Slip Road Linkage (used to enter a Highway or lower class road) X
1222 Off-Ramp or Slip Road Linkage (used to exit a Highway or lower class road) X
1223 On/Off-Ramp or Slip Road Linkage (used to enter or exit a Highway or lower class road) X
1300 Primary Arterial X
1321 Primary Arterial Linkage (ramp/slip road used to enter or exit a Primary Arterial or loser class road) X
1400 Secondary Arterial X
1421 Arterial Linkage (ramp/slip road used to enter or exit an Arterial or lower class road) X
1450 Tertiary Street - Neighborhood Collector X
1471 Tertiary Street Linkage (ramp/slip road used to enter a Tertiary Street or lower class road) X
1500 Minor Residential X
1521 Ramp/Slip Road used to enter or exit a Residential Street X
1700 Private Named Road X
1800 Unnamed Private Road/Driveway X
1950 Public planned street with addresses (will be active soon) X
5101 Freeway with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
5201 Highway with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
5301 Primary Arterial with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
5401 Arterial with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
5402 Secondary arterial with rapid transit, but no regular vehicle traffic.
X
5450 Tertiary Street with Railroad. Auto traffic and rail trackage in shared ROW. X
5451 Tertiary Street with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
5500 Minor Residential with Railroad. Auto traffic and rail trackage in shared ROW. X
5501 Minor Residential with Rapid Transit (MAX or streetcar). Auto traffic and rail trackage in shared ROW. X
7700 Short segments indicating mile post locations along certain highways to assist emergency dispatch in Clackamas and Washington Counties. These are short pseudo-segments that do not exist (Clackamas and Washington Counties only). X
8224 Unknown Type (only in Yamhill County, SUBAREA='Y') X
9000 Forest Service Road X
X
Street Classification. To be replaced by CFCC
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
0 Addresses on both sides of the street segment. X
1 Addresses on the right side of the street segment. Street segment side is determined by moving along the segment in the direction of address value increase. X
2 Addresses on the left side of the street segment. Street segment side is determined by moving along the segment in the direction of address value increase. X
3 Addresses do not exist on either side of the street segment. X
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
A31 Secondary, unseparated X
A33 NEW Secondary w/ MAX, unseparated X
A34 Secondary w/ RR, unseparated X
A35 Secondary, separated X
A37 NEW Secondary, w/ MAX, separated X
A38 Secondary w/ RR, separated X
A41 Local, unseparated X
A43 NEW Local w/ MAX, unseparated X
A44 Local w/ RR, unseparated X
A45 Local, separated X
A47 NEW Local, w/ MAX, separated X
A48 Local w/ RR, separated X
A51 Vehicular trail, unseparated X
A61 Cul-de-sac X
A62 Traffic circle X
A63 Access ramp X
A64 Service drive, frontage road X
A71 Walkway or pedestrian trail X
A72 Stairway or pedestrian stepped road X
A73 Alleys X
A74 Driveways, private service roads X
A75 NEW - Bicycle trails X
B01 Railroad track - general X
B51 Light rail X
C10 Pipeline X
C20 Power transmission line X
F10 Nonvisible jurisdiction boundary X
F30 Point-to-point line between features X
F40 Property line X
F50 Zip Code boundary X
F72 1990 Statistical boundary X
H10 Stream X
H20 Canal, ditch X
H30 Lake or pond X
H40 Water reservoir X
X
The Census Feature Class Code value for the street segment. This field is no longer actively maintained.
1 SUBAREA Data Maintenance Sub Area String 1
Add
C Clackamas County X
M Multnomah County X
P Portland X
W Washington County X
X
The jurisdiction responsible for maintenance of the street segment.
1 STRUC_TYPE Structure Type Integer 4
Add
0 No information X
10 At grade, no structure X
21 Overpass; a structure over grade level X
23 Bridge; Structure over water X
32 Tunnel; Structure under land X
X
The basic type of structure related to the street segment.
1 LEFT_JUR LEFT_JUR 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 UPD_DATE Segment Data Last Update Date Date 36
Add
X
1 CREATE_DAT Segment Data Creation Date Date 36
Add
X
1 F_ZLEV From Z Level Integer 2
Add
X
1 T_ZLEV To Z Level Integer 2
Add
X