<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20260406</CreaDate>
<CreaTime>06382500</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">gtrn_pub_roads_arc</itemName>
<imsContentType export="False">003</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Geographic</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Angular Unit: Degree (0.017453)</csUnits>
<peXml Sync="TRUE">&lt;GeographicCoordinateSystem xsi:type='typens:GeographicCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'&gt;&lt;WKT&gt;GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433],AUTHORITY[&amp;quot;EPSG&amp;quot;,4269]]&lt;/WKT&gt;&lt;XOrigin&gt;-400&lt;/XOrigin&gt;&lt;YOrigin&gt;-400&lt;/YOrigin&gt;&lt;XYScale&gt;999999999.99999988&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;2e-08&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;LeftLongitude&gt;-180&lt;/LeftLongitude&gt;&lt;WKID&gt;4269&lt;/WKID&gt;&lt;LatestWKID&gt;4269&lt;/LatestWKID&gt;&lt;/GeographicCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20260407</SyncDate>
<SyncTime>07412900</SyncTime>
<ModDate>20260407</ModDate>
<ModTime>07412900</ModTime>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<mdContact>
<editorSource>external</editorSource>
<editorDigest>5a5e623f2f1754e1ac1730244bffa682caeb0e82</editorDigest>
<rpIndName>Scott Kiefer</rpIndName>
<rpOrgName>Bureau of Land Management (BLM), Oregon State Office</rpOrgName>
<rpPosName>GS0301 - Geographic Information System Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="True"/>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>skiefer@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown</displayName>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GIS Specialist
Role: Unknown</displayName>
<editorSave>True</editorSave>
<displayName>Name: Scott Kiefer
Organization: Bureau of Land Management (BLM), Oregon State Office
Position: GS0301 - Geographic Information System Specialist
Role: Unknown</displayName>
<role>
<RoleCd value="007"/>
</role>
</mdContact>
<mdDateSt Sync="TRUE">20250409</mdDateSt>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Eric Hiebenthal</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Data Management Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>503-808-6565</voiceNum>
<faxNum>503-808-6374</faxNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ehiebent@blm.gov</eMailAdd>
</cntAddress>
<cntHours>7:30 a.m. to 4:00 p.m.</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<planAvDtTm date="unknown"/>
</distorOrdPrc>
</distributor>
<distTranOps>
<onLineSrc>
<linkage>https://gbp-blm-egis.hub.arcgis.com/pages/oregon</linkage>
</onLineSrc>
</distTranOps>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<placeKeys>
<thesaName>
<resTitle>BLM-STATE</resTitle>
</thesaName>
<keyword>Oregon</keyword>
<keyword>Washington</keyword>
</placeKeys>
<themeKeys>
<thesaName>
<resTitle>BLM-THEME</resTitle>
</thesaName>
<keyword>Facility</keyword>
<keyword>Geospatial</keyword>
</themeKeys>
<themeKeys>
<thesaName>
<resTitle>NONE</resTitle>
</thesaName>
<keyword>Ground Transportation</keyword>
<keyword>GTRN</keyword>
<keyword>Inventoried Roads</keyword>
<keyword>Non-Inventoried Roads</keyword>
<keyword>Roads</keyword>
<keyword>Transportation Networks</keyword>
</themeKeys>
<idCitation>
<citRespParty>
<rpIndName>U.S. Department of the Interior, Bureau of Land Management (BLM)</rpIndName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<resTitle>BLM OR GTRN Publication Roads Line</resTitle>
<date>
<pubDate>2026-04-07</pubDate>
</date>
<citRespParty>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpCntInfo>
<cntAddress>
<delPoint>Portland, Oregon</delPoint>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="010"/>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>U.S. Department of Interior, Bureau of Land Management (BLM)</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
<otherCitDet>Known locally as gtrn_pub_roads_arc</otherCitDet>
</idCitation>
<idAbs>GTRN_PUB_ROADS_ARC: Internal BLM Use Only. Not for release. Contains records with CartoRoads Hide Domain values. Publication transportation dataset showing both BLM inventoried and non-inventoried roads in Oregon &amp; Washington. This data does not include highways. For highway data see the citation in the Cross Reference Section.</idAbs>
<idPurp>This data is intended for Resource Management Planning.</idPurp>
<idStatus>
<ProgCd value="007"/>
</idStatus>
<idPoC>
<rpIndName>Chris Knauf</rpIndName>
<rpOrgName>BLM OSO</rpOrgName>
<rpPosName>Travel Plan Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6427</voiceNum>
</cntPhone>
<cntAddress addressType="physical">
<delPoint>333 SW First Ave</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97204</postCode>
<country>US</country>
<eMailAdd>cknauf@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<resMaint>
<maintFreq>
<MaintFreqCd value="001"/>
</maintFreq>
</resMaint>
<searchKeys>
<keyword>Facility</keyword>
<keyword>Geospatial</keyword>
<keyword>Ground Transportation</keyword>
<keyword>GTRN</keyword>
<keyword>Inventoried Roads</keyword>
<keyword>Non-Inventoried Roads</keyword>
<keyword>Oregon</keyword>
<keyword>Roads</keyword>
<keyword>transportation</keyword>
<keyword>Transportation Networks</keyword>
<keyword>Washington</keyword>
</searchKeys>
<resConst>
<LegConsts>
<useLimit>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.</useLimit>
<othConsts>None, these data are considered public domain.</othConsts>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</resConst>
<aggrInfo>
<aggrDSName>
<resTitle>highways_arc</resTitle>
<date>
<pubDate date="unknown" time="unknown"/>
</date>
<citRespParty>
<rpOrgName>OR BLM</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</aggrDSName>
<assocType>
<AscTypeCd value="001"/>
</assocType>
</aggrInfo>
<spatRpType>
<SpatRepTypCd value="001"/>
</spatRpType>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<envirDesc Sync="FALSE">Esri ArcGIS 13.1.3.41833</envirDesc>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-125</westBL>
<eastBL>-116</eastBL>
<southBL>41.5</southBL>
<northBL>49.5</northBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>publication date</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2026-04-07</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<suppInfo>Data Dictionary for this data is available on-line http://www.blm.gov/or/gis/files/docs/BLMGroundTransportation_WebDD.pdf BLM (Bureau of Land Management) GTRN (Ground Transportation) 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&amp;C (Oregon &amp; 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. A published revision of the Department Manual’s Part 305: Departmental Science Effects, Chapter 3: Integrity of Scientific and Scholarly Activities (305 DM 3), effective December 16, 2014, is available online at http://elips.doi.gov/ELIPS/DocView.aspx?id=4056. Scholarly information considered in Departmental decision making must be robust, of the highest quality, and the result of as rigorous scientific and scholarly processes as can be achieved. Most importantly, it must be trustworthy. This policy helps us to achieve that standard (http://www.doi.gov/scientificintegrity/index.cfm).</suppInfo>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-124.188680</westBL>
<eastBL Sync="TRUE">-117.132756</eastBL>
<northBL Sync="TRUE">49.000506</northBL>
<southBL Sync="TRUE">42.026486</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<idCredit>Bureau of Land Management (BLM), Oregon State Office</idCredit>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<resConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Non classified</classSys>
<handDesc>None</handDesc>
</SecConsts>
</resConst>
<tpCat>
<TopicCatCd value="018"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
<maintNote>Last metadata review date: 20240422</maintNote>
</mdMaint>
<mdConst>
<SecConsts>
<class>
<ClasscationCd value="001"/>
</class>
<classSys>Non classified</classSys>
<handDesc>Non Classified</handDesc>
</SecConsts>
</mdConst>
<mdConst>
<Consts>
<useLimit>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.</useLimit>
</Consts>
</mdConst>
<mdConst>
<LegConsts>
<othConsts>None, these data are considered public domain.</othConsts>
</LegConsts>
</mdConst>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<report type="DQConcConsis">
<measDesc>Data are considered to be logically consistent.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Dataset is considered to be complete.</measDesc>
</report>
<report type="DQQuanAttAcc">
<measDesc>Unknown</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Unknown</measDesc>
</report>
<dataLineage>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm date="unknown">Unknown</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>U.S. Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist / ArcSDE Administrator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>BLM_Inv_Roads_arc</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="used">
<srcCitatn>
<resAltTitle>Non_Inv_Roads_arc</resAltTitle>
</srcCitatn>
</stepSrc>
<stepSrc type="produced">
<srcCitatn>
<resAltTitle>gtrn_pub_roads_arc</resAltTitle>
</srcCitatn>
</stepSrc>
</prcStep>
<dataSource>
<srcDesc>BLM inventoried roads</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>BLM_Inv_Roads_arc</resTitle>
<resAltTitle>BLM_Inv_Roads_arc</resAltTitle>
<date>
<pubDate date="inapplicable"/>
</date>
<citRespParty>
<rpOrgName>OR BLM</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date - weekly</exDesc>
</srcExt>
</dataSource>
<dataSource>
<srcDesc>Non BLM inventoried roads</srcDesc>
<srcMedName>
<MedNameCd value="015"/>
</srcMedName>
<srcCitatn>
<resTitle>Non_Inv_Roads_arc</resTitle>
<resAltTitle>Non_Inv_Roads_arc</resAltTitle>
<date>
<pubDate date="inapplicable" time="unknown"/>
</date>
<citRespParty>
<rpOrgName>OR BLM</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<presForm>
<PresFormCd value="005"/>
</presForm>
<presForm>
<fgdcGeoform>vector digital data</fgdcGeoform>
</presForm>
</srcCitatn>
<srcExt>
<exDesc>publication date - weekly</exDesc>
</srcExt>
</dataSource>
<prcStep>
<stepDesc>Changed RWO_HALF_WIDTH from feet to meters in BLM inventoried roads and Non-inventoried roads.
Updated 57,0079 records in BLM_INV_ROADS_ARC Updated 8,156 records in NON_INV_ROADS_ARC.
Multiplied each record in feet by 0.3048 to get meters.</stepDesc>
<stepDateTm>20230629</stepDateTm>
<stepProc>
<rpIndName>Bryant Mecklem</rpIndName>
<rpOrgName>U.S. Bureau of Land Management Oregon State Office</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<role>
<RoleCd value="007"/>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97204</postCode>
<eMailAdd>bmecklem@blm.gov</eMailAdd>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>(503)808-6506</voiceNum>
</cntPhone>
</rpCntInfo>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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).</stepDesc>
<stepDateTm>2008-10-06</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>RoadName for non-inventoried roads and trails expanded to 50 characters wide from 30.</stepDesc>
<stepDateTm>2009-04-28</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2010-10-29</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Updated field order, changed field names ROUTEEQNUM to LINLOCID and SEGEQNUM to SEGASSETID.</stepDesc>
<stepDateTm>2010-11-01</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>U.S. Bureau of Land Management, OR/WA State Office</rpOrgName>
<rpPosName>GIS Specialist / ArcSDE Administrator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>503-808-6416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2010-12-27</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Altered domains for route special designations and their names.</stepDesc>
<stepDateTm>2010-12-28</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>U.S. Bureau of Land Management, OR/WA State Office</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>503-808-6416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2011-01-03</stepDateTm>
<stepProc>
<rpIndName>Stacy Fenton</rpIndName>
<rpOrgName>Bureau ofLand Management, Burns District Office</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 573-4499</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>28910 Hwy 20 West</delPoint>
<city>Hines</city>
<adminArea>OR</adminArea>
<postCode>97738</postCode>
<country>US</country>
<eMailAdd>sfenton@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Aligned some roads to 2005 NAIP in Non-Inv and Inv roads. Also added Cave Gulch Acces Route provided by Bill Dragt.</stepDesc>
<stepDateTm>2011-01-11</stepDateTm>
<stepProc>
<rpIndName>Stacy Fenton</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Spec.</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 573-4499</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>28910 Hwy 20 West</delPoint>
<city>Hines</city>
<adminArea>OR</adminArea>
<postCode>97738-9424</postCode>
<country>US</country>
<eMailAdd>sfenton</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Closed numerous roads on Emigrant RD, Malheur NF</stepDesc>
<stepDateTm>2011-02-10</stepDateTm>
<stepProc>
<rpIndName>Stacy Fenton</rpIndName>
<rpOrgName>Bureau of Land Management, Burns District Office</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 573-4499</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>sfenton</delPoint>
<city>Hines</city>
<adminArea>OR</adminArea>
<postCode>97738</postCode>
<country>US</country>
<eMailAdd>sfenton@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>FLHP field was added.</stepDesc>
<stepDateTm>2011-06-17</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2011-07-26</stepDateTm>
<stepProc>
<rpIndName>Dennis Glover</rpIndName>
<rpOrgName>Bureau of Land Management, Medford Office</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 618-2343</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>3040 Biddle Road</delPoint>
<city>Medford</city>
<adminArea>OR</adminArea>
<postCode>97504</postCode>
<country>US</country>
<eMailAdd>dglover@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2011-08-30</stepDateTm>
<stepProc>
<rpIndName>Kelly Hazen</rpIndName>
<rpOrgName>Bureau of Land Management, Burns District Office</rpOrgName>
<rpPosName>Natural Resource Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 573-4470</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>28910 Hwy 20 West</delPoint>
<city>Hines</city>
<adminArea>OR</adminArea>
<postCode>97738</postCode>
<country>US</country>
<eMailAdd>khazen@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>SurfaceType domain value ‘Natural (Graded &amp; Drained) was changed to ‘Natural Improved’. Definitions were added to the two ‘natural’ domain values.</stepDesc>
<stepDateTm>2011-12-16</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2012-01-05</stepDateTm>
<stepProc>
<rpIndName>Paul Whitman</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>Planning &amp; Environmental Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541)947-6110</voiceNum>
<faxNum>(541) 947-6199</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>1301 S. G Street</delPoint>
<city>Lakeview</city>
<adminArea>OR</adminArea>
<postCode>97630-1800</postCode>
<country>US</country>
<eMailAdd>pwhitman@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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&amp;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.</stepDesc>
<stepDateTm>2012-03-16</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2012-06-05</stepDateTm>
<stepProc>
<rpIndName>Pam Keller</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Spec</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(541) 573-4486</voiceNum>
<faxNum>(541) 573-4411</faxNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>28910 Hwy 20 West</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97738-9424</postCode>
<country>US</country>
<eMailAdd>pkeller@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>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.</stepDesc>
<stepDateTm>2012-06-29</stepDateTm>
<stepProc>
<rpIndName>Rachele Moore</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6566</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>r1moore@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Publication roads and trails will no longer have fields for district code &amp; 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).</stepDesc>
<stepDateTm>2013-10-25</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>GIS_MILES field added</stepDesc>
<stepDateTm>2016-08-23</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>BLM</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>(503) 808-6416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
<prcStep>
<stepDesc>Added field PACER, removed field FCI_CONDCODE</stepDesc>
<stepDateTm>2022-08-22</stepDateTm>
<stepProc>
<rpIndName>Steve Salas</rpIndName>
<rpOrgName>U.S. Bureau of Land Management</rpOrgName>
<rpPosName>GIS Specialist</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>5038086416</voiceNum>
</cntPhone>
<cntAddress addressType="postal">
<delPoint>P.O. Box 2965</delPoint>
<city>Portland</city>
<adminArea>OR</adminArea>
<postCode>97208</postCode>
<country>US</country>
<eMailAdd>ssalas@blm.gov</eMailAdd>
</cntAddress>
</rpCntInfo>
<role>
<RoleCd value="009"/>
</role>
</stepProc>
</prcStep>
</dataLineage>
</dqInfo>
<spatRepInfo>
<Indref>None</Indref>
<VectSpatRep>
<geometObjs Name="GTRN_PUB_ROADS_ARC">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="4269"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.5(3.0.1)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="GTRN_PUB_ROADS_ARC">
<enttyp>
<enttypl Sync="FALSE">GTRN_PUB_ROADS_ARC</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypd>BLM ORWA Roads</enttypd>
<enttypds>BLM</enttypds>
</enttyp>
<attr>
<attrlabl Sync="FALSE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>INVCAT</attrlabl>
<attalias>InvCat</attalias>
<attrdef>This field indicates the source of the data in publication. If the source is BLM_Inv_Roads_arc or BLM_Inv_Trails_arc then the value is ‘BLM’. If the data source is Non_Inv_Roads_arc or Non_Inv_Trails_arc then the value is ‘Other’. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>BLM</edomv>
<edomvd>BLM</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Other</edomv>
<edomvd>Other</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>ROADNUM</attrlabl>
<attalias>RoadNum</attalias>
<attrdef>The intent of this field is to hold the road number of the primary route owner. The route number placed in this field should be consistent with the agency in the Ownership Designation (OWN_DSGTN) field.
RoadNum is derived from BLM_RD_NO, USFS_RD_NO, COUNTY_RD_NO, and OTHER_RD_NO based on the road owner in the OWN_DSGTN field. RoadNum will be populated with the BLM_RD_NO for privately owned roads where the inventory category (InvCat) = ‘BLM’.
This field is used for cartographic labeling and needs to be formatted to allow for map labels. Data Population Ruleset
1. If the only road number field populated does not match the road owner then RoadNum will be left blank and RoadNum2 will be populated.
2. If the road owner is not known and only one of the four road number fields is populated then RoadNum will be populated with the sole attributed value.
3. If the road owner is not known and more than one of the four road number fields is populated then RoadNum will be populated based on an agreement in the road number fields and the majority underlying land owner. That is:
a. If the BLM_RD_NO field is populated and the underlying land owner, or land owner majority, is BLM, then RoadNum will be populated with the BLM_RD_NO field.
b. If the USFS_RD_NO field is populated and the underlying land owner, or land owner majority, is FS, then RoadNum will be populated with the USFS_RD_NO field.
c. If the COUNTY_RD_NO field is populated and the underlying land owner, or land owner majority, is private, then RoadNum will be populated with the COUNTY_RD_NO field.
4. If the road owner is not known and more than one of the four road number fields is populated and the populated road number field does not correspond with the underlying land owner, then RoadNum and RoadNum2 will not be populated in the GTRN publication dataset.
Optional Eastern Oregon Label Expressions (using the GTRN publication dataset field names):
-00 Routes
• Label SQL Query: “BLMRDNUM” LIKE '____-00'
• Label Expression: Left ([BLMRDNUM],4)
-A0 Routes
• Label SQL Query: “BLMRDNUM” LIKE '____-_0' AND “BLMRDNUM” NOT LIKE '____-00'
• Label Expression: Left ([BLMRDNUM],6)
-AA Routes
• Label SQL Query: “BLMRDNUM” LIKE '____-__' AND (“BLMRDNUM” NOT LIKE '____-0_' AND “BLMRDNUM” NOT LIKE '____-_0')
• Label Expression: [BLMRDNUM]</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Examples: “16-2-30.0 “,”6197-00”</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>ROADNUM2</attrlabl>
<attalias>RoadNum2</attalias>
<attrdef>The intent of this field is to hold any secondary road numbers. These secondary numbers can either be a second number assigned by the primary road owner or the number assigned by an agency other than the primary road owner. RoadNum2 is derived from BLM_Rd_No, USFS_Rd_No, County_Rd_No, and Other_Rd_No once RoadNum has been populated. The route number placed in this field does not necessarily need to be consistent with the agency in the ownership designation field. This field is used for cartographic labeling and needs to be formatted to allow for map labels. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Examples: “1-8-25.0”</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>BLMRDNUM</attrlabl>
<attalias>BLMRdNum</attalias>
<attrdef>This field contains the BLM road number.
This field is used to populate RoadNum where OwnerDesg = ‘BLM’ and where InvCat = ‘BLM’ AND OwnerDesg (OWN_DSGTN) = ‘PVT’.
In western Oregon FAMS routes consist of four elements based on where a route starts: township, range, section, and segment number. The FAMS data entry convention includes leading zeros and township-range direction. RoadNum is the cartographic labeling representation of the FAMS field RouteNum for inventoried routes, i.e., no leading zeros and include the township-range direction only when it’s north or east. The first three elements – township, range, and section – are separated by dashes (-) rather than spaces. The fourth route number element, segment numbers (an alpha-numeric value), should be stored in the RouteSeg (O_CSEGS) field and not the Rt_Num1 field. BLM_RD_NO: 10-5-20.5
RT_NUM (from FAMS): 10 S 05 W 20.00
In eastern Oregon BLMRdNum is a six-digit alpha-numeric system comprised of the RouteNum and RouteSpur FAMS fields. BLMRdNum: 8276-A0
RouteNum (from FAMS): 8276
RouteSpur (from FAMS): A0
Each district is assigned a unique block of numbers for the first 4 places of the road number as follows:
• Burns: 6200, 7200, 8200
• Lakeview: 6100, 7100, 8100
• Prineville: 6500, 7500, 8500
• Spokane: 6000, 6700, 6800, 6900, 7000, 7800, 7900, 8800, 8900, 9800
• Vale: 6300, 6600, 7300, 7600, 8300, 8600
Spurs will be numbered with a 2-digit alpha-numeric system, with a zero used rather than a blank space for the sake of clarity. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROUTESEG</attrlabl>
<attalias>RouteSeg</attalias>
<attrdef>This field provides the route segment identifier for O&amp;C routes. When combined with route number, the full route segment identifier is formed (see ROUTE_ID).</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>USFSRDNUM</attrlabl>
<attalias>USFSRdNum</attalias>
<attrdef>This field contains the current FS road number. Values should be a 7-digit number with no text and no punctuation, e.g., 2231714. The first four digits (2231) represent a Forest Service primary road; the last three digits (714) represent a Forest Service secondary road. This field is used to populate RoadNum where OwnerDesg = ‘FS’. The 7-digit number is condensed to 2-, 4-, or 3-digits in the RoadNum field for a more label friendly format.
FS Arterial
USFSRdNum Format: 2200000
RoadNum and RoadNum2 Format: 22
FS Collector
USFSRdNum Format: 2231000
RoadNum and RoadNum2 Format: 2231
FS Local
USFSRdNum Format: 2231714
RoadNum and RoadNum2 Format: 714</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>COUNTYRDNUM</attrlabl>
<attalias>CountyRdNum</attalias>
<attrdef>This field contains the current county road number. No prefix should be used. If there is a letter identifier, capitalize the letter. This field is used to populate RoadNum when OwnerDesg = ‘Cnty’.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>OTHERRDNUM</attrlabl>
<attalias>OtherRdNum</attalias>
<attrdef>This field contains the road number for National Park Service (NPS), Fish and Wildlife (FWS), Bureau of Indian Affairs (BIA), Other Federal (OTHF), State Forestry (STF), Other State (STO), Municipal (MUN), and non-Inv Private (PVT) roads.
BLM, FS, and county road numbers should be entered in their respective fields.
This field is used to populate RoadNum where OwnerDesg = ‘NPS, FSW, BIA, OTHF, STF, STO, MUN’ and where OwnerDesg = ‘PVT AND InvCat = ‘Other’.
</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROADNAME</attrlabl>
<attalias>RoadName</attalias>
<attrdef>The intent of this field is to hold the road or trail name of the primary route owner. Note: For Inventoried roads and trails this field is populated from the text to the right of the colon: in the FAMS Location Description. Road numbers and names will be entered into the FAMS LOCATION DESCRIPTION field at the location tab in the locations module as follows:
6376-A0: Rattlesnake Cutoff 2 Spur
20 S 11 W 36.00: Smith River Rd
19 S 08 W 19.04:
If the road is not named a colon must still be placed after the road number.
For acceptable abbreviations see the Street Suffix Abbreviations list.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROADNAME2</attrlabl>
<attalias>RoadName2</attalias>
<attrdef>The intent of this field is to hold a secondary road or trail name. For acceptable abbreviations see the Street Suffix Abbreviations list.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>OWNERSHIP</attrlabl>
<attalias>Ownership</attalias>
<attrdef>The ownership (juris) field represents the entity that has the authority to set terms of road maintenance and conditions of road use. Land ownership does not necessarily mean the road is owned by the same entity. Similarly, road ownership does not necessarily mean the road is controlled by the same entity.
This field applies to all roads in OR/WA, however, the definitions of ownership and control, as shown in the Road Control and Road Ownership Table Ruleset, come from the O&amp;C Logging Road Right-of-Way Handbook, H-2812-1, dated February 2009. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Bureau of Land Management</edomv>
<edomvd>Bureau of Land Management</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Other Agency</edomv>
<edomvd>Other Agency - Includes city, county, state, and federal agencies (including the Federal Highway Administration)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Private</edomv>
<edomvd>Private</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Not Known</edomv>
<edomvd>Not Known</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>OWNERDESG</attrlabl>
<attalias>OwnerDesg</attalias>
<attrdef>The ownership designation field further distinguishes the other agency value in the FAMS ownership (juris) field. BIA owned routes could be BIA owned routes or tribal routes held in trust by the BIA. Tribal roads not held in trust by the BIA should be considered private route ownership. This field also allows cartographic representation for non-inventoried roads. This field does not relate to land ownership. Non-compatible values will result in an edit version being rejected during the submission process (see the Ownership Designation and Ownership Compatibility Matrix).</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>BLM</edomv>
<edomvd>Bureau of Land Management</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>FS</edomv>
<edomvd>Forest Service</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NPS</edomv>
<edomvd>National Park Service</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>FWS</edomv>
<edomvd>Fish and Wildlife Service</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BIA</edomv>
<edomvd>Bureau of Indian Affairs</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OTHF</edomv>
<edomvd>Other Federal Agency</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>STF</edomv>
<edomvd>State Forestry route (i.e., Oregon ODF or Washington DNR)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>STO</edomv>
<edomvd>Other state route (e.g., State Park)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>CNTY</edomv>
<edomvd>County route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MUN</edomv>
<edomvd>Municipal route (urban, residential, etc.)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>PVT</edomv>
<edomvd>Private route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NKN</edomv>
<edomvd>Not Known</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CONTROL</attrlabl>
<attalias>Control</attalias>
<attrdef>The control field represents the entity that has the right to authorize third party use of the road subject to the rights of the road owner. Road control does not necessarily mean the road is owned by the same entity.
Privately owned roads on BLM land are always controlled by the United States.
This field applies to all roads in OR/WA, however, the definitions of ownership and control, as shown in the Road Control and Road Ownership Table Ruleset, come from the O&amp;C Logging Road Right-of-Way Handbook, H-2812-1, dated February 2009.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Bureau of Land Management</edomv>
<edomvd>Bureau of Land Management</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Other Agency</edomv>
<edomvd>Other Agency - includes city, county, state, and federal agencies (including the Federal Highway Administration)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Private</edomv>
<edomvd>Private</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Not Known</edomv>
<edomvd>Not Known</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>ACCESSRGHTS</attrlabl>
<attalias>AccessRghts</attalias>
<attrdef>The access rights field captures which roads public access is secured and which roads the BLM has the legal administrative right to use on a road segment by road segment basis. This field must be used in tandem with the Access Rights Continuity field.
This field does not define physical access. Physical access is determined through a combination of Access Rights, Access Rights Continuity, and Closure Status. This field is independent of management decisions made by the BLM and is a reflection of exclusive and non-exclusive easements and reciprocal right-of-way agreements. The access rights values in this field should not be in conflict with the access rights values identified in the ESMTROW dataset. In instances where the ESMTROW dataset has more than one access right value the most inclusive value should be used in GTRN, i.e., if the BLM has an exclusive easement (public access is secured) with a private landowner and a non-exclusive (admin access rights) with a timber industry entity on that same road segment then GTRN should display the public, or most inclusive, access rights.
More GTRN road segments may have the access rights identified than are identified in the ESMTROW dataset (see the Road Owner / Land Owner Access Rights Ruleset). For example, BLM roads on BLM lands do not require an easement; BLM roads on BLM lands will always have public access rights. Even though BLM roads on BLM lands will always have public access rights, as a result of the checkerboard land pattern the public’s access to those roads may be restricted. It is therefore necessary to assess the AccessRightsContinuity field.
The ESMTROW data layer includes additional information about the easement or right-of-way, e.g., case number, the authorized use, and the type of feature. It is important to include the access rights information in both data layers.
</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>PUBLIC</edomv>
<edomvd>Public Access (including BLM) is secured</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ADMIN</edomv>
<edomvd>BLM administrative rights; no public access is secured</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NONE</edomv>
<edomvd>No public or BLM access is allowed</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UNKNOWN</edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>ACCESSRGHTSCONTINUITY</attrlabl>
<attalias>AccessRghtsContinuity</attalias>
<attrdef>The access rights continuity field captures which roads public access is secured and which roads the BLM has the legal administrative right to use in the context of the road network. This field must be used in tandem with the Access Rights field.
This field does not define physical access. Physical access is determined through a combination of Access Rights, Access Rights Continuity, and Closure Status.
Public access rights are most typically interrupted by use rights secured thru Reciprocal Right-of-Way Agreements (RROW’s), or any other non-exclusive easement. All BLM roads tributary to roads without secured public access also do not have secured public access.
As an example, the BLM-administered land in western Oregon is predominantly intermingled in a checkerboard pattern with private land. Intermingled private lands are owned primarily by timber companies and are managed for commercial timber production. Legal access to federal and private timberlands is provided through long-term or perpetual RROW’s between the United States and private timberland owners as authorized by the Federal Land and Policy Management Act of 1976 (FLPMA) and other Federal regulations. A RROW provides both the United States and the private landowner with a non-exclusive right to use, construct and maintain logging roads on each other’s property for forest management and removal of forest products. These RROW’s do not grant rights for public access and recreational use of roads constructed under these agreements. BLM typically negotiates exclusive easements with private landowners to obtain access for forest management activities when a reciprocal agreement is not needed. Unlike RROW’s, exclusive road easements typically do grant rights for public use.
This attribute has several useful applications: 1) Travel and Transportation Management (TTM) planning, determining which BLM roads have continuous public access rights and are therefore “open to public travel” is a critical first step in the TTM planning process. 2) Allocation, this is the setting apart or segregation of a portion of the road replacement cost, capital expenditure, or road maintenance fees attributable to road uses other than log hauling (e.g. recreation and other public uses). The net effect of allocation is that RROW permittees are not required to share in road costs which are not directly attributable to hauling of timber and other forest products. 3) Federal Lands Transportation Program (FLTP) road nominations, all roads nominated for inclusion in this FHWA program must be “open to public travel”, i.e., have continuous public access rights. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>PUBLIC_CONT</edomv>
<edomvd>Continuous Public Access (including BLM) is secured</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ADMIN_CONT</edomv>
<edomvd>BLM administrative rights; no continuous public access is secured</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NONE_CONT</edomv>
<edomvd>No public or BLM access is allowed</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UNKNOWN</edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SPECIALDESG</attrlabl>
<attalias>SpecialDesg</attalias>
<attrdef>Special designation routes are routes that have been identified through formal national, state, or agency designation processes to have a level of scenic, natural, cultural, recreational, or archeological importance beyond a traffic thoroughfare.
More than one of these attributes may apply to a single route segment. If this is the case, choose the value that is highest in the hierarchy. All-American Road: All-American Roads are designated by the US Secretary of Transportation for their scenic, historic, natural, cultural, recreational, or archeological qualities and are considered to be the "best of the best." These routes represent the finest examples of scenic drives in America, making them "designations unto themselves." These routes must have prior designation as a State Scenic Byway or State Scenic and Recreational Highway to be submitted for national designation. National Scenic Byway: National Scenic Byways are designated by the US Secretary of Transportation for their scenic, historic, natural, cultural, recreational, or archeological qualities and merit national level recognition. These routes must have prior designation as a State Scenic Byway or State Scenic and Recreation Highway to be submitted for national designation. BLM Back Country Byway: Back Country Byways are designated through a resource management plan (RMP) and showcase the variety of richness of BLM's off-the-beaten track public lands. Most of the byways are either paved or graded gravel and dirt roads, passable in ordinary passenger cars. Others are safely driven only in a high-clearance truck or 4-wheel drive vehicle.
National Forest Scenic Byway: The Chief of the Forest Service administratively designates National Forest Scenic Byways. These routes represent the best of the roads running through the national forests and showcase outstanding national forest and grassland scenery.
State Scenic Byway (OR): Oregon State Scenic Byways are designated by the Oregon Transportation Commission. They have high national or statewide appeal, feature historic, recreational, archeological, cultural, or natural appeal in addition to scenic qualities, are a minimum of 30 miles long, and must be passable by passenger car.
State Tour Route (OR): Oregon State Tour Routes are designated by the Oregon Transportation Commission. They have high local or regional appeal, feature similar qualities as State Scenic Byways, are a minimum of 20 miles long, and must be passable by passenger car or four-wheel drive vehicle.
State Scenic and Recreational Highway (WA): Washington State Scenic and Recreation Highways are designated by the state legislative statute for the purpose of ensuring the state's most spectacular and diverse landscapes, including scenic, natural, recreational, cultural, and historic resources. State Scenic Bikeway (OR): Oregon State Scenic Bikeways are designated by the Oregon Recreation and Parks Commission. Bikeways are signed bike routes on roads and bicycle paths that provide access to national, state, or regional resources of superlative quality and scenic splendor. They can be linear routes a minimum of 40 miles long, or a loop a minimum of 5 miles long. Auto Tour Route: These routes are usually self-designated by a variety of entities including counties, state tourism offices, local chambers of commerce, regional industry groups, and land management agencies. They usually highlight and market a local or regional characteristic or product such as a collection of covered bridges, waterfalls, wineries, farm stands, etc. A subset of auto tour routes focuses specifically on wildlife viewing opportunities, including the OR and WA Birding Trails. National Scenic Trail: Part of the congressionally designated National Trail System, these trails comprise of continuous protected scenic corridors for outdoor recreation.
National Historic Trail: Part of the congressionally designated National Trail System, these trails recognize broad facets of history such as prominent past routes of exploration, migration, trade, communication, and military action. Historic trails generally consist of remnant sites and trail sections, and thus are not necessarily continuous.
National Recreation Trail: Part of the congressionally designated National Trail System, these trails are recognized by the Federal Government as contributing to the National Trail System. They vary in length, terrain, difficulty, and accessibility.
National Geologic Trail: Part of the congressionally designated national geologic trail. It is a network of touring routes with interpretive opportunities distributed across the vast west. May consist of both foot and vehicle travel. The Special Designation and Special Designation Name Compatibility Matrix provides a cross reference with the special designation name and the special designation type.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>AAR</edomv>
<edomvd>All-American Road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NSB</edomv>
<edomvd>National Scenic Byway</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BCB</edomv>
<edomvd>BLM Back Country Byway</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>FSB</edomv>
<edomvd>National Forest Scenic Byway</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SSB</edomv>
<edomvd>State Scenic Byway (OR)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>STR</edomv>
<edomvd>State Tour Route (OR)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SSRH</edomv>
<edomvd>State Scenic and Recreation Highway (WA)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SSBI</edomv>
<edomvd>State Scenic Bikeway (OR)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ATR</edomv>
<edomvd>Auto Tour Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NST</edomv>
<edomvd>National Scenic Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NHT</edomv>
<edomvd>National Historic Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NRT</edomv>
<edomvd>National Recreation Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NGT</edomv>
<edomvd>National Geologic Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SST</edomv>
<edomvd>State Scenic Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SRT</edomv>
<edomvd>State Regional Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NON</edomv>
<edomvd>None</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>DSGNAME</attrlabl>
<attalias>DsgName</attalias>
<attrdef>The official name of a specially designated route.
The Special Designation and Special Designation Name Compatibility Matrix provides a cross reference with the special designation name and the special designation type.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">75</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomvds>BLM</edomvds>
<edomv>Blitzen Valley Auto Tour Route</edomv>
<edomvd>Blitzen Valley Auto Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Blue Mountain Century Scenic Bikeway</edomv>
<edomvd>Blue Mountain Century Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Blue Mountain National Forest Scenic Byway</edomv>
<edomvd>Blue Mountain National Forest Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>California National Historic Trail</edomv>
<edomvd>California National Historic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cape Flattery Tribal Scenic Byway</edomv>
<edomvd>Cape Flattery Tribal Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cascade Lakes Scenic Byway</edomv>
<edomvd>Cascade Lakes Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cascade Loop</edomv>
<edomvd>Cascade Loop</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cascade Siskiyou Scenic Bikeway</edomv>
<edomvd>Cascade Siskiyou Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cascading Rivers Bikeway</edomv>
<edomvd>Cascading Rivers Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Charleston-Bandon Loop Tour Route</edomv>
<edomvd>Charleston-Bandon Loop Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>China Ditch Auto Tour Route</edomv>
<edomvd>China Ditch Auto Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Chinook Scenic Byway</edomv>
<edomvd>Chinook Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Christmas Valley Back Country Byway</edomv>
<edomvd>Christmas Valley Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Chuckanut Drive</edomv>
<edomvd>Chuckanut Drive</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Columbia River Gorge Scenic Byway - Washington</edomv>
<edomvd>Columbia River Gorge Scenic Byway - Washington</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cottage Grove Covered Bridge Tour Route</edomv>
<edomvd>Cottage Grove Covered Bridge Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Coulee Corridor Scenic Byway</edomv>
<edomvd>Coulee Corridor Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Covered Bridges Scenic Bikeway</edomv>
<edomvd>Covered Bridges Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Cow Creek Back Country Byway</edomv>
<edomvd>Cow Creek Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Diamond Craters Auto Tour Route</edomv>
<edomvd>Diamond Craters Auto Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Diamond Loop Back Country Byway
</edomv>
<edomvd>Diamond Loop Back Country Byway
</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>East Steens Tour Route</edomv>
<edomvd>East Steens Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Elkhorn Drive National Forest Scenic Byway</edomv>
<edomvd>Elkhorn Drive National Forest Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Galice-Hellgate Back Country Byway</edomv>
<edomvd>Galice-Hellgate Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Grande Tour Route</edomv>
<edomvd>Grande Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Grande Tour Scenic Bikeway</edomv>
<edomvd>Grande Tour Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Grave Creek to Marial Back Country Byway</edomv>
<edomvd>Grave Creek to Marial Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Hells Canyon Scenic Byway</edomv>
<edomvd>Hells Canyon Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Hidden Coast Scenic Byway</edomv>
<edomvd>Hidden Coast Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>High Desert Discovery Scenic Byway</edomv>
<edomvd>High Desert Discovery Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Historic Columbia River Highway Scenic Byway</edomv>
<edomvd>Historic Columbia River Highway Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Ice Age Floods National Geologic Trail</edomv>
<edomvd>Ice Age Floods National Geologic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>International Selkirk Loop Scenic Byway</edomv>
<edomvd>International Selkirk Loop Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Journey Through Time Scenic Byway</edomv>
<edomvd>Journey Through Time Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Lakeview to Steens Back Country Byway</edomv>
<edomvd>Lakeview to Steens Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Lewis and Clark National Historic Trail</edomv>
<edomvd>Lewis and Clark National Historic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Lewis and Clark Trail Highway</edomv>
<edomvd>Lewis and Clark Trail Highway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Lower Crooked River Back Country Byway</edomv>
<edomvd>Lower Crooked River Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Lower Deschutes River Back Country Byway</edomv>
<edomvd>Lower Deschutes River Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Madras Mountain Views Scenic Bikeway</edomv>
<edomvd>Madras Mountain Views Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>McKenzie Pass-Santiam Pass Scenic Byway</edomv>
<edomvd>McKenzie Pass-Santiam Pass Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>McKenzie Pass Scenic Bikeway</edomv>
<edomvd>McKenzie Pass Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Mountain Loop Scenic Byway</edomv>
<edomvd>Mountain Loop Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Mountains to Sound Greenway Scenic Byway</edomv>
<edomvd>Mountains to Sound Greenway Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Mt. Baker National Forest Scenic Byway</edomv>
<edomvd>Mt. Baker National Forest Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Mt. Hood Scenic Byway</edomv>
<edomvd>Mt. Hood Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Myrtle Creek-Canyonville Tour Route</edomv>
<edomvd>Myrtle Creek-Canyonville Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Nestucca River Back Country Byway</edomv>
<edomvd>Nestucca River Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Nez Perce National Historic Trail</edomv>
<edomvd>Nez Perce National Historic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>North Cascades Scenic Highway National Forest Byway</edomv>
<edomvd>North Cascades Scenic Highway National Forest Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>North Pend Oreille Scenic Byway</edomv>
<edomvd>North Pend Oreille Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>North Umpqua - Tioga Section National Recreation Trail</edomv>
<edomvd>North Umpqua - Tioga Section National Recreation Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Okanogan Trails Scenic Byway</edomv>
<edomvd>Okanogan Trails Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Old Growth Ridge National Recreation Trail</edomv>
<edomvd>Old Growth Ridge National Recreation Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Old West Scenic Bikeway</edomv>
<edomvd>Old West Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Oregon Outback Scenic Bikeway</edomv>
<edomvd>Oregon Outback Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Oregon Outback Scenic Byway</edomv>
<edomvd>Oregon Outback Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Oregon Trail National Historic Trail</edomv>
<edomvd>Oregon Trail National Historic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Over the Rivers &amp; Through the Woods Scenic Byway</edomv>
<edomvd>Over the Rivers &amp; Through the Woods Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Pacific Coast Scenic Byway</edomv>
<edomvd>Pacific Coast Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Pacific Crest National Scenic Trail</edomv>
<edomvd>Pacific Crest National Scenic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Pacific Northwest National Scenic Trail</edomv>
<edomvd>Pacific Northwest National Scenic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Painted Hills Scenic Bikeway</edomv>
<edomvd>Painted Hills Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Palouse Scenic Byway</edomv>
<edomvd>Palouse Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Quartzville Back Country Byway</edomv>
<edomvd>Quartzville Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Robert Aufderheide Memorial Drive Scenic Byway</edomv>
<edomvd>Robert Aufderheide Memorial Drive Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Rogue-Umpqua Scenic Byway</edomv>
<edomvd>Rogue-Umpqua Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Rogue - Coquille Scenic Byway</edomv>
<edomvd>Rogue - Coquille Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Rogue River National Recreation Trail</edomv>
<edomvd>Rogue River National Recreation Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Rogue Umpqua / North Umpqua River Scenic Byway</edomv>
<edomvd>Rogue Umpqua / North Umpqua River Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Row River National Recreation Trail</edomv>
<edomvd>Row River National Recreation Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Sherman Pass National Forest Scenic Byway</edomv>
<edomvd>Sherman Pass National Forest Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Silver Falls Tour Route</edomv>
<edomvd>Silver Falls Tour Route</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Sisters to Smith Rock Scenic Bikeway</edomv>
<edomvd>Sisters to Smith Rock Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Snake River-Mormon Basin Back Country Byway</edomv>
<edomvd>Snake River-Mormon Basin Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>South Fork Alsea River Back Country Byway</edomv>
<edomvd>South Fork Alsea River Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>South Fork John Day River Back Country Byway</edomv>
<edomvd>South Fork John Day River Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Spirit Lake Memorial Highway Scenic Byway</edomv>
<edomvd>Spirit Lake Memorial Highway Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>State of Jefferson Scenic Byway</edomv>
<edomvd>State of Jefferson Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Steens Mountain Back Country Byway</edomv>
<edomvd>Steens Mountain Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Sterling Mine Ditch State Scenic Trail</edomv>
<edomvd>Sterling Mine Ditch State Scenic Trail</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Stevens Pass Greenway Scenic Byway</edomv>
<edomvd>Stevens Pass Greenway Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Strait of Juan de Fuca Highway Scenic Byway</edomv>
<edomvd>Strait of Juan de Fuca Highway Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Sutton Mountain Back Country Byway</edomv>
<edomvd>Sutton Mountain Back Country Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Tualatin Valley Scenic Bikeway</edomv>
<edomvd>Tualatin Valley Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Twin Bridges Loop Scenic Bikeway</edomv>
<edomvd>Twin Bridges Loop Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Volcanic Legacy Scenic Byway</edomv>
<edomvd>Volcanic Legacy Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>West Cascades Scenic Byway</edomv>
<edomvd>West Cascades Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Whidbey Island Scenic Byway</edomv>
<edomvd>Whidbey Island Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>White Pass Scenic Byway</edomv>
<edomvd>White Pass Scenic Byway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Wild Rivers Coast Scenic Bikeway</edomv>
<edomvd>Wild Rivers Coast Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Willamette Valley Scenic Bikeway</edomv>
<edomvd>Willamette Valley Scenic Bikeway</edomvd>
</edom>
<edom>
<edomvds>BLM</edomvds>
<edomv>Yakima River Canyon</edomv>
<edomvd>Yakima River Canyon</edomvd>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SURFACE</attrlabl>
<attalias>Surface</attalias>
<attrdef>This field describes the surface material of the road or trail as used to calculate the Current Replacement Value or Annual Maintenance needs in FAMS 6.0. Bituminous – Road surface materials may include full depth asphalt, asphalt overlay, or a bituminous surface treatment.
Concrete – Road surface materials consisting of concrete pavement.
Aggregate – Road surface materials may include pit-run material, local or imported aggregate, crushed sandstone or cinder material.
Natural – Road surface materials consisting of naturally occurring soils; imported roadway surfacing materials are excluded.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NATURALIMPROVED</attrlabl>
<attalias>NaturalImproved</attalias>
<attrdef>This field describes whether a natural surface type is improved or unimproved.
Y (Yes, Natural Improved): A natural on-site surface that has been improved by being graded without drainage features or graded and drained with either an inslope, outslope, or crowned cross section. Drainage features could also include, but are not limited to, side ditches, lead-off ditches, cross drain culverts, and drain dips/water bars. N (No, Natural Unimproved): A natural on-site surface without grading or drainage features. No assumption is made about whether a natural unimproved road or trail was originally constructed or user-created.
NA (Not Applicable): The Surface is not Natural.
U (Unknown): The Surface value ‘Natural’, but it is unknown whether it is improved or unimproved. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Y</edomv>
<edomvd>Yes</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>N</edomv>
<edomvd>No</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NA</edomv>
<edomvd>Not Applicable</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>U</edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CLOSURESTAT</attrlabl>
<attalias>ClosureStat</attalias>
<attrdef>The Closure Status field represents BLM management decisions. BLM interdisciplinary teams make determinations about route closures based on impacts to resources and resource protection. These decisions are based on RMP management direction and are implemented during an EA, an EIS, or a Travel Management Plan. The Closure Status field also represents closure restraints placed on routes through Executive Orders, Legislative Decisions, and court orders. These limitations are outside of the BLM decision space and typically include prohibited vehicular traffic within wilderness or areas of critical environmental concern.
BLM management decisions are confined by realty instruments on a route, e.g., easements, rights-of-way, and reciprocal rights-of-way. Restrictions placed on a route via a realty instrument can be found in the Access Rights and Access Rights Continuity fields. This field does not define legal or physical access. Legal access is determined through a combination of the Access and Access Rights Continuity fields. Physical access is determined through a combination of the Drivability field and closure devices. The Access Rights and Access Rights Continuity fields, which identify the roads for which public access is secured, and the Drivability field, a description of the physical drivability of a route, are independent of the Closure Status field. Refer to the OR/WA BLM Structures dataset to determine the location of route closure devices, e.g., gates. This field does not capture short term closure information. This information is captured with a spatial overlay with the defining closure polygon data. Fire, landslides, and eagle nesting are examples of short-term closure situations.
Open Yearlong (OP)
Currently operated and maintained with no use limitations enforced by a closure device or regulation other than restrictions based on size, weight, or class of registration. Routes may not have secured continuous public access rights (see Access Rights Continuity). Segments may be closed during extreme weather or emergency conditions. Open yearlong segments will be placed in FAMS operating status. This domain value applies to BLM owned routes.
Open Seasonally (SC)
Currently operated and maintained with a seasonal public and commercial use limitation enforced by a closure device. The seasonal use limitation does not apply to administrative use by BLM and/or its permittees. Seasonally open segments will be placed in FAMS operating status. This domain value applies to BLM owned routes.
Restricted Yearlong (RY)
Currently operated and maintained with a yearlong public use limitation. In western Oregon this limitation is enforced by a closure device, typically a gate or sign. In eastern Oregon and Washington this limitation is usually not enforced by a closure device. The restricted yearlong limitation can be the result of a realty instrument or the result of a BLM management decision based on an interdisciplinary team recommendation. The yearlong use limitation does not apply to BLM and/or its permittees. Restricted yearlong segments will be placed in FAMS operating status. This domain value applies to BLM owned routes.
Closed (CL) (Legislated)
Routes closed as a result of an Executive Order, Legislative Decision, or court order. Vehicle use is prohibited except with the approval of an authorized officer. Use a different code if the closure status was determined as a result of a BLM management decision based on an interdisciplinary team recommendation. Closed roads within wilderness should be removed from FAMS and moved to a NonInv dataset unless a BLM management decision changes a closed road to a trail. Closed segments that remain in FAMS will be placed in FAMS storage status. This domain value applies only to BLM owned routes.
Decommission (long-term) (DR)
Not currently operated and maintained based either on resource protection needs or maintenance needs as determined through an interdisciplinary process. Closed, with an earthen barrier or its equivalent, to motorized vehicles for an extended/indefinite period, but will be operated and maintained again in the future. Prior to closure will be left in an erosion-resistant condition by establishing cross drains, eliminating diversion potential at stream channels, and stabilizing or removing fills on unstable areas. Exposed soils will be treated to reduce sediment delivery to streams. This closure status category includes segments that have been or will be closed due to a natural process (abandonment). Decommissioned segments will be placed in FAMS storage status. This domain value applies to BLM owned routes.
Full Decommission (permanent) (FD)
No longer operated and maintained based on an interdisciplinary process establishing no future need for a segment, e.g., a response to resource protection and/or lack of use. Use of the route is unauthorized. Closed, usually with an earthen barrier or its equivalent, to motorized vehicles on a permanent basis; may be subsoiled (or tilled), seeded, mulched, and planted to reestablish vegetation. Cross drains, fills in stream channels, and unstable areas will be removed, if necessary, to restore natural hydrologic flow. Future maintenance will not be required. This closure status category includes segments that have been or will be closed due to a natural process (abandonment) and where hydrologic flow has been naturally restored. Fully decommissioned segments will be placed in FAMS decommission status. This domain value applies to BLM owned routes.
Obliteration (full site restoration/permanent) (OB)
No longer operated and maintained based on an interdisciplinary process establishing no future need for a segment. Closed, usually with an earthen barrier or its equivalent, to motorized vehicles on a permanent basis; all drainage structures will be removed. Fill material used in the original construction will be excavated and placed on the subgrade in an attempt to reestablish the original ground line. Exposed soil will be vegetated with native trees or other native vegetation. Obliterated segments will be placed in FAMS decommission status. Closure by obliteration is rarely used. This domain value applies to BLM owned routes.
Other Closed (OC)
Roads or trails that are closed for public use for at least a portion of the year. These routes may be closed seasonally or year-round. These routes are outside of the scope of BLM management decisions and as such the BLM definitions don’t apply. The route owner should be consulted for the road or trail term of use on these routes. This domain value applies only to non-BLM owned routes.
Data Clean-up (DC)
Applies to segments moved to the FAMS 'decommission' status because they were either invalid, duplicate, or erroneous. These segments are excluded from the nightly FAMS tables. This domain value applies to BLM owned and non-BLM owned routes.
</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>OP</edomv>
<edomvd>Operating</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SC</edomv>
<edomvd>Seasonal Closure</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>RY</edomv>
<edomvd>Restricted Yearlong</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>CL</edomv>
<edomvd>Closed Legislatively</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>STRG</edomv>
<edomvd>Storage</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DCOM</edomv>
<edomvd>Decommission</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OB</edomv>
<edomvd>Obliteration</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OC</edomv>
<edomvd>Other Closed</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NKN</edomv>
<edomvd>Not Known </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>FLTP</attrlabl>
<attalias>FLTP</attalias>
<attrdef>The Federal Lands Transportation Program (FLTP), established under the Moving Ahead for Progress in the 21st Century Act (MAP-21), Public Law 112-141, is administered by the USDOT Federal Highway Administration's (FHWA) Office of Federal Lands Highway in coordination with its core partners: National Park Service, Bureau of Indian Affairs, US Fish and Wildlife Service, Forest Service, Bureau of Land Management, and US Army Corps of Engineers. The FLTP funds projects that improve access within the Federal estate on transportation facilities in the national Federal Lands transportation facility inventory owned and maintained by the Federal government.
A Federal lands transportation facility (FLTF) is defined as a public highway, road, bridge, trail, or transit system that is located on, is adjacent to, or provides access to Federal lands for which title and maintenance responsibility is vested in the Federal Government, and that appears on the national FLTF inventory. The inventory includes transportation facilities owned and maintained by a Federal Land Management Agency (FLMA) that provides access to high-use Federal recreation sites or Federal economic generators as determined by the FLMA.
BLM’s current definitions of “high use Federal recreation sites” and “high use Federal economic generators” are based on the Bureau’s existing planning and management guidance and summarized below:
High Use Recreation Sites
High Use Recreation Sites generally include those areas that have been identified as a Recreation Management Area in a land use plan. NLCS locations, as well as those recreation destinations with significant volume are generally consistent with the High Use designation. Roads that provide primary or sole access to the NLCS locations as well as those to heavily utilized Recreation Management Areas constitute the subset supporting the BLM”s high use recreation sites.
Federal Economic Generators
These are public lands that provide significant revenue generation through energy development, timber, or grazing uses as well as high volume recreation use constitute the BLM’s economic generators. Roads that provide primary or sole access to economic development are the principle means of “leveraging” the economic opportunity within the Nation’s public lands. Federal economic generator roads typically include roads providing access to mineral and renewable energy development, timber and grazing activities, and high-volume recreation locations.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Y</edomv>
<edomvd>Yes</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>N</edomv>
<edomvd>No</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>U</edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>ROADCLASS</attrlabl>
<attalias>RoadClass</attalias>
<attrdef>Functional classification, which is the grouping of roads by the character of service they provide, establishes a systematic approach to road planning, design, and maintenance. Stratifying the Bureau’s road network by functional classes provides a rational and cost-effective basis for (1) the selection and application of geometric design criteria and standards (e.g., maximum road grades, roadway width, and design speed); and (2) the assignment of appropriate road maintenance intensity levels (i.e., from basic custodial care to annual scheduled and preventative maintenance programs).
Most rural highway travel involves movement through networks of roads that can be described using a functional system based on traffic volume, vehicle speed, trip distance, travel mobility, and property access. The system of functional classifications in descending order consists of arterial (for main traffic movement), collector, local (for land access) and resource roads. The functional classification system helps determine how travel movement can be channelized through the network in a logical and efficient manner. Each element of the functional system can serve as a collecting facility for the next highest element.
This functional classification system is more fully described in the Federal Highway Administration (FHWA) publication Highway Functional Classification: Concepts, Criteria, and Procedures (Revised 1989). The Bureau has added resource roads to the system identified in this FHWA plan to better account for the unique function of many Bureau roads in providing very small-scale public land access. These resource roads typically carry extremely low traffic volume and accommodate only one or two types of resource management (see BLM manual 9113).
Arterial Roads (for non-inventoried roads only) – The rural arterial system consists of a network of roads with the following service characteristics:
a) Linkage of cities, larger towns, and other traffic generators (such as major resort areas) capable of attracting travel over long distances.
b) Integrated interstate and inter-county service.
c) Internal spacing consistent with population density, so that all developed areas of the State are within a reasonable distance of arterial highways.
d) Trip lengths and travel densities greater than those predominantly served by rural collector, local, and resource systems.
e) Design standards provide for high travel speeds and minimum interference to through movement.
As Bureau roads are predominantly low volume and are generally extensions of or connectors to State Highway and rural County Road systems, an arterial classification does not apply normally to Bureau roads (see BLM manual 9113). In fact, in western Oregon BLM manages no arterial roads.
Collector Roads – The rural collector system generally serves travel primarily of intra-county rather than statewide distances and constitutes those roads on which predominant travel distance and speed are less than on arterial routes. These roads serve larger towns; important agricultural areas (e.g. forest management areas); county, state, and federal parks; and other traffic generators of equivalent intra-county importance. These roads link to the arterial system and are spaced at intervals consistent with population density to accommodate traffic from local roads and bring all developed areas within reasonable distances of collector roads.
Designation of Bureau collector roads is based on the following criteria:
a) Roads that normally provide access to large blocks of public land and connect with state and county road systems. b) Roads that accommodate multiple uses and generally receive the highest volume of traffic of all roads in the Bureau road system. c) Roads designed to the Bureau’s highest standards may be double lane. d) Roads designated as scenic routes or Back Country Byways (Type I, see BLM Handbook H-8357-1).
e) Roads that provide access to recreational areas containing a number of developed sites and facilities.
f) Roads that provide the most extensive linkage to the local road system.
g) Only roads mapped by ODOT as collectors in accordance with their “Guidelines for Updating Federal-Aid Urban Boundary and Functional Classification” document dated July 2003 will be mapped by BLM as collectors. ODOT functional classification maps can be found at the following website: http://egov.oregon.gov/ODOT/TD/TDATA/gis/CountyMaps.shtml
Local Roads – The rural local system primarily provides access to lands adjacent to the collector network and serves travel over relatively short distances. Designation of Bureau local roads is based on the following criteria:
a) Roads that normally serve smaller areas than collectors and connect with collectors or state and county road systems.
b) Roads that accommodate fewer uses and receive lower traffic volumes than collectors.
c) Roads designed typically to a single lane width with steeper grades, sharper horizontal curves, and lower design speeds than collector roads due to mountainous terrain.
d) Roads that provide access to small recreational sites, trailheads, special sites and facilities (i.e., communication sites).
e) Roads that provide the most extensive linkage to the resource road system and are spaced at appropriate intervals to collect traffic from resource roads and provide for public land areas to be within a reasonable distance of a local road. This eliminates multiple parallel roads.
f) All local roads tie together arterial, collector, and/or other local roads; no dead-end roads.
a. Exception: Dead-end local roads must access, (1) developed recreation/administrative sites, BLM quarries, or fire program improvements (e.g., waterholes) or (2) a minimum of 5 sections (3,200 acres) regardless of the number of tributary spurs or the length of the road.
g) Not every road tributary to a collector road needs to be a local road.
h) Not every linking road needs to be a local road.
i) Typically, the local network mileage will be 2-4 times the collector network mileage. This is a reasonableness check, not a hard and fast rule, based on AASHTO classification study data collected in many states which show there is considerable consistency in the relative extents of the functional class systems.
Resource Roads - The Bureau resource road system provides access to the remaining portion of the public lands not accessed by collector or local roads. Designation of Bureau resource roads is based on the following criteria:
a) Roads that provide point access to public lands and connect with local or collector roads.
b) Roads are typically for only one or two types of resource management and carry very low traffic volumes. Typically they are low standard, single lane, natural or aggregate surfaced logging spurs.
c) Location and design of these roads are governed by safety standards, environmental compatibility and minimal construction and maintenance costs, and with minimal consideration for user cost, comfort, or travel time.
d) Roads have no established or designated recreational use (e.g., comfort station, trailhead, wayside) to attract the public.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Arterial</edomv>
<edomvd>Arterial</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Collector</edomv>
<edomvd>Collector</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Local</edomv>
<edomvd>Local</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Resource</edomv>
<edomvd>Resource</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Not Known</edomv>
<edomvd>Not Known</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CARTOROAD</attrlabl>
<attalias>CartoRoad</attalias>
<attrdef>This field allows for query and display or non-display according to map scale or locally important issues. The attribute has a cartographic rather than analytical purpose.
Major Road
Main thoroughfares; generally these roads are an interstate, federal, state, or county highway, but this is not a pre-requisite. These roads are generally displayed at all scales.
Intermediate Road
Roads that are considered thoroughfares; these are not considered major thoroughfares, however, because of irregular maintenance, seasonal availability, or the length of the thoroughfare. These roads are generally displayed at the scale of our resource area or recreation series maps. Minor Road
Roads that are not considered thoroughfares and are usually single destination or single purpose resource management roads. These roads should only be displayed at large scales.
Do Not Display or Distribute
These roads should not be displayed on any map. These roads should be removed from the dataset before it’s distributed to the public. Examples include closed roads, obscure roads, roads under injunction, or roads with a locally sensitive reason for exclusion.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Major</edomv>
<edomvd>Major road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Intermediate</edomv>
<edomvd>Intermediate road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Minor</edomv>
<edomvd>Minor road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Hide</edomv>
<edomvd>Hide - Do not display or distribute</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown </edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>AVGWIDTH</attrlabl>
<attalias>AvgWidth</attalias>
<attrdef>This field is a record of the average width of a route, measured in feet.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SUBWIDTH</attrlabl>
<attalias>SubWidth</attalias>
<attrdef>This field is a record of the historical subgrade width of a route, measured in feet.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>NUMLANES</attrlabl>
<attalias>NumLanes</attalias>
<attrdef>A record of the number of lanes of a road.
For inventoried roads (populated via FAMS) this field is calculated from the average width field. This field is not the same as the FAMS NumLanes field. The FAMS NumLanes field uses a threshold of 16’ and is used in cost replacement value (CRV) and annual maintenance exercises.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>SL</edomv>
<edomvd>Single Lane Road (&lt;20' average width) - Two way</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DL</edomv>
<edomvd>Double Lane Road (&gt;= 20' average width) - Double lane is a function of width - Two way - Two way</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ML</edomv>
<edomvd>MultiLane Road - Two or more defined lanes - One way or two way traffic - Two or more defined lanes</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MD</edomv>
<edomvd>MultiLane, Divided Road - Physical barrier or median separating one or more lanes in each direction. - Physical barrier or median separating one or more lanes in each direction. If median is greater than 40 feet, road will be represented as two lines, each coded as ML.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NKN</edomv>
<edomvd>Not Known </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>RWOHALFWIDTH</attrlabl>
<attalias>RWOHalfWidth</attalias>
<attrdef>The half width (in meters) of the width used for the District Designated Reserve (DDR-Roads). This field only applies to districts within the NW and SW Oregon RMPs. The default value is 6.858 (22.5 feet), which will result in a 13.716-meter (45-foot) DDR-Road buffer in the land use allocation (LUA) dataset. Districts can update the DDR-Roads from the default width of 13.716-meter (45-feet) based on empirical field information on the actual on-the-ground width of the area maintained for the road. The DDR-Roads should encompass the entirety of the area that will be managed to maintain the road, typically encompassing the subgrade, ditch line, and roadside brushing area, not solely the road surface.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>DRIVABILITY</attrlabl>
<attalias>Drivability</attalias>
<attrdef>This field describes the physical drivability of a road in order to aid in safe travel by the public across the BLM road network. Unlike the ‘Closure Status’ field this field is independent of management decisions. The field ‘Drivability_ObsDate’ provides information on the currency of the information stored in this field.
This field is not intended to replace visual and sound driving principles. Users should be aware of their skills and limitations as well as those of the vehicle they are operating. In instances where the vehicle type use varies by season or other condition the most restrictive domain value should be used.
Passable – 2wd Low Clearance Passenger Vehicle
Roads passable by a 2wd vehicle designed to carry passengers on improved roads.
Passable – Moderate Terrain Vehicle (eastern Oregon and Washington): Roads that are not passable by all classes of 2wd vehicles but do not require a 4wd high clearance vehicle. Roads in this category typically have a rough or uneven surface and/or have had a narrowing in the road width. High clearance 2wd vehicles such as a standard pickup truck and 4wd sport utility vehicles with low gearing otherwise designed for rough roads are included in this category. Roads in western Oregon may exhibit these characteristics; however, the relatively short duration before a deteriorating western Oregon road becomes impassable or passable only to high clearance vehicles makes data maintenance at this gradation impractical.
Passable – 4wd High Clearance Vehicle: Roads passable only by high clearance 4wd vehicles. Impassable
Roads impassable to all vehicle types as a result of road deterioration or vegetation overgrowth; project-level road maintenance is required to make these roads passable. Road deterioration or vegetation overgrowth may be a result of neglect, irregular maintenance, or management decisions. Roads with a ‘Closure Status’ of decommissioned (DR), full decommission (FD) or obliterated (OB) indicate that the roads are impassable as a result of a management decision; these roads are impassable by definition. Roads with a ‘Closure Status’ of closed (CL) offer no indication of the drivability of the road.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>2wdLow</edomv>
<edomvd>Passable - 2wd Low Clearance Passenger Vehicle</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Moderate</edomv>
<edomvd>Passable - Moderate Terrain Vehicle (eastern Oregon and Washington)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>4wdHigh</edomv>
<edomvd>Passable - 4wd High Clearance Vehicle</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Impassable</edomv>
<edomvd>Impassable - Impassable</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown </edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>DRIVABILITYOBSDATE</attrlabl>
<attalias>DrivabilityObsDate</attalias>
<attrdef>This field captures the date the drivability of the road was observed. The date should be populated: YYYYMMDD.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PLANCAT</attrlabl>
<attalias>PlanCat</attalias>
<attrdef>The Planning Category field represents BLM management decisions. BLM interdisciplinary teams make recommendations about route planning categories based on intended identified use of the linear asset. These implementation-level NEPA-supported decisions are based on Resource Management Plan (RMP) management direction and are implemented following completion of an EA, an EIS, or a Travel and Transportation Management Plan.
The intent of this field is to identify the routes where the BLM has the authority to make a designation/decision about the route and the planning category of a route. The BLM has the authority to make designation/decisions on routes that the BLM owns and controls as well as private industry routes within a reciprocal right-of-way (RROW) that the BLM controls. Route ownership and control are defined in the Ownership field.
Routes formally designated as a road, primitive road, or trail that are the subject and result of a Travel Management Plan (TMP) make up the BLM Transportation System. Information about these routes is input and maintained in FAMS. Routes can be entered into FAMS as a road, primitive road, or trail without a TMP as long as the information in FAMS is updated as necessary after a TMP is completed.
Changes to the BLM’s transportation system, as recorded in FAMS, may occur as part of the formal evaluation and designation process through one of four events:
a) Record of Decision (ROD) – for a Resource Management / Environmental Impact Statement (RMP/EIS) or an amendment of an RMP/EIS.
b) Decision Records for an Activity Plan, Plan Amendment/Environment Assessment (EA).
c) Federal Register Notice Action (under authority of 43 CFR 8341.2, 8364.1, 8365.3-6, or 9268.3) that has a follow-up land-use planning action and associated NEPA action.
d) Management decision of appropriate routes in an area that has been designated open to off-highway vehicle use.
Routes owned by private industry or another agency can be entered into FAMS as a road, primitive road, or trail when the BLM has an interest in these routes as a result of a maintenance agreement or a reciprocal right-of-way agreement. These routes are part of the BLM Transportation System.
BLM Road: A route managed for use by low-clearance vehicles having four or more wheels and maintained for regular and continuous use. The BLM owns and controls the route. Roads are part of BLM’s Transportation System; FAMS is the system of record for these routes. BLM Primitive Road: A route managed for use by four-wheel drive or high-clearance vehicles. Primitive roads do not normally meet any BLM road design standards. The BLM owns and controls the route. Primitive Roads are part of BLM’s Transportation System; FAMS is the system of record for these routes.
BLM Trails: A route managed for human-powered, stock, or off-highway vehicle forms of transportation or for historical or heritage values. Trails are not generally managed for use by four-wheel drive or high-clearance vehicles. The BLM owns and controls the route. Trails are part of BLM’s Transportation System; FAMS is the system of record for these routes.
BLM WSA Ways: Routes within a Wilderness Study Area (WSA) that are not excluded from the WSA, as in the case of a “cherry-stem” road. They were officially recognized and mapped (as “Ways”) during the FLPMA Sec. 603 Wilderness Inventories (Sec. 603 WSAs) and any Sec. 202 inventories meeting the criteria of the Utah Settlement Agreement (Sec. 202 WSAs). The term “way” derives from a “roadless” definition in the Congressional Record adopted in BLM’s 1978 Wilderness Inventory Handbook, which concludes that “a way maintained solely by the passage of vehicles does not constitute a road.” Based on the complete “roadless” definition, BLM WSA Ways are defined as “A trace maintained solely by the passage of vehicles which has not been improved and/or maintained by mechanical means to insure relatively regular and continuous use.” The BLM owns and controls the route. WSAs are NOT part of BLM’s Transportation System; GTRN is the system of record for these routes. BLM Primitive Route: Routes within (not forming a boundary and not excluded in a “cherry-stem”) a Wilderness Inventory Unit found to possess Wilderness Characteristics. They were found to not be “improved or maintained by mechanical means to insure relatively regular and continuous use.” They are kept passable solely by the passage of vehicles and no hand or power tools have been applied. There is a Land Use Plan decision to protect the Wilderness Characteristics of this Wilderness Characteristics Unit. The ultimate disposition of these routes will depend on the specific protections applied to the area via the RMP and any step-down TMP decisions. The BLM owns and controls the route. Primitive Routes are NOT part of BLM’s Transportation System; GTRN is the system of record for these routes.
BLM Interim Primitive Route: Routes within (not forming a boundary and not excluded in a “cherry-stem”) a Wilderness Inventory Unit found to possess Wilderness Characteristics. They were found to not be “improved or maintained by mechanical means to insure relatively regular and continuous use”. They are kept passable solely by the passage of vehicles and no hand or power tools have been applied. There is not a Land Use Plan decision to protect the Wilderness Characteristics of this Wilderness Characteristics Unit. The ultimate disposition of these routes will depend on the specific management allocations applied to the area via the RMP and any step-down TTMP decisions. Unless otherwise prohibited, these primitive routes may be managed at BLM discretion (including improvement by mechanical means) with appropriate NEPA compliance, including analysis of impacts to wilderness characteristics. A change in route status should be reflected in the Wilderness Inventory Report and may warrant reevaluation of the Wilderness Inventory Unit. The BLM owns and controls the route. Interim Primitive Routes are may or may not currently be part of BLM’s Transportation System; GTRN is the system of record for these routes. Following any Land Use Plan decision to protect the Wilderness Characteristics of the Wilderness Inventory Unit, these routes will need to be re-classified as BLM Primitive Routes.
BLM Permanently Removed Route: Routes identified to be permanently removed during a BLM Travel and Transportation Management Plan (TTMP); a decision has been made during the planning process not to retain these routes. These routes have a closure rehab/decommissioning plan. BLM Permanently Removed Route is synonymous with Linear Disturbance. Permanently Removed Routes may include engineered (planned) as well as unplanned routes. Routes within a legislative designation, e.g., wilderness designation, that are not designated as a BLM Trail are included in this category. On-the-ground evidence of these routes may exist for some time after the decision is made to permanently remove the routes. The routes remain in the GIS system in order to provide spatial reference of decisions. The BLM owns and controls the route. Permanently Removed Routes are NOT part of BLM’s Transportation System as they are no longer routes; GTRN is the system of record for these routes.
BLM Temporary Route: A short-term overland road, primitive road, or trail that is authorized or acquired for the development, construction, or staging of a project or event that has a finite lifespan. Temporary routes are a subset of BLM Permanently Removed Routes and do not need to be moved to the BLM Permanently Removed Route category at the close of the project. Roads built for a timber sale in western Oregon are an example of a temporary route and have a maximum life-span of three years. Routes identified in a mining claim Plan of Operation are another example of a temporary route and have a life-span that may extend to a couple of decades. The project is responsible for remediation at the close of the project; temporary routes will never become a designated route. The BLM owns and controls the route. Temporary Routes are NOT part of BLM’s Transportation System; GTRN is the system of record for these routes. Temporary Routes tracked for reporting in association with the BLM Forest Management Programmatic for Western Oregon (BLM Forest Management Programmatic) Biological Opinion date 03/09/2018 issued by National Marine Fisheries Service covering forest management activities implemented by the two 2016 western Oregon RMPs will need to have construction year, average width, ownership designation and surface type populated with valid values. Total miles of Temporary Routes will use GIS Miles, which is an auto-calculated field. BLM No TTMP Decision: A route that is within the BLM decision space. That is, the BLM owns and controls the route and/or BLM controls a private road within a reciprocal right-of-way (RROW) on BLM land. No BLM Travel and Transportation Management planning decision has been made on the route. There is no route-level record of decision (ROD). PVT RROW Road on BLM Land: A route managed for use by low-clearance vehicles having four or more wheels, and maintained for regular and continuous use. The road is on BLM land, i.e., the BLM controls the road, but the road is owned by a private timber company. The road is encumbered by a reciprocal right-of-way (RROW). The BLM has the authority to make an OHV Route Designation on these routes, including decisions that limit the OHV vehicle type or season. Privately owned RROW roads may or may not be part of BLM’s Transportation System; FAMS or GTRN are the system of record for these routes.
Non-BLM Route: BLM does NOT have the route designation authority, i.e., BLM does not own or control the route. Non-BLM Transportation Features include State and US Highways, USFS and other agency roads, county roads, and private roads on BLM land not encumbered by a RROW agreement, all of which may incidentally cross BLM lands.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>BLM Road</edomv>
<edomvd>BLM Road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Primitive Road</edomv>
<edomvd>BLM Primitive Road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Trail</edomv>
<edomvd>BLM Trail</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM WSA Way</edomv>
<edomvd>BLM WSA Way</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Primitive Route</edomv>
<edomvd>BLM Primitive Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Interim Primitive Route</edomv>
<edomvd>BLM Interim Primitive Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Permanently Removed Route</edomv>
<edomvd>BLM Permanently Removed Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Temporary Route</edomv>
<edomvd>BLM Temporary Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM No TTMP Decision</edomv>
<edomvd>BLM No TTMP Decision</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Private RROW Road on BLM Land</edomv>
<edomvd>Private RROW Road on BLM Land</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Non-BLM Route</edomv>
<edomvd>Non-BLM Route</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown</edomv>
<edomvd>Unknown</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>PLANID</attrlabl>
<attalias>PlanID</attalias>
<attrdef>The official name of the activity or land use plan governing the management of the route. Land use plan names should only be used if the land use plan addresses route maintenance or a specific action taken on a route. In most instances, you should only select activity plan values from the available list. Plan names are filled in when the plan is final. The PLANID domain is populated from BLM’s ePlanning database.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Project Plan Name Text. The Plan Name Text refers to the official name for the plan or project. This is a lengthy list of domain values. The domain is available at the following web location: https://www.blm.gov/site-page/oregon-data-management</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>OHVDSGTN</attrlabl>
<attalias>OHVDsgtn</attalias>
<attrdef>The Off-Highway Vehicle (OHV) Route Designation field represents BLM management decisions. BLM interdisciplinary teams make recommendations about route OHV designation based on impacts to resources and resource protection as well as to balance the recreational needs of the public and reduce conflict between different user groups. These implementation-level NEPA-supported decisions are based on Resource Management Plan (RMP) management direction and are implemented following completion of an EA, an EIS, or a Travel and Transportation Management Plan.
This field represents the OHV route designation on routes as described in terms of Code of Federal Regulation 43 CFR Part 8342 as Open, Limited, or Closed. An off-highway, or off-road, vehicle is defined as: (a) Any motorized vehicle capable of, or designed for, travel on or immediately over land, water, or other natural terrain, excluding: (1) Any nonamphibious registered motorboat; (2) Any military, fire, emergency, or law enforcement vehicle while being used for emergency purposes; (3) Any vehicle whose use is expressly authorized by the authorized officer, or otherwise officially approved; (4) Vehicles in official use; and (5) Any combat or combat support vehicle when used in times of national defense emergencies. BLM IB 2015-060 classifies e-bikes as motorized vehicles; they are considered off-highway vehicles when being operated off a highway. Mechanized vehicles, e.g., non-motorized bicycles, are not considered off-highway vehicles. The OHV Route Designation field does not apply to mechanized use on a route. See the Trail Use field for mechanized route use.
The BLM has the authority to make OHV route designations on routes that the BLM owns and controls as well as private industry routes within a reciprocal right-of-way (RROW) that the BLM controls. Route ownership and control are defined in the Ownership field.
OHV route designations are related to, but differ, from off-highway vehicle area designations. OHV area designations cover the extent of all BLM surface jurisdiction lands and are determined through a Land Use Planning process (Resource Management Plan (RMP)). OHV route designations apply to individual routes and are determined through the Travel Management Planning process (TMP). A Travel Management Plan can occur concurrently or subsequently with a Land Use Plan (LUP).
The OHV area designation sets the over-arching constraints of the routes within an OHV area designation.
•	If an OHV area designation is open, then all routes within the area will have an open OHV route designation.
•	If an OHV area designation is closed, then all routes within the area will have a closed OHV route designation.
•	If an OHV area is limited, then routes within the area can have an open, closed, or limited route designation.
This field is related to the Planning Category, Planning Identifier, Off-highway Vehicle Limited Vehicle Type, Off-highway Vehicle Limited Season, Road Use, Trail Use, Closure Status, and Trail Closure Status fields (see the Off-Highway Vehicle (OHV) Route Designation Compatibility Matrix).
Open Route: All off-highway vehicle use on the route is permitted at all times, by all OHV vehicle types, subject to operating regulations and vehicle standards.
Limited Route: Off-highway vehicle use on the route is restricted by season and/or OHV vehicle type.
Closed Route: Off-highway vehicle use on the route is prohibited at all times, by all OHV vehicle types.
Non-TTMP Route: Off-highway vehicle use on the route is not applicable because the route is permanently closed, e.g., full decommission (FD), obliterated (OB), closed permanently.
Non-BLM Route: BLM does NOT have the route designation authority, i.e., BLM does not own or control the route. Non-BLM Transportation Features include State and US Highways, USFS and other agency roads, county roads, and private roads on BLM land not encumbered by a RROW agreement, all of which may incidentally cross BLM lands.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Open Route</edomv>
<edomvd>Open Route – all off-highway vehicle use on the route is permitted at all times, by all OHV vehicle types</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Limited Route</edomv>
<edomvd>Limited Route – off-highway vehicle use on the route is restricted by season and/or OHV vehicle type</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Closed Route</edomv>
<edomvd>Closed Route – off-highway vehicle use on the route is prohibited at all times, by all OHV vehicle types</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Non-TTMP Route</edomv>
<edomvd>Non-TTMP Route – off-highway vehicle use on the route is not applicable because the route is permanently closed</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Non-BLM Route</edomv>
<edomvd>Non-BLM Route – BLM does NOT have the route designation authority</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown </edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>OHVLMTVEHICLE</attrlabl>
<attalias>OHVLmtVehicle</attalias>
<attrdef>The Off-Highway Vehicle Limited Vehicle Type Designation field represents BLM management decisions. BLM interdisciplinary teams make recommendations about off-highway vehicle types based on impacts to resources and resource protection as well as to balance the recreational needs of the public and reduce conflict between different user groups. These implementation-level NEPA-supported decisions are based on Resource Management Plan (RMP) management direction and are implemented following completion of an EA, an EIS, or a Travel and Transportation Management Plan.
This field represents limitations to off-highway vehicle (OHV) by type on OHV designated routes. A designated OHV route may have additional limitations. This field does not apply if the OHV Route Designation is open or closed; if the OHV Route Designation is open or closed then populate this field with NA Rte.
An off-highway, or off-road, vehicle is defined as: (a) Any motorized vehicle capable of, or designed for, travel on or immediately over land, water, or other natural terrain, excluding: (1) Any nonamphibious registered motorboat; (2) Any military, fire, emergency, or law enforcement vehicle while being used for emergency purposes; (3) Any vehicle whose use is expressly authorized by the authorized officer, or otherwise officially approved; (4) Vehicles in official use; and (5) Any combat or combat support vehicle when used in times of national defense emergencies. OHV route designations are related to, but differ, from off-highway vehicle area designations. OHV area designations cover the extent of all BLM surface jurisdiction lands and are determined through a Land Use Planning process (Resource Management Plan (RMP)). OHV route designations apply to individual routes and are determined through the Travel Management Planning process (TMP). A Travel Management Plan can occur concurrently or subsequently with a Land Use Plan (LUP).
The OHV area designation sets the over-arching constraints of the routes within an OHV area designation.
•	If an OHV area is limited, then routes within the area can have an open, closed, or limted route designation.
•	If an OHV route designation is limited, then the OHV area designation must be limited.
This field is related to the Planning Category, Planning Identifier, Off-highway Vehicle Route Designation, Off-highway Vehicle Limited Vehicle Type, Road Use, Trail Use, Closure Status, and Trail Closure Status fields. For a view of the inter-relatedness of these fields, refer to the OHV Route Designation.
In the trails feature class, the off-highway vehicle limited vehicle type must have the same value as the trail use field, unless the trail is coincident with the roads feature class. The ability to limit OHV vehicle types on roads and primitive roads, which are all managed for street legal vehicles, necessitates having both fields.
UTV (Class IV, OR – 801.194): Any motorized vehicle that:
•	Travels on four or more pneumatic tires that are six inches or more in width and that are designed for use on wheels with a rim diameter of 14 inches or less;
•	Is designed for or capable of cross-country travel on or immediately over land, water, sand, snow, ice, marsh, swampland, or other natural terrain;
•	Has non-straddling seating;
•	Has a steering wheel for steering control;
•	Has a dry weight of 1,800 pounds or less; and
•	Is 65 inches wide or less at its widest point.
ATV (Class I, OR – 801.190): A motorized, off-highway recreational vehicle 50 inches or less in width with a dry weight of 1,200 pounds or less that travels on three or more pneumatic tires that are six inches or more in width and that are designed for use on wheels with a rim diameter of 14 inches or less, uses handlebars for steering, has a seat designed to be straddled for the operator, and is designed for or capable of cross-country travel on or immediately over land, water, sand, snow, ice, marsh, swampland or, other natural terrain. Motorcycle (Class III, OR – 801.194): A motorcycle that travels on two tires and that is actually being operated off highway. BLM IB 2015-060 classifies e-bikes as motorized vehicles as defined at 43 CFR 8340.5.
NA Route: The OHV Route Designation is open route, closed route, or non-
TTMP route or the OHV Route Designation is limited, but does not have a vehicle type restriction.
Non-BLM Route: BLM does NOT have the route designation authority, i.e., BLM does not own or control the route. Non-BLM Transportation Features include State and US Highways, USFS and other agency roads, county roads, and private roads on BLM land not encumbered by a RROW agreement, all of which may incidentally cross BLM lands. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>UTV</edomv>
<edomvd>UTV - Class IV, I, and III off-highway vehicle use only</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ATV</edomv>
<edomvd>ATV - Class I and III off-highway vehicle use only</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Motorcycle</edomv>
<edomvd>Motorcycle - Class III off-highway vehicle use only</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NA Route</edomv>
<edomvd>NA Route – the OHV Route Designation is open route, closed route, or non-TTMP route or the OHV Route Designation is limited, but does not have a vehicle type restriction</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Non-BLM Route</edomv>
<edomvd>Non-BLM Route – BLM does not have the route designation authority</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown </edomv>
<edomvd>Unknown </edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>OHVLMTSEASON</attrlabl>
<attalias>OHVLmtSeason</attalias>
<attrdef>The Off-Highway Vehicle (OHV) Limited Season Designation field represents BLM management decisions. BLM interdisciplinary teams make recommendations about route OHV designation based on impacts to resources and resource protection as well as to balance the recreational needs of the public and reduce conflict between different user groups. These implementation-level NEPA-supported decisions are based on Resource Management Plan (RMP) management direction and are implemented following completion of an EA, an EIS, or a Travel and Transportation Management Plan.
This field represents limitations of off-highway vehicle (OHV) by season on OHV designated routes. A designated OHV route may have additional limitations. This field does not apply if the OHV Route Designation is open or closed; if the OHV Route Designation is open or closed then leave this field blank.
OHV seasonal limitations are typically related to wildlife habitat or resource protection. Actual seasonal end dates are based on local direction and may deviate from the end date listed in the data. The seven primary groups and general date ranges of protection are:
•	Bat (White-Nose Syndrome) (Anytime)
•	Deer (November through March)
•	Elk (December through March)
•	Raptor (March through July)
•	Sage Grouse (May through June)
•	Resource Protection (Generally Wet Season)
•	Fire (Anytime)
Seasonal limitations should be entered Wildlife Group MM/DD – MM/DD. A semi-colon should be used to separate multiple date ranges, e.g., Raptor 03/01 – 07/31; Sage Grouse 05/01 – 06/30. Additional time of day restrictions can be added after the date, e.g., Raptor 03/01 – 07/31; Sage Grouse 05/01 – 06/30, 2 hours before sunrise to 1 hour after sunrise.
An off-highway, or off-road, vehicle is defined as: (a) Any motorized vehicle capable of, or designed for, travel on or immediately over land, water, or other natural terrain, excluding: (1) Any nonamphibious registered motorboat; (2) Any military, fire, emergency, or law enforcement vehicle while being used for emergency purposes; (3) Any vehicle whose use is expressly authorized by the authorized officer, or otherwise officially approved; (4) Vehicles in official use; and (5) Any combat or combat support vehicle when used in times of national defense emergencies. OHV route designations are related to, but differ, from off-highway vehicle area designations. OHV area designations cover the extent of all BLM surface jurisdiction lands and are determined through a Land Use Planning process (Resource Management Plan (RMP)). OHV route designations apply to individual routes and are determined through the Travel Management Planning process (TMP). A Travel Management Plan can occur concurrently or subsequently with a Land Use Plan (LUP).
The OHV area designation sets the over-arching constraints of the routes within an OHV area designation.
•	If an OHV area is limited, then routes within the area can have an open, closed, or limted route designation.
•	If an OHV route designation is limited, then the OHV area designation must be limited.
This field is related to the Planning Category, Planning Identifier, Off-highway Vehicle Route Designation, Off-highway Vehicle Limited Vehicle Type, Road Use, Trail Use, Closure Status, and Trail Closure Status fields. For a view of the inter-relatedness of these fields, refer to the OHV Route Designation.
In the trails feature class, the off-highway vehicle limited season must not be in conflict with the trail closure status field, unless the trail is coincident with the roads feature class. The ability to limit when a route is open or seasonally closed by street legal vehicles, off-highway vehicles, and non-motorized modes of transportation necessitates having fields with similar concepts.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">100</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>INVENTORYYEAR</attrlabl>
<attalias>InventoryYear</attalias>
<attrdef>The intent of this field is to capture the calendar year a contractor or BLM staff conducted a route inventory according to Technical Reference 9113-1 (Planning and Conducting Route Inventories for Travel and Transportation Management). This field is related to the INVENTORY_CREW field; if one field is populated then both fields should be populated.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>INVENTORYCREW</attrlabl>
<attalias>InventoryCrew</attalias>
<attrdef>The intent of this field is to capture the contractor or BLM staff that conducted a route inventory. This field is related to the INVENTORY_YEAR field; if one field is populated then both fields should be populated. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>BLM Staff</edomv>
<edomvd>BLM Staff, including annuit and in-house contract staff</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM Volunteer</edomv>
<edomvd>BLM Volunteer</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Partner Group</edomv>
<edomvd>Partner Group</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Logan Simpson</edomv>
<edomvd>Logan Simpson</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Advanced Resource Solutions, Inc.</edomv>
<edomvd>Advanced Resource Solutions, Inc.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>North State Resources, Inc.</edomv>
<edomvd>North State Resources, Inc.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown</edomv>
<edomvd>Unknown</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>LINLOCID</attrlabl>
<attalias>LinLocID</attalias>
<attrdef>FAMS key value assigned to all route segments that make up a BLM inventoried route.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>SEGASSETID</attrlabl>
<attalias>SegAssetID</attalias>
<attrdef>The linking field for joining the FAMS table to a BLM inventoried route/trail. This field links to the BLM inventoried route/trail ‘FAMSKEY’ on each route segment.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROUTEID</attrlabl>
<attalias>RouteID</attalias>
<attrdef>Provides the full BLM route and segment number. This field can be used for cartographic labeling or as a relate key to other datasets or tables. In western Oregon RouteID is: RouteNum (rt_num) + RouteSeg (o_csegs). In eastern Oregon RouteID is: RouteNum (rt_num) + RouteSpur (rte_spur) + BeginMilePost (begml). RouteSeg (o_csegs) and RouteSpur (rte_spur) do not exist in the trails feature class and therefore are not included in the Route_ID equation for trails.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">110</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROUTENUM</attrlabl>
<attalias>RouteNum</attalias>
<attrdef>The route number provides the identifier for each BLM road and trail. Other agency route numbers should be placed in primary route name (RT_NM1) field.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ROUTESPUR</attrlabl>
<attalias>RouteSpur</attalias>
<attrdef>The value given to a spur.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>PASER</attrlabl>
<attalias>PASER</attalias>
<attrdef>PASER was originally developed by the University of Wisconsin-Madison Transportation Information Center for paved roads but was modified by the BLM National Roads Team for use with all of our surface types. The BLM PASER scale is 1-5 for bituminous and aggregate surfaces and 1-4 for natural surfaces. PASER uses visual inspection to evaluate pavement surface conditions. BLM PASER uses mostly a visual inspection to evaluate pavement surface conditions, but the aggregate surface depth is physically potholed to collect accurate aggregate depth information. When assessed correctly, PASER ratings provide a basis for comparing the quality of roadway segments. PASER ratings cannot be disaggregated into measurements of specific distress types. The advantage to this method is that roads may be assessed quickly, possibly even by "windshield survey." A primary disadvantage is that because PASER ratings cannot be disaggregated into component distress data, the metric cannot be used in mechanistic-empirical transportation asset management programs.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>5</edomv>
<edomvd>Excellent (New)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>Good</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Fair</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Poor</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>1</edomv>
<edomvd>Failed (Impassable)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NE</edomv>
<edomvd>Not Evaluated</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UE</edomv>
<edomvd>Unable to Evaluate</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>FCI_CONDCODE</attrlabl>
<attalias>FCI_CondCode</attalias>
<attrdef>This field depicts the overall condition of a trail as measured by the Facility Condition Index (FCI) metric. FCI is defined as the ratio of deferred maintenance/current replacement value. FCI is a critically important ranking factor for trail projects submitted for inclusion in BLM’s 5-year deferred maintenance/capital improvement program. FCI is computed for FAMS inventoried trails only.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>GOOD</edomv>
<edomvd>Good - FCI = 0.00 to 0.05</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>FAIR</edomv>
<edomvd>Fair - FCI = 0.06 to 0.15</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>POOR</edomv>
<edomvd>Poor - FCI &gt; 0.15</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CONSTRYEAR</attrlabl>
<attalias>ConstrYear</attalias>
<attrdef>This field is a record of the construction year (FY) of the route.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>MAINTYR</attrlabl>
<attalias>MaintYr</attalias>
<attrdef>The field indicates the fiscal year in which the maintenance of the route segment actually occurs. The correct format is YYYY.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>MAINTINT</attrlabl>
<attalias>MaintInt</attalias>
<attrdef>Maintenance is divided into four intensity levels in accordance with the BLM Manual 9113. The intensity levels provide a progressive system of maintenance with even the lowest intensity level ensuring resource protection by controlling surface erosion and sedimentation. Maintenance intensities provide consistent objectives and standards for the care and maintenance of BLM roads based on identified management objectives. Maintenance intensities provide operational guidance to field personnel on the appropriate intensity, frequency, and type of maintenance activities that should be undertaken to keep the road in acceptable condition and provide guidance for the minimum standards of care for the annual maintenance of a road. Western Oregon guidance has been included to assist the reader in determining an appropriate maintenance intensity level for each BLM owned road. Roads functionally classified as resource roads may receive more extensive maintenance during periods of increased administrative or commercial use. The benefitting activity or user (BLM timber sale purchaser or permittee) may be responsible for funding the maintenance work required for their use. Lack of funding or short-term increases in maintenance shall not be considered when assigning long-term maintenance intensity levels. Roads not owned by the BLM, which were constructed on BLM lands under right-of-way grants or permits will be maintained in accordance with the terms of the grant or permit.
Maintenance Intensity Levels and descriptions are provided below:
Intensity Level 0
Maintenance Description: Existing routes that will no longer be maintained and no longer be declared a route. Routes identified as Level 0 are identified for removal from the Transportation System entirely.
Maintenance Objectives:
•	No planned annual maintenance.
•	Meet identified environmental needs.
•	No preventative maintenance or planned annual maintenance activities.
Maintenance Funds: No annual maintenance funds.
Western Oregon Guidance: The objective of this maintenance intensity level should include road segments currently closed to vehicles that may be used again in the future. This will facilitate assigning decommissioned roads at this level. Roads in storage should be assigned this maintenance intensity level.
Intensity Level 1
Maintenance Description: Routes where minimum (low intensity) maintenance is required to protect adjacent lands and resource values. These roads may be impassable for extended periods of time.
Maintenance Objectives:
•	Low (Minimal) maintenance intensity.
•	Emphasis is given to maintaining drainage and runoff patterns as needed to protect adjacent lands. Grading, brushing, or slide removal is not performed unless route bed drainage is being adversely affected, causing erosion.
•	Meets identified resource management objectives.
•	Perform maintenance as necessary to protect adjacent lands and resource values.
•	No preventative maintenance.
•	Planned maintenance activities limited to environmental and resource protection.
•	Route surface and other physical features are not maintained for regular traffic.
Maintenance Funds: Maintenance funds provided to address environmental and resource protection requirements. No maintenance funds provided to perform preventative maintenance.
Western Oregon Guidance: Traffic is generally administrative with some minor specialized use or moderate seasonal use. These are typically low standard, low volume, single lane, natural or aggregate surfaced logging spurs, functionally classified as resource roads. These roads will be the third priority for expending both annual (6252) and collected (9110) maintenance funding each year. Storm-proofing will be used to maintain open resource roads found within riparian reserve areas receiving infrequent maintenance. Storm-proofing puts a road into more of a self-maintaining condition and will reduce chronic sediment inputs along stream channels and water-bodies. BMPs for storm-proofing may involve:
•	Relieving inboard ditches more frequently.
•	Rocking road surfaces.
•	Seeding, mulching, and re-vegetating erosion prone surfaces, where sediment delivery to stream channels may result.
•	Applying site-specific measures to alleviate concentration of road drainage causing erosion and sediment delivery to streams. •	Lowering risk of stream diversion potential at stream crossings
•	Upgrading stream crossings to pass the 100 year flood with allowance for debris and bedload.
•	Removing or lowering unstable fills.
•	Outsloping in-sloped ditch roads.
•	Road drainage control to stabilize dissipation areas.
Intensity Level 2
RESERVED FOR POSSIBLE FUTURE USE
Intensity Level 3
Maintenance Description: Routes requiring moderate maintenance due to low volume use (for example, seasonally or year-round for commercial, recreational, or administrative access). Maintenance Intensities may not provide year-round access but are intended to generally provide resources appropriate to keep the route in use for the majority of the year.
Maintenance Objectives:
•	Medium (Moderate) maintenance intensity.
•	Drainage structures will be maintained as needed. Surface maintenance will be conducted to provide a reasonable level of riding comfort at prudent speeds for the route conditions and intended use. Brushing is conducted as needed to improve sight distance when appropriate for management uses. Landslides adversely affecting drainage receive high priority for removal; otherwise, they will be removed on a scheduled basis.
•	Meets identified environmental needs.
•	Generally maintained for year-round traffic.
•	Perform annual maintenance necessary to protect adjacent lands and resource values.
•	Perform preventative maintenance as required to generally keep the route in acceptable condition.
•	Planned maintenance activities should include environmental and resource protection efforts, annual route surface.
•	Route surface and other physical features are maintained for regular traffic.
Maintenance Funds: Maintenance funds provided to preserve the route in the current condition; perform planned preventive maintenance activities on a scheduled basis; and address environmental and resource protection requirements.
Western Oregon Guidance: These road segments are functionally classified as local roads and serve as a connection to the BLM collector and resource road network. These roads will be the second priority for expending both annual (6252) and collected (9110) maintenance funding each year. Intensity Level 4
RESERVED FOR POSSIBLE FUTURE USE
Intensity Level 5
Maintenance Description: Route for high (maximum) maintenance due to year-round needs, high volume of traffic, or significant use. Also, may include route identified through management objectives as requiring high intensities of maintenance or to be maintained open on a year-round basis.
Maintenance Objectives:
•	High (Maximum) maintenance intensity.
•	The entire route will be maintained at least annually. Problems will be repaired as discovered. These routes may be closed or have limited access due to weather conditions but are generally intended for year-round use.
•	Meets identified environmental needs.
•	Generally maintained for year-round traffic.
•	Perform annual maintenance necessary to protect adjacent lands and resource values.
•	Perform preventative maintenance as required to generally keep the route in acceptable condition.
•	Planned maintenance activities should include environmental and resource protection efforts, annual route surface.
•	Route surface and other physical features are maintained for regular traffic.
Maintenance Funds: Maintenance funds provided to preserve the route in the current condition; perform planned preventative maintenance activities on a scheduled basis; and address environmental and resource protection requirements.
Western Oregon Guidance: These road segments generally link the state and county arterial road network with BLM’s local road network and are functionally classified as collector roads. These roads will be the first priority for expending both annual (6252) and collected (9110) maintenance funding each year. </attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>MAINTENANCE INTENSITY 1</edomv>
<edomvd>MAINTENANCE INTENSITY 1</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAINTENANCE INTENSITY 2</edomv>
<edomvd>MAINTENANCE INTENSITY 2</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAINTENANCE INTENSITY 3</edomv>
<edomvd>MAINTENANCE INTENSITY 3</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAINTENANCE INTENSITY 4</edomv>
<edomvd>MAINTENANCE INTENSITY 4</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAINTENANCE INTENSITY 5</edomv>
<edomvd>MAINTENANCE INTENSITY 5</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>MAINTRESP</attrlabl>
<attalias>MaintResp</attalias>
<attrdef>This field indicates the agency or entity responsible for maintenance on the road or trail.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>Bureau of Land Management</edomv>
<edomvd>Maintained by BLM</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>BLM/Shared</edomv>
<edomvd>Maintained by multiple entities</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Timber Sale Operator</edomv>
<edomvd>Maintained by TSO for duration of the sale. The ultimate maintenance responsibility remains with the BLM.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Contract</edomv>
<edomvd>Maintenance done by a contracted company. The ultimate maintenance responsibility remains with the BLM.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Private</edomv>
<edomvd>Privately controlled road. No BLM maintenance</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Other Agency</edomv>
<edomvd>County, State, BPA, etc.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>Unknown</edomv>
<edomvd>Unknown</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CAPITALIMP</attrlabl>
<attalias>CapitalImp</attalias>
<attrdef>The capital improvement field identifies the agency or entity that made a capital improvement to a road if this agency or entity is different than the road owner. Capital improvement does not change road ownership. Capital improvements include work and materials expended to better a road by increasing its construction standard when compared to its original construction standard. Examples of capital improvements include widening and/or surfacing the roadway, adding drainage structures, and replacing bridges.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">3</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>BL</edomv>
<edomvd>The BLM improved a non-BLM road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>PV</edomv>
<edomvd>A private entity improved a BLM road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OA</edomv>
<edomvd>Another agency improved a BLM road</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NA</edomv>
<edomvd>Not Applicable, capital improvements have only been made by the road owner</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UNK</edomv>
<edomvd>Unknown</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>CLOSURERSN</attrlabl>
<attalias>ClosureRsn</attalias>
<attrdef>This field is a record of why the road has been closed.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>WLD</edomv>
<edomvd>Wildlife/Big Game hunting concerns</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OWL</edomv>
<edomvd>Northern Spotted Owl</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>FSH</edomv>
<edomvd>Fisheries</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>REC</edomv>
<edomvd>Recreation</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MNT</edomv>
<edomvd>Maintenance - closed due to maintenance problem</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OTE</edomv>
<edomvd>Other Threatened &amp; Endangered Species</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>ADM</edomv>
<edomvd>Administrative</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>POC</edomv>
<edomvd>Port Orford Cedar</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>NOX</edomv>
<edomvd>Noxious Weed</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WSA</edomv>
<edomvd>Road is closed because it is in a Wilderness Study Area</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OTH</edomv>
<edomvd>Other</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>BEGINMILEPOST</attrlabl>
<attalias>BeginMilePost</attalias>
<attrdef>The milepost value for the segment origin.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ENDMILEPOST</attrlabl>
<attalias>EndMilePost</attalias>
<attrdef>Record of the end milepost value for a BLM inventoried route segment.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>TOTALMILES</attrlabl>
<attalias>TotalMiles</attalias>
<attrdef>Ground measured (clocked) length (miles) of the segment.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>GIS_MILES</attrlabl>
<attalias>GIS_MILES</attalias>
<attrdef>The length of a linear feature in miles. BLM_ORG_CD is used to determine the appropriate projection. The GIS miles are calculated when the publication dataset is created as the inventoried route datasets do not have a BLM_ORG_CD field; BLM_ORG_CD is derived from the STATE_CD, DIST_CD, and RA_CD fields in the FAMS tables. •	NAD 1983 USFS R6 Albers: Prineville
•	NAD 1983 UTM Zone 10N: Coos Bay, Lakeview, Medford, NW Oregon, Roseburg
•	NAD 1983 UTM Zone 11N: Burns, Spokane, Vale
These three projections all use linear units of meters, so the ESRI Geodatabase-controlled field SHAPE.LENGTH can be used to convert to miles with the factor based on the U.S. Survey Foot: GIS_MILES = SHAPE.LENGTH * 0.0002471044.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>BLMORGCODE</attrlabl>
<attalias>BLMOrgCode</attalias>
<attrdef>A combination of the BLM administrative state and field office that has administrative responsibility for the spatial entity. This includes determining the office to cover the entity for planning purposes and the office that is the lead for GIS edits. Another agency or individual may have the physical management responsibility for the on-the-ground entity. This field applies particularly when a spatial entity crosses field office or district boundaries and the administrative responsibility is assigned to one or the other rather than splitting the spatial unit. Similarly, OR/WA BLM may have administrative responsibility over some area that is physically located in Nevada, Idaho, or California and vice versa. When appropriate, identify the office to the district or even the state level rather than to the field office level.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom>Administrative Unit Organization Code. Standard BLM organization codes generated from the national list. This is a lengthy domain used by multiple datasets. For the full list of values go to: https://gis.blm.gov/ORDownload/Domains/dom_BLM_ORG_CODE.xls.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>COUNTYCD</attrlabl>
<attalias>CountyCd</attalias>
<attrdef>The county that legally owns and controls the road and has the authority to set terms of the road maintenance and conditions of road use. Land ownership does not necessarily mean the road is owned by the same entity. In many situations, the land is owned by one entity and the road is owned by another. This field is a further drill down of the Ownership and Ownership Designation fields. Conditions for this field require that the value ‘Other Agency’ be populated for the Ownership field and that the value of ‘Cnty’ be populated for the Ownership Designation field.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">35</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>OR001
</edomv>
<edomvd>OR001 - Baker, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR003
</edomv>
<edomvd>OR003 - Benton, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR005
</edomv>
<edomvd>OR005 - Clackamas, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR007
</edomv>
<edomvd>OR007 - Clatsop, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR009
</edomv>
<edomvd>OR009 - Columbia, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR011
</edomv>
<edomvd>OR011 - Coos, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR013
</edomv>
<edomvd>OR013 - Crook, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR015</edomv>
<edomvd>OR015 - Curry, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR017
</edomv>
<edomvd>OR017 - Deschutes, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR019</edomv>
<edomvd>OR019 - Douglas, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR021</edomv>
<edomvd>OR021 - Gilliam, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR023
</edomv>
<edomvd>OR023 - Grant, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR025</edomv>
<edomvd>OR025 - Harney, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR027
</edomv>
<edomvd>OR027 - Hood River, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR029
</edomv>
<edomvd>OR029 - Jackson, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR031
</edomv>
<edomvd>OR031 - Jefferson, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR033
</edomv>
<edomvd>OR033 - Josephine, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR035</edomv>
<edomvd>OR035 - Klamath, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR037</edomv>
<edomvd>OR037 - Lake, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR039</edomv>
<edomvd>OR039 - Lane, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR041
</edomv>
<edomvd>OR041 - Lincoln, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR043</edomv>
<edomvd>OR043 - Linn, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR045
</edomv>
<edomvd>OR045 - Malheur, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR047
</edomv>
<edomvd>OR047 - Marion, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR049
</edomv>
<edomvd>OR049 - Morrow, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR051</edomv>
<edomvd>OR051 - Multnomah, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR053</edomv>
<edomvd>OR053 - Polk, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR055</edomv>
<edomvd>OR055 - Sherman, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR057</edomv>
<edomvd>OR057 - Tillamook, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR059
</edomv>
<edomvd>OR059 - Umatilla, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR061</edomv>
<edomvd>OR061 - Union, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR063</edomv>
<edomvd>OR063 - Wallowa, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR065
</edomv>
<edomvd>OR065 - Wasco, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR067</edomv>
<edomvd>OR067 - Washington, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR069</edomv>
<edomvd>OR069 - Wheeler, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>OR071</edomv>
<edomvd>OR071 - Yamhill, Oregon
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA001</edomv>
<edomvd>WA001 - Adams, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA003
</edomv>
<edomvd>WA003 - Asotin, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA005</edomv>
<edomvd>WA005 - Benton, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA007</edomv>
<edomvd>WA007 - Chelan, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA009</edomv>
<edomvd>WA009 - Clallam, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA011
</edomv>
<edomvd>WA011 - Clark, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA013</edomv>
<edomvd>WA013 - Columbia, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA015</edomv>
<edomvd>WA015 - Cowlitz, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA017</edomv>
<edomvd>WA017 - Douglas, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA019</edomv>
<edomvd>WA019 - Ferry, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA021</edomv>
<edomvd>WA021 - Franklin, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA023</edomv>
<edomvd>WA023 - Garfield, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA025</edomv>
<edomvd>WA025 - Grant, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA027</edomv>
<edomvd>WA027 - Grays Harbor, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA029</edomv>
<edomvd>WA029 - Island, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA031</edomv>
<edomvd>WA031 - Jefferson, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA033</edomv>
<edomvd>WA033 - King, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA035</edomv>
<edomvd>WA035 - Kitsap, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA037</edomv>
<edomvd>WA037 - Kittitas, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA039</edomv>
<edomvd>WA039 - Klickitat, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA041
</edomv>
<edomvd>WA041 - Lewis, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA043
</edomv>
<edomvd>WA043 - Lincoln, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA045</edomv>
<edomvd>WA045 - Mason, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA047</edomv>
<edomvd>WA047 - Okanogan, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA049</edomv>
<edomvd>WA049 - Pacific, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA051</edomv>
<edomvd>WA051 - Pend Oreille, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA053</edomv>
<edomvd>WA053 - Pierce, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA055</edomv>
<edomvd>WA055 - San Juan, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA057</edomv>
<edomvd>WA057 - Skagit, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA059</edomv>
<edomvd>WA059 - Skamania, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA061</edomv>
<edomvd>WA061 - Snohomish, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA063</edomv>
<edomvd>WA063 - Spokane, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA065</edomv>
<edomvd>WA065 - Stevens, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA067
</edomv>
<edomvd>WA067 - Thurston, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA069</edomv>
<edomvd>WA069 - Wahkiakum, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA071</edomv>
<edomvd>WA071 - Walla Walla, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA073</edomv>
<edomvd>WA073 - Whatcom, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA075</edomv>
<edomvd>WA075 - Whitman, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WA077</edomv>
<edomvd>WA077 - Yakima, Washington
</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>COMMENTS</attrlabl>
<attalias>Comments</attalias>
<attrdef>A field to be used at the discretion of District Offices. This field is not required. Personally Identifiable Information (PII) should not be entered into this field.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">255</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>FRMWKID</attrlabl>
<attalias>FrmwkID</attalias>
<attrdef>This is a key field that was originally used to link GTRN features to the All Oregon Roads table. This field is being used to link GTRN with district tables.
Framework ID number assignments (applies only to new number assignments, the original All Oregon Roads number assignments remain valid):
Roads:
300,000 for Lakeview
400,000 for Burns
500,000 for Vale
600,000 for Vale
700,000 for Prineville
800,000 for Prineville
900,000 for Spokane
Trails:
3,300,000 for Lakeview
3,400,000 for Burns
3,500,000 for Vale
3,600,000 for Vale
3,700,000 for Prineville
3,800,000 for Prineville
3,900,000 for Spokane</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">9</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>USFSKEYNUM</attrlabl>
<attalias>USFSKeyNum</attalias>
<attrdef>This is a key field used to link GTRN features to the USFS road database. There is currently no available USFS database to join. This field should not be edited.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">34</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>TIGERNUM</attrlabl>
<attalias>TigerNum</attalias>
<attrdef>This field was used for the All Oregon Roads project. It may eventually link GTRN features to the 2000 TIGER data.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">9</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>ACCURACYFT</attrlabl>
<attalias>AccuracyFt</attalias>
<attrdef>How close, in feet, the spatial GIS depiction is to the actual location on the ground. There are several factors to consider in GIS error: scale and accuracy of map-based sources, accuracy of Global Positioning System (GPS) equipment, and the skill level of the data manipulators. A value of “0” indicates no entry was made. This is the correct value when the COORD_SRC is another GIS theme (Digital Line Graph, Cadastral National Spatial Data Infrastructure and Digital Elevation Model (DEM)) because the accuracy is determined by that theme. However, if COORD_SRC is MAP (digitized from a paper map) or GPS, a value of “0” indicates a missing value that should be filled in either with a non-zero number or “-1.” A value of “-1” indicates that the accuracy is unknown, and no reliable estimate can be made.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl>COORDSRC</attrlabl>
<attalias>CoordSrc</attalias>
<attrdef>The actual source of the GIS coordinates for the spatial features.</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">7</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<edom>
<edomv>CADNSDI</edomv>
<edomvd>CADNSDI - Lines from or snapped to the CADNSDI dataset</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>CFF</edomv>
<edomvd>CFF - Lines duplicated or buffered from Cartographic Feature Files (USFS)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DEM</edomv>
<edomvd>DEM - Digital Elevation Model (30m or better accuracy) used for creation of contours</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DGPS</edomv>
<edomvd>DGPS - Feature obtained from a Global Positioning System device with Real Time Correction (SBAS)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DIS</edomv>
<edomvd>DIS - Lines generated to connect discontinuous features</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DLG</edomv>
<edomvd>DLG - Lines duplicated or buffered from (24K scale accuracy) USGS Digital Line Graphs</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DOQ</edomv>
<edomvd>DOQ - Screen digitized linework over digital orthophotography backdrop (DOQ, NAIP, OSIP, or others)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>DRG</edomv>
<edomvd>DRG - Screen digitized linework over Digital Raster Graphic backdrop</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>GCD</edomv>
<edomvd>GCD - Lines snapped to Geographic Coordinate Database Points</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>GPS</edomv>
<edomvd>GPS - Lines obtained from a Global Positioning System device</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>IMG</edomv>
<edomvd>IMG - Linework derived from interpretation of satellite or other non-photographic imagery</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>LiDAR</edomv>
<edomvd>LiDAR - LiDAR points, lines, or polygons generated through interpretation or analysis.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MAP</edomv>
<edomvd>MAP - Digitized coordinates from hardcopy map or onto a map backdrop</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>MTP</edomv>
<edomvd>MTP - Lines duplicated from Digital Master Title Plat</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SOURCEL</edomv>
<edomvd>SOURCEL - Coordinates duplicated from a BLM GIS source layer.</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SOURCEX</edomv>
<edomvd>SOURCEX - Source Layer from non-BLM GIS</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>SRV</edomv>
<edomvd>SRV - Survey methods were used to create the linework (e.g., COGO)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>TIGER</edomv>
<edomvd>TIGER - Tiger Data</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>TRS</edomv>
<edomvd>TRS - Coordinates only given as a legal description (township, range, section)</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>UNK</edomv>
<edomvd>UNK - Unknown coordinate source</edomvd>
<edomvds>BLM</edomvds>
</edom>
<edom>
<edomv>WOD</edomv>
<edomvd>WOD - WODDB Photogrammetric</edomvd>
<edomvds>BLM</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>SOURCEVINTAGE</attrlabl>
<attalias>SourceVintage</attalias>
<attrdef>The vintage of the coordinate source materials. This is a date field with the format being: mm/dd/yyyy (i.e. 05/24/2006).</attrdef>
<attrdefs>BLM</attrdefs>
<attrtype Sync="TRUE">Date</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="FALSE">SHAPE</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="FALSE">SHAPE_Length</attrlabl>
<attalias Sync="TRUE">SHAPE_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Length of feature in internal units.</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
<overview>
<eaover>Data Dictionary for this data is available on-line http://www.blm.gov/or/gis/files/docs/BLMGroundTransportation_WebDD.pdf</eaover>
</overview>
</eainfo>
</metadata>
