Metadata: Gecoding Streets

Gecoding Streets

Category Transportation - Streets
Feature Dataset Name STAND-ALONE
Item Name STREETS_GEOCODING_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, Clackamas County and Washington County developed for geocoding purposes. This dataset does not yet include the data fields and structure necessary for performing routing operations.
Purpose Provides a dataset including all address segments to be used for geocoding (locating) addresses in the Portland Region.
Supplemental Information
Last Dataset Update 06/09/2021 17:21
Last Source Update 06/09/2021 04:46
Maintenance/Update Frequency Weekly
Extent Clackamas County, Multnomah County, and Washington County, Oregon
Data Type Vector
Shape Type Poly Line
Feature Count 114204
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, Geocoding
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
Bureau of Technology Services - Corporate GIS
503 823-5632
503 823-5194
Maps@portlandoregon.gov
1120 SW Fifth Avenue, Suite 450
Portland, OR 97204

City of Portland - BTS/CGIS
503-823-4000
503-823-5194
Maps@portlandoregon.gov
File(s)
Add
Images
52062.png 71.65Kb 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.
Add

Attribute Tables & Domains

X
streets_geocoding_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, in feet.
1 LOCALID Segment ID Integer 4
Add
X
The 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 (e.g.: 0321 SW Main St.).
1 PREFIX Street Name Prefix String 2
Add
X
The Street Name Prefix (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 name suffix (e.g. 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 String 5
Add
X
Beginning value of the address range on the left side of the street segment.
1 LEFTADD2 Left Side To Address String 5
Add
X
Ending value of the address range on the left side of the street segment.
1 RGTADD1 Right Side From Address String 5
Add
X
Beginning value of the address range on the right side of the street segment.
1 RGTADD2 Right Side To Address String 5
Add
X
Ending value of the address range on the right side of the street segment.
1 LEFTZIP Left Side Zip Code String 6
Add
X
The Zip Code value to the left side of the street segment.
1 RIGHTZIP Right Side Zip Code String 6
Add
X
The Zip Code value to the right side of the street segment.
1 TYPE Transport Type Integer 4
Add
1110 Freeway (Default Freeway Code) X
1121 On-Ramp (Freeway/Highway to Freeway/Highway) X
1122 Off-Ramp (Freeway/Highway to Freeway/Highway) X
1123 On and Off Ramp (Freeway/Highway to Freeway/Highway) X
1200 Highway X
1300 Primary Arterial X
1400 Secondary Arterial X
1450 Major Residential X
1500 Minor Residential X
1600 Alley X
1700 Private Named Road
X
1800 Driveways and Private Unnamed Roads X
1900 Public ROW exists but no built roadway exists
X
1950 Unimproved Rights-of-Way in the Development Process (Usually Addressed, Will be Active Soon) X
1970 Virtual Streets with Addresses (Segments Added to Account for Anomaly Addresses; not real streets) X
1980 Unimproved Rights-of-Way with Addresses 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
2000 Unimproved, unmaintained uses for local access, e.g. gravel
X
2100 Railroad
X
3100 A Non-specific or Shared Use Path
X
3230 Steps (most have address ranges)
X
5401 Secondary with Rapid Transit X
5500 Minor with Railroad X
5501 Minor with Rapid Transit X
9000 Forest Service Road 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. No longer actively maintained.
1 SUBAREA Data Maintenance Sub Area String 1
Add
X
The jurisdiction responsible for maintenance of the street segment in the street centerline data.
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. No longer maintained.
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 Update Date Date 36
Add
X
1 CREATE_DAT Create Date Date 36
Add
X