signed_rtes signed_rtes This file includes all signed Interstate, State, and US routes for the State of Oregon. To show location of routes and provide cross-reference to ODOT highway numbers. This file includes all applicable jurisdictions of roadways to give a complete picture of routes located within Oregon. Please note that not all signed routes are State of Oregon highways. en 2008 publication date Complete As needed -124.807486 -116.419828 46.218776 41.920156 223125.2000002254965.20000088303.8000001652481.931829 Highways Bypass Expressway Freeway Highway Interstate Route Street Road signed_rtes signed_rtes_2008 Oregon North America OR Oregon Pacific Northwest United States US USA none 2008 2008
None None Road Inventory and Classification Services Unit, Oregon Department of Transportation. mailing address
555 13th St. NE, Suite # 2
Salem OR 97301-4178 USA 503 986-4134 odotrics@odot.state.or.us 7:00 am to 5:00 pm M thru F (PST) Call, email, or write Road Inventory and Classification Services Unit (RICS), Oregon Department of Transportation. None None None Windows XP Professional SP1, Geomedia Professional v6.0, ArcGIS v9.2
false Shapefile HWYNAME, HWYNUMB, RDWY_ID, MLGE_TYP, OVLP_CD, BEGMP, ENDMP, I_RTE, I-SIGN, US_RTE_1, US_SIGN_1, US_RTE_2, US_SIGN_2, OR_RTE_1, OR_SIGN_1, OR_RTE_2, OR_SIGN_2, ALL_RTE were obtained from ODOT's current Integrated Transportation Information System (ITIS) database. RD_NAME, JRSDCT, FC_RD_ID are from the HGIS_15 database. LRS_KEY and GIS_PRC_DT was determined by the Geographic Information Service Unit. Routes were generated by dynamic segmentation from data received from Integrated Transportation Information System (ITIS) and the HGIS_15 database. Attributes were checked to verify that all route records were placed. This file is complete and is dependent upon receipt of completed information from Integrated Transportation Information System (ITIS) and HGIS_15 databases at the time of posting. No horizontal positional accuracy has been determined No vertical positional accuracy has been determined Route data was received from ODOT Integrated Transportation Information System (ITIS) database in tabular format. Tabular data was modified to eliminate multiple routes in a single record. " Comment" field was added to store the multiple route names and records duplicated to parse out the individual route ids. Tabular data was then dynamically segmented to the highway layer using Geomedia 6.0 software. The new dynamically segmented lines were then exported to shapefile format. Route data for the non state segments were extracted from the HGIS_15 database. The following modifications were made to the resultant shapefile using ArcGIS v9.2: the MP field was recalculated to 2 decimal points; the Geomedia generated "status" field was dropped; fields were rearranged according to ODOT Spatial Data Standards. 04/15/2008 Geographic Information Services Unit, Oregon Department of Transportation (ODOT) B. McConnell mailing and physical address
555 13th St. NE, Suite #2
Salem OR 97301-4178 USA 503.986.3154 503.986.4249 odot.maps@odot.state.or.us Monday through Friday, 8:00 AM to 5:00 PM. Call, email, or write. Dataset copied.20090310 0 Oregon Vector String1417 SimplePolylineFALSE1417TRUEFALSE Coordinate Pair 0.0000000.000000 international feet Lambert Conformal Conic43.00000045.500000-120.50000041.7500001312335.9580050.000000 North American Datum of 1983 Geodetic Reference System 80 6378137.000000 298.257000 GCS_North_American_1983OGIC signed_rte Signed Interstate, State, and US routes for the State of Oregon. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Feature Class1417 US_SIGN_2 Numerical value for United States Route sign Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value ALL_RTE All route types assigned to a particular segment. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation BEGMP The milepoint measurement of the beginning of a roadway feature which is closest to the beginning of the segment. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Real number to 2 decimal places -999.99 999.99 mile 0.010000 ITIS measurements are based on features located to +/- 0.02 mile. String46 EFFECTV_DT This date or time period in which the data extract is relevant or current. Roadway Inventory and Classification Services (RICS) Unit String30 ENDMP The milepoint measurement of the end of a roadway feature which is closest to the end of the segment. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Real number to 2 decimal places -999.99 999.99 mile 0.010000 ITIS measurements are based on features located to +/- 0.02 mile. String5 FC_RD_ID The assigned Functional Class road indentification number. Roadway Inventory and Classification Services (RICS) Unit Real Number Number9 GIS_PRC_DT The date that the data was processed. Geographic Information Services Unit, Oregon Department of Transportation. String5 HWYNAME The official state highway name. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation The official name of the state highway that is stored in the Integrated Transportation Information System (ITIS). String5 HWYNUMB A unique three-digit identifier assigned to an Oregon State Highway Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value 001 456 Number82 I_RTE Interstate route Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Number82 I_SIGN Numerical value for Interstate sign. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value String10 JRSDCT Jurisdiction of the applicable segment. Roadway Inventory and Classification Services (RICS) Unit As needed String10 LRS_KEY Linear Referencing System highway identifier. This is a representation of elements contained in the Integrated Transportation Information System (ITIS) database used to identify a highway, connection or frontage road. The first nine characters are the inventory route numbers and the last three characters are the sub-route numbers. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation The twelve digit alphanumeric string is broken down into its components as: 1 - Place holder 0 (zero); 2-4 - Hwy Number 001 - 499; 5-6 - Hwy Suffix 00 (zero zero), AA-ZZ (alphabetic characters); 7 - Roadway Identifier (1-5); 8 - Mileage Type (Z, T, Y); 9 - Overlap Mileage Code (0-9); 10 - Jurisdiction Code (S); 11-12 - Two Place holders 00 (zero zero) String10 MLGE_TYP Identifies the type of highway mileage. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation T Temporary mileage: Temporary Traveled Routes (TTR) are roads that are meant to temporarily function as state highways until a replacement state highway alignment is built or dedicated. These roads do not belong to ODOT, but ODOT has legally agreed to maintain them. TTR's can occur because of a detour or highway construction. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Y Spur: An offshoot of the normal alignment of a highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Z Overlapping Mileage: Overlapping mileage occurs when a section of highway is lengthened due to new construction. Example: A section of highway from milepoint 49.00 to milepoint 50.00 is washed out. The washed out section must be replaced, but, the old alignment cannot be used. A new alignment is built around the problem area, but the new alignment is 4.62 miles longer than the original alignment. The new distance between milepoint 49.00 and milepoint 50 is now 5.62 miles. In order to reflect the true distance along the highway without remileposting the entire road, overlapping mileage is created. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String10 OR_RTE_1 First occurrence of an Oregon Route. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String10 OR_RTE_2 Second occurrence of an Oregon Route. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String10 OR_SIGN_1 Numerical value for Oregon Route sign Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value String10 OR_SIGN_2 Numerical value for Oregon Route sign Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value String10 OVLP_CD A code that is used to identify each unique instance of duplicate milepoints. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 1 9 1 First occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 2 Second occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 3 Third occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 4 Fourth occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 5 Fifth occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 6 Sixth occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 7 Seventh occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 8 Eighth occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 9 Ninth occurrence of duplicate mileage on a specific highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String10 RDWY_ID The number assigned to a roadway where more than one roadbed exists for the highway. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 1 The primary roadway. Direction of travel is in the direction of increasing milepoints. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 2 The secondary roadway. Direction of travel is in the direction of decreasing milepoints. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 3 A split roadway with the direction of travel in the direction of increasing milepoints. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 4 A split roadway with the direction of travel in the direction of decreasing milepoints. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation 5 Located line. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String10 Shape Polyline Geographic Information Services Unit, Oregon Department of Transportation. String20 US_RTE_1 First occurrence of a United States Route. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation String16 US_RTE_2 Second occurrence of a United States Route. Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Number10 US_SIGN_1 Numerical value for United States Route sign Integrated Transportation Information System (ITIS) database, Oregon Department of Transportation Integer value String12 FIDFIDString15Internal feature number.ESRISequential unique whole numbers that are automatically generated.RD_NAMERD_NAMEString10 signed_rte contains BEGMP, ENDMP, HWYNAME, HWYNUMB, I_RTE, I_SIGN, LRS_KEY, MLGE_TYP, OVLP_CD, RDWY_ID, Shape, US_RTE_1, US_RTE_2, US_SIGN_1, US_SIGN_2, OR_RTE_1, OR_SIGN_1, OR_RTE_2, OR_SIGN_2, ALL_RTE, GIS_PRC_DT and EFFECTV_DT Transportation Routes for Oregon Geographic Information Services Unit, Oregon Department of Transportation (ODOT). mailing and physical address
555 13th St. NE, Suite #2
Salem OR 97301-4178 USA 503.986.3154 503.986.4249 odot.maps@odot.state.or.us Monday through Friday, 8:00 AM to 5:00 PM. Call, email, or write. This product is for informational purposes and may not have been prepared for legal, engineering or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information. SHP 9.1 ESRI shapefile format false 3.225 CD-ROM, DVD email at odot.maps@odot.state.or.us; call 503.986.3154 SHP 3.1 ESRI shapefile format false 3.225 CD-ROM, DVD email at odot.maps@odot.state.or.us; call 503.986.3154 SHP 9.2 ESRI shapefile format false 3.225 CD-ROM, DVD email at odot.maps@odot.state.or.us; call 503.986.3154 Call or email. Usually within one week. 3.225 false 3.225 ESRI Arcview 3.0 or better, Window NT unknown Downloadable Data 20080416 Geographic Information Services Unit, Oregon Department of Transportation (ODOT). mailing and physical address
555 13th St. NE, Suite #2
Salem OR 97301-4178 USA 503.986.3154 503.986.4249 odot.maps@odot.state.or.us Monday through Friday, 8:00 AM to 5:00 PM. Call, email, or write. FGDC Content Standards for Digital Geospatial Metadata local time none none Unclassified enFGDC-STD-001-1998http://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile 20080418080058002008041808005800{7EFF6B46-0F42-47F4-BDE8-9F015491D59D}2009031016044700TRUEProject signed_rtes "H:\ES 341\PROJECT\Roads\signed_rtes_Project1.shp" PROJCS['NAD_1927_UTM_Zone_10N',GEOGCS['GCS_North_American_1927',DATUM['D_North_American_1927',SPHEROID['Clarke_1866',6378206.4,294.9786982]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['False_Easting',500000.0],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-123.0],PARAMETER['Scale_Factor',0.9996],PARAMETER['Latitude_Of_Origin',0.0],UNIT['Meter',1.0]] NAD_1927_To_NAD_1983_NADCON PROJCS['OGIC',GEOGCS['GCS_North_American_1983',DATUM['D_North_American_1983',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]],PROJECTION['Lambert_Conformal_Conic'],PARAMETER['False_Easting',1312335.958005249],PARAMETER['False_Northing',0.0],PARAMETER['Central_Meridian',-120.5],PARAMETER['Standard_Parallel_1',43.0],PARAMETER['Standard_Parallel_2',45.5],PARAMETER['Scale_Factor',1.0],PARAMETER['Latitude_Of_Origin',41.75],UNIT['Foot',0.3048]]20080418Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 2; ESRI ArcCatalog 9.2.2.1350signed_rtes223125.22254965.21652481.93182988303.81-124.802154-116.77595746.28289141.9193671ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://Local Area Network3.225ShapefileOGIC1417