Description: This dataset includes all public roads in Umatilla County with this version of the dataset being meant for internal use only. It was originally sourced from the All Public Roads state layer in November 2025 which can be found here. This dataset supersedes the previous roads layer used by the county. Several steps were taken to ensure network connectivity and to find and prevent errors. The data is segmented primarily on the intersections of roads, but some roads are segmented based on surface type or other fields.The main focus of this release is county owned roads. Only roads with a county road number are considered county owned roads. Future updates to this dataset will focus on other roads as well. County owned roads were compiled from many sources including previous county road books and the county road record. Legally recognized rights of way with no corresponding road are not available publicly and should be used with caution due to possible legal issues. This dataset should not be used for legal purposes.FIELDSFULL NAMEThis is the main name of the road whether that be the legally recognized name or the name used in addressing. Several roads are unnamed including a few county owned roads. County owned roads that do not have any legally recognized name have been given a placeholder name with the county road number such as COUNTY 1354 RD. Data originated from combining the the PREFIX, NAME, TYPE, and SUFFIX fieldsCOUNTY RD #The county road number that legally defines a road. Most county roads have legal names. However, multiple road names can share a number and multiple numbers can have the same road name. County owned roads initially were numbered sequentially but in the 1980s were renumbered so that they roughly describe the road extent geographically. Odd numbers indicate north-south roads. Even numbers indicate east-west roads. A road number ending with a 5 indicates a north-south arterial road. A road number ending with a 0 indicates an east-west arterial road. Data originated from both this ordinance and in the index section of the 2020 county road book.PREFIXThe directional prefix of the road name. The domain values are N, W, S, E, NW, NE, SW, SE. Field originated from the state All Public Roads dataset.NAMEThe main name of the road. Names generally do not include non number/letter characters. The name can include multiple words. Field originated from the state All Public Roads dataset.TYPEThe road name type of the road. Most types follow the USPS C1 Street Suffix Abbreviations standard. The domain descriptions are ACCESS, ALLEY, AVENUE, BOULEVARD, BRIDGE, BYPASS, CANYON, CIRCLE, CONNECTOR, COURT, COVE, CREEK, CREST, CROSSING, CUTOFF, DRIVE, DRIVEWAY, EXTENSION, FREEWAY, GRADE, HEIGHTS, HIGHWAY, HOLLOW, JUNCTION, LANDING, LANE, LOOP, PARKWAY, PASS, PIKE, PLACE, POINT, RAMP, RIDGE, ROAD, ROW, RUN, SPUR, SQUARE, STREET, SWITCHBACK, TERRACE, TRACE, TRAIL, TURNOUT, VIA, VIEW, WAY, and FRONTAGE. Field originated from the state All Public Roads dataset.SUFFIXThe directional suffix of the road name. The domain values are N, W, S, E, NW, NE, SW, SE. Field originated from the state All Public Roads dataset.ROAD CLASSIFICATIONThe 2025 TIGER/Line road classification. This has no correlation to the actual TIGER dataset besides for the schema. The domain descriptions are PRIMARY ROAD, SECONDARY ROAD, LOCAL NEIGHBORHOOD ROAD, VEHICULAR TRAIL, RAMP, FRONTAGE, ALLEY, SERVICE ROAD, and PARKING LOT ROAD. Roads were classified based on other known information with an example being that all highways were classified as primary roads.ROAD OWNERThe owner of the road. In most cases the road owner and manager are the same. In cases where a management agreement exists it is noted in the OWNERSHIP NOTES field. All county owned roads have a county road number. Field originated from the state All Public Roads dataset.OWNERSHIP NOTESNotes in regards to the ownership and maintenance of a road including the transfer year or date if available and reference to any agreements involved. HISTORICAL DEDICATIONSYears where sections of a particular county owned road were dedicated during. The current classification system for county-owned roads is an amalgamation of roads previously dedicated to the county before the renumbering that took place in the 1980s. This has no correlation with when sections of the road were actually built, it only is when legal rights-of-way were established. Data originated from a stack of papers listing county roads and their dedication years.OLD COUNTY RD #Previous county road numbers under the previous sequential county road numbering system. The current classification system for county-owned roads is an amalgamation of roads previously dedicated to the county before the renumbering that took place in the 1980s. Because of this the old county road numbers are in a list that is shared with every segment that has the same county road number as documentation of where old county roads are is poor. In some cases roads only have one old county road number which usually indicates that the county road has the same extent as the previous one. This is not an exhaustive list of old county road numbers although the old county road numbers range from roughly one to one thousand. Data originated from the index section of the 2020 county road book.RIGHT OF WAY WIDTH (FT)The width of the right of way (ROW) that was established when that section of road was dedicated. The current classification system for county-owned roads is an amalgamation of roads previously dedicated to the county before the renumbering that took place in the 1980s. The ROW width is not the actual width the road was built at, just the legal width the road takes up. Over time Oregon law has changed the road width requirements for newly dedicated roads. Most historical ROW widths are not specified in the actual dedication although are implied based on what the law was at the time. Until the 1930s 60 FT was the minimum width if no width was stated. Nowadays widths are required to be stated with the required minimum width set at 50 FT. The domain values for this field are 25, 30, 33, 33 & 40, 35, 40, 40 & 50, 45, 50, 50 & 60, 60, 60 & 40, 60 & 66, 66, 70, 80, 80 & 100, and 100. Data was sourced from the ROW width pdf’s in the county road record. Their accuracy is questionable and in most cases roads need legalization in order to determine the true ROW width when there are multiple listed for a segment.ATV ALLOWEDCounty owned roads that ATV’s are allowed on under this ordinance. The county roads chosen for this ordinance were done so as a collaboration between multiple departments including the board of commissioners and the GIS department. The domain values for this field are YES and NO.OVER DIMENSION PERMITWhether or not a county owned road has permits available for over-dimension vehicles. The domain values for this field are YES and NO. Data comes from a spreadsheet that listed county owned roads that have permits available for over-dimension vehicles.NO PILOT CAR REQUIRED (FT)The size of a vehicle that requires an over-dimension permit and no pilot car. The domain values for this field are < 9W x 95L, < 95L, < 8W x 95L, < 11W x 95L, and < 10W x 95L. Data comes from a spreadsheet that listed county owned roads that have permits available for over-dimension vehicles.FRONT PILOT CAR REQUIRED (FT)The size of a vehicle that requires an over-dimension permit and only a front pilot car. The domain values for this field are 10-12W x 95-120L, 11-12W x 95-120L, 11-13W x 95-120L, 8-10W x 95-120L, 9-11W x 95-120L, and 95-120L. Data comes from a spreadsheet that listed county owned roads that have permits available for over-dimension vehicles.FRONT AND REAR PILOT CAR REQUIRED (FT)The size of a vehicle that requires an over-dimension permit and both front and rear pilot cars. The domain values for this field are > 10W x 120L, > 11W x 120L, > 12W x 120L, > 13W x 120L, > 8W x 120LData comes from a spreadsheet that listed county owned roads that have permits available for over-dimension vehicles.SURFACE TYPEThe surface type of the road was collected from imagery. The domain values are PAVED, GRAVEL, DIRT, and RIGHT-OF-WAY. Paved roads include asphalt, concrete, and chipseal roads. Dirt roads typically have some evidence of frequent use such as tire tracks and a clear centerline between them. Right of ways are any roads that do not have a physical road built on them or any evidence of use at all typically. These roads are not being distributed publicly and their locations are legally questionable. This dataset doesn’t segment surface type when the surface type change is close to an intersection. ODOT #The number assigned to a highway by the Oregon Department of Transportation (ODOT). ODOT’s numbering scheme is different from the publicly known numbering system. Any road assigned an ODOT route number is owned by ODOT. The domain values for the ODOT number include 002, 006, 008, 028, 036, 052, 054, 067, 070, 320, 330, 331, 332, 333, 334, 335, 339, and 341. Field originated from the state All Public Roads dataset.HWY#The number that a highway is commonly referred to and is signed as. ODOT’s numbering scheme is different from the publicly known numbering system. In the early 2000s, ODOT began publicly using their ODOT route numbers for highways that previously lacked a publicly recognized number. In Umatilla County, these previously unsigned highways are numbered between 300-350. The domain values for the HWY number include 11, 204, 207, 244, 30, 320, 331, 332, 334, 335, 339, 37, 395, 730, 74, 82, and 84.START MPThe starting mile post for a highway segment. Field originated from the state All Public Roads dataset.END MPThe ending mile post for a highway segment. Field originated from the state All Public Roads dataset.ALIASThe secondary name given to a road. This does not include only a difference in the PREFIX, SUFFIX, or TYPE compared to the FULL NAME. Those differences can be found in ALIAS NOTES. County roads and highways both can be aliased by their numbers as well. Field originated from the state All Public Roads dataset.ALIAS PREFIXThe directional prefix of the secondary road name. The domain values are N, W, S, E, NW, NE, SW, SE. Field originated from the state All Public Roads dataset.ALIAS NAMEThe secondary name of the road. Names generally do not include non number/letter characters. The name can include multiple words. Field originated from the state All Public Roads dataset.ALIAS TYPEThe secondary road names type of the road. Most types follow the USPS C1 Street Suffix Abbreviations standard. The domain descriptions are ACCESS, ALLEY, AVENUE, BOULEVARD, BRIDGE, BYPASS, CANYON, CIRCLE, CONNECTOR, COURT, COVE, CREEK, CREST, CROSSING, CUTOFF, DRIVE, DRIVEWAY, EXTENSION, FREEWAY, GRADE, HEIGHTS, HIGHWAY, HOLLOW, JUNCTION, LANDING, LANE, LOOP, PARKWAY, PASS, PIKE, PLACE, POINT, RAMP, RIDGE, ROAD, ROW, RUN, SPUR, SQUARE, STREET, SWITCHBACK, TERRACE, TRACE, TRAIL, TURNOUT, VIA, VIEW, WAY, and FRONTAGE. Field originated from the state All Public Roads dataset.ALIAS SUFFIXThe directional suffix of the secondary road name. The domain values are N, W, S, E, NW, NE, SW, SE. Field originated from the state All Public Roads dataset.ALIAS NOTESAny other aliases besides the secondary name for the road as well as any other notes in regards to the names given to a road.UPDATE DATEThe date when a particular segment's attributes or shape were last updated. Field originated from the state All Public Roads dataset.CREATION DATEContains the date when a record in the attribute table was created. Many original creation dates were lost due to an attribute rule that automatically populates this field when some operations were performed on the entire dataset. Field originated from the state All Public Roads dataset.SPEED LIMITThe speed limit of a road as publicly displayed on a road sign. NOTESAny notes that don’t fit into any other fields.UNUSED FIELDSThese are fields that originated from the state All Public Roads dataset but are unused by Umatilla County and are hidden from the public. They include GIS PRODUCTION DATE, EFFECTIVE DATE, ORIGINATOR ID, ORIGINATOR, LEFT LOW ADDRESS RANGE, LEFT HIGH ADDRESS RANGE, RIGHT LOW ADDRESS RANGE, RIGHT HIGH ADDRESS RANGE, LRS KEY, LRS LOCAL, BASE ID, SEG MARK ID, MANAGER ID, OWNER ID, and ROAD MANAGER
NO_PILOT_CAR (type: esriFieldTypeString, alias: NO PILOT CAR REQUIRED (FT), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [< 9W x 95L: < 9W x 95L], [< 95L: < 95L], [< 8W x 95L: < 8W x 95L], ... 2 more ...)
FRONT_PILOT_CAR (type: esriFieldTypeString, alias: FRONT PILOT CAR REQUIRED (FT), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [10-12W x 95-120L: 10-12W x 95-120L], [11-12W x 95-120L: 11-12W x 95-120L], [11-13W x 95-120L: 11-13W x 95-120L], ... 3 more ...)
FRONT_AND_REAR_PILOT_CARS (type: esriFieldTypeString, alias: FRONT AND REAR PILOT CARS REQUIRED (FT), SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [> 10W x 120L: > 10W x 120L], [> 11W x 120L: > 11W x 120L], [> 12W x 120L: > 12W x 120L], ... 2 more ...)