. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR Oregon and Washington Highways Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR Oregon and Washington Highways Line

Abstract:
highways_arc: This file includes all state owned or maintained highways, connections, frontage roads, temporary traveled routes and located lines in the states of Oregon and Washington.

Supplemental information:
Dataset locally known as highways_arc This data is intended for use at scales of 1:24,000 or smaller.

  1. How should this data set be cited?

    Bureau of Land Management Oregon State Office, 20120917, BLM OR Oregon and Washington Highways Line.

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.590343
    East: -116.833891
    North: 49.002328
    South: 41.865135

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar date: 20120917
    Currentness reference:
    publication date

  5. What is the general form of this data set?

    Geospatial data presentation form: vector digital data

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

      Indirect spatial reference:
      Oregon

      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (26333)

    2. What coordinate system is used to represent geographic features?

      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 2e-008. Longitudes are given to the nearest 2e-008. Latitude and longitude values are specified in Decimal Degrees.

      The horizontal datum used is D North American 1983.
      The ellipsoid used is GRS 1980.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257222101.

  7. How does the data set describe geographic features?

    highways_arc
    A segment of highway between two intersecting locations of other highway segments (Source: Geographic Information Services Unit, Oregon Department of Transportation.)

    SHAPE
    Feature geometry. (Source: ESRI)
                      

    Coordinates defining the features.

    us_sign_2
    US Highway route number (overlapping route). (Source: Bureau of Land Management - Oregon State Office)
                      

    hwyname
    Highway route name. (Source: Bureau of Land Management - Oregon State Office)
                      

    objectid
    Internal feature number. (Source: ESRI)
                      

    Sequential unique whole numbers that are automatically generated.

    hwy_class
    Highway classification based on highway sign attribute. (Source: Bureau of Land Management - Oregon State Office)
                      

    ValueDefinition
    INT
    Interstate Highway
    USH
    US Highway
    STH
    State Highway
    CNTY
    County Highway
    MUN
    Municipal Road

    lrs
    Linear Reference System highway identifier (Oregon only). This is a representation of elements contained in the State of Oregon's 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. (Source: Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01))
                      

    The twelve digit alphanumeric string is broken down into its components as: 1: Place holder 0 (zero) 2-4: Hwy Number 001 to 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)

    rdwy_id
    The number assigned to a roadway where more than one roadbed exists for the highway. (Source: Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01))
                      

    ValueDefinition
    1
    The primary roadway. Direction of travel is in the direction of increasing mile points.  (Oregon only)
    2
    The secondary roadway. Direction of travel is in the direction of decreasing mile points.  (Oregon only)
    3
    A split roadway with the direction of travel in the direction of increasing mile points.  (Oregon only)
    4
    A split roadway with the direction of travel in the direction of decreasing mile points.  (Oregon only)
    5
    Located line.  (Oregon only)
    6
    Used to differentiate split highways for display at small scales in Washington state only.
    7
    Used to differentiate split highways for non display at small scales in Washington state only.

    rdwy_typ
    A unique identifier assigned to the roadway designating a spur, frontage road, connection or regular roadway. (Source: Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01))
                      

    ValueDefinition
    reg
    Regular highway
    frt
    Frontage road
    con
    Connection
    spr
    Spur

    hwy_seg_id
    A unique identifier assigned to the roadway designating a spur, frontage road, connection or regular roadway.  (Oregon only) (Source: Oregon Transportation Management System (OTMS) GIS Base Layer Development Project (GIS01))
                      

    i_sign
    Interstate route number. (Source: Bureau of Land Management - Oregon State Office)
                      

    us_sign_1
    US Highway route number. (Source: Bureau of Land Management - Oregon State Office)
                      

    hwylocname
    Alternate name (e.g. local street name). (Source: Bureau of Land Management - Oregon State Office)
                      

    st_sign_1
    State Highway route number. (Source: Bureau of Land Management - Oregon State Office)
                      

    st_sign_2
    State Highway route number (overlapping route). (Source: Bureau of Land Management - Oregon State Office)
                      

    DSG_NAME
    SPEC_DSGTN
    SHAPE_Length
    Length of feature in internal units. (Source: ESRI)
                      

    Positive real numbers that are automatically generated.

Back to Top

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

    • Bureau of Land Management Oregon State Office

  2. Who also contributed to the data set?

    Geographic Information Services Unit, Oregon Department of Transportation and the Cartography/GIS Section of the Washington State Department of Transportation.

  3. To whom should users address questions about the data?

    Chris Knauf
    Bureau of Land Management
    Outdoor Recreation Planner
    P.O. Box 2965
    Portland, OR 97201
    US

    (503) 808-6427 (voice)
    cknauf@blm.gov
Back to Top

Why was the data set created?

This data provides a detailed view of the state highway system based on the Linear Referencing system (LRS) used by both the Oregon Department of Transportation and the Washington State Department of Transportation. 1:24k resolution.

Back to Top

How was the data set created?

  1. Where did the data come from?

    SR24kLRSLinesSPS.shp (source 1 of 4)

    Cartography/GIS Section, Washington State Department of Transportation (WSDOT), 20060724, SR24kLRSLinesSPS.shp.

    Type of source media: None

    Hwy_SEG (source 2 of 4)

    Geographic Information Services Unit, Oregon Department of Transportation (ODOT), Hwy_SEG.

    Type of source media: None

    USGS DOQ (source 3 of 4)

    United States Geologic Survey Denver, Colorado 80225 or Reston, Virginia 22092, 19950101, 1:24,000 7.5 minute United States Geologic Survey Quadrangles.

    Type of source media: None
    Source scale denominator: 24000

    routes_xref_2005 (source 4 of 4)

    Geographic Information Services Unit, Oregon Department of Transportation (ODOT), unknown, routes_xref_2005.

    Type of source media: None

  2. What changes have been made?

    Date: unknown (change 1 of 24)
    Highway class (hwy_class) attribute field added. Values populated based on highway sign attributes.

    Person responsible for change:
    Erik Brewster
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    Date: unknown (change 2 of 24)
    The highway sign and name attributes from routes_xref_2005 were spatially joined to the highway segments.

    Person responsible for change:
    Erik Brewster
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    Date: unknown (change 3 of 24)
    Manual corrections and verfication of attribute transfer were made where necessary.

    Person responsible for change:
    Erik Brewster
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    09-11-08: Populated the DSG_Name field with attribute from Burns district and Roseburg district back country byways layers they gave the state office. Also populated DSG_Name where it overlays with Back_Country_Byways layer in SDE. Our goal is to remove that layer from SDE once we can add a code to query back country byways, scenic routes, etc.

    Person responsible for change:
    Ryan Kelley
    BLM OR/WA State Office
    503-808-6495 (voice)
    rkelley@or.blm.gov

    Date: unknown (change 5 of 24)
    The shapefiles were imported to a personal geodatabase and reprojected.

    Person responsible for change:
    Erik Brewster
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    Date: 20050608 (change 6 of 24)
    The Hwy_SEG and routes_xref_2005 shapefiles were obtained via ftp from ODOT.

    Person responsible for change:
    Erik Brewster
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    Date: 20060612 (change 7 of 24)
    Copied interstate, US, and state highways from the OR/WA BLM GTRN layer to fill gaps in the ODOT highway Layer

    Person responsible for change:
    Nate Smith
    GIS Specialist
    PO BOX 2965
    Portland, OR 97208
    US

    Date: 20060825 (change 8 of 24)
    Attributed frontage and connector roads in Jackson and Josephine counties. The hwylocname and hwy_class fields were populated based on John McGlothlin's local data.

    Person responsible for change:
    Erik Brewster
    Northrop Grumman - BLM Oregon State Office

    Date: 20080110 (change 9 of 24)
    Added highways from WA DOT source for the state of Washington. Coded RDWY_ID with new values 6 and 7 for cartographic purposes.

    Person responsible for change:
    Ryan Kelley
    Northrop Grumman - BLM OR/WA State Office
    503-808-6495 (voice)
    rkelley@blm.gov

    Date: 20080226 (change 10 of 24)
    Corrected US Highway 30 attribute information for 64 segments near The Dalles. Highway 30 was originally incorrectly attributed as a State Highway. Both HWY_CLASS and US_SIGN_1 fields were populated with the correct information for these segments.

    Person responsible for change:
    Ryan Kelley
    Northrop Grumman - BLM OR/WA State Office
    503-808-6495 (voice)
    rkelley@blm.gov

    Date: 20080317 (change 11 of 24)
    Fixed topology errors using these rules (must not overlap, must not self-overlap, must be single part). Worked with Gavin Hoban in Prineville also for questions about rdwy_typ overlap discrepencies.

    Person responsible for change:
    Ryan Kelley
    Northrop Grumman - BLM OR/WA State Office
    503-808-6495 (voice)
    rkelley@blm.gov

    Date: 20090403 (change 12 of 24)
    Placed Succor Creek Road (from Oregon T22S-R46E Sec 28 to Oregon T27S-R46E Sec 11, connecting Oregon highway 201 to US 95) in BLM's editable GTRN dataset on advice of Vale district office GIS staff indicating that this is a dirt road.

    Person responsible for change:
    Steve Salas
    U.S. BLM Oregon State Office
    GIS Specialist / ArcSDE Administrator
    503-808-6416 (voice)
    ssalas@blm.gov

    Date: 20090630 (change 13 of 24)
    Added portion of HWY 95 in Nothern Nevada as requested by Vale District Office

    Person responsible for change:
    Erin Frostad
    BLM
    Carto Tech
    503-808-6524 (voice)
    efrostad@blm.gov

    Date: 20091027 (change 14 of 24)
    Updated Salem Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Bruce Ahrendt reviewed.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)
    efrostad@blm.gov

    Date: 20091118 (change 15 of 24)
    Updated Roseburg Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Gary Passow reviewed.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20091120 (change 16 of 24)
    Updated Coos Bay Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Alan Ward reviewed.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20100114 (change 17 of 24)
    Updated Burns Highways - removed 2 frontage roads and a connection - approved by Pam Keller

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20100120 (change 18 of 24)
    Updated Vale Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Brent Grasty reviewed.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20100203 (change 19 of 24)
    Updated Eugene Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Jay Ruegger reviewed.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20100309 (change 20 of 24)
    Updated Deschutes county highways within urban growth boundary areas Removed frontage roads, overpasses/underpasses from Highways and added them to GTRN.

    Person responsible for change:
    Noah Layosa

    Date: 20100608 (change 21 of 24)
    Updated Prineville Highways - removed frontage, overpasses/underpasses from Highways and added them to GTRN. Updated connections and secondary roads to maintain connectivity. Greg Daniels ok'd.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20120131 (change 22 of 24)
    Added a small segement S of KFalls to connect hwy 161 together for Mike Limb.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20120313 (change 23 of 24)
    Removed Highway 227 in Douglas County and added as County Route 1 in GTRN.

    Person responsible for change:
    Erin Frostad
    BLM
    GIS Tech
    503-808-6524 (voice)

    Date: 20120912 (change 24 of 24)
    Changed highway names from all-uppercase to mixed case. Correct arcs that were missing designation of Snake River-Mormon BCB. Standardized blanks in several fields to null.

    Person responsible for change:
    Shelley Moore
    U.S. Bureau of Land Management, OR/WA State Office
    GIS Specialist
    503-808-6566 (voice)
    r1moore@blm.gov

Back to Top

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?

    In Oregon, the Highway segment id, lrs, roadway id, and roadway type were obtained from the Oregon Department of Transportation's Hwy_seg shapefile. Interstate sign, US sign 1, US sign 2, ST sign 1, ST sign 2, and highway name were obtained from ODOT'S routes_xref_2005 shapefile. In Washington, Interstate sign, US sign 1, US sign 2, ST sign 1, ST sign 2 were populated from WSDOT's SR24kLRSLinesSPS shapefile, while roadway id and roadway type were populated by the Bureau of Land Management Oregon State Office. .Highway local name and highway class were created by the Bureau of Land Management Oregon State Office. OBJECTID, Shape and Shape_Length were generated from ArcGIS software. In Washington, State Route numbers were obtained from the 2005B State Highway Log.

  2. How accurate are the geographic locations?

    Oregons highway data has been determined to meet or exceed NSDI map accuracy standards for 1:24,000 scale maps. Accuracy was determined by the combined use of USGS digital ortho photo quads and the NGS benchmarks to apply an accuracy statement to the highway linework via verification of known and visible NGS benchmarks on the orthoquads. The Washington data's positional accuracy has not been determined.

  3. How accurate are the heights or depths?

    No vertical positional accuracy has been determined

  4. Where are the gaps in the data? What is missing?

    This theme contains all highways and related access features (interchange ramps, frontage roads, etc.) for the states of Oregon and Washington.

  5. How consistent are the relationships among the observations, including topology?

    Where appropriate, line segment ends have been snapped together to eliminate gaps at interchanges, intersections and along contiguous sections of roadway.

Back to Top

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access constraints: PUBLIC DATA: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and may contain errors or omissions. The User assumes the entire risk associated with its use of these data and bears all responsibility in determining whether these data are fit for the User's intended use. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived, and both scale and accuracy may vary across the data set. These data may not have the accuracy, resolution, completeness, timeliness, or other characteristics appropriate for applications that potential users of the data may contemplate. The User is encouraged to carefully consider the content of the metadata file associated with these data. These data are neither legal documents nor land surveys, and must not be used as such. Official records may be referenced at most BLM offices. Please report any errors in the data to the BLM office from which it was obtained. The BLM should be cited as the data source in any products derived from these data. Any Users wishing to modify the data should describe the types of modifications they have performed. The User should not misrepresent the data, nor imply that changes made were approved or endorsed by BLM. This data may be updated by the BLM without notification.

Distributor 1 of 1

  1. Who distributes the data set?

    Eric Hiebenthal
    Bureau of Land Management
    GIS Data Management Specialist
    P.O Box 2965
    Portland, OR 97208
    US

    503-808-6340 (voice)
    503-808-6419 (FAX)
    ehiebent@blm.gov
    Contact Instructions:
    contact instructions

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    The BLM assumes no responsibility for errors or omissions. No warranty is made by the BLM as to the accuracy, reliability, or completeness of these data for individual use or aggregate use with other data; nor shall the act of distribution to contractors, partners, or beyond, constitute any such warranty for individual or aggregate data use with other data. Although these data have been processed successfully on computers of BLM, no warranty, expressed or implied, is made by BLM regarding the use of these data on any other system, or for general or scientific purposes, nor does the fact of distribution constitute or imply any such warranty. In no event shall the BLM have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of the use or reliance on the geographic data or arising out of the delivery, installation, operation, or support by BLM.

  4. How can I download or order the data?

    • Cost to order the data: Contact distributor.


    • Special instructions:

      Data are only available through the Oregon/Washington State office of the Bureau of Land Management.

  5. Is there some other way to get the data?

  6. What hardware or software do I need in order to use the data set?

Back to Top

Who wrote the metadata?

Dates:
Last modified: 20110722
Last reviewed: 20120920

Metadata author:
Roger Mills
Bureau of Land Management, Oregon State Office
GIS Specialist
P.O. Box 2965
Portland, OR 97208
US

(503) 808-6340 (voice)
(503) 808-6419 (FAX)
r2mills@blm.gov
Hours of Service: 8:00-4:00
Contact Instructions:
None

Metadata standard:
FGDC Content Standard for Digital Geospatial Metadata(FGDC-STD-001-1998)

Back to Top