. .

U.S. DEPARTMENT OF THE INTERIOR

BUREAU OF LAND MANAGEMENT

Oregon / Washington

GIS Metadata


BLM OR GTRN Web Roads Line

Frequently-asked questions:


What does this data set describe?

Title:
BLM OR GTRN Web Roads Line

Abstract:
GTRN_PUB_ROADS_ARC: Publication transportation dataset for BLM web display showing both BLM inventoried and non-inventoried roads in Oregon & Washington. This data does not include highways. For highway data see the citation in the Cross Reference Section.

Supplemental information:
Data Dictionary for this data is available on-line www.blm.gov/or/gis/files/docs/BLMGroundTransportation_WebDD.pdf BLM (Bureau of Land Management), USFS (United States Forest Service), USGS (United States Geographic Survey), WODDB (Western Oregon Digital Database), TRB (WODDB Transportation Theme), QC3 (Third round of Quality Control for TRB theme), TIMS (Transportation Information Management System), FIMMS (Facilities Inventory Maintenance ManagementSystem), FAMS (Facilities Assets Management System), DLG (Digital Line Graph), CFF (Cartographic Feature File), RMP (Resource Management Plan), TMO (Transportation Maintenance Objective), O&C (Oregon & California Revested Railroad Lands), PD (Public Domain Lands), CBWR (Coos Bay Wagon Road Lands), MLR (Multiple Land Resource) This dataset is updated on a weekly basis by the BLM Oregon State Office. Please see process contact for details.

  1. How should this data set be cited?

    OR/WA BLM, 20140729, BLM OR GTRN Web Roads Line: OR BLM, Portland, OR.

    Other citation details:
    Known locally as gtrn_pub_roads_arc

  2. What geographic area does the data set cover?

    Bounding coordinates:
    West: -124.722692
    East: -116.500972
    North: 49.002515
    South: 41.833604

  3. What does it look like?

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

    Calendar date: 20140729
    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:
      None

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

    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?

    GTRN_PUB_ROADS_ARC
    OBJECTID
    Internal feature number. (Source: Esri)
                      

    Sequential unique whole numbers that are automatically generated.

    INVCAT
    ROADNUM
    ROADNUM2
    BLMRdNum
    USFSRDNUM
    COUNTYRDNUM
    OtherRdNum
    ROADNAME
    RoadName2
    DSG_NAME
    SPECIALDESG
    WSA_WAYS
    FLTP
    OWNERSHIP
    OWNERDESG
    CONTROL
    ACCESSRGHTS
    ACCESSRGHTSCONTINUITY
    DRIVABILITY
    DRIVABILITYOBSDATE
    CAPITALIMP
    MAINTRESP
    MAINTLVL
    MAINTYR
    ROADCLASS
    CARTOROAD
    SURFACE
    SURFACETYPE
    FCI_CondCode
    CONSTRYEAR
    AVGWIDTH
    SUBGWIDTH
    NUMLANES
    CLOSURESTAT
    CLOSURERSN
    BEGINMILEPOST
    ENDMILEPOST
    TOTALMILES
    BLMORGCODE
    COUNTYCD
    COMMENTS
    ROUTENUM
    ROUTESEG
    ROUTESPUR
    ROUTEID
    LINLOCID
    SEGASSETID
    FRMWKID
    USFSKEYNUM
    TIGERNUM
    AccuracyFt
    CoordSrc
    SourceVintage
    SHAPE
    Feature geometry. (Source: Esri)
                      

    Coordinates defining the features.

    SHAPE_Length
    Length of feature in internal units. (Source: Esri)
                      

    Positive real numbers that are automatically generated.

    Entity and attribute detail citation:
    Data Dictionary for this data is available on-line www.blm.gov/or/gis/files/docs/BLMGroundTransportation_WebDD.pdf
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)

    • OR/WA BLM

  2. Who also contributed to the data set?

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

    Chris Knauf
    BLM OSO
    Travel Plan Coordinator
    333 SW First Ave
    Portland, OR 97204
    US

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

Why was the data set created?

Resource Management Planning

Back to Top

How was the data set created?

  1. Where did the data come from?

    Non_Inv_Roads_arc (source 1 of 2)

    OR BLM, unpublished material, Non_Inv_Roads_arc.

    Type of source media: onLine
    Source contribution:
    Non BLM inventoried roads

    BLM_Inv_Roads_arc (source 2 of 2)

    OR BLM, unpublished material, BLM_Inv_Roads_arc.

    Type of source media: onLine
    Source contribution:
    BLM inventoried roads

  2. What changes have been made?

    Date: unknown (change 1 of 19)
    Data from two feature classes in the editing database are loaded to this feature class: BLM_Inv_Roads_arc and Non_Inv_Roads_arc. Feature-level metadata and edit tracking fields are not retained. Remaining field names are changed. Data from Non_Inv_Roads_arc is assigned a value of Other in the new field InvCat. Data from BLM_Inv_Roads_arc is supplemented with tabular information from the table FAMS_Roads to populate fields that are not found in this source feature class. These roads are assigned a value of BLM in the InvCat field.

    Person responsible for change:
    Steve Salas
    U.S. Bureau of Land Management
    GIS Specialist / ArcSDE Administrator
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6416 (voice)
    ssalas@blm.gov

    Data sources used in this process:
    • BLM_Inv_Roads_arc
    • Non_Inv_Roads_arc

    Data sources produced in this process:
    • gtrn_pub_roads_arc

    Date: 20081006 (change 2 of 19)
    Added the field CartoRoad, DsgName, MaintYr, SubgWidth, Wsa_Ways ClosureStat field added the domain closed (CL). OwnerDesg added domains Fish and Wildlife Service (FWS) and Other Federal Agency (OTHF).

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20090428 (change 3 of 19)
    RoadName for non-inventoried roads and trails expanded to 50 characters wide from 30.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20101029 (change 4 of 19)
    The order of the fields was changed in all tables. This was done to clean-up logical groupings of fields and to fix the inconsistent field order between tables. FAMS Location Number (linear asset) and FAMS Asset Number (segment) - the FAMS terminology changed at FAMS 6.0. EqNum_Parent became Lin_Loc_ID in the FAMS table and LinLocID in the publication datasets; EqNum_Child became Seg_Asset_ID in the FAMS table and SegAssetID in the publication datasets. A prefix of L was added to the SegAssetID values. OwnerDesg domain changed from private road to private route. MaintResp domain was updated to match the FAMS 6.0 domain; Maintenance Agreement BLM was removed. Surface and SurfaceType- At FAMS 6.0 the Surface domain was condensed to just four values. The FAMS 5.0 Surface Type values were retained as an editable GTRN field; the FAMS 6.0 values populate the Surface field. Segment Beginning Milepost - was renamed to BeginMilePost. CountyCd field was added to GTRN in order to capture which county has control over a road. Optional1 field was increased from a length of 20 to a length of 75. Facility_ID, Segment_ID, FIMMSKey, and Cnty_Cd were removed from the Roads and Trails FAMS table as these are no longer populated in FAMS. CountyCd was also removed from the roads and trails publication datasets.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20101101 (change 5 of 19)
    Updated field order, changed field names ROUTEEQNUM to LINLOCID and SEGEQNUM to SEGASSETID.

    Person responsible for change:
    Steve Salas
    U.S. Bureau of Land Management, OR/WA State Office
    GIS Specialist / ArcSDE Administrator
    P.O. Box 2965
    Portland, OR 97208
    US

    503-808-6416 (voice)
    ssalas@blm.gov

    Date: 20101227 (change 6 of 19)
    DesgName - a domain list was added to this field. SpecialDesg - the domain list was modified. This field is no longer coming from FAMS and now exists in all feature classes: BLM inventoried roads and trails, non-inventoried roads and trails, and highways. *The Special Designation field was removed from the FAMS application during the May 26, 2011 release.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20101228 (change 7 of 19)
    Altered domains for route special designations and their names.

    Person responsible for change:
    Steve Salas
    U.S. Bureau of Land Management, OR/WA State Office
    GIS Specialist
    503-808-6416 (voice)
    ssalas@blm.gov

    Date: 20110103 (change 8 of 19)
    Added and spatially corrected roads identified in the Burns WIM process. Aligned other roads to NAIP if I could see them. This affected both inventoried and non-inventoried roads.

    Person responsible for change:
    Stacy Fenton
    Bureau ofLand Management, Burns District Office
    GIS Specialist
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4499 (voice)
    sfenton@blm.gov

    Date: 20110111 (change 9 of 19)
    Aligned some roads to 2005 NAIP in Non-Inv and Inv roads. Also added Cave Gulch Acces Route provided by Bill Dragt.

    Person responsible for change:
    Stacy Fenton
    Bureau of Land Management
    GIS Spec.
    28910 Hwy 20 West
    Hines, OR 97738-9424
    US

    (541) 573-4499 (voice)
    sfenton

    Date: 20110210 (change 10 of 19)
    Closed numerous roads on Emigrant RD, Malheur NF

    Person responsible for change:
    Stacy Fenton
    Bureau of Land Management, Burns District Office
    GIS Specialist
    sfenton
    Hines, OR 97738
    US

    (541) 573-4499 (voice)
    sfenton@blm.gov

    Date: 20110617 (change 11 of 19)
    FLHP field was added.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20110726 (change 12 of 19)
    Removed SpecialDesignation = BCB from Medford District Non_Inv Roads. Added "PBCB" to Optional_1 attribute for Medford Proposed Back Country Byways referenced in 1995 RMP.

    Person responsible for change:
    Dennis Glover
    Bureau of Land Management, Medford Office
    GIS Specialist
    3040 Biddle Road
    Medford, OR 97504
    US

    (541) 618-2343 (voice)
    dglover@blm.gov

    Date: 20110830 (change 13 of 19)
    Added new roads not visible on NAIP inside the CMPA on private land, moved inventory roads to non-inventory roads. Split 4 Inventory Roads at intersections with newly added non-inventory roads. Assigned 11 new frmwk_id to split inventory road segments.

    Person responsible for change:
    Kelly Hazen
    Bureau of Land Management, Burns District Office
    Natural Resource Specialist
    28910 Hwy 20 West
    Hines, OR 97738
    US

    (541) 573-4470 (voice)
    khazen@blm.gov

    Date: 20111216 (change 14 of 19)
    SurfaceType domain value 'Natural (Graded & Drained) was changed to 'Natural Improved'. Definitions were added to the two 'natural' domain values.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20120105 (change 15 of 19)
    A large number of these arcs had SURF_TYP attribute updates performed. SURF_TYP values for all routes where recent field inventory found evidence of past or historic blading/grading/construction were updated. Many of these routes had formerly been attributed with a surface type of "Natural Unimproved". These arcs where updated with a surface type of "Natural Improved" to more accurately reflect the revised definition of a natural improved route having a natural on site surface that has either been improved by being graded without drainage features or graded and drained.

    Person responsible for change:
    Paul Whitman
    Bureau of Land Management
    Planning & Environmental Coordinator
    1301 S. G Street
    Lakeview, OR 97630-1800
    US

    (541)947-6110 (voice)
    (541) 947-6199 (FAX)
    pwhitman@blm.gov

    Date: 20120316 (change 16 of 19)
    AccessRights domain was changed to match the ESMTROW domain. The access rights field became a GTRN data field and is no longer a field coming from FAMS; existing data was not brought over. AccessRightsContinuity field was added and must be used in tandem with the access rights field. Ownership and Control - the O&C Logging Road Right-of-Way Handbook, H-2812-1, dated February 2009, clarified our understanding of ownership and control. The existing GTRN 'control' field (the FAMS 'juris' field) was renamed to 'Ownership' and a new 'Control' field was added. Drivability and DriveabilityObsDate fields were added to capture the physical drivability of a road.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20120605 (change 17 of 19)
    Reconciling BLM_INV_ROADS to agree with Road Condition Assessment field inventory and FAMS. Moved many segments between INV and NONINV. Took into consideration Wilderness Characteristics field inventory. Added streets and roads received from Harney County which have addresses but were missing on GTRN.

    Person responsible for change:
    Pam Keller
    Bureau of Land Management
    GIS Spec
    28910 Hwy 20 West
    Portland, OR 97738-9424
    US

    (541) 573-4486 (voice)
    (541) 573-4411 (FAX)
    pkeller@blm.gov

    Date: 20120629 (change 18 of 19)
    OwnDsgtn and Ownership - a domain was added to the OwnDsgtn field for state forestry routes (STF). Ownership was removed from the non-inventoried roads and trails datasets and is being populated from the OwnDsgtn field in the publication roads and trails datasets. Optional1 - was renamed to Comments and expanded to a length of 255 characters. Closure Year, Planned Closure Program, TMO Implementation Year, TMO Recommended Action, TMO Recommendation Year, and Reason for TMO Action were removed from the orsoedit roads FAMS table and from the roads publication dataset. There is a request to remove these fields from the FAMS database.

    Person responsible for change:
    Rachele Moore
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6566 (voice)
    r1moore@blm.gov

    Date: 20131025 (change 19 of 19)
    Publication roads and trails will no longer have fields for district code & resource area code - this information will be folded into BLM Org. Code. (which could be the FBMS district or RA code - up to the user to populate).

    Person responsible for change:
    Steve Salas
    Bureau of Land Management
    GIS Specialist
    P.O. Box 2965
    Portland, OR 97208
    US

    (503) 808-6416 (voice)
    ssalas@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?

  2. How accurate are the geographic locations?

    Unknown

  3. How accurate are the heights or depths?

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

    Dataset is considered to be complete.

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

    Data are considered to be logically consistent.

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: None, these data are considered public domain.
Use constraints:
These data are provided by Bureau of Land Management (BLM) "as is" and might 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 sources from which they were derived, and both scale and accuracy may vary across the data set. These data might 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-6565 (voice)
    503-808-6374 (FAX)
    ehiebent@blm.gov
    Hours of Service: 7:30 a.m. to 4:00 p.m.

  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?

  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: 20060413
Last reviewed: 20140429

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