TravelRoutesDataDictionary V2

Travel Routes
National Data Dictionary

ROADS
Infrastructure Application
Version 2.0
April 2009
Travel Routes Road User Board

Data Dictionary Sub-Team
Carol Russell - R1
Donna Sheehy - R1
Tom Erkert - R6
Bob Goetz - R10
Table of Contents
1 Introduction..............................................................................................................1-1
1.1 Conventions.....................................................................................................1-1
2 Change Log.............................................................................................................2-1
3 Data Structure and Required Roles........................................................................3-1
3.1 Data Structure..................................................................................................3-1
3.2 Required Roles for Road data stewards..........................................................3-3
3.3 Tabular Component..........................................................................................3-5
3.3.1 Routes.......................................................................................................3-5
3.4 Spatial Component...........................................................................................3-7
3.4.1 Routes – Road and Trail...........................................................................3-7
3.4.2 TravelRoute_ln........................................................................................3-11
3.4.3 TravelManagementArea.........................................................................3-12
4 Table/Column Definitions.........................................................................................4-1
4.1 System /Audit Columns....................................................................................4-1
4.2 Common Columns...........................................................................................4-3
5 Route Basics Table..................................................................................................5-1
6 Route Linear Events Table......................................................................................6-1
6.1 Route Linear Event Definitions........................................................................6-5
6.2 Linear Event Application Matrix..................................................................…6-38
7 Record of Events Table...........................................................................................7-1
8 Coding Scenarios....................................................................................................8-1
9 Special Situations....................................................................................................9-1
9.1 Roads Policy Initiative and Unauthorized Roads.............................................9-1
9.2 Campground Loops..........................................................................................9-4
9.3 Decommissioning Through Routes or Planned Route Connections...............9-6
9.4 Dual Route Designations.................................................................................9-8
9.5 Y Intersections................................................................................................9-11
9.6 Duplication of Another Unit’s Data.................................................................9-12
10 Glossary................................................................................................................10-1
10.1 Travel Routes Terms......................................................................................10-1
10.2 Policy Terms...................................................................................................10-3
11 References............................................................................................................11-1
12 Appendix A – Flow Charts.....................................................................................12-1
13 Appendix B – Retired Columns.............................................................................13-1
1 Introduction
The purpose of this document is to provide business rules, scenarios, and

definitions of the tables/columns and linear events used within the Travel Routes
module of the Infrastructure (INFRA) application to assist the user in consistent
data entry and retrieval.
While the Travel Routes module contains spatial and tabular data structures for
both roads and trails, this data dictionary only contains the information for
Roads.
For the trails Data Dictionary, refer to;

http://fsweb.wo.fs.fed.us/rhwr/ibsc/tr-data-dictionary.shtml
Data Dictionaries for ATM, RMO, Authorizations, and Work Items, are separate
documents located at http://fsweb.r6.fs.fed.us/eng/travel_routes/user_board/.
1.1 Conventions
The following conventions are used throughout the data dictionary:
Words in Italics – Instructional comments to the reader on an action that

can be taken
(1) Reference Number, see appropriate chapter
Introduction Travel Routes Data Dictionary Page: 1

2 Change Log
This data dictionary is dynamic and will constantly change to reflect changes in
business rules, new data structures and program areas implemented. This change
log is for Version 2 and greater.
Version Chapter Description Date
2.0 Version 2.0 included the following changes,

updates and edits:
Formatting and organization.
"Retired" linear events moved to an appendix
Linear events combined into one chapter
Business rules, scenarios, and definitions
edited to be in conformance with the new
travel management policy, FSM, and FSH
direction.
New Record of Events types.
Updates to glossary and references.
Chapter 3 was re-written to reflect the
changes in the "snapshot" tables and the new
standards for the spatial component.
The list of required roles for the Roads module
was added
Change Log Travel Routes Data Dictionary Page: 1

3 Data Structure and Required Roles
3.1 Data Structure

The Travel Routes application supports distinct spatial and tabular
components that work together to provide a transportation atlas for roads
and trails.
 The spatial component has evolved from a coverage format to a
geodatabase format. Whether the data is stored in the Spatial Data
Engine (SDE) database, file geodatabase or a personal geodatabase,
the structure is the same.
 The tabular component is related attribute data that is stored within
the Oracle database and managed through the Infrastructure
application. Attributes apply either to the entire travel route (road or
trail) or to some measured distance (up to its entire length) along the
travel route (linear events), or to point features at a specific distance
along the route (route features). The general model of the Travel
Routes tabular components is shown in .
Route ROAD
Information that is common
to the entire route. Contains
one record for each route.
Road data modules

Route Features Linear Events Authorizations Road Management
Information on Information on linear Information about Objectives (RMO’s)
features or structures attributes that occur along existing or needed Information describing the
that occur a route and have a road-related road’s management
at a point or points associated length authorizations objectives.
along a road or trail on a road or trail
Record of Events Access & Travel Work Items Road Maintenance

(ROE) Management (ATM) Information about Plans (RMP)
Information on date related Information about travel maintenance and CIP Tool to prioritize road work
road events: management along the needs along a road. WI’s tasks to be included in an
Construction, Surveys, length of the road or trail may be linear or point work annual program of work.
Decisions etc.
Figure Data Structure and Required Roles-1 Travel Routes Tabular Data Modules
Data Structure and Required Roles Travel Routes Data Dictionary Page: 1
The spatial side of the application manages representations of the geometry
of the road network. It uses the Arc/INFO dynamic segmentation model
where lines (arcs) represent the alignment between intersections and routes
represent ordered collections of arcs and/or parts of arcs. A small set of
attributes, which allow linking to the attribute data stored in Oracle, are
stored on the arcs/routes.
The descriptive attributes for a route are stored in the Oracle database,
which also contains the unique link. Measured event data for a route are
stored in Oracle with the unique link and the beginning and ending
measures for the portion of the route to which the event applies. These
links and measures allow the spatial and tabular components to work
together in the Travel Routes application.
The descriptive attributes are managed via the INFRA application. This
national application contains the forms to input and edit data and maintain
data integrity of the tabular data. The modules shown in are implemented
through the INFRA application.
3.2 Required Roles for Road data stewards
Roles: To manipulate the data in I-Web you must be granted access to

certain FS organizations and also granted the roles that control what you
may do with the data owned by those organizations. Controlling access in
this way protects the integrity of important Forest Service data and also
helps the agency meet eGov initiatives. When you apply for a user
account and password, you will be asked to specify a certain role (see
Figure 3-2 for road data steward roles). If you're confused about which
role you should request, speak with your manager/supervisor.
Security Id: This field’s ID number:
(1) Identifies which organization the asset (features, land units, etc.)
belongs to; and therefore
(2) Acts as a filter that controls what asset records a user can see and
edit.
For example, a road record with a security ID of 0808 “belongs” to the
George Washington National Forest in Region 8. Only users who have
been granted access to the organization 0808 (and who also have the
appropriate Travel Routes roles) can edit the details of this road. Road
data stewards do not need to request the district organizations as travel
routes data for both roads and trails will be managed in Infra at the Forest
level.
If a user needs access to an organization that their account does not have
currently, they must submit a request using the User Management
Application (UMA) to ask that this organization be added to their account.
UMA is an application within I-Web that allows users to request brand
new accounts or request changes to their existing accounts.
Figure 3-2 describes the Roles needed to maintain Road data. When
requesting a role, you must also specify the needed organization(s),
RRFF.
Security
ID Org Purpose
Roles
Level
Required to add, update and delete Road
data. This role will allow the user to make
II_RTE_MGR RRFF
edits to route basics, linear events and the
record of events.
Required to add, update and delete Road
features (Table: II_FEATURES).
II_FEAT_MGR RRFF Maintaining Road Bridge data or Culvert
Installation (FHWA data) requires the BMC
MGR role.
Required to add, update and delete Work
II_WK_ITM_MGR RRFF Items for Roads. Required to maintain Work
Item data in ERL
Required to maintain Travel Management
II_ATM_MGR RRFF data. This role is also needed to resize the
Road MP’s
Required to create and maintain Road
II_RMO_MGR RRFF
Management Objectives data (RMOs).
Figure 3-2 Required Roles
3.3 Tabular Component
3.3.1 Routes
The structure of the basic route and linear event attributes within the
Oracle database are shown in Figure 3-2. This is the core relationship
that forms the foundation of the travel routes model.
RTE_BASICS RTE_LINEAR_EVENTS
PK CN PK CN
I1 OBJ_CLASS FK1,I1,U1 RTE_CN

I1 OBJ_TECH U1 BMP
I1 OBJ_NAME U1 EMP
ID U1 VALUE
NAME U1 LINEAR_EVENT
SPUR_NO REMARKS
BMP STATUS
EMP MASTER_SITE
BEGIN_TERMINI CREATED_BY
END_TERMINI CREATED_DATE
COMMENTS CREATED_IN_INSTANCE
I2 TRANS_ID MODIFIED_BY
MASTER_SITE MODIFIED_IN_INSTANCE
CREATED_BY MODIFIED_DATE
CREATED_DATE
CREATED_IN_INSTANCE
MODIFIED_BY Legend
MODIFIED_IN_INSTANCE CN = Control Number
MODIFIED_DATE
PK = Primary Key
CHECKED_OUT_BY
CHECKED_OUT_DATE FK# = Foreign Key
U# = Unique Index
I# = Non-Unique Index
Figure Data Structure and Required Roles-2. Route Basics and Linear Events Table Relationships
Traditionally, attribute data is stored in a table where a separate column (field)
is defined for each attribute. In Travel Routes, the attribute data is stored as a
series of linear event and value combinations in the RTE_LINEAR_EVENTS
table. For each record in this table the linear event field holds the name of a
linear event (e.g. objective maintenance level) and the value field holds the
value of the named linear event (e.g. 3 - SUITABLE FOR PASSENGER
CARS) for a section along the route. This is commonly referred to as the
“long/skinny approach”. While this data structure is efficient and extensible
(allows for local customization), it’s not conducive to ad-hoc queries where
multiple attributes need to be queried simultaneously. While several complex
queries have been devised [4], there are situations where the queries don’t
work correctly such as when linear events contain gaps and overlaps.
3.3.1.1 Static Summary Tables
There are two types of static, aka snapshot, tables (they don’t
automatically change as the database changes) that can be used for ad
hoc queries (both spatial and tabular) that flatten out the linear event
model to a more traditional approach. These tables, described in the
following sections, are much easier to use for querying the database and
should be used for both spatial and tabular queries. Oracle procedures
are used to populate and maintain these tables. These tables are not to
be edited directly as the data is dropped and re-created when the refresh
procedure is run. Prior to the consolidation of our data to the I-Web, the
procedures were run by the local data stewards. After the consolidation
the procedures were rewritten to refresh these tables nightly [5].
3.3.1.1.1 Road Core Table (II_ROAD_CORE)

In Oracle the name of this table is “II_ROAD_CORE”. It has a separate
column for each of the nationally required linear events. This table is
used for upward level reporting and is the source data for reporting
processes run by the WO as well. The manner in which this table is
updated changed when the Road data was consolidated in 2005. The
table is updated by a process that runs nightly. As of July 2007 the
process was modified to only update the records that had changed since
the previous update. This modification greatly improved the refresh
performance.
In 2008 a button, “Push to Road Core”, was added to the Maintain Road
data screen. This button gives users the ability to update the
II_ROAD_CORE on demand – albeit only for road at a time. This is
especially useful for users who do not want to wait until tomorrow to see
the results of their updates to be available in GIS or User Views
3.3.1.1.2 Road Linear Events (II_ROAD_LINEAR_EVENTS_rrff)

The Oracle table name of these tables is
“II_ROAD_LINEAR_EVENTS_rrff”, where rrff is the concatenation of the
2 digit region and 2 digit forest identifier (ex: 0116 = Region 1, Forest 16
which is the Lolo NF). Each forest (rrff) has an
II_ROAD_LINEAR_EVENTS_rrff table. There is a separate column for
each unique linear event in the database. Therefore the structure of the
table can change because of regional and forest authority linear events
that can be added. These tables are the source data used in the
ArcView Travel Routes Extension query builder. The data refresh is
done nightly in the same manner as for the II_ROAD_CORE table.
3.3.1.1.3 MVUM Road “snapshot” tables (II_MVUM_ROAD_ALLOW and

II_MVUM_ROAD_RESTRICT)
The Oracle MVUM tables have the same list of columns (data structure)
and exist primarily for the purpose of creating GIS data for the Motor
Vehicle Use Map (MVUM). The MVUM_ROAD_RESTRICT is populated
using an algorithm that calculates the “inverse” of the restrictions to
determine what motorized uses are allowed. The MVUM tables contain
ATM data and a few core linear events (System, Jurisdiction, Route
Status, Operational ML, Surface Type and Admin Org). The ATM
columns include all the motorized Modes of Travel and the
corresponding date range. The tables contain an ERROR FLAG field
that can be used for MVUM Symbol error checking, and the SBS
SYMBOL NAME used to display roads with the legend used on the
Secondary Base (Forest Visitor) Map.
3.4 Spatial Component

The structure is two-tiered. The first level is a feature dataset. It is a collection
of spatially or thematically related feature classes that share a common
coordinate system. It can be thought of as a folder containing similar or
related GIS themes. Underneath this dataset are individual feature classes. A
feature class is a collection of features of the same type, (such as roads or
trails) with a common set of attribute, or data fields.
The feature dataset holding Road information is called Transportation.
Underneath this feature dataset are four feature classes: Road, Trail,
TravelManagementArea, and TravelRoute_ln.
The National GIS Data Dictionary, contains detailed specifications for this
feature dataset
(http://fsweb.datamgt.fs.fed.us/current_data_dictionary/index.shtml). The
pertinent components of the standards contained within the National GIS
Data Dictionary are repeated here for completeness.
The key linkage between the spatial and tabular data is the route control
number (CN). This identifier is unique across the Forest Service. In addition
the route number (ID in RTE_BASICS) is also very important in building and
maintaining the spatial data.
3.4.1 Routes – Road and Trail

A route is a line feature class that is set to hold ‘measures’ or ‘m-values’. This
allows for the feature to be calibrated to a different length or value, than the
actual GIS length of the feature. This may also be referred to as being
‘dynamically segmented’, ‘linear referenced’ or ‘routed’. This characteristic
differentiates this GIS feature class from other simple line features.
Previously, when the Travel_Routes coverage was the standard, there were
two subclasses called the Road ‘route’ (travel_route.ratroad) and the Trail
route (travel_route.rattrail).
One route system will be created for roads (ROAD) and another for trails
(TRAIL).
The route feature attribute tables (.rat) have identical structures except for the
ArcInfo key items (fields) <route> # and <route>-id, where <route> equals
road or trail. These data structures are compatible with the SDI application.
Route measures and route direction must correspond to those stored in the
RTE_BASICS table in Oracle.
The BMP and EMP items are redundant to those carried in the RTE_BASICS
table in Oracle. They are included to facilitate route calibration and because
the SDI application was designed to use them. The RTE_NO and RTE_CN
are also redundant to the ID and CN columns in the RTE_BASICS table.
These items are included for the linkage to the tabular data and for ease in
labeling routes in Arc/Info and Arcview.
The ACTION and ACTIONSTAMP items are required for the SDI application
to work. It maintains a history of when the route was linked to RTE_BASICS
and if the route needs to be re-calibrated.
Figure 3-4 shows the structure of the Road feature class attribute table.
Column Name
Description Domain Type L* P S N
(Alias)
Shape Feature geometry. Geometry 0 0 0 Y
OBJECTID Internal feature number. OID 4 0 0 Y
Control number generated in Oracle to
uniquely identify each route across all
Forest Service units. The value is brought
from Oracle and used as a unique identifier
RTE_CN ( CN# ) 34 0 0 Y
for each spatial feature. It is used to join String
each route to the corresponding rows in the
views GC_RTE_BASICS_V,
GC_ROADS_V, and GC_TRAILS_V by
matching with the column RTE_CN.
The local route number for a route. This
String 30 0 0 Y
RTE_NO item identifies routes within a Forest
Service unit.
Name of the road. This information is String 30 0 0 Y
Name
maintained in the Infra Roads application.
Beginning measure point of the route. The
Double 8 0 0 Y
BMP value is copied from Oracle (RTE_BASICS)
and used as an aid in calibration.
Ending measure point of the route. The
Double 8 0 0 Y
EMP value is copied from Oracle (RTE_BASICS)
and used as an aid in calibration.
Identifies the status of the calibration of the RT_ACTION String 10 0 0 Y
RT_ACTION
route.
ACTIONSTAMP The date that the value was placed into the Date 8 0 0 Y
ACTION item.
Date of feature creation or latest update. String 20 0 0 Y
REV_DATE
DATA_SOURCE Feature data source code DATA_SOURCE String 2 0 0 Y
Distance (+/-), in dataset distance units, of

Single 4 0 0 Y
ACCURACY expected difference between feature and
real world object locations.
Globally Unique Identifier for each feature, 0 38 0 0 Y
GlobalID
managed by ESRI software.
Length of feature in internal units. Double 8 0 0 Y
Shape_Length
* Field information as reported in ArcCatalog metadata. L = Length, P = Precision, S = Scale, N = Nulls Allowed
Figure 3-4. Attribute table for Road feature class
Code Description
The route is properly calibrated to the BMP/EMP
CALIBRATED values in RTE_BASICS.
The route needs to be re-calibrated to the BMP/EMP
REMEASURE values in RTE_BASICS.
The route is properly calibrated to the BMP/EMP
values in RTE_BASICS and has had mid-point
MCALIBRATE calibration performed with internal calibration points
at road.
MANUAL User will calibrate the route manually.
Figure 3-5 Domain for Rt_Action field
Code Description
01 Original Cartographic Feature File (CFF)
02 GPS – Uncorrected Data
03 GPS – Differentially Corrected Data
04 GPS Survey Grade and Sub-meter
05 Resurvey Plat
06 Photogrammetric Compilation
07 Digitized From Hardcopy PBS/SEQ
08 Digitized From Hardcopy Orthophotography
09 Automated Lands Project (ALP)
20 Digitized from other source
21 Geographic Coordinate Database (GCDB)
22 Other Cadastral Information
23 Other Agency Digital
24 Other
30 Remote Sensing Data – Base Level
31 Remote Sensing Data – Mid Level
32 Remote Sensing Data – Broad Level
33 Remote Sensing Data – National Level
Figure 3-6 Domain for Data_Source field
3.4.2 TravelRoute_ln
There is another linear feature class defined, TravelRoute_ln. It contains no ‘m’
values and cannot be linearly referenced. In the coverage model, this would
represent the ‘arc’ feature class. It does not have the capability to carry
measures and is an optional feature class. It is available to hold any local
attributes that a unit may find valuable. It contains the same items as the ‘old’
arc layer, and is meant for any local uses that arc layer had previously.
Note: It does NOT factor into the Road or Trail feature class in any way. It is
NOT required for these other feature classes.
Column Name
(Alias)
Geometry 0 0 0
Shape Feature geometry. N
OID 4 0 0
OBJECTID Internal feature number. N
The local route number for a

route. This item identifies String 30 0 0 Y
RTE_NO
routes within a Forest
Service unit.
The local identifier for the
TRL_NO String 30 0 0 Y
trail. The Trail number should
(TRAIL_NO)
be unique within a forest.
Name of the road. This
String 30 0 0 Y
RTE_NAME information is maintained in
the Infra Roads application.
Name of the trail. This
String 30 0 0 Y
TRL_NAME information is maintained in
the Infra Trails application.
Date of feature creation or Date 20 0 0 Y
REV_DATE
latest update.
String 2 0 0
DATA_SOURCE Feature data source code DATA_SOURCE
Y
Distance (+/-), in dataset
distance units, of expected
Single 4 0 0 Y
ACCURACY difference between feature
and real world object
locations.
Globally Unique Identifier for
Global ID 38 0 0 N
GlobalID each feature, managed by
ESRI software.
Length of feature in internal Double 8 0 0 Y
Shape_Length
units.
Figure 3-7 Domain for TravelRoute_ln
3.4.3 TravelManagementArea
The polygon feature class TravelManagementArea is used to represent areas
open for motorized cross country travel, as defined in the Transportation Rule.
The tabular data for this feature is in the fsdba.land_units Infra table, with a
OBJ_NAME of Travel_Management_Area. Once a land unit record has been
established, ATM records can be created and associated with the land unit
record.
Currently this feature class is only used for Motor Vehicle Use Map purposes,
but further uses are being considered.
Column Name
(Alias)
OID 4 0 0
OBJECTID Internal feature number.
Y
Geometry 0 0 0
Shape Feature geometry.
Y
Control number generated in Oracle
to uniquely identify each all Forest
Service units. The value is brought
from Oracle and used as a unique
identifier for each spatial feature. It is
String 34 0 0 Y
CN (CN#) used to join each travel management
area to the corresponding row in the
Land Unit table by matching with the
column CN. It will join to the
II_MVUM_TRAVEL_MGT_AREA_V
view on the LU_CN field.
The unique name or number
assigned by the Forest to each area.
String 30 0 0 Y
ID This name or number is unique within
a Forest but may not be unique
between Forests.
Date of feature creation or latest String 20 0 0 Y
REV_DATE
update.
DATA_SOURCE String 2 0 0 Y
Feature data source code DATA_SOURCE
Distance (+/-), in dataset distance

units, of expected difference between Single 4 0 0 Y
ACCURACY
feature and real world object
locations.
Globally Unique Identifier for each 0 38 0 0 Y
GlobalID
feature, managed by ESRI software.
Double 8 0 0 Y
Shape_Length Length of feature in internal units.
Area of feature in internal units Double 8 0 0 Y

Shape_Area
squared.
Figure 3-8 Domain for TravelManagementArea
4 Table/Column Definitions
The purpose of this section is to document the tabular data structure.
The columns are organized after the table name chapter generally by the order in which
they occur in the table structure. A figure of the column is placed in the chapter that first
describes the table. These figures include hyperlinks to quickly jump to the column of
interest.
The format of each column or linear event definition holds basic information on:
 Name
 Definition
 Column structural definition (i.e. data type, etc)
 Reference to the USFS Manual, Handbooks, Code of Federal Regulation, or
US Code if applicable.
 Requirements for population
 Business rules for application of the column or linear event
 General notes
 Codes available along with the definition of each code
Retired and obsolete columns are located in the appendix.
4.1 System /Audit Columns
Many tables within INFRA have audit columns which log information on:
The user that created the record
The date the record was created
The Oracle instance number the record was created in
The user that last modified the record
The date the record was last modified
The Oracle instance number where the record was last modified
The Oracle database maintains these columns through the use of insert and
update triggers defined within the database. Therefore, no user action is
required to populate these. These columns can be useful when troubleshooting
problematic data. The audit columns are located below and are not repeated in
the table sections to minimize redundancy
When the Infra databases that were located at each forest were migrated to
the central database instance for Iweb, a new column called SECURITY_ID
was introduced. This column is contained in RTE_BASICS, II_FEATURES,
and other tables where the parent record of a primary asset is stored. It is
composed of the Region and Forest numbers (ie RRFF). The data was
Table/Column Definitions Travel Routes Data Dictionary Page: 1

generated from the database instance that the data came from and it does not
necessarily indicate the ADMIN_ORG that the asset is assigned to.
Audit Columns
Used in Tables:
RTE_BASICS
AUDIT COLUMNS
RTE_LINEAR_EVENTS
Requirements for Population
Road Requirement
System
All Required - System Generated
Business 1.) Audit column, no input required - populated with an Oracle insert trigger.
Rules:
AUDIT NAMES
Name: CREATED_BY
Definition: The user that created the record.
Name: MODIFIED_BY
Definition: The user that last modified the record.
Reference: OPS$USER
Data Type: varchar2 Size: 30 Mandatory: No
Notes: 1.) This column may contain information on conversion routines or mass loading such
as ERL1-ERL2 data.
AUDIT DATES
Name CREATED_DATE
Definition: The date when the record was originally created.
Name: MODIFIED_DATE
Definition: The date when the record was last modified.
Data Type: date Mandatory: No
AUDIT INSTANCES
Name: CREATED_IN_INSTANCE
Definition: The Oracle instance number of where the record was created. This is taken from the
INSTANCE_ID column in the THIS_DB_INSTANCE table.
Name: MODIFIED_IN_INSTANCE
Definition: The Oracle instance number of where the record was last modified.. This is taken from
the INSTANCE_ID column in the THIS_DB_INSTANCE table.
Data Type: number Precision: 6 Scale: 0 Mandatory: No
Look Up: THIS_DB_INSTANCE

4.2 Common Columns
There are some columns that are common to most of the tables. They are
shown below and not repeated in the table sections to avoid redundancy.
They include:
CN
BMP
EMP
RTE_CN
REMARKS

Common Columns
Used in Tables:
RTE_BASICS
Name: CN RTE_LINEAR_EVENTS
II_RTE_RECORD_OF_EVENTS
Unique identifier of a record. It is a unique number within the Forest Service that is
Definition: composed of a sequence number concatenated with the oracle database instance
identifier.
Reference: Authority: WO
Format: Sequence Number & Oracle Instance Number
Data Type: varchar2 Size: 34 Mandatory Yes

Road System Requirement
All Required - System Generated
Business
Rules:
Notes:
1.) The sequence number is generated by the RTE_CN_SEQ
2.) Generated by an insert trigger in the oracle database

Common Columns
Used in Tables:
RTE_LINEAR_EVENTS
Name: RTE_CN
Unique identifier of a route. It is a unique number within the Forest Service that is
Definition: composed of a sequence number concatenated with the oracle database instance
identifier. It is a foreign key to the CN column in RTE_BASICS.
Authority: WO
Format: Sequence Number & Oracle Instance Number
Data Type: varchar2 Size: 34 Mandatory: Yes

All Required
Business
Rules:
Notes:

Common Columns
Used in Tables:
RTE_BASICS
MEASURE POINTS RTE_LINEAR_EVENTS
Name: BMP
Definition: Beginning measure point of the route segment
Name: EMP
Definition: Ending measure point of the route segment. The EMP is the BMP plus the measured length
of the route.
Format: 999.999 Unit of Measure: Miles
Data Type: number Precision: 8 Scale: 4 Mandatory: Yes

All Required
Business 1) Start or end the measure point of a route at its logical beginning or ending measure
Rules: point. This may be where the route is originally signed. For example, Figure 4-1 shows a
US Highway starting at an Interstate route. The US Highway begins its measure point at
the interstate route. The forest has included the US Highway in the database and its
spatial coverage where the US Highway begins but only where the road is within close
proximity to national forest lands. In this case, the BMP of the US Highway route within
Travel Routes should be the milepost of where the route enters the forest coverage extent
measured from its original BMP of the route (MP 52.3). The milepost measures are
typically available through a state department of transportation office.
2) If a NFSR starts outside the forest boundary and continues into the forest, the BMP
should begin where the route junctions with its parent route (Federal, State, County,
Private) as shown in Figure 4-2. The example shows a route where an easement has
been acquired across private land to access forest lands.
3) The measure point must be in the same physical location as that shown in the GIS
coverage. The measure point of the route in the coverage will be calibrated to the
measure point in RTE_BASICS. If the measure point is changed, the corresponding point
of the route in the spatial layer must also be changed to match.
4) Measure points should be measured in the field with a Distance Measuring Instrument
properly calibrated or a GPS unit. Measure points can be recorded up to the nearest .001
miles if one of these instruments is used. The accuracy recorded should be consistent
with the accuracy of the instrument used to determine the measure.
5) Measure points must run in the same direction as what is signed on the ground
6) Measure points must run in the same direction as those indicated in

ROUTE_BASICS.
7) If the measure point of a route is at the junction of another road system, the measure
point is located at the centerline-centerline intersection to accommodate how the route
systems are built in GIS.
8) If a portion of a route is decommissioned and will still be managed as a single route, do
not change the EMP, instead use the ROUTE STATUS linear event to capture the change

in status

5
o.
o 12
National
Forest .9
.3 97
52 Extent of GIS
Coverage
Figure Table/Column Definitions-1 US Route Beginning Measure Example
Private Land
r Creek Lane
FS Land
00000
FS Road - 54
County - Bea
MP 5.219
MP 0.0
Forest Boundary
Figure Table/Column Definitions-2 Route Beginning Measure Example

Common Columns
Used in Tables:
RTE_LINEAR_EVENTS
Name: REMARKS
Definition: Additional comments or descriptive remarks.
Look Up:

All Optional
Business 1.) Specific business rules give guidance for using this field.
Rules:
2.) If a remark exists for a record, further remarks can be appended by placing a
comma then the new remark
Notes:

5 Route Basics Table
RTE_BASICS is the parent table for all routes. It contains one record for each route.
It includes route definitions for both roads and trails, which can be separated by using
the object name (OBJ_NAME).
You can click on the column of interest in Figure 5-1 to navigate to the definition.
RTE_BASICS
Column Name Null? Remarks Reference
CN NOT NULL PRIMARY KEY Refer to page 4-4
OBJ_CLASS NOT NULL Refer to page 5-2
OBJ_TECH NOT NULL Refer to page 5-3
OBJ_NAME NOT NULL Refer to page 5-4
SECURITY_ID NOT NULL Refer to page 5-5
ID NOT NULL Refer to page 5-6
NAME Refer to page 5-8
BMP Refer to page 4-6
EMP Refer to page 4-6
BEGIN_TERMINI Refer to page 5-9
END_TERMINI Refer to page 5-9
COMMENTS Refer to page 5-10
CHECKED_OUT_BY Refer to page 5-11
CHECKED_OUT_DATE Refer to page 5-12
RTE_SUBTYPE Used only by Trails
UNAUTHORIZED_INDICATOR NOT NULL For Trails, “N” for Roads
SPUR_NO No longer used
No longer used. Prior to the
TRANS_ID IWeb this field was populated Refer to Appendix B
with the Oracle instance ID.
MASTER_SITE Not used
CREATED_BY
CREATED_DATE
CREATED_IN_INSTANCE Audit fields
Refer to Section 4.1
MODIFIED_BY
MODIFIED_IN_INSTANCE
MODIFIED_DATE
Figure 5.1 RTE_BASICS Table Diagram
Route Basics Table Travel Routes Data Dictionary Page: 1

RTE_BASICS
Used in Tables:
Name: OBJ_CLASS RTE_BASICS
Definition: The highest level grouping of objects within the INFRA database.
Authority: WO

All Required – Forms generated
Business 1.) Only ROUTE is used for Roads and Trails

Rules:
Notes:
Valid Codes
Code Description
ACCOMPLISHMENT_INSTRUMENT
CONTACT
DOCUMENT
EVENTS
FEATURE
FISCAL
LAND_UNIT
POOLED
REPORT
ROUTE Only code used for travel routes
STATUS PARCEL
SYSTEM_LIBRARY

RTE_BASICS
Used in Tables:
Name: OBJ_TECH RTE_BASICS
Definition: The primary technology used to store and access the object

All Optional
Business 1. ‘ORACLE’ is the only value stored for travel routes even though ARCVIEW and SDI
Rules: are commonly used
Notes:
Valid Codes
Code Description
ARCVIEW
ORACLE Only code stored in the RTE_BASICS table
ORACLE FORMS 45
SDI

RTE_BASICS
Used in Tables:
Name: OBJ_NAME RTE_BASICS
The name of the object. Used to differentiate between objects (ROAD or TRAIL) of the
Definition:
same class.
Reference: 36 CFR 212.1, FSM 7705, FSM 2353.05, FSH 2309.18.05
Authority: WO
Data Type: varchar2 Size: 30 Scale: Mandatory: Yes

Business 1.) This attribute always needs to be included in queries as roads and trails are mixed
Rules: within the same storage structure
Notes:
Valid Codes
Code Description
A motor vehicle route over 50 inches wide, unless identified and managed as a
ROAD
trail. (36 CFR 212.1)
A route 50 inches or less in width or a route over 50 inches wide that is identified
TRAIL
and managed as a trail. (36 CFR 212.1)

RTE_BASICS
Used in Tables:
Name: SECURITY_ID RTE_BASICS
The Security ID number identifies to which organization the asset (routes, features, land
Definition: units, etc.) belongs and acts as a filter that controls what asset records a user can see
and edit.
Format: RRFF , the 2 digit code for the Region plus 2 digit code for the Forest

All Required
Business As Travel Routes, including Roads and Trails, can span multiple districts, the Security ID
Rules: format is RRFF. The Security ID format is RRFF for any Features that are on the route.
Notes: If a data steward only has been granted the RTE MGR role for just one forest, the
Security Id will be auto-populated by the form. For a data steward who has been
granted the RTE MGR role for multiple forests, the form will auto-populate the Security
ID field with the smallest valid ORG value the data steward has been granted. For
example, if a road data steward on the Lolo NF (0116) also has the RTE MGR role for
the Bitterroot (0103) the form will auto-populate the field with 0103 when a new road
record is entered.

RTE_BASICS
Used in Tables:
Name: ID RTE_BASICS
Definition: The official identifier of the route
Reference: EM-7100-15 Sign and Poster Guidelines for the Forest Authority: WO
Service, Chapter 3A, FSM 7710.11.2

All Required
Business General Rules

Rules:
1.) In general the ID should be the same identifier that is signed on the ground.
2.) Different regions have different numbering strategies for Forest Service Roads. It is
recognized that it would be difficult to standardize the numbering strategies because
of the large investment in signs and documents.
3.) At a minimum include all Forest Roads which includes “any road wholly or partially
within or adjacent to and serving the National Forest System, and which is
necessary for the protection, administration, and utilization of the National Forest
System and the use and development of its resources” (23 U.S.C. 101). Forest
roads are required in the forest road atlas (FSM 7711.2). It’s strongly recommended
that other roads needed for mapping and analysis also be included in the forest road
atlas.
4.) It’s recommended that the road number(id) be unique within a forest because:
i. SDI contains a tool to populate the route control number within the route
attribute table in the gis coverage. This tool works by linking on the route
number. If a duplicate exists it is more difficult for this tool to function correctly.
ii. Some forests have created automated processes to route their coverages
when needed. These routines rely on the route number being unique within the
coverage.
5.) Dual route designations are discouraged as the travel routes model was not
designed to model these (See Chapter 9.4 for further explanation).
Forest Roads
6.) Interstate routes shall be designated with “I” then a hyphen then the route number
and then a one digit letter for the cardinal direction. “I” shall be capitalized.
Example: I-5N for northbound Interstate 5, I-84E for eastbound Interstate 84.
Divided highways are actually two different roadways, which can have different
alignments and measures. MPs should match state signing on the ground.
7.) Federal routes shall be designated with a “US” then a hyphen then the route
number. “US” shall be all caps. Example US-12 (US Highway 12)

8.) State Highways shall be designated with a 2 digit postal code then a hyphen then
the route number. Postal code shall be all caps. Example OR-82, WA-504, NH-5
9.) Other governmental routes such as Other Federal, State roads, County, Township,
and City (Municipal) roads shall be designated with a 3 digit alpha code to indicate
the organization, then a hyphen, then the actual road number or name. For
example:
BLM-1230 (Bureau of Land Management Road 1230)
NPS-Paradise (National Park Service Paradise Road)
HUM-Bear Creek Road (Humboldt County Bear Creek Road)
LAC-Bear Creek Road (Los Angeles County Bear Creek Road)
CTY-Bear Creek Road (Bear Creek County Road)
SLR-4555 (State Lands Road 4555)
WAL-586 (Wallowa County Road 586
10.)Campground Loops - Because loops are spatially unique roads, append an alpha
character to the route number separated by a hyphen. If the primary route going
into a campground was designated as the 9028000 and had two loops off of that
they would be coded as 9028000-A and 9028000-B. For more information see
Section 9-2.
11.) Private Routes –It’s recommended to use an abbreviation for the landowner
followed by a hyphen then the private identifier or name. Example: WEYCO-202
(Weyerhaeuser road 202).
Unauthorized Roads
12.)Unknown/unauthorized routes will be entered as a separate road number and not a

continuation of an existing NFSR road number. If an unauthorized route continues
off the end of an existing NFSR, it will be recorded as a separate road number (see
suggested numbering schemes below).
13.)A systematic approach for numbering unauthorized roads is desirable. This can be
done by using an existing local numbering scheme or one of the following
recommended systems:
i. Parent#+MP+Direction+sequence number separated by a hyphen. A road that
comes off of route 2808032 at mp 1.23 and goes right (in direction of increasing
measure) would be 2808032-1.23R-1. For more information see Chapter 9.1
ii. U+Any Numbering system. For example U252. If the road becomes a forest
road in the future, the road number needs to be changed to be consistent with
the local system.
Temporary Roads
14.)Temporary roads are not intended to be tracked in the Transportation Atlas (36 CFR
212.2). If they are included, they should have a road number consistent with the
document that authorizes their construction and use.
Notes:

RTE_BASICS
Used in Tables:
Name: NAME RTE_BASICS
Definition: Common name of the route

All Optional
Business 1. Use where appropriate. Do not code other meanings within this attribute such
Rules: as the timber sale name that built or is operating on a road.
Notes:

RTE_BASICS
Used in Tables:
ROUTE TERMINI RTE_BASICS
Name: BEGIN_TERMINI
Definition: A description of where the route begins
Name: END_TERMINI
Definition: A description of where the route ends

All Other Optional
FS Required
Business 1) If the route begins or ends at a junction with another route, record the junctioning
Rules: route ID
2) Prefix the junctioning route ID with either the word Road or Trail. For example, if a
road started at the junction of road 8303000 then the entry would be Road 8303000.
For non-FS road systems, the prefix should begin with an appropriate prefix such as
HWY (Highway), FH (Forest Highway), etc.
3) It’s recommended to input a milepost along the parent route after the text in
business rule #2 (i.e. Road 8303000 at MP 3.105).
Notes:

RTE_BASICS
Used in Tables:
Name: COMMENTS RTE_BASICS
Definition: General descriptive remarks

All Optional
Business
Rules:
Notes:

RTE_BASICS
Used in Tables:
Name: CHECKED_OUT_BY RTE_BASICS
Definition: The name of the user that has reserved the road for a mobile road survey. This column
is populated by the electronic road log (ERL) tool.
Format: USER (OPS$ has been stripped off)

All N/A – System Populated
Business 1) Populated with base user’s name if the road is checked out for mobile road survey
Rules: for the Electronic Road Log (ERL) application.
2) No editing will be allowed until this column is cleared and the data is checked back
in.
1.) This column was added to facilitate data integrity as part of the ERL application.
Notes:
2.) The RELEASE tab on the Maintain Data form allows users to release any road(s)
that they have reserved.

RTE_BASICS
Used in Tables:
Name: CHECKED_OUT_DATE RTE_BASICS
The date that the road was reserved in the Reserve Mobile Route form in INFRA Travel
Definition:
Routes. This column is populated by the electronic road log (ERL) tool.
Data Type: Date Mandatory: No

All N/A – System Populated
Business 1.) Populated with the date the user reserved a road in the mobile road survey for the
Rules: Electronic Road Log (ERL) application.
2.) No editing will be allowed until this column is cleared and the data is checked back
in.
Notes: 1.) This column was added to facilitate data integrity as part of the ERL application.
2.) The RELEASE tab on the Maintain Data form allows users to release any road(s)
that they have reserved.

6 Route Linear Events Table
The RTE_LINEAR_EVENT table shown in Figure 6-1 holds the descriptors for a
route and the value of those descriptors. This table is typically called an “event”
table. It contains one record for each event along a route. Only one unique
combination of RTE_CN, BMP, EMP, LINEAR_EVENT and VALUE can be defined.
Overlapping linear events are possible but only allowable in a few cases.
You can click on the column of interest in Figure 6.1 to navigate to the definition.
RTE_LINEAR_EVENTS
CN NOT NULL PRIMARY KEY Refer to Page 4-4
RTE_CN NOT NULL Refer to Page 4-5
BMP NOT NULL Refer to Page 4-6
EMP NOT NULL Refer to Page 4-6
LINEAR_EVENT NOT NULL Refer to Page 6-2
VALUE NOT NULL Refer to Page 6-4
REMARKS Refer to Page 4-8
STATUS No longer used
Refer to Appendix B
MASTER_SITE Not used
CREATED_BY
CREATED_DATE
Refer to Section 4-1
MODIFIED_BY
MODIFIED_DATE
Figure 6.1 RTE_LINEAR_EVENTS Table Diagram
Route Linear Events Table Travel Routes Data Dictionary Page: 1

RTE_LINEAR_EVENTS
Used in Tables:
Name: LINEAR_EVENT RTE_LINEAR_EVENTS
A specific linear characteristic of a route such as the surface type or operational

Definition:
maintenance level.
Look Up: II_ATT, II_ATT_OCC

FS Required – See specific linear events
All Other See Linear Event Application Matrix
Business 1) Extensive coding and validation exists. All Washington Office authority linear events
Rules: are defined in this data dictionary.
2) List of Values (LOV's) are taken from the II_ATT and II_ATT_OCC tables. II_ATT
defines the linear event and II_ATT_OCC determines if the linear event can be used
for a road or a trail.
3) See the listing for each linear event to determine if the linear event is required for
specific road systems (See Section 6.1).
4) Some additional linear events can be added to the database for local conditions,
which is called “extensibility. Extensibility is not allowed for the “Big 3” – System,
Jurisdiction, and Status and other WO codes. All requests for additional Linear
Events must be submitted via Base tickets and can only be added by the Infra
development personnel. Region and Forest authority linear events must be
coordinated at the regional level to ensure consistency. See the INFRA System
Administration User Guide (Section 4). It’s strongly encouraged that regions and
forests that add linear events document them.
Notes: 1) A linear event can be continuous, have gaps, or have overlaps. This dictionary
describes for each linear event if overlaps are allowed. It is must be noted that
anytime a linear event contains overlaps, mileage summaries using this linear event
will not be accurate. To determine if gaps are allowed, review the Linear Event
Application Matrix (Section 6-2)
2) A continuous linear event is shown in Figure 6-2. In this case the JURISDICTION
linear event is recorded continuously along the length of the route. There would be
3 records entered for JURISDICTION as shown.
3) A gap in a linear event is shown in Figure 6-3. In this case the MILEAGE SOURCE
linear event is only populated for two segments along the route and there is a gap
between them. There would only be 2 records entered for the MILEAGE SOURCE
linear event as shown. In general gaps are not appropriate for mandatory linear
events on Forest Service Roads.
4) An overlap in a linear event is shown in Figure 6-4. In this case there are two
critical traffic entries along the same segment of road from MP 2.0 to 6.0.

0.0 2.0 6.0 8.0
JURIS = SH JURIS = C JURIS = FS
0.0 8.0
BMP EMP Linear Event Value

0.0 2.0 JURISDICTION SH – STATE HIGHWAY
2.0 6.0 JURISDICTION C – COUNTY, PARISH, BOROUGH
6.0 8.0 JURISDICTION FS – FOREST SERVICE
Figure 6-2 Continuous Linear Event
0.0 2.0 6.0 8.0

SOURCE = DMI SOURCE = GPS
0.0 8.0

0.0 2.0 MILEAGE SOURCE DMI – DISTANCE MEASURING
INSTRUMENT
6.0 8.0 MILEAGE SOURCE GPS – GLOBAL POSITIONING
Figure 6-3 Gap in Linear Event
CRITICAL TRAFFIC = LOGGING TRUCK
0.0
2.0 6.0 8.0
CRITICAL TRAFFIC = SEMI-TRACTOR TRAILER
0.0 8.0

0.0 8.0 CRITICAL TRAFFIC LOGT – LOGGING TRUCK
2.0 6.0 CRITICAL TRAFFIC SEMI –TRACTOR TRAILER TRUCK
Figure 6-4 Overlap Linear Event

RTE_LINEAR_EVENTS
Used in Tables:
Name: VALUE RTE_LINEAR_EVENTS
The value of the linear event for the segment. For example: Asphalt for the surface
Definition:
type
Look Up: II_CODES

FS Required – See specific linear events
All Other See Linear Event Application Matrix
Business 1.) For Linear Events that have no List of Values defined (such as Design Speed, etc.)
Rules: in the II_CODES table, valid coding is defined by the Linear Event business rules
and definition.
2.) Don’t use punctuation marks within the value as it can cause problems with
several Oracle procedures. Punctuation marks such as %, #, /, !,’, *,?, & should
not be used.
Notes: 1.) Many linear events have a list of values that are defined in the II_CODES table.
2.) If a linear event does not have valid values (codes) defined in the II_CODES table,
any data can be stored.

6.1 Route Linear Event Definitions
The linear events under Washington Office Authority are listed below. The
coding and linear events for Washington Office authority shall not be
modified. Click on the name to navigate to the definition of that linear event.
Some of these linear events are spatial attributes and as such should be
generated and maintained through GIS. A generic procedure has been
developed by the INFRA development team to allow maintenance of spatial
attributes via a spatial overlay but it requires a “land unit” coverage that is
linked to the land units module of Infra. An asterisk notes the spatial linear
events after their name below
 ADMIN_ORG*
 CONGRESSIONAL DISTRICT*
 COUNTY*
 CRITICAL TRAFFIC
 DESIGN SPEED
 DESIGN TRAFFIC
 FUNCTIONAL CLASS
 JURISDICTION
 LANES
 LEGAL
 LEVELS OF TREATMENT
 MANAGING_ORG
 MILEAGE SOURCE
 OBJECTIVE MAINT LEVEL
 OPER MAINT LEVEL
 OTHER SYSTEM
 PRIMARY MAINTAINER
 QUAD*
 ROAD TEMPLATE
 ROUTE STATUS
 SERVICE LIFE
 SURFACE TYPE
 SYSTEM
 TEMPLATE SLOPE CODE
 TRAFFIC SERVICE LEVEL
 TRAVEL WAY WIDTH
The values for all linear events are stored in English units. There is currently
no initiative to convert to metric units.

Warning - There are many times when there is a question on how many
miles of USFS roads there are classified by a set of linear events. All
queries must include logic to exclude those roads that are under other
jurisdictions and are not currently on the NFSR system. To do that, each
query should contain the following criteria:
 ROUTE STATUS = ‘EX – EXISTING’

 JURISDICTION = ‘FS – FOREST SERVICE’
 SYSTEM = ‘NFSR – NATIONAL FOREST SYSTEM ROAD’
 ADMIN_ORG -= Set to value of forest that you want to query.
Other forests roads may be duplicated in the database. Use the
MANAGING_ORG instead to find out how many miles are managed by
the forest.
In addition to the WO authority linear events, Regions and Forests can

establish their own linear events and coding. Regions and forests that create
linear events should establish them as a supplement to this document and
post them on their intranet site. They should also be coordinated at the
regional level to ensure consistency.

Route Linear Events
Used in Tables:
Name: ADMIN_ORG RTE_LINEAR_EVENTS
The Forest Service unit where the route segment physically resides or the primary
Definition:
Forest Service unit served by the route segment.
Reference: No reference in directive system Authority: WO
Format: RRFFDD
RR is the 2-digit code for the Region
FF is the 2-digit code for the Forest
DD is the 2-digit code for the District.
Overlap: No
Look Up: ID column in II_CONTACTS Linear Event: Yes

All Other Optional
FS Required
Unauthorized Required
Business 1.) Coding is validated against the ID column in the II_CONTACTS table where the
Rules: OBJ_NAME = ‘ORGANIZATION’.
2.) Management responsibilities should be indicated by the MANAGING_ORG. In most

cases the ADMIN_ORG will be the same as MANAGING_ORG. However, because
of organizational consolidation it is common to have one district or forest manage a
route segment that is closer to their base of operations than the unit that the asset
physically resides on.
3.) If the route segment is outside the proclaimed forest boundary, enter the primary
Forest Service unit served by the route segment. The primary Forest Service unit
may be a region (01), forest (0105), or district (010502) organization.( Refer to
Figure 6-5 and 6-6).
Notes: 1.) See Section 9.6 on how to use this linear event for recording other forest road
segments within a local database.

ne
Private Land FS Land
r Creek La
00000
FS Road - 54
County - Bea
MP 6.521
MP 5.219
MP 0.0
Forest Boundary
District 060301 Manages and Maintains the Route
ADMIN_ORG = 060301, MP 0.0 - 6.521

MANAGING_ORG = 060301, MP 0.0 - 6.521
Figure 6-5. Recording ADMIN_ORG and MANAGING_ORG outside Forest Boundary
Isolated Parcel
USFS Land
MP 6.0
MP 0.0
6 5
13
ad
White Mountain Ro
FS
NATIONAL FOREST
District 092202 Manages and Maintains the Route
ADMIN_ORG = 092202, MP 0.0 - 6.0

MANAGING_ORG = 092202, MP 0.0 - 6.0
3 1
ad
Ro
FS
Township Road 12
Figure 6-6 Recording ADMIN_ORG and MANAGING_ORG for Isolated Parcel

Route Linear Events
Used in Tables:
Name: CONGRESSIONAL DISTRICT RTE_LINEAR_EVENTS
Congressional districts are established for representation in the United States House of
Definition: Representatives. The quantity and boundaries of districts are typically determined after
each census.
Format: 99 Overlap: No
Look Up: NAME column in II_CODES Linear Event: Yes

FS Required
Business 1.) Shall be zero padded for single digit districts (i.e. 01).
Rules:
2.) Lookup values should be established for coding specific to each forest.
Notes: 1.) This is a spatial attribute and should be generated through a GIS coverage.

Route Linear Events
Used in Tables:
Name: COUNTY RTE_LINEAR_EVENTS
State and County/BOROUGH/PARISH/TOWNSHIP in which the route segment

Definition:
physically resides.
Format: SS - COUNTY Overlap: No
Linear Event: Yes

FS Required
Business 1.) Lookup values should be established for coding specific to each forest.
Rules:
Notes: 1.) This attribute replaces the STATE and COUNTY attributes. It was changed to
facilitate uniqueness.
2.) This is a spatial attribute and should be generated through a GIS coverage.
3.) Example coding:

NH - CARROL = Carrol County, New Hampshire
CO - JEFFERSON = Jefferson County, Colorado
OR - JEFFERSON = Jefferson County, Oregon

Route Linear Events
Used in Tables:
Name: CRITICAL TRAFFIC RTE_LINEAR_EVENTS
The vehicle, normally the largest (by weight, size, or unique configuration), whose limited
Definition:
use on the road is necessary to complete the planned activity. Also known as critical vehicle.
Reference: FSH 7709.56 Section 4.1, Road Preconstruction Handbook Authority: WO

(9/87)
Overlap: Yes

All Optional
Business
Rules:
Notes: Critical vehicle examples:

(a) Log yarder on a timber access road.
(b) Semitrailer truck carrying construction equipment on a recreation access road.
(c) Overlength, overwidth semitrailer trucks carrying drill rig components on a minerals
access road.
(d) Construction equipment used to build the facility.
(e) Recreation vehicles, such as large motorhomes, with or without other vehicles in tow.
Valid Codes
Code Description
4WD - FOUR WHEEL DRIVE Four Wheel Drive High Clearance Vehicle
BUS - BUS Bus
BUS(40) - 40 PASSENGER TOUR BUS 40 Passenger Tour Bus
CAR - PASSENGER CAR Passenger car
FLATBED - H15 TRUCK H15 Truck (Tandem Axle or Triaxle straight frame truck)
GARBAGE - GARBAGE TRUCK Garbage or other service truck
LOGT - LOGGING TRUCK Logging Truck with adjustable reach pole trailer
LOWBOY - LOWBOY TRACTOR TRAILER Low-boy Tractor Trailer
MOTORHOME - MOTORHOME Motor Home
OHH - OFF HIGHWAY HAUL VEHICLE Off Highway Haul Vehicles
PICKUP - PICKUP TRUCK Pickup Truck - High Clearance Vehicle
S4WD - SHORT BASE 4WHEEL Short base four-wheel drive i.e. Jeep
SEMI - TRACTOR TRAILER TRUCK Semi Truck (Tractor Trailer)
SERVICE - SERVICE VEHICLES Service Vehicle
TRAILER - RECREATION CAMPER TRAILER Car/Truck w/Camper-Boat Trailer
TRUCK - STRAIGHT TRUCK Straight Truck (H-Load)
YARDER - CABLE LOGGING EQUIPMENT Yarder - Cable Logging Equipment
Route Linear Events
Used in Tables:
Name: DESIGN SPEED RTE_LINEAR_EVENTS
The speed determined for design and correlation of the physical features of a route that
influence vehicle operation. The maximum safe speed that the design vehicle can
Definition: maintain over a specified segment of a route when conditions are so favorable that the
design features of the road, rather than operational limitations of the vehicle, govern.
The design speed is the safe speed for the design situation only.

(5/87)
Format: 99 Unit of Measure: MPH
Overlap: No
Linear Event: Yes

FS Optional
Business 1.) Indicate the average design speed in MPH to the nearest 5 MPH.
Rules:
2.) Enter the numeric value only (15), don’t include the units as the units are defined as
MPH.
3.) When original design information is not available, only populate this field if an
engineering study has been completed for purposes of establishing need for
warning and regulatory signing. This only applies to existing roads.
Notes: 1) Terrain and other physical controls may dictate a change in design speed for certain
segments. Apply these changes to segments between major changes in
topography or intersections.

Route Linear Events
Used in Tables:
Name: DESIGN TRAFFIC RTE_LINEAR_EVENTS
The vehicle frequently using the road that determines the minimum standard for a particular
design element. No single vehicle controls the standards for all the design elements for a
Definition: road. Determine the maximum and minimum standards from the type and configuration of
the vehicles using the road. Analyze each design element to determine which vehicle
governs the standard for that element. Also known as design vehicle.

(9/87)
Overlap: No

FS Optional
Business
Rules:
Notes:
Valid Codes
Code Description
4WD - FOUR WHEEL DRIVE Four Wheel Drive High Clearance Vehicle
BUS - BUS Bus
BUS(40) - 40 PASSENGER TOUR BUS 40 Passenger Tour Bus
CAR - PASSENGER CAR Passenger car
FLATBED - H15 TRUCK H15 Truck (Tandem Axle or Triaxle straight frame truck)
GARBAGE - GARBAGE TRUCK Garbage or other service truck
LOGT - LOGGING TRUCK Logging Truck with adjustable reach pole trailer
LOWBOY - LOWBOY TRACTOR TRAILER Low-boy Tractor Trailer
MOTORHOME - MOTORHOME Motor Home
OHH - OFF HIGHWAY HAUL VEHICLE Off Highway Haul Vehicles
PICKUP - PICKUP TRUCK Pickup Truck - High Clearance Vehicle
S4WD - SHORT BASE 4WHEEL Short base four-wheel drive i.e. Jeep
SEMI - TRACTOR TRAILER TRUCK Semi Truck (Tractor Trailer)
SERVICE - SERVICE VEHICLES Service Vehicle
TRAILER - RECREATION CAMPER TRAILER Car/Truck w/Camper-Boat Trailer
TRUCK - STRAIGHT TRUCK Straight Truck (H-Load)
YARDER - CABLE LOGGING EQUIPMENT Yarder - Cable Logging Equipment

Route Linear Events
Used in Tables:
Name: FUNCTIONAL CLASS RTE_LINEAR_EVENTS
The way a road services land and resource management needs, and the character of
Definition:
service it provides.
Reference: FSM 7700.5 Authority: WO
Overlap: No

FS Required
Business
Rules:
Notes:
Valid Codes
Code Description
A - ARTERIAL An NFS road that provides service to large land areas and usually connects
with other arterial roads or public highways.
An NFS road that serves smaller areas than an arterial road and that
C – COLLECTOR usually connects arterial roads to local roads or terminal facilities. Provides
service to smaller land areas than an arterial road. It usually connects
forest arterial roads to local forest roads or terminal facilities.
An NFS road that connects a terminal facility with collector roads, arterial
L - LOCAL roads, or public highways and that usually serves a single purpose involving
intermittent use.

Route Linear Events
Used in Tables:
Name: JURISDICTION RTE_LINEAR_EVENTS
The legal right to control or regulate use of a transportation facility. Jurisdiction requires
Definition: authority, but not necessarily ownership. The authority to construct or maintain a road
may be derived from fee title, an easement, an agreement, or some other similar method.
Reference: FSM 7703.3, FSM 5490 Authority: WO
Overlap: No

All Required
Business 1.) Road ROW Construction and Use Agreements (Cost Share) - The current standard
Rules: easement granted to the US Government via this agreement provides sufficient
authority to establish Forest Service jurisdiction. However, older agreements may not
grant sufficient authority. The FRTA easement granted to a cooperator giving right-of-
way over a Forest Service road retains jurisdiction with the Forest Service.
2.) Use the OFS – OTHER FOREST SERVICE when data from a neighboring forest is
put into the local database. The data is usually needed for gis or management
purposes. Coding the road segment with OFS will prevent the mileage from being
double counted as the data is aggregated at the regional or national scale.
3.) This linear event is not extensible by the forests.

Notes:
Valid Codes
Code Description
BIA - BUREAU OF INDIAN AFFAIRS USDI Bureau of Indian Affairs
BLM - BUREAU OF LAND MANAGEMENT USDI Bureau of Land Management
BOR - BUREAU OF RECLAMATION USDI Bureau of Reclamation
C - COUNTY, PARISH, BOROUGH County, Parish, Borough
COE - CORPS OF ENGINEERS US Army Corps of Engineers
CU – COMMERCIAL USER Commercial User
DOD - DEFENSE DEPARTMENT US Defense Department
DOE - DEPARTMENT OF ENERGY US Department of Energy
FAA - FEDERAL AVIATION ADMINISTRATION USDOT Federal Aviation Administration
FS - FOREST SERVICE USDA Forest Service
FWS - FISH AND WILDLIFE SERVICE USDI Fish and Wildlife Service
L - LOCAL Town, Township, Municipal Agency (City or other local civil government)
NPS - NATIONAL PARK SERVICE USDI National Park Service
OF - OTHER FEDERAL AGENCY Other Federal Agencies
OFS – OTHER FOREST SERVICE Adjacent USDA Forest Service unit.
P - PRIVATE Private (profit & not for profit)
S - STATE State Agency
SH –STATE HIGHWAY State Highway Department
SL – STATE LANDS State Lands organizations (Department of Natural Resources)
T – TRIBAL ROAD Non-Federal Tribal Road
UNK – UNKNOWN Needs to be researched and resolved
Route Linear Events
Used in Tables:
Name: LANES RTE_LINEAR_EVENTS
Definition: The number of lanes the travel way has.

(5/87)Authority: WO
AASHTO Green Book for public road agencies
Overlap: No

FS Required
State-County Required
Business 1.) Only full lanes are to be used

Rules:
2.) Numeric widths of route segments should be recorded using TRAVEL WAY WIDTH.
Notes:
Valid Codes
Code Description
1 - SINGLE LANE
2 - DOUBLE LANE
3 – THREE LANE
4 – FOUR LANE

Route Linear Events
Used in Tables:
Name: LEGAL RTE_LINEAR_EVENTS
Definition: The legal description of the beginning termini of the route (the BMP of the route).
GIS Core Dictionary Authority: WO

Reference: (http://fsweb.wo.fs.fed.us/im/standards/gis/coredata)
ALPS Data Dictionary (http://fsweb.r6.fs.fed.us/alp)
Overlap: No
Linear Event: Yes

FS Optional
Business 1.) This is commonly recorded for PUBLIC LANDS SURVEY SYSTEM (PLSS) Forests
Rules: where "Legal" is the Township/Range/Section.
2.) A SUGGESTED Format for TRS: 0050N0060E13 to record
T5N R6E S13
Or
0050N0060E020 to record
T5N R6E S02
Legal description coding according to national standards is:

###XN###XE##
where:
### - 3 digit whole Township or Range number
X - Fractional Township, range or Section number as follows:
1 - 1/4 township
2 - 1/2 township
3 - 3/4 township
0 - not a fractional township
N or E - North or East of the principle meridian or base line
Last two ## digits contain the section number, all 2 digits must be
entered
Notes: 1.) Not applicable to non-plss forests
2.) Protraction Blocks may be entered as PB 46

Route Linear Events
Used in Tables:
Name: LEVELS OF TREATMENT RTE_LINEAR_EVENTS
Describes a summary of the treatments completed either on a decommissioned road or

Definition: a road placed in storage (ML1). It describes the intensity of the work performed in
relation to hydrologic, vegetative, and stability factors.
Overlap: No

FS Optional
Business 1.) All treatments include blocking the entrance of the road.
Rules:
2.) Only to be used for roads placed in storage or decommissioned.
Notes: 1.) The codes represent a summary of treatments that have been performed
on a road. They describe the existing condition. Individual treatments and associated
costs may be recorded in work items.
2.) The intent of this linear event is to allow a quick summary as to overall
condition of the road in order to assess emergency access, needs for further
treatment and potential impacts of the road system to soil and water resources.
3.) Valid codes are shown on the following page

LEVELS OF TREATMENT continued
Valid Codes
Code Description
B – BLOCKED Entrance has been blocked. No other treatment to road prism or drainage.
CMP’s on streams and drainages have been removed and associated fills
have been sloped back and stabilized. Ditch relief culverts may be
C – CMP REMOVED
bypassed and left in place or removed. Former drainage patterns have
been re-established.
V – REVEGETATED Road prism has been re-vegetated.
U – UNSTABLE FILLS REMOVED Unstable fills have been removed.
W – WATERBARRED/OUTSLOPED The road prism has been water barred and/or outsloped.
The road prism has been fully obliterated. (top of cut to toe of fill) by
R - RECONTOURED restoring natural contours and slopes. All CMP’s have been removed and
all watercourses have been restored to natural channels and floodplains.
CU – COMBINATION CMP’s have been removed. Unstable fills have been removed.
CMP’s have been removed The road prism has been water barred and/or
CW – COMBINATION
outsloped.
CV - COMBINATION CMP’s have been removed. The road prism has been re-vegetated
The road prism has been re-vegetated and unstable fills have been
VU - COMBINATION
removed.
WV - COMBINATION The road prism has been water barred and/or outsloped, and re-vegetated.
The road prism has been water barred and/or outsloped. Unstable fills
WU - COMBINATION
have been removed.
CMP’s have been removed The road prism has been water barred and/or
CWU - COMBINATION
outsloped, and unstable fills have been removed.
CMP’s have been removed. The road prism has been water barred and/or
CWV - COMBINATION
outsloped, and re-vegetated.
CMP’s have been removed. The road prism has been re-vegetated.
CVU - COMBINATION
Unstable fills have been removed.
The road prism has been water barred and/or outsloped and re-vegetated.
WVU - COMBINATION
Unstable fills have been removed.
CMP’s have been removed. The road prism has been re-vegetated, water
WUVC - COMBINATION
barred and/or outsloped. Unstable fills have been removed.

Route Linear Events
Used in Tables:
Name: MANAGING_ORG RTE_LINEAR_EVENTS
The Forest Service unit (region/forest/district) that has long-term responsibility for the
Definition:
management of the route segment.
Reference: No reference in directive system Authority: WO
Format: RRFFDD Overlap: No

RR is the 2-digit code for the Region
FF is the 2-digit code for the Forest
DD is the 2-digit code for the District.
Look Up: Coding is validated against the ID column in the Linear Event: Yes
II_CONTACTS table where the OBJ_NAME =
‘ORGANIZATION’.

FS Required
Business 1.) Management means the administrative unit that has the responsibility for road
Rules: management (regulating traffic, signing, scheduling maintenance, issuing road use
permits, etc).
2.) The unit that has management responsibility shall maintain all data within Infra and
is considered the data steward for the route.
3.) Not applicable for non-NFSRs
Notes: 1.) See Section 9.6 on how to use this linear event for recording other forest road
segments within a local database. Also see the ADMIN_ORG linear event.
2.) MANAGING_ORG should default to ADMIN_ORG when a new record is added to

the database.

Route Linear Events
Used in Tables:
Name: MILEAGE SOURCE RTE_LINEAR_EVENTS
Definition: Mileage source represents the source of the measure points recorded for a road segment.
Overlap: No
Linear Event: Yes

All Optional
Business 1.) Mileage source represents the source of the distance measures for a road segment.
Rules: Different values would be used only where the source of the measures change. It’s not
to be used for recording linear event changes.
Notes: 1.) This information is not necessarily the same as the source for the “line work”, the
spatial representation of the route. Rather, it represents the source of the measures
(MP’s) recorded in RTE_LINEAR_EVENTS for the route segment.
For example, if the entire length of a 10.0 mile long road was obtained using GPS
equipment, the Value (Code) GPS – GLOBAL POSITIONING would be applied from
BMP 0.0 to EMP 10.0. If measurement of only the first portion of the road to a junction
at MP 6.0 had been obtained with GPS equipment, and the length for the remainder of
the road had been obtained from cartographic feature files, MILEAGE SOURCE would
be coded GPS – GLOBAL POSITIONING from BMP 0.0 to EMP 6.0, and ARC -
SPATIAL DATA from BMP 6.0 to EMP 10.0
Valid Codes
Code Description
Mileage source from GIS, cartographic feature files, AutoCAD,
ARC – SPATIAL DATA Orthophotography, or other digital spatial data sources. Not
measured on the ground.
Mileage determined on the ground using an Electronic Distance
DMI – DISTANCE MEASURING INSTRUMENT Measuring Instrument such as a Jamar or Nitestar digital
measuring instrument that is properly calibrated.
Mileage determined on the ground using Global Positioning
GPS – GLOBAL POSITIONING
equipment.
MAPW – MAP WHEEL Mileage determined by using a map wheel from existing maps.
WHEEL – MEASURING WHEEL Mileage determined on the ground using a measuring wheel
ODOM – ODOMETER READING Mileage determined on the ground by vehicle odometer reading
Other mileage source – specify in remarks such as cloth tape,
OTHER – OTHER SOURCE
steel chain, etc.
STRING – STRING BOX Mileage determined on the ground using a string box (hip chain)
Mileage based on survey done for original construction or
SURVEY – CONSTRUCTION SURVEY
reconstruction.
PED – PEDOMETER Mileage determine by walking with a pedometer.

Route Linear Events
Used in Tables:
Name: OBJECTIVE MAINT LEVEL RTE_LINEAR_EVENTS
The maintenance level to be assigned at a future date considering future road management
Definition:
objectives, traffic needs, budget constraints, and environmental concerns.
Reference: FSH 7709.59 Chapter 60, Transportation System Operations Authority: WO

and Maintenance Handbook
Overlap: No

FS Required
All Other N/A
Business 1.) Codes C or D should not be used unless an appropriate decision document is on file.
Rules: The results of Travel analysis need to be included in a pre-decisional planning
document.
2.) Sport Utility Vehicles (SUV) are classified as a high clearance vehicles.
Notes: 1.) See Chapter 9.1Roads Policy Initiative and Unauthorized Roads for further guidance in
using this linear event.
2.) A typical low standard timber sale road usually is operated at a higher maintenance
level during the sale than afterwards. Typically these roads would have an Operational
Maintenance Level of 2 and an Objective Maintenance Level of 1.
3.) See the Glossary for a full definition of Maintenance Level. The descriptions contained
below are shortened so they can be held within the code table (II_CODES).
Valid Codes
Code Description
Assigned to roads that have been placed in storage (> one
1 - BASIC CUSTODIAL CARE (CLOSED) year) between intermittent uses. Basic custodial maintenance
is performed. Road is closed to vehicular traffic
2 - HIGH CLEARANCE VEHICLES Assigned to roads open for use by high clearance vehicles.
Assigned to roads open for and maintained for travel by a
3 - SUITABLE FOR PASSENGER CARS
prudent driver in a standard passenger car.
Assigned to roads that provide a moderate degree of user
4 - MODERATE DEGREE OF USER COMFORT
comfort and convenience at moderate travel speeds.
Assigned to roads that provide a high degree of user comfort
5 - HIGH DEGREE OF USER COMFORT
and convenience.
C - CONVERT USE Convert use of the facility to another use such as a trail.
Assigned to roads that have been or are to be
D - DECOMMISSION
decommissioned.

Route Linear Events
Used in Tables:
Name: OPER MAINT LEVEL RTE_LINEAR_EVENTS
The Maintenance level currently assigned to the road considering today's needs, road
Definition: condition, budget constraints and environmental concerns; in other words it defines the
level to which the road is currently being maintained.

Overlap: No

FS Required
All Other N/A
Business 1.) If a road is being operated at a Maintenance Level 1, it should also have a Service
Rules: Life of I - Intermittent Term Service or IS – Intermittent Stored Service.
2.) Sport Utility Vehicles (SUV) are classified as a high clearance vehicles
Notes: 1.) See Chapter 9.1Roads Policy Initiative and Unauthorized Roads for further guidance
in using this linear event.
2.) A typical low standard timber sale road usually is operated at a higher maintenance
level during the sale than afterwards. Typically these roads would have an operational
maintenance level of 2 and an objective maintenance level of 1.
3.) See the Glossary for a full definition of Maintenance Levels. The descriptions
contained below are shortened so they can be held within the code table (II_CODES).
Valid Codes
Code Description
Assigned to roads that have been placed in storage (> one
year) between intermittent uses. Basic custodial
1 - BASIC CUSTODIAL CARE (CLOSED)
maintenance is performed. Road is closed to vehicular
traffic
2 - HIGH CLEARANCE VEHICLES Assigned to roads open for use by high clearance vehicles.
Assigned to roads open for and maintained for travel by a
3 - SUITABLE FOR PASSENGER CARS
prudent driver in a standard passenger car.
Assigned to roads that provide a moderate degree of user
4 - MODERATE DEGREE OF USER COMFORT
comfort and convenience at moderate travel speeds.
Assigned to roads that provide a high degree of user comfort
5 - HIGH DEGREE OF USER COMFORT
and convenience.

Route Linear Events
Used in Tables:
Name: OTHER SYSTEM RTE_LINEAR_EVENTS
Additional network(s) of travel ways designated over the primary route that serve a
Definition:
common need or purpose
Reference: U.S.C. 101 23 CFR 660 and FSM 7740 Federal Lands Authority: WO
Highway Program
Overlap: Yes

FS Optional
Business 1.) Use for additional networks of roads such as scenic byways, Forest Highways, and
Rules: national trail associations.
2.) Forest Highways shall be coded as OTHER SYSTEM and must be on the official
FHWA list of approved routes on the forest highway system. Figure 6-7 shows how a
typical Forest Highway would be coded where a portion of the entire route is already
transferred to a public authority and a portion is waiting to be transferred.
3.) Roads that are also managed as designated system trails (i.e. snowmobile trails and
cross country ski trails), should be entered here as a secondary system as NFST –
NATIONAL FOREST SYSTEM TRAIL.
4.) OGM – OIL, GAS, MINERALS should be used where the sole purpose of the road is
for oil, gas, or minerals exploration and or production. In the exploration phase, the
road should also be coded as SYSTEM = TMP – TEMPORARY. If the operation goes
into production, set SYSTEM = NFSR – NATIONAL FOREST SYSTEM ROAD (see
Appendix, Figure ).
Notes: 1.) There may be multiple systems over a single route. This linear event contains overlaps.
Therefore, any mileage summary including this will not be accurate.
2.) Appropriate codes are listed on the following page.

OTHER SYSTEM - continued
Valid Codes
Code Description
C - COUNTY, PARISH, BOROUGH County, Parish or Borough network
A forest road under the jurisdiction of and maintained by a
FH - FOREST HIGHWAY public authority and open to public travel (U.S.C. 101 23 CFR
660 and FSM 7740.5)
I - INTERSTATE HIGHWAY Interstate Highway
Town, Township, Municipal Agency (City or other local civil
L – LOCAL
government)
State designation for roads that have unique scenic or
SSB – STATE SCENIC BYWAY
recreational qualities
National designation for roads that have unique scenic or
NFSB – NATIONAL FOREST SCENIC BYWAY
recreational qualities designated by the Chief of USFS
National designation for roads that have unique scenic or
NSB – NATIONAL SCENIC BYWAY
recreational qualities designated by FHWA
OF - OTHER FEDERAL Other Federal Agency (such as BLM, NPS, BIA, etc.)
OR – OTHER ROAD Other locally designated route system
OS – OTHER STATE State roads other than those on the state highway system
P – PRIVATE Private
SH - STATE HIGHWAY State Highway (primary or secondary)
US - US HIGHWAY OR ROUTE US Highway
NFST – NATIONAL FOREST SYSTEM TRAIL A forest trail that is under the jurisdiction of the Forest
NDT – NATIONALLY DESIGNATED TRAIL National Scenic, Historic, or Recreation trails
OT - OTHER TRAIL All other trails systems
OGM – OIL, GAS, MINERALS Sole purpose of the road is for Oil, Gas, or Mineral exploration
and/or production.

Private Land FS Land
Road Segment waiting to be

Road Segment Transfered to
transfered to State.
State because of
Improvements are being
improvements under the
planned under the Forest
Forest Highway Program
Highway Program.
System = SH System = NFSR

Jurisdiction = S Jurisdiction = FS
Other System = FH Other System = FH
Figure 6-7 Use of OTHER SYSTEM to code Forest Highways

Route Linear Events
Used in Tables:
Name: PRIMARY MAINTAINER RTE_LINEAR_EVENTS
Definition: The agency or party having primary (largest share) financial responsibility for maintenance.

Overlap: No

FS Required
Business 1.) Value should agree with the annual maintenance plan.
Rules:
2.) When another Forest Service unit maintains a road then the MANAGING_ORG linear
event will indicate which FS unit is maintaining it. This will eliminate double counting of
mileage when data is aggregated up to a regional or national level and clarify
maintenance responsibilities.
Notes:
Valid Codes
Code Description
BIA - BUREAU OF INDIAN AFFAIRS USDI Bureau of Indian Affairs
BLM - BUREAU OF LAND MANAGEMENT USDI Bureau of Land Management
BOR - BUREAU OF RECLAMATION USDI Bureau of Reclamation
C - COUNTY, PARISH, BOROUGH County, Parish, Borough
CO - COOPERATOR Cooperator (industrial cost share)
COE - CORPS OF ENGINEERS US Army Corps of Engineers
CU - COMMERCIAL USER Commercial user
DOD - DEFENSE DEPARTMENT US Defense Department
DOE - DEPARTMENT OF ENERGY US Department of Energy
FAA - FEDERAL AVIATION ADMINISTRATION USDOT Federal Aviation Administration
FS - FOREST SERVICE USDA Forest Service
FWS - FISH AND WILDLIFE SERVICE USDI Fish and Wildlife Service
L - LOCAL Town, Township, Municipal Agency (City or other local
civil government)
NPS - NATIONAL PARK SERVICE USDI National Park Service
OF - OTHER FEDERAL AGENCIES Other Federal Agencies
P - PRIVATE Private (profit & not for profit)
S - STATE State Agency
SH –STATE HIGHWAY State Highway Department
SLR – STATE LANDS ROAD State lands organizations (Department of Natural
Resources)
UNK – UNKNOWN Not known and needs to be resolved

Route Linear Events
Used in Tables:
Name: QUAD RTE_LINEAR_EVENTS
Definition: The USGS Quadrangle OR QUARTER QUADRANGLE location of the route.
Format: Local forest code / local forest format. Overlap: No
Linear Event: Yes

All Optional
Business 1.) Format: Local forest code / local forest format.

Rules:
2.) Enter the list of valid Quads into the Infra System library to ensure consistency in
recording this information.
3.) USGS Quadrangles shall be 1:24,000 quads for continental U.S., Puerto Rico, and
Hawaii and 1:63,360 for Alaska.
Notes: 1.) Currently used by units/organizations to locate roads where a gis coverage is not
available.
2.) Spatial attribute that should be populated from gis if desired.

Route Linear Events
Used in Tables:
Name: ROAD TEMPLATE RTE_LINEAR_EVENTS
The cross-section of the roadway outside the traveled way, including ditch, shoulder, or
Definition:
berm
Reference: FSH 7709.56 Section 4.24 Road Preconstruction Handbook Authority: WO

(5/87)
Overlap: No

FS Optional
Business
Rules:
Notes:
Valid Codes
Code Description
A - DITCH, SHOULDER, AND BERM Shoulder and Berm
B - DITCH AND SHOULDER Ditch and shoulder
C - DITCH AND BERM Ditch and berm
D - DITCH Ditch
E - SHOULDER Shoulder
F - SHOULDER AND BERM Shoulder and berm
G - BERM Berm
H - NO DITCH, SHOULDER, OR BERM No ditch shoulder or berm
P - PRIMITIVE Primitive, not constructed to a standard

Route Linear Events
Used in Tables:
Name: ROUTE STATUS RTE_LINEAR_EVENTS
Definition: Current physical state of being of the route segment
Reference: Federal Accounting Standards Advisory Board – 1998 Authority: WO

36 CFR 212.1, FSM 7703, FSM 7712
Overlap: No

All Required
Business 1.) Decommissioning eliminates all maintenance needs for the asset. (Fed Acct Stds
Rules: Advisory Board/ 1998). It results in the stabilization and restoration of unneeded
roads to a more natural state (36 CFR 212.1)
2.) Road Management decisions must be informed by travel analysis and disclosed in
an appropriate NEPA Document (FSM 7712.11). Only change the route status
through an appropriate decision document.
3.) Only change the Route Status after the appropriate NEPA decision has been made
and the work (if required) has been completed.
4.) Use this linear event to document decommissioning. Don’t delete the route from the
database and coverage. Temporary roads are a local decision to either remove or
preserve the data within INFRA.
5.) This linear event does not allow extensibility by the Forests.
Notes:
Valid Codes
Code Description
A route that was no longer needed and has been converted to
CV – CONVERTED
another use
A route that was no longer needed and has been removed from
DE - DECOMMISSIONED
service.
EX - EXISTING A route that physically exists.
Planned route identified in a completed NEPA document, with a
PL - PLANNED
Record of Decision.

Route Linear Events
Used in Tables:
Name: SERVICE LIFE RTE_LINEAR_EVENTS
Definition: The length of time that a facility is expected to provide a specified service
Reference: FSH 7709.59 Authority: WO
Overlap: No

FS Optional
Business 1.) If a road segment is coded as IS – INTERMITTENT STORED SERVICE it must also
Rules: be coded as Operational Maintenance Level 1.
Notes: 1.) Short term is defined as a facility developed and operated for a limited period of
time, which will cease to exist as a transportation facility after the purpose for which
it was constructed is completed, and the occupied land is reclaimed and managed
for natural resource purposes.
Valid Codes
Code Description
C - LONG TERM SERVICE Continuous or annual recurrent service
A road which is closed to vehicle traffic between periods of
I - INTERMITTENT TERM SERVICE
use. The closed period must exceed one year
Intermittent service road, closed to traffic. The road is in a
IS - INTERMITTENT STORED
condition that THERE IS LITTLE RESOURCE RISK IF
SERVICE
maintenance IS NOT PERFORMED. (self-maintaining).
S - SHORT TERM SERVICE Short term use (including temporary roads)

Route Linear Events
Used in Tables:
Name: SURFACE TYPE RTE_LINEAR_EVENTS
The wearing course; usually designed to resist skidding, traffic abrasion, and the
Definition:
disintegrating effects of weather.
Reference: EM 7720-100LL, Section 102 Authority: WO
Overlap: No

FS Required
State-County Required
All Other Optional
Business 1.) P - PAVED should only be used if type of hard surface cannot be reliably
Rules: determined.
2.) Required for State and County systems to assist with automated map production.
3.) If an admixture is used that is transient in nature, then code the surface as the
primary base material.
Notes:
Valid Codes
Code Description
AC - ASPHALT Asphaltic Concrete
AGG - CRUSHED AGGREGATE OR GRAVEL Crushed or screened graded material
Built up surface of asphalt emulsion and aggregate,
BST - BITUMINOUS SURFACE TREATMENT
not a dust palliative.
CSOIL - COMPACTED SOIL Compacted Native Material
Template has been cleared and rough shape
FSOIL – FROZEN SOIL completed but can’t be used until frozen conditions
exist.
Imported or processed material (pit run, select
IMP - IMPROVED NATIVE MATERIAL borrow, or admixture added to the surface soil and
compacted)
NAT - NATIVE MATERIAL No imported or processed materials
OTHER - OTHER Other Surface Type - Specify in Remarks
P - PAVED Unknown manufactured hard surface
PCC – PORTLAND CEMENT CONCRETE Portland Cement Concrete

Route Linear Events
Used in Tables:
Name: SYSTEM RTE_LINEAR_EVENTS
Definition: A network of travel ways serving a common need or purpose, managed by an entity with
the authority to finance, build, operate and maintain the routes.
Overlap: No

All Required
Business 1.) Overlapping Systems are not allowed. To record additional system designations on
Rules: a single route segment, use the OTHER SYSTEM linear event.
2.) NOT – NOT NEEDED designation can only be applied to roads with FS Jurisdiction.
3.) UND - UNDETERMINED designation will be applied to routes until the appropriate
system has been determined.
4.) The NOT and UND codes are only to be used for unauthorized roads.
5.) Forest Highways will be coded in OTHER SYSTEM and the primary system will be
the entity that has primary management of the road.
6.) Public Forest Service Roads are considered to be part of the National Forest
System Road (NFSR) system. See the PFSR CLASSIFICATION linear event in the
Appendix XX.
7.) BLM, NPS, BIA agency roads should be coded as OF - OTHER FEDERAL in
SYSTEM. The JURISDICTION should be coded as appropriate to the individual
agency.
8.) Road segments that are coded as NOT – NOT NEEDED should have the
OBJECTIVE MAINTENANCE LEVEL set to D – DECOMMISSION or C –
CONVERT USE.
9.) Not extensible by the local Forest.
Notes: 1.) System is not the same as Jurisdiction. Interstate and State highways are both
under State jurisdiction but belong to different System’s of roads.
2.) Valid codes are shown on the following page

SYSTEM continued
Valid Codes
Code Description
C - COUNTY, PARISH, BOROUGH County, Parish or Borough
I - INTERSTATE HIGHWAY Interstate Highway
Town, Township, Municipal Agency (City or other local civil
L - LOCAL
government)
A forest road other than a road which has been authorized
by a legally documented right-of-way held by a State, county
NFSR – NATIONAL FOREST SYSTEM ROAD or other local public road authority. (36 CFR 212.1, 36 CFR
251.51, 36 CFR 261.2). Previously known as FDR -
FOREST DEVELOPMENT ROAD
A road not needed for long term management of National
NOT – NOT NEEDED
Forest Resources (FSM 7712.01 B(2), (36 CFR 212))
OF - OTHER FEDERAL Other Federal Agency (such as BLM, NPS, BIA, etc.)
OS – OTHER STATE State roads other than those on the state highway system
P - PRIVATE Private
SH - STATE HIGHWAY State Highway (primary or secondary)
Roads authorized by contract, permit, lease, other written
authorization, or emergency operation not intended to be
TMP – TEMPORARY
part of the forest transportation system and not necessary
for long-term resource management. (36 CFR 212.1)
An existing road whose purpose and need has yet to be
UND - UNDETERMINED
determined.
US - US HIGHWAY OR ROUTE US Highway

Route Linear Events
Used in Tables:
Name: TEMPLATE SLOPE CODE RTE_LINEAR_EVENTS
Definition: The cross section of the traveled way
Overlap: No

FS Optional
Business
Rules:
Notes:
Valid Codes
Code Description
C - CROWN Surface Crowned
F - FLAT Surface Flat
I - INSLOPE Surface Insloped
O - OUTSLOPE Surface Outsloped
P – PRIMITIVE No constructed cross section (wheel track)

Travel Routes Data Dictionary
Used in Tables:
Name: TRAFFIC SERVICE LEVEL RTE_LINEAR_EVENTS
A description of the road's significant traffic characteristics and operating conditions. The
Definition: levels reflect a number of factors, such as speed, travel time, traffic interruptions,
freedom to maneuver, safety, driver comfort, convenience, and operating cost.

(9/87)
Overlap: No

FS Optional
Business
Rules:
Notes:
Valid Codes
Code Description
Free flowing, mixed traffic; stable, smooth surface.
A - FREE FLOWING MIXED TRAFFIC
Provides safe service to all traffic.
Congested during heavy traffic, slower speeds and

B - CONGESTED DURING HEAVY
periodic dust; accommodates any legal-size load or
TRAFFIC
vehicle
Interrupted traffic flow, limited passing facilities, may not

C - FLOW INTERRUPTED - USE
accommodate some vehicles. Low design speeds.
LIMITED
Unstable surface under certain traffic or weather.
Traffic flow is slow and may be blocked by management

D - SLOW FLOW OR MAY BE activities. Two-way traffic is difficult, backing may be
BLOCKED required. Rough and irregular surface. Travel with low
clearance vehicles is difficult. Single purpose facility.

Route Linear Events
Used in Tables:
Name: TRAVEL WAY WIDTH RTE_LINEAR_EVENTS
The width of that portion of the roadway used for the movement of vehicles; not
including turnouts, curve widening or shoulders. The traveled way provides space for the
Definition: design vehicle width and for necessary steering corrections and offtracking. For double-
lane roads, this width provides "head-on clearance," which is needed for vehicles
traveling in opposite directions to pass each other.

(5/87)
Format: 99 Unit of Measure: Feet
Overlap: No
Look Up: Linear Event: Yes

FS Optional
Business 1.) Round to the nearest foot.

Rules:
2.) Do not include the units of measurement within the value
Notes:

6.2 Linear Event Application Matrix
It’s important to recognize that only certain linear events are required for certain
systems. Figure 6-8 describes the linear events required for each system.
Road System Status
Forest Road Decommissioned/
Unauthorized Roads
Systems Converted1
Not
NFSR Other3 Undetermined
LINEAR EVENT2 Needed
ACCESS RIGHTS
ADMIN_ORG R R R R
CONGRESSIONAL DISTRICT R R R R
COUNTY R R R R
CRITICAL TRAFFIC
DESIGN SPEED
DESIGN TRAFFIC
FUNCTIONAL CLASS R
JURISDICTION R R R (if known) R
LANES R R
LEGAL
LEVELS OF TREATMENT
MANAGING_ORG R R R R
MILEAGE SOURCE
OBJECTIVE MAINT LEVEL R R R
OPER MAINT LEVEL R
OTHER SYSTEM R4
PRIMARY MAINTAINER R
QUAD
ROAD TEMPLATE
ROUTE STATUS R R R R R
SERVICE LIFE
SURFACE TYPE R R
SYSTEM R R R R R
TEMPLATE SLOPE CODE
TRAFFIC SERVICE LEVEL
TRAVEL WAY WIDTH
Figure 6-8 Required Linear Event Application Matrix
Code Description
R Required
Not Applicable
Optional
1
For decommissioned roads (ROUTE STATUS = DE), preserve existing values (optional for System=TMP).
2
Linear Events shown in Bold are required
3
Includes Federal, State, County, and Private Roads. Federal, State, and County roads should have records in
the oracle database. Forest Highways require geopolitical boundary information.
4
Only for those roads that have special designations such as Forest Highways, Scenic Byways, etc.

7 Record of Events Table
The Record of Events data structure is designed to hold date related linear event
information. That is, data that is date related that changes along a route. This is a
generic data structure that will allow storage of items such as construction and
decommissioning dates, when a road is designated or nominated in a scenic byway
program, or when there are route status changes (FSM 7711.1).
If roads undergo an event described under the CONSTRUCTION event, the date that
the work was completed is required. This data will be used to determine various
performance metrics for upward level reporting.
RTE_RECORD_OF_EVENTS
CN NOT NULL PRIMARY KEY Refer to Page 4-4
RTE_CN NOT NULL Refer to Page 4-5
EVENT NOT NULL Refer to Page 7-2
EVENT_SUBTYPE NOT NULL Refer to Page 7-3
EVENT_DATE NOT NULL Refer to Page 7-6
DATE_ACCURACY NOT NULL Refer to Page 7-7
BMP Refer to Page 4-6
EMP Refer to Page 4-6
REMARKS Refer to Page 4-8
CREATED_BY
CREATED_DATE
Refer to Section 4.1
MODIFIED_BY
MODIFIED_DATE
ACCOMPLISHED_BY Refer to Page 7-8
Figure 7-3 Record of Events Data Structure
Record of Events Table Travel Routes Data Dictionary Page: 1

Record of Events
Used in Tables:
Name: EVENT II_RTE_RECORD_OF_EVENTS
The event category for a record in the record of events table. It is the parent category
Definition:
for the event subcategories

All Optional
Business
1.) CONSTRUCTION event types are required to be entered when the event occurs.
Rules:
This is required for upward reporting of required performance metrics. Starting in
FY 2007 all construction event sub-types will be required. The minimum date
precision is the nearest year following the business rules in the DATE_ACCURACY
column.
Notes:
Valid Codes
Code Description
CHANGE ATTRIBUTE The date that important linear events or attributes were changed
CONSTRUCTION Related to construction, reconstruction, or decommissioning
DECISION DOC NEPA Planning Documentation
Special designations such as PFSR, Scenic Byway, etc. Must be

DESIGNATION
officially designated
INSPECTION Different types of physical inspections
LAND_EXCHANGE Changes in land ownership
NATURAL EVENT Events that naturally occur such as floods, etc.
NOMINATION Nominated for a special designation, not approved yet
Transportation Planning Documentation such as Travel Analysis,

PLANNING DOC
RMO, etc.
TRAVEL MGMT This Event type is no longer used - see ATM

Record of Events
Used in Tables:
Name: EVENT_SUBTYPE II_RTE_RECORD_OF_EVENTS
Definition: A subcategory of a parent event. This is used to classify the event.

All Optional
Business 1.) It’s recommended to use a GIS Coverage instead of recording NATURAL EVENTS in
Rules: this data structure. The data for natural events is truly spatial in nature and may have
additional information requirements that are not suitable to record here.
2.) When entering that a physical inventory was completed (real property inventory), enter
the name of the person doing the inspection in the remarks.
3.) CONSTRUCTION event types are required to be entered when the event occurs. This
is required for upward reporting of required performance metrics. Starting in FY 2007
all construction event sub-types will be required. The minimum date precision is the
nearest year following the business rules in the DATE_ACCURACY column.
Notes:
Valid Codes
EVENT EVENT_SUBTYPE Description
CHANGE
FC – FUNCTIONAL CLASS Change of Functional Class
ATTRIBUTE
J – JURISDICTION Change of jurisdiction
OP – OPER MAINTENANCE Change of operational maintenance level
LEVEL
OB – OBJ MAINTENANCE Change of objective maintenance level
LEVEL
RL – ROUTE LENGTH Change of road length
RN – ROUTE NUMBER Change of road number
RS – ROUTE STATUS Change of Route Status
SL – SERVICE LIFE Change of Service Life
CONSTRUCTION C - CONSTRUCTION Original construction

CV – CONVERTED Converted to a TRAIL or other System.
A road that has been stabilized to a more
DE - DECOMMISSIONED
natural state (36 CFR 212.1)
R – RECONSTRUCTION Reconstruction

DECISION DOC NEPA decision to ADD road segment to the
ADD – NEPA ADD
NFSR system
NEPA decision to convert the road segment to
another use. Removes road segment from
CV – NEPA CONVERT
NFSR system and adds it to another system
such as NFST or County.
NEPA decision to decommission the road
DE – NEPA DECOMMISSION segment. Removes road segment from NFSR
system.
NEPA decision to KEEP the road segment on
NK – NEPA KEEP
the NFSR system
NEPA decision that the undetermined road
NN – NEPA NOT NEEDED
segment is not needed.
NEPA decision to place the road segment in
NS – NEPA STORED storage as ML1. Road segment remains as a
NFSR
DESIGNATION FH – FOREST HIGHWAY Designated as a Forest Highway

LB – LOCAL BYWAY Designated as a local byway
PR – PUBLIC ROAD Designated as a Public Forest Service Road
SB – SCENIC BYWAY Designated as a Scenic Byway
OT – OTHER Some other designation, describe in remarks
INSPECTION Condition survey completed to record annual &

CS – CONDITION SURVEY deferred maintenance and capital improvement
needs.
Fish passage survey completed on all fish
FP – FISH PASSAGE
culverts on the route segment.
GPS – GLOBAL POSITION GPS Survey conducted on the road location.
SURVEY
MMUA – MOTORIZED Motorized Mixed Use Analysis and report
MIXED USE ANALYSIS completed.
Verified for existence for the real property
PI – PHYSICAL INVENTORY inventory. Enter the name of the inspector in
remarks.
LAND_EXCHANGE FP - FS TO PVT FS lands transferred to private jurisdiction.

PF - PVT TO FS Private lands transferred to FS jurisdiction.
FS – FS TO STATE FS lands transferred to state jurisdiction.
SF – STATE TO FS State lands transferred to FS jurisdiction.
NATURAL EVENT A - AVALANCHE Damage caused by an avalanche

FR - FIRE Damage caused by a wildfire.
F - FLOOD Flood damage – washout, ditch scour, etc

NATURAL EVENT Debris avalanche or rotational failure that
L – LANDSLIDE restricted or blocked any portion of the roadway
(Continued)
V - VOLCANO Damage caused by a volcano
O - OTHER Some other natural occurrence
NOMINATION FH – FOREST HIGHWAY Nominated as a Forest Highway

LB – LOCAL BYWAY Nominated as a local byway
PR – PUBLIC ROAD Nominated as a Public Forest Service Road
SB – SCENIC BYWAY Nominated as a Scenic Byway
OT – OTHER Some other Nomination, describe in remarks
PLANNING DOC Travel analysis complete, recommend road

ADD – TAP ADD
segment be added to the NFSR system
Travel analysis complete, recommend road
segment be removed from NFSR system and
CV – TAP CONVERT
converted to a other system such as NFST or
County
DE – TAP DECOMMISSION segment be decommissioned and removed from
the NFSR system.
KP – TAP KEEP segment needed for long term management and
remain as a NFSR.
Travel analysis complete, recommend
NN – TAP NOT NEEDED undetermined road segment not needed and
should not be added to the NFSR system.
Road Management Objective is complete
RMO – RMO COMPLETE As of 10/2008 this may only be populated from
the RMO module.
TAP – TAP COMPLETE Travel analysis complete.
TS – TAP STORE segment be placed in storage as ML1. Road
segment remains as a NFSR
TRAVEL MGMT OY – OPEN YEARLONG Changed to Open Yearlong

RS – RESTRICTED Changed to seasonal restriction
This event type SEASONALLY
disabled 4/09
RY – RESTRICTED YEARLONG Changed to yearlong restriction
Travel management
information is CS – CLOSED SEASONALLY Changed to seasonal closure
recorded in ATM CY – CLOSED YEARLONG Changed to yearlong closure

Record of Events
Used in Tables:
Name: EVENT_DATE II_RTE_RECORD_OF_EVENTS
Definition: The date that the event occurred
Data Type: Date Mandatory: Yes

All Optional
Business 1.) If an event is only known to a precision of one year, record the date as if it occurred
Rules: on the January 1 of that year. For example, if it were known that a road was
constructed in 1984, it would be recorded as 1/1/1984. The DATE_ACCURACY
would be set to Y – ESTIMATED YEAR.
2.) If an event is only know to a precision of one decade, record the date as if it
occurred on January 1 of the first year of the decade. For example, if it was known
through progressive aerial photography flights that a road was built in the 1960’s,
record it as 1/1/1960. The DATE_ACCURACY would be set to D – ESTIMATED
DECADE.
Notes:

Record of Events
Used in Tables:
Name: DATE_ACCURACY II_RTE_RECORD_OF_EVENTS
Definition: The confidence of the event date

All Optional
Business
Rules:
Notes:
Valid Codes
Code Description
K – KNOWN Date is known to the nearest day
Y – ESTIMATED YEAR Date is estimated to nearest year
D – ESTIMATED DECADE Date is estimated to nearest decade

Record of Events
Used in Tables:
Name: ACCOMPLISHED_BY II_RTE_RECORD_OF_EVENTS
Definition: The name of the person(s) who conducted the inspection or survey

Business Condition survey records are required to record the person(s) who actually conducted
Rules: the survey. This is an auditing requirement
Notes: Before the Accomplished by field was added, the names of the persons conducting the
survey were recorded in the Remarks field.

8 Coding Scenarios
To assist the reader with implementation of the data dictionary, a set of common
scenarios have been developed. These scenarios are intended to demonstrate how
linear events and other road modules work together to depict different situations as a
road is worked through administrative and physical processes.
Field values shown in the scenarios represent typical coding situations. Specific values
will depend in on local forest decision documents. They do not represent all of the
mandatory values required for NFS roads.
Abbreviations used in these scenarios:

NFS – National Forest System
MVUM – Motor Vehicle Use Map
Coding Scenarios Travel Routes Data Dictionary Page: 1

Index of Scenarios
Scenario Page
Description Number
Number
An unrecorded existing road is found. It is open and being used by high
1
clearance traffic. An analysis determines that it is needed for long-term access 8-3
2 Decommission an existing national forest system road 8-4

3 Convert an existing national forest system road to a trail 8-4
Government needs to obtain an easement from a private landowner on road
4a open and available for forest access. 8-5
Governmentneeds to obtain an easement from a private landowner on road
4b not currently providing access to the National forest. 8-5
5 New temporary timber access road. 8-6

NFS road turned over to local government (Town, Township, Municipality), and
6 added to Forest Highway system. 8-7
Old road constructed by the FS under the temporary road provisions of the
timber sale contract was never properly “closed out”. It is currently not in the
7 roads atlas. It is open but is not designated for motor vehicle use on the 8-8
MVUM.
Forest Service & County enter into a Forest Road Agreement covering an
8a existing NFS Road.County will not accept jurisdiction but is willing to assume 8-8
responsibility for annual maintenancce.
Forest Service & County enter into a Forest Road Agreement covering an
8b existing County Road. 8-8
9a Oil & Gas Roads with public use 8-9

9b Oil & Gas Roads with administrative use only. 8-9
A record exists in INFRA for an NFSR road, but a field inspection cannot find
10 evidence of the road. 8-10
11a Grown in road with outstanding resource issues 8-3

11b Grown in road with no resource issues to address 8-3
A road and non-motorized trail occupy the same template for all or part of the
12 road/ trail 8-3

Scenario #1:
ne An existing road is found that is not recorded in the road
atlas. It is open and being used by high clearance vehicles.
An analysis determines that it is needed for long-term Route Obj Oper Serv
access System Juris Status ML ML Life
An existing road is found during a field review. The road
provides access to NFS land and is illegally being used by
high-clearance vehicles. It is not recorded in the INFRA Travel
UND EX
Routes data base nor shown on any local administrative or
transportation maps. It has not been designated for Motor
Vehicles and is not displayed on the MVUM.
Research is unable to determine jurisdiction. Since it is on NFS
UND FS EX
land, it becomes Forest Service jurisdiction by default.
Following appropriate analysis, a travel management decision is
made to place the road on the system and manage for long-
term intermittent use. The route is designated for Highway NFSR FS EX 1 2 IS
Vehicles and shown on the MVUM for the current use
period.
Upon completion of the current use period, the road is placed in
storage (ML1) and is not designated for motor vehicles. It will NFSR FS EX 1 1 IS
not be displayed on the MVUM.
Optional: Add appropriate change attribute records to the Event = DECISION DOC
Record of Events table (System, ML). Event_Subtype = ADD – NEPA ADD
Date Accurary: Known or Year
Mandatory – add appropriate records in the ATM module for
any motor vehicle designation.

Scenario #2: Route Obj Oper Serv
Decommission an existing NFS road. System Juris Status ML ML Life
An existing NFS road is in the road atlas The road is
designated for highway vehicles and is displayed on the NFSR FS EX 3 2 C
MVUM.
Following appropriate analysis, a decision is made to
decommission the road. The road is kept open during the
NFSR FS EX D 2 C
interim and designated on the MVUM as a road open to
Highway Vehicles.
Decommissioning activities have been completed. By only
changing the “Route Status” value, the old data is preserved. NFSR FS DE D 2 C
The road will not display on the MVUM.
Mandatory: Add appropriate records to the Record of Event = CONSTRUCTION
Events table to indicate when the decommissioning was Event_Subtype = DE – DECOMMISSION
done and the change attribute records ( STATUS, OBl ML) Date Accurary: Known or Year
Work Items – add decom activities, close
Optional: data cleanup others
Features - Status
Mandatory – add or remove appropriate records in the ATM
module for any motor vehicle designation.

Convert an existing NFS road to a trail. System Juris Status ML ML Life
The following information represents the Infra ROAD record.
An existing NFS road is in the road atlas and designated for
NFSR FS EX 1 2 I
Highway Vehicles on the MVUM.
Following appropriate analysis, a decision is made to convert
the road to a non-motorized NFS trail. The route is not
NFSR FS EX C 2 I
designated for motor vehicles during the interim. Delete any
motor vehicle designations in ATM.
Conversion activities have been completed. By only changing
the “Rte Status” value, the old data is preserved. Be sure to NFSR FS CV C 2 I
add the new trail in Infra Travel Routes (see below).
Event = CONSTRUCTION
Mandatory: Add appropriate records to the Record of
Event_Subtype = CV - CONVERTED
Events table to indicate when the conversion was done.
Mandatory – add appropriate records in the ATM module for
any motor vehicle designation.
The following information represents the corresponding Infra TRAIL record.
Planned forest trail. (Created following NEPA decision on road.) NFST FS PL
Conversion activities have been completed. NFST FS EX

Scenario #4a:
Government needs to obtain an easement from a private Route Obj Oper Serv
System Juris
landowner on a road that is open and available for forest Status ML ML Life
access.
An existing private road is currently being used to provide
administrative and public access the National Forest. The P P EX
forest has not been managing or maintaining the road.
Following appropriate analysis, a decision is made that the
road should be managed as a system road for long-term use
and that a permanent easement is needed. The road is not NFSR P EX 3 2 C
designated for motor vehicles and is not displayed on the
MVUM during the interim.
A permanent easement is obtained. The road is now
designated for Highway vehicles and is displayed on the NFSR FS EX 3 2 C
MVUM.
Capital improvements are complete, and the road is now
NFSR FS EX 3 3 C
being maintained to the desired standard.
Event = CHANGE ATTRIBUTE
Optional: Add appropriate record(s) to the Record of
Event_Subtype = JURISDICTION
Events table.
Mandatory – Add appropriate records in the ATM module
for any motor vehicle designation.
Add appropriate records in the Authorizations module.
Scenario #4b:
Government needs to obtain an easement from a
private landowner on road not currently providing Route Obj Oper Serv
access to the National Forest. System Juris Status ML ML Life
An existing private road is not available for forest access P P EX
Following appropriate analysis, a decision is made that the
road is needed for long term access to the NF and that a
permanent easement is needed Condemnation may be
P P EX
necessary Administrative and public traffic is not allowed
during the interim The road is not designated for motor
vehicles or shown on the MVUM.
A permanent easement is obtained. The road is designated
NFSR FS EX 3 2 C
for Highway Vehicles and shown on the MVUM.
Capital improvements are complete, and road is now being
NFSR FS EX 3 3 C
maintained to the desired standard.
Optional: Add appropriate record(s) to the Record of Event = CHANGE ATTRIBUTE
Events table. Event_Subtype = JURISDICTION
Mandatory – add appropriate records in the ATM
module for the motor vehicle designation.
Add appropriate records in the Authorizations module.

New temporary timber access road. System Juris Status ML ML Life
Following appropriate analysis, a decision is made to
access a timber management area with a temporary road.
TMP FS PL S
While it is not required nationally, the Forest Plan requires
tracking and management of all temporary roads
The timber sale is sold and the temporary road is
TMP FS EX S
constructed.
The sale is closed, and the road has been
decommissioned according to the requirements of the TMP FS DE S
decision document.
Note: Add appropriate record(s) to the Record of
Events table – temporary roads are not required to be
Event = CONSTRUCTION
placed into the inventory. If however, the road has
Event_Subtype = DE – DECOMMISSION
been input and has been decommissioned, a record
placed into record of events is required.
Notes: Optional: Delete route from Infra database and linework from the travel routes coverage.

Scenario #6:
NFS road turned over to local
government (Town, Township,
Municipality), and added to Forest Other Route Obj Oper Serv
Highway system. System System Juris Status ML ML Life
Existing NFS road receives significant
volumes of local public residential traffic
not related to forest management. The NFSR FS EX 5 3 C
road is designated for Highway Vehicles
and displayed on the MVUM.
Forest meets with the local government
and jointly proposes the road be added to
the Forest Highway system; and that the
local government take over all operation
and maintenance responsibility following
NFSR FS EX 5 3 C
completion of capital improvements
necessary to meet their standards.
Coding does not change until road is
designated. Use remarks field to track
proposed designations.
Road is designated a Forest Highway by
the tripartite team (State DOT, FHWA, NFSR FH FS EX 5 3 C
Forest Service).
Contract completed, and jurisdiction has
been transferred through issuance of a
USDOT Easement. If only a segment of
the designated Forest Highway is included Delete data which no
L FH L EX
in the completed project, change only the longer applies.
coding for the affected segment: The road
will now show on the MVUM as a Public
Road
Optional: Add appropriate record(s) to Event = CHANGE ATTRIBUTE
the Record of Events table. Event Subtype = JURISDICTION, SYSTEM
Mandatory – Add appropriate records in Remove ATM data when road is transferred to the Local
the ATM module for any motor vehicle Jurisdiction.
designation on NFSRs.
Add appropriate records in the
Authorizations module.

Scenario #7:
Old road constructed by the FS under the temporary road
provisions of the timber sale contract was never properly
“closed out”. It is currently not in the roads atlas. It is
open but is not designated for motor vehicle use on the Route Obj Oper Serv
MVUM. System Juris Status ML ML Life
An existing road is found during a road condition survey, and,
because it is located on NF land, it is assumed to be an old
“temporary” timber access road which was never “put to bed”.
Since the timber contract has long since been closed, it is no UND FS EX
longer a “temporary” road. It is now an “unauthorized” road.
Until a decision is made on the long-term need of this road it is
shown as “Undetermined”.
While the original decision document stated the road was
intended for temporary access to timber sale units, it is no
longer valid due to its age. Following appropriate analysis, the NOT FS EX D
decision is made that the road is not needed for long-term use,
and it is to be decommissioned.
Decommissioning activities have been completed. NOT FS DE D
Mandatory: Add appropriate record(s) to the Record of
Events table to indicate when the decommissioning was Event = CONSTRUCTION
done. Because the road is in the database, a record in the Event_Subtype = DE – DECOMMISSION
record of events is required. Date Accurary: Known or Year
Scenario #8a:
Forest Service & County enter into a Forest Road
Agreement covering an existing NFS Road. County
will not accept jurisdiction but is willing to assume Route Obj Oper Prim
responsibility for annual maintenance. System Juris Status ML ML Maint
Existing NFS road is serving as a major link to the County
NFSR FS EX 4 4 FS
or State road system.
Forest Road Agreement signed and Maintenance Plan
NFSR FS EX 4 4 C
implemented
Add appropriate records in the Authorizations
module.
Scenario #8b:
Forest Service & County enter into a Forest Road Route Obj Oper Prim
Agreement covering an existing County Road. System Juris Status ML ML Maint
Existing County road is serving as a major link to the
National Forest Road System. The County does not want
C C EX C
to give up jurisdiction but is willing to let the Forest
Service maintain the road.
Forest Road Agreement signed and Maintenance Plan
C C EX 4 4 FS
implemented
Add appropriate records in the Authorizations
module.

Scenario #9a: Other Route Obj Oper Serv
Oil & Gas Roads with public use. System System Juris Status ML ML Life
Road is built for exploration of oil & gas. TMP OGM FS EX S
Well goes into production. The public is allowed to
use the road. The road is designated for Highway NFSR OGM FS EX 3 3 C
Vehicles on the MVUM.
After the well is abandoned, appropriate analysis
determines it’s still needed for forest access. The
NFSR OGM FS EX 3 3 S
road is designated for Highway Vehicles on the
MVUM.
Mandatory: Add appropriate record(s) to the ATM module
to indicate any Motor Vehicle designation.
See Appendix A – Figure 12-2 Oil, Gas, and Minerals Road Coding Flow Chart
Scenario #9b: Other Route Obj Oper Serv

Oil & Gas Roads with administrative use only. System System Juris Status ML ML Life
Road is built for exploration of oil & gas. TMP OGM FS EX S
Well goes into production. The public is not
allowed to use the road. In addition to the oil
company traffic, only administrative FS traffic is NFSR OGM FS EX 2 2 C
allowed. The road is not designated for Motor
Vehicles on the MVUM
After the well is abandoned, appropriate analysis
determines it’s no longer needed, but road is not yet NFSR OGM FS EX D 2 S
decommissioned.
Road is decommissioned
(Note: Linear event values are preserved from last NFSR OGM FS DE D 2 S
known state)
Mandatory: Add appropriate record(s) to the Record of Event = CONSTRUCTION
Events table to indicate when the decommissioning was Event_Subtype = DE – DECOMMISSION
done Date Accurary: Known or Year
See Appendix A – Figure 12-2 Oil, Gas, and Minerals Road Coding Flow Chart

Scenario #10:
A record exists in Infra for an NFS road, but a field Route Obj Oper Serv
inspection cannot find evidence of the road. System Juris Status ML ML Life
NFS road exists in INFRA. Its location is shown on
older administrative or transportation maps. It has not
NFSR FS EX 3 1 I
been designated for Motor Vehicles and is not shown
on the current MVUM.
During physical inventory, no trace of the road is
found
on the ground. There is no evidence that the road
existed – no contract document, no photos showing a
NFSR FS EX 3 1 I
location, no NEPA documentation of any
decommissioning decisions, no records other than the
entry in INFRA and the location on the Administrative
maps
If there is no evidence that the road ever existed, it
could be a mapping error, something that had been
planned but never built. This is considered to be a
data error. Delete the record from Infra, and remove
any line work from the Travel routes coverage Delete Delete Delete Delete Delete Delete
pertinent to this “non-existent” road. There would be
no reporting of the road as having been
decommissioned. No TAP is necessary to correct
erroneous data in the inventory.
Scenario #11a: Route Obj Oper Serv

Grown in road with outstanding resource issues System Juris Status ML ML Life
A NFS road exists in INFRA. Its location is shown on
local administrative or transportation maps. It has not
NFSR FS EX 1 2 C
been designated for Motor Vehicles and is not shown
on the current MVUM.
During physical inventory, traces of the road are found
on the ground. The road is heavily grown in and
obviously has not provided any vehicle access for
many years. The road would require major
reconstruction work to open and make available for
NFSR FS EX 1 1 I
use. There is no NEPA documentation of any
decommissioning decisions, no records of closure, no
RMO. An inspection of the road finds outstanding
resource issues that need to be corrected. Correct the
erroneous OPR ML record n INFRA.
The road cannot be removed from the system until there
is a documented decision that it is no longer needed
and should be decommissioned. The road cannot be NFSR FS EX 1 1 I
declared decommissioned with outstanding resource
issues. Travel analysis is now required.
Following appropriate analysis, a decision is made that
the road is not needed for long-term use, and it is to be NFSR FS EX D 1 I
decommissioned.
Decommissioning activities have been completed. NFSR FS DE D 1 I
Mandatory: Add appropriate record(s) to the Record Event = CONSTRUCTION
of Events table to indicate when the Event_Subtype = DE – DECOMMISSION
decommissioning was done - STATUS, OBJ ML, Date Accurary: Known or Year

Scenario #11b: Route Obj Oper Serv
Grown in road with no resource issues to address. System Juris Status ML ML Life
A NFS road exists in INFRA. Its location is shown on
local administrative or transportation maps. It is no
longer open or available for vehicle access. It has not NFSR FS EX 1 2 C
been designated for Motor Vehicles and is not shown on
the current MVUM.
During physical inventory, traces of the road are found
on the ground. The road is heavily grown in and
obviously has not provided any vehicle access for many
years. The road would require major reconstruction
work to open and available for use. There is no NEPA
documentation of any decommissioning decisions, no NFSR FS EX 1 1 I
records of closure, no RMO. An inspection of the road
determines no outstanding resource issues that need to
be corrected. In effect, the road has been naturally
decommissioned. . Correct the erroneous OPR ML
record n INFRA.
The road cannot be removed from the system until there
is a documented decision that the road is no longer
needed and should be decommissioned. Roads analysis
is now required to decommission the road. The level of NFSR FS EX 1 1 I
analysis may be minimal since the road has not been
open and available for use and there are no outstanding
resource issues.
Following appropriate analysis, a decision is made that
the road is not needed for long-term use. It is declared NFSR FS DE D 1 I
decommissioned and removed from the system
Mandatory: Add appropriate record(s) to the Record Event = CONSTRUCTION
of Events table to indicate when the Event_Subtype = DE – DECOMMISSION
decommissioning was done Date Accurary: Known or Year
Used by: (Roads) (Trails) (Both) (Both) (Roads)

Scenario #12:
A road and non-motorized trail SYSTEM TRAIL OTHER
JURIS STATUS
occupy the same template for all SYSTEM SYSTEM
or part of the road/ trail.
NFS Road 123 shares the NFST
NFSR FS EX
template with NFS Trail 456 from MP 2 – 3.5
0 4.5 0 4.5 0 4.5
Road MP 2 to 3.5. (B  C)
NFS TRAIL 456 shares the FS
NFST EX
template with NFS Road 123 from 0
0  3.2 0  3.2
Trail MP 1 to 2.5. 3.2

A 0.0
3.2
B F
Road 123
C
0.0
Trail 456
E 4.5
Use the Route to Route Links to indicate the portion of roads and trails that are shared systems.
ID BMP EMP Overlap Section (B – C)

123 0.0 4.5 2.0 -> 3.5
456 0.0 3.2 1.0->2.5
Spatial:
1. Build and calibrate a route for Road #123 and place it in the ROAD route system of the travel_route
coverage. The route is built from selecting arcs A-B, B-C, C-D. The route is calibrated to the
RTE_BASICS table for Road 123 which has a BMP = 0.0 and an EMP = 4.5
2. Build and calibrate a route for Trail #456 and place it in the TRAIL route system of the travel_route
coverage. The route is built from selecting arcs E-B, B-C, C-F. The route is calibrated to the
RTE_BASICS table for Trail 456 which has a BMP = 0.0 and an EMP = 3.2.

9 Special Situations
9.1 Roads Policy Initiative and Unauthorized Roads
There is a sequence of events that will typically happen when inventorying
unknown roads. The following sequence describes the events and actions
that would be taken as a road is found in the field and as it is evaluated
through the Travel Analysis Process. The flow diagram shown in Figure 12-1
shows how coding would be done as a road works through the Travel
Analysis Process.
1. Event: Road is “found” in the field.
 Road number is assigned (see next section) and the basic route
information (RTE_BASICS) is populated in Oracle.
 Road alignment is added to the GIS Coverage, route system built
and linked to Oracle.
 Populate SYSTEM linear event to UND – UNDETERMINED. Road
has not gone through Travel analysis or NEPA yet.
 Populate ROUTE STATUS linear event to EX – EXISTING as the
road exists.
2. Event: Jurisdiction is determined
 Populate JURISDICTION linear event as
appropriate.
3. Event: Travel analysis – Decision made that the road is needed
 Assign a new number to the road that is consistent with numbering in
the region.
 Change the route number in Travel Routes and in the GIS Coverage
 Change SYSTEM linear event to NFSR – NATIONAL FOREST
SYSTEM ROAD or as appropriate for other system classifications if the
jurisdiction is other than Forest Service.
 Populate all required linear events based on the approved RMO and
field data
4. Event: Travel analysis – Decision is made that the road is not needed
 Change SYSTEM linear event to NOT – NOT NEEDED
 Populate OBJECTIVE MAINT LEVEL to D – DECOMMISSION if the
decision has been made to decommission the route or C - CONVERT
USE if the route will be converted to some other use. Only change the
OBJECTIVE MAINT LEVEL after an appropriate decision document has
been completed (travel analysis is not a decision document).
Special Situations Travel Routes Data Dictionary Page: 1

Numbering of unknown/unauthorized roads is problematic. Most regions are
already using some system to number these roads. Some regions do not have
the capability to map these routes at the time they are discovered and therefore
need some intelligence on location built into the road number. The diagram in
Figure 9-4 shows a recommended (not required) approach to numbering these
roads in the database and on the GIS coverage. In all cases, if a road is added
to the system through travel analysis and an approved RMO, the road number
will need to be changed so that it’s compatible with the forests road numbering
strategy. Unknown/unauthorized routes will be entered as a separate road
number and not just a continuation of an existing NFSR road number.

2
R-
23
0-1.
00
02
64
1
R-
- 1.23
00
0 20
64 6402000-1.23R-3
MP = 1.23
640200
0-1.23 640
R-5 20 00-
1.23
R -4
6402000-1.23R-7
640200
0-1.23
R-6
8
R-
.23
0
00
0-1
02
64
6402000-1.23R-11
00
02
64
0
-1 6402000-1.23R-9
R
23
1.
0-
00
02
64
Road number may be assigned as follows:
Parent#+MP+Direction+Sequence Number separated by a hyphen
A road that comes off of route 2808032 at mp 1.23 and goes right
(in direction of increasing measure) would be 2808032-1.23R-1
Figure 9-4. Road Numbering Strategy for Unknown/Unauthorized Roads

9.2 Campground Loops
Campgrounds are a unique situation in that most contain a series of loops that
access vehicle length spurs into the actual campsites. The loops should be on
the National Forest Service Road system (NFSR) as they are part of the long-term
transportation network. However, loops are not typically signed with a route
marker and have traditionally been lumped into the mileage for the primary road
that accesses the campground. This is no longer possible when the spatial
situation is considered. Each loop is a spatially unique alignment and as such
must be identified and labeled in both the spatial and tabular data. A typical
campground scenario is shown in .
Accurate loops in routed gis coverage’s are possible but require special
techniques to build and maintain because of the ambiguity in the directionality of
the route. If the arcs intersect, a route can still be built but it must be built in
several steps by selecting the arcs that don’t cross, building a route, then building
another route with the arcs that cross and finally appending the later route to the
first route. While this process will work, it doesn’t lend itself to automated
processing and requires specialized effort.
The recommended alternative is to leave a small break where the loop comes
back onto itself. The size of this break should be greater than the fuzzy tolerance
for the coverage (typically > 1 meter). It’s highly recommended to create a small
break, as the route system will be much easier to maintain.
The numbering of the loops is another issue. Use the parent route number of the
road that accesses the campground then append a hyphen and an alpha (i.e.
9027000-B) for the loop designation.

Note:
campsite spurs are
not considered part of
the FSR Road
System. They are
terminal facilities and
0
tracked as a
00 PARKING FA.CILITY
00
90
-A
0 00
27
90
90
27
00
0
B
0-
00
27
90
Note:
Leave a small break betwen
the end of the loop and the
beginning of the loop to
facilitate easy creation of the
route. Break size should be
> Fuzzy Toleranace of the
coverage.
If a route crosses itself, it

has to be built in two steps
because of the ambiguity in
route direction.
Figure 9-5. Campground Loops

9.3 Decommissioning Portions of Through Routes or Planned Route
Connections
It is relatively common to consider decommissioning of a portion of a route that

has access from both ends. This typically occurs because of extensive damage
to the road from natural disasters (floods, etc.). The other situation where this
can occur is when a through route is planned and construction is completed from
both ends but never connected. The general scenario is shown in Figure 9-6.
While this situation can be modeled in the spatial and tabular data, there are
ramifications of the strategy used.
0.0
0
00
600
2
250000
0
3.51
Section
Decommissioned
5.70
11.90
990000
0
Figure 9-6. Decommissioning a part of a through route

There are two cases that can arise:
1. In the case of a decommissioned segment, the entire alignment of the
road already exists within the road coverage. In this case, add several
records to the linear events for the route that changes the route status.
The entries for the road are shown in Figure 9-4a. Don’t remove the
alignment of the decommissioned segment from the coverage. Calibration
of the route will remain as it had. However, it’s recommended to closely
review the management objectives for the road and consider re-
numbering the routes. If the route will have two different road numbers,
they are treated as two different routes.

0.0 3.51 ROUTE STATUS EX – EXISTING
3.51 5.70 ROUTE STATUS DE – DECOMMISSIONED
5.70 11.90 ROUTE STATUS EX – EXISTING
Figure 9-4a. Example Decommissioned Route Section
2. At one time the road was planned as a through route but the segment
within the middle was never built. In this case, a discontinuous route
needs to be used. Calibration is the real issue and the calibration of each
portion of the route needs to be done independently. Hopefully, the mile
posting was done with some thought and there aren’t two beginnings of
the route (i.e. a bmp of 0.0 at both ends) in which case the routes need to
be renumbered. If the route has continuous measures the following
procedure should be used in ArcEdit:
 Create the route system by selecting the arcs then use the
makeroute command.
 Change the edit feature to the route.subclass and make sure
the route is selected
 Use the subselect command to select only the sections of the
first segment
 Use the remeasure command to set the bmp emp (remeasure
0.0 3.51 measure)
 Use the subselect command to select only the sections of the
last segment
 Use the remeasure command to set the bmp emp (remeasure
5.70 11.90 measure)
It’s highly recommended that the management objectives and long-

term transportation needs be reviewed. In many cases the land
management objectives have changed and there is no need for the
through route anymore. In this case, the road segments should be
re-numbered into two different routes, re-signed, and processed
normally.

9.4 Dual Route Designations
This situation arises when there is a segment of road that either has a dual
route designation or junctions with another route or continues in another
location as shown in Figure 9-7. These situations were not modeled in the
design of Travel Routes. Dual route or offset route designations are
discouraged, as they are confusing to the public. However, if local conditions
warrant their use, the following work around(s) can be used.
46
72
00
4670000
0
00 0
4671
46
72
00
0
Figure 9-7. Dual Route General Case

The basic principle is to model the dual route without double counting the
mileage and double entering the events for the shared segment of road.
First, decide on which route is the through route. In the example shown in
Figure 9-7, Road 4671000 is the through route. Create the route system and
calibrate the route normally.

There are then two options:
1. Create the route as a discontinuous route without including arc B-C
(Figure 9-8). It’s recommended to milepost the road as shown in Figure
9-8 with no increment in the mile posting. This means that you can
calibrate the entire route with the remeasure command in arcedit in one
step (remeasure 0.0 6.0 measure). This is the easiest solution and is
recommended in most cases. The linear events and features for the
4672000 road would be entered normally in travel routes as shown in
Figure 9-.
A
0.0
46
72
4.9
00
4670000
0
000
4671
3.3
B
3.0
3.0
C
2.5
0.0
46
72
00
Note: 0
4671000 is through route
6.0
D
Figure 9-8. Shared Routes - Discontinuous Alternative
Road BMP EMP Linear Event Value

4671000 0.0 4.9 ROUTE STATUS EX - EXISTING
Figure 9-6a. Shared Routes - Discontinuous Route, Linear Events
Road BMP EMP

4671000 0.0 4.9
4672000 0.0 6.0
Table 9-6b Route Basics data for Alternative 1

2. Create the route as a continuous route and increment the mile posting
on the shared segment. In this case the route would be built from the
arcs A-B, B-C, C-D as shown in Figure 9-9. The mile posting for road
4672000 would be revised to increment through the shared segment.
A
0.0
46
72
4.9
00
4670000
0
00 0
4671
3.3
B
3.0
3.8
2.5 C
0.0
46
72
00
Note: 0
4671000 is through route
6.8
D
Figure 9-9. Shared Routes - Continuous Alternative

In this case, the route system is simply built and calibrated as normal.
The linear events in INFRA though would show a gap in the route as
shown in Figurer 9-7a. The data in the RTE_BASICS table (Figure 9-
7b) would show the length road 4672000 as 6.8 miles when in reality the
road is only 6.0 miles long without the overlap. This alternative is spatially
more accurate than Alternative 1 and would allow placement of road
numbers on maps with both designations.
Road BMP EMP Linear Event Value
Figure 9-7a. Shared Routes - Continuous Route, Linear Events
Road BMP EMP

4671000 0.0 4.9
4672000 0.0 6.8
Figure 9-7b Route Basics data for Alternative 2

9.5 Y Intersections
In many parts of the country, Y-type intersections have been constructed as
shown in Figure 9-10. Although this is against current design policy, there are
numerous places on the ground where it occurs. Typically, the back leg of the Y
intersection is 100’ or less in length.
Prim Not Routed

ary D or Attributed
irecti
o
or Us n of Hau
e l
Attributed
Collector Road
Figure 9-10. Y Intersection

It’s highly recommended to not try to attribute or route the back leg of the
Y intersection. This will eliminate calibration and routing problems in the
coverage.
The following is recommended:
1. Determine the leg of the Y that is in the direction of primary haul or
use
2. Attribute the arcs of the primary route as normal
3. Don’t attribute the arc that is the alternate leg of the Y-Intersection
and don’t route it.

9.6 Duplication of Another Unit’s Data
Sometimes it’s desirable at the local level to duplicate spatial and tabular data
of a route system from another forest’s database. Typically this happens in the
following situations:
1. When a neighboring forest wants to have the data in their database for
display and analysis purposes. Please note that this reason is not
wholly supportable. A connection can be made to another forests
database in the GIS software (Arc/Info or ArcView). However, it does
make it more cumbersome to work with as queries have to be
duplicated against another database instance.
2. When one unit manages the route, but through agreement, another
unit maintains the route.
The problem with just adding the duplicated tabular data is that mileage and
maintenance needs summaries that are aggregated up the chain of command
will be duplicated. To prevent this situation, the forest that is managing the
route on another forest should codify JURISDICTION = OFS – OTHER
FOREST SERVICE. All queries at regional and national levels run against
ROUTE STATUS = EX, JURISDICTION = FS and therefore these identical
road miles will only be counted once.
The example in Figure 9-11 shows two forests that share a common border
with a state highway providing main access to both forests. Forest 2 manages
Road 7518 as it's closer to their road management and maintenance
organizations.

6.0
Forest 1
(Org = 090103)
3.0 Road Managed

by Forest 2
Forest 2
(Org = 090205)
18
75
0.8
0.0
NH-5
Private Land
State Highway
0.0
Figure 9-11 Use of MANAGING_ORG
Forest 1’s Forest 2’s

Segment Linear Event Database Database
0.0 – 3.0 ADMIN_ORG 090205 090205
MANAGING_ORG 090205 090205
JURISDICTION OFS FS
PRIMARY MAINTAINER FS FS
3.0 – 6.0 ADMIN_ORG 090103 090103
MANAGING_ORG 090205 090205
JURISDICTION FS OFS
PRIMARY MAINTAINER FS FS
Figure 9-9a Road 7518 Coding Chart

10 Glossary
10.1 Travel Routes Terms
 Arc. A line defined as a set of ordered x, y coordinates used to represent linear

features and polygon boundaries.
 Attribute/Column. A field within a database table.
 Authority. A code to denote who is the managing authority for codes and linear
events. Currently this can be set to WO (Washington Office), REGION (Regional
Office) or FOREST (individual national forest).
 Child Table. A table within a relational database that is related to another table. The
child table usually has multiple records in it related to the other (parent) table.
 Code Structure. Used to denote where a code for a linear event is a child of another
code. This can be used to establish a hierarchy between codes and develop a lineage
so that different codes can be aggregated up to one unique code. See the INFRA
Administrators User Guide for more information on Code Structure.
 Concatenated. A term for when two or more character strings are merged together.
For example, if X = Green and Y = Tree the concatenation of X & Y would be
“GreenTree”.
 Coverage. An Arc/Info term for a set of feature classes representing geographic
features. Each feature class stores a set of points, lines (arcs), polygons, or
annotation (text). A coverage is a georelational data model that stores vector data
containing both the spatial (location) and attribute (descriptive) data for geographic
features. It generally represents a single feature class such as roads.
 Data Type. A characteristic of a column in a database or a stream of data. It
characterizes the data into similar types (Varchar2, Number, Char, Date, etc)
 Event Tables. An ArcGIS term for tables containing information about events that can
be located along a route. Each row in the event table references an event and its
location is expressed as measurements along named (identifiable) linear features.
There are two types, a point event describes a discrete location along a route (a point)
whereas a line event describes a portion of a route (a line).
 Extensible. The ability to add custom coding to the database without requiring a
programmer to change the code of the application that is used to maintain the
database. The Travel Routes database was designed to be extensible in that new
linear events can be added and look up values for those linear events can be added
without requiring the INFRA development team to modify the database to accept the
change.
Glossary Travel Routes Data Dictionary Page: 1

 Foreign Key A column in a child table that references the primary key in a parent
table.
 Fuzzy Tolerance An Arc/Info term that represents the minimum distance separating all
arc coordinates (nodes and vertices) in a coverage. By definition, it also defines the
distance a coordinate can move during certain operations.
 Geodatabase. The geodatabase is the native data model in ArcGIS for storing
geographic information and is the primary data format used for editing and data
management. An ArcGIS geodatabase is a collection of geographic datasets of various
types held in a common file system folder, a Microsoft Access database, or a multiuser
relational database (such as Oracle).
 Index. A way to find rows in a database very quickly.
 Insert Trigger. A piece of programming code that executes when a new row is inserted
into a database table. Typically these are used to generate unique identifiers such as
the control numbers used throughout the INFRA application.
 Mandatory. Those columns within a table that can’t be null.
 Map Scale. The ratio of the distance on a map to the distance on the earth. It is
typically expressed as a fraction (i.e. 1:24,000). This means that 1 unit on the map
equals 24,000 units on the ground.
 Overlap. Where a linear event’s values have overlapping measures. For example,
where easements have been granted to multiple cost share partners over different
segments of the same route.
 Precision. In the context of a numeric database column, is the number of digits to the
left of the decimal point plus the decimal point itself.
 Primary Key. The column(s) within a table that uniquely identify a row and have a
primary key constraint enabled within the database.
 Required. Those columns within a table or a linear event where the business rules
require it to be populated.
 Route. A road or trail that is signed and managed as a unique entity. Management can
change along its length but it is singularly identified. This term is also used in GIS to
denote any linear feature, such as a highway, river, or pipe, that has a unique identifier
and a common measurement system along each linear feature.
 Route Feature Class. An ArcGIS term for a collection of routes with a common
measurement system. These measurement values can be used to locate events,
assets, and conditions along its set of linear features.
 Scale. In the context of a numeric database column, is the number of digits to the right
of the decimal point.
 Shapefile. An ArcGIS term for a simple, nontopological format for storing geometric
locations and attribute information of geographic features. Geographic features can be
represented by points, lines, or polygons.

 Size. In the context of a string database column, is the maximum number of characters
that can be stored.
 Well Normalized. The process of designing a database to the principles outlined by
E.F. Codd. There are a series of steps (or forms) that describe how data is organized
and related to each other.
 WO Authority. Those linear events and codes that are to be used consistently across
the country and are defined nationally. Regions and Forests will not change these
linear events or codes but can add additional linear events or codes (extensibility).

10.2 Policy Terms
 Abbreviations:
o AASHTO. American Association of State Highway and Transportation Officials.
o CFR. Code of Federal Regulations.
o EM. Forest Service Engineering Manual.
o EO. Executive Order.
o FSH. Forest Service Handbook.
o FSM. Forest Service Manual.
o MVUM. Motor Vehicle Use Map
o NFS. National Forest System
o USC. United States Code
 Access Right (1). The right of ingress to and egress from a property that abuts a street or
highway. (23 CFR 710.105)
 Access Right (2). The authority to pass over a property for purposes of ingress to or
egress from a piece of property. (FSM 5460.5)
 Administrative NFS Road. Any NFS road that is not a public road. (FSM 7730.5)
 Administrative unit. A National Forest, a National Grassland, a purchase unit, a land

utilization project, Columbia River Gorge National Scenic Area, Land between the Lakes,
Lake Tahoe Basin Management Unit, Midewin National Tallgrass Prairie, or other
comparable unit of the National Forest System. (36 CFR 212.1, 36 CFR 261.2, FSH 7705)

 All-Terrain Vehicle (ATV). A type of off-highway vehicle that travels on three or more low-
pressure tires; has handle-bar steering; is less than or equal to 50 inches in width; and has
a seat designed to be straddled by the operator. (FSM 2353.05, FSH 2309.18.05, FSM
7705)
 Annual Maintenance. Work performed to maintain serviceability, or repair failures during

the year in which they occur. Includes preventive and/or cyclic maintenance performed in
the year in which it is scheduled to occur. Unscheduled or catastrophic failures of
components or assets may need to be repaired as a part of annual maintenance.
(Financial Health - Common Definitions for Maintenance and Construction Terms, July 22,
1998)
 Area. A discrete, specifically delineated space that is smaller and in most cases much
smaller, than a Ranger District. (36 CFR 212.1, 36 CFR 261.2, FSM 7705)
 Arterial Road (1). A road that provides for relatively high travel speeds and minimum
interference to through movement. (AASHTO, 2001, A Policy on Geometric Design of
Highways and Streets)
 Arterial Road (2). A NFS road that provides service to large land areas and usually
connects with other arterial roads or public highways. (FSM 7705)
 Average Daily Traffic. The total number of vehicles passing a given point during a given
time period divided by the number of days in that time period. (AASHTO, 2001, A Policy on
Geometric Design of Highways and Streets)
 Bridge (1). A structure, including supports, erected over a depression or an obstruction,

such as water, a highway, or a railway, having a track or passageway for carrying traffic or
other moving loads, and having an opening measured along the center of the roadway of
more than 20 feet between undercopings of abutments or spring lines of arches, or extreme
ends of the openings for multiple boxes; it may include multiple pipes where the clear
distance between openings is less than half of the smaller contiguous opening. (23 CFR
650.403)
 Bridge (2). A road or trail structure, including supports, erected over a depression or an
obstruction, such as water, a road, a trail, or railway, and having a deck for carrying traffic
or other loads. (FSM 7705)
 Capital Improvement. The construction, installation, or assembly of a new fixed asset, or

the significant alteration, expansion, or extension of an existing fixed asset to
accommodate a change of purpose. (Financial Health - Common Definitions for
Maintenance and Construction Terms, July 22, 1998)

 Catastrophic Failure. The sudden failure of a major element or segment of the highway
system due to an external cause. The failure must not be primarily attributable to gradual
and progressive deterioration or lack of proper maintenance. The closure of a facility
because of imminent danger or collapse is not I n itself a sudden failure. (23 CFR 668.103)
 Collector Road (1). A road that serves predominant travel distances shorter than arterial
roads at more moderate speeds. (AASHTO, 2001, A Policy on Geometric Design of
 Collector Road (2). A NFS road that serves smaller areas than an arterial road and that
usually connects arterial roads to local roads or terminal facilities. (FSM 7705)
 Commensurate Share. The proportion of maintenance and reconstruction associated with

an NFS road that is assignable to a commercial hauler for purposes of cost recovery under
FSM 7730 (16 U.S.C. 537). (FSM 7730.5)
 Commercial Hauler. A person or entity engaging in commercial hauling. (FSM 7730.5)
 Commercial Hauling. For purposes only of cost recovery under FSM 7730, commercial
use of NFS roads to transport:
1. Federal or non-federal products from Federal, State, or private lands;
2. Livestock, other than livestock authorized to use NFS lands, feed for livestock
authorized to use NFS lands, and livestock from farms and ranches in or adjacent to
the NFS; or
3. Goods for, supplies for, or customers of commercial uses or activities on NFS lands
pursuant to a special use authorization or other written authorization issued by the
Forest Service, other than:
a. A Forest Service contract;
b. An agreement between the Forest Service and another Federal agency,
unless the agreement specifically provides for cost recovery;
c. A grazing permit;
d. An authorization for a concession involving federally-owned facilities; and
e. A special recreation permit issued under the Federal Lands Recreation
Enhancement Act (16 U.S.C. 6802(d)(2)). (FSM 7730.5)
 Commercial Use or Activity. Any use or activity on National Forest System lands (a)
where an entry or participation fee is charged, or (b) where the primary purpose is the sale
of a good or service, and in either case, regardless of whether the use or activity is
intended to produce a profit. (36 CFR 251.51, FSM 7730.5)
 Cooperator. An individual or entity that is a party to an investment sharing agreement or is

granted an easement for acquisition, construction, or maintenance of a NFS road pursuant
to Title 16, U.S.C.535. (FSM 7730.5)

 Cost Recovery. Requiring users of NFS roads to maintain them commensurate with their
use, to reconstruct them when necessary to accommodate their use, or to deposit sufficient
funds to cover the users’ share of the maintenance or reconstruction (16 U.S.C. 537; 36
CFR 212.5(d)). (FSM 7730.5)
 Condemnation. The acquisition of lands or interests therein by the Secretary without the
consent of the owner. In the case of the Act, condemnation is a limited authority that may
be exercised by the Secretary only in the event that a standard or standards set forth
herein are violated for all private land categories except mining lands. Where mining lands
are involved, the Secretary may exercise his or her condemnation authority not-
withstanding the fact that the mining land owner has complied with the relevant standards
of this section. (36 CFR 292.21)
 Construction (1). The supervising, inspecting, actual building, and incurrence of all costs
incidental to the construction or reconstruction of a highway, including bond costs and other
costs relating to the issuance in accordance with section 122 of bonds or other debt
financing instruments and costs incurred by the State in performing Federal-aid project
related audits that directly benefit the Federal-aid highway program. Such term includes--
(A) locating, surveying, and mapping (including the establishment of temporary and
permanent geodetic markers in accordance with specifications of the National Oceanic and
Atmospheric Administration of the Department of Commerce);
(B) resurfacing, restoration, and rehabilitation;
(C) acquisition of rights-of-way;
(D) relocation assistance, acquisition of replacement housing sites, and acquisition and
rehabilitation, relocation, and construction of replacement housing;
(E) elimination of hazards of railway grade crossings;
(F) elimination of roadside obstacles;
(G) improvements that directly facilitate and control traffic flow, such as grade
separation of intersections, widening of lanes, channelization of traffic, traffic control
systems, and passenger loading and unloading areas; and
(H) capital improvements that directly facilitate an effective vehicle weight enforcement
program, such as scales (fixed and portable), scale pits, scale installation, and scale
houses. (23 USC 101)
 Construction (2). The erection, construction, installation, or assembly of a new fixed

asset. (Financial Health - Common Definitions for Maintenance and Construction Terms,
July 22, 1998)

 Construction engineering. All work and expense of setting out, controlling, inspecting,
and measuring the construction or reconstruction of a forest transportation facility
including:
(1) Construction surveys to establish line and grade for the work,
to control the work, and to measure quantities;
(2) Redesigning, adjusting, and changing the plans, specifications,
and materials to meet conditions;
(3) Inspecting, directing, and controlling operations for compliance
with plans and specifications;
(4) Inspecting, testing, and accepting materials and equipment to be
installed in the work; and
(5) Inspecting, measuring, and accepting completed work. (36 CFR 212)
 Critical Vehicle. The vehicle, normally the largest (by weight, size, or unique
configuration), whose limited use on the road is necessary to complete the planned activity.
(FSH 7709.56, Section 4.1)
 Culvert. A conduit or passageway under a road, trail, or other obstruction. A culvert differs
from a bridge in that the top of a culvert does not serve as the road surface and is
constructed entirely below the elevation of the traveled way. (Handbook of Steel Drainage
& Highway Construction Products).
 Cyclic Maintenance. Preventive maintenance activities that recur on a periodic and

scheduled cycle. (Financial Health - Common Definitions for Maintenance and Construction
Terms, July 22, 1998)
 Danger Tree. A standing tree that presents a hazard to people due to conditions such as,
but not limited to, deterioration or physical damage to the root system, trunk, stem, or limbs
and the direction or lean of the tree. This term is synonymous with Hazard Tree previously
used terminology. : (FSH 6709.11, FSH 7709.59, Section 40.5) In regard to this definition a
Qualified Person is a person who has knowledge, training, and experience in identifying
danger trees.
 Decommission. Demolition, dismantling, removal, obliteration and/or disposal of a

deteriorated or otherwise unneeded asset or component, including necessary cleanup
work. This action eliminates the deferred maintenance needs for the fixed asset. Portions of
an asset or component may remain if they do not cause problems nor require maintenance.
(Financial Health - Common Definitions for Maintenance and Construction Terms, July 22,
1998)

 Deferred Maintenance. Maintenance that was not performed when it should have been or
when it was scheduled and which, therefore, was put off or delayed for a future period.
When allowed to accumulate without limits or consideration of useful life, deferred
maintenance leads to deterioration of performance, increased costs to repair, and decrease
in asset value. Deferred maintenance needs may be categorized as critical or non-critical at
any point in time. Continued deferral of non-critical maintenance will normally result in an
increase in critical deferred maintenance. Code compliance (e.g. life safety, ADA, OSHA,
environmental, etc.), Forest Plan Direction, Best Management Practices, Biological
Evaluations, other regulatory or Executive Order compliance requirements, or applicable
standards not met on schedule are considered deferred maintenance. (Financial Health -
Common Definitions for Maintenance and Construction Terms, July 22, 1998)
 Department of Transportation Easement. An easement issued by the Federal Highway

Administration to a Public Road Authority for a Federal-Aid road or Forest Highway
crossing National Forest System lands. (FSH 2709.12, 20)
 Design Speed. A selected speed used to determine the various geometric design features
of the roadway with respect to topography, anticipated operating speed, the adjacent land
use, and the functional classification of the road. The selected design speed should be
consistent with the speeds that drivers are likely to expect on a given highway facility.
(AASHTO, 2001, A Policy on Geometric Design of Highways and Streets)
 Design Vehicle. A selected vehicle, with representative weight, dimensions, and operating
characteristics, used to establish the design controls for the road. There are four general
classes of design vehicles: (1) passenger cars, (2) buses, (3) trucks, and (4) recreational
vehicles. (AASHTO, 2001, A Policy on Geometric Design of Highways and Streets)
 Designated Road, Trail, or Area. A National Forest System road, a National Forest
System trail, or an area on National Forest System lands that is designated for motor
vehicle use pursuant to 36 CFR 212.51 on a motor vehicle use map (MVUM). (36 CFR
212.1, FSM 7705)
 Easement (1). A type of special use authorization (usually granted for linear rights-of-way)
that is utilized in those situations where a conveyance of a limited and transferable interest
in National Forest System land is necessary or desirable to serve or facilitate authorized
long-term uses, and that may be compensable according to its terms. (36 CFR 251.51)
 Easement (2). An interest in real property that conveys a right to use a portion of an
owner's property or a portion of an owner's rights in the property. (23 CFR 710.105)
 Easement (3). An interest in land owned by another party that entitles the holder to a
specific limited use or enjoyment. (FSM 5460.5)

 Emergency Repairs. Those repairs including temporary traffic operations undertaken
during or immediately following the disaster occurrence for the purpose of:
(1) Minimizing the extent of the damage,
(2) Protecting remaining facilities, or
(3) Restoring essential traffic. (23 CFR 668.103)
 Emergency Relief Federally-Owned (ERFO) Roads Program. A program administered

by the Federal Highway Administration that provides funding for repair and reconstruction
of federally-owned roads and trails damaged or destroyed by natural disasters over a wide
area or by catastrophic failures from external causes (23 U.S.C. 125). (FSM 7730.5)
 Engineering Analysis. An analysis and evaluation conducted by a qualified engineer, or

under the supervision of a qualified engineer, of an NFS road, road segment, or road
system being considered for motorized mixed use. The analysis and evaluation may
include recommended mitigation measures. The analysis may be simply documentation of
engineering judgment or may be a more complex engineering report that includes many
factors related to motorized mixed use. (FSM 7705)
 Engineering Judgment. The evaluation of available information and the application of

engineering principles, standards, guidance, and practices for the purpose of considering
motorized mixed use for a road. Engineering judgment shall be exercised by a qualified
engineer or by an individual who is working under the supervision of a qualified engineer
and who is applying procedures and criteria established by the qualified engineer. (FSM
7705)
 Engineering Report. A report signed by a qualified engineer and presented to a

responsible official who is considering designation of a road for motorized mixed use that
analyzes risk factors pertaining to the proposed designation. The report may identify
alternatives, as well as risks associated with those alternatives, for mitigation of factors
contributing to the probability and severity of crashes. (FSM 7705)
 Fatality. A fatality in the National Forest Road System annual fatality report is the death of
a person (either an occupant of a vehicle or a non-motorist) that is the result of a crash
involving a state highway legal motor vehicle (including motorcycles) traveling on a System
Road open to traffic (operationally maintenance level 2, 3, 4, or 5) that occurs within 30
days of the crash. (Annual Roads Accomplishment Report FY 2002)
 Federal Aid Highway. A highway eligble for assistance under 23 U.S.C. 101 other than a
highway classified as a local road or a rural minor collector. (23 U.S.C. 101)
 Federal Lands Highway. A Forest highway, public lands highway, park road, parkway,
refuge road and Indian Reservation road that is a public road. (23 U.S.C. 101)
 FLPMA. Federal Land Policy Management Act of October 21, 1976 (90 Stat 2743, 43
U.S.C. 1715.

 Fee Title (or Fee Simple). The full and complete possessory ownership of a parcel of
land. An inheritable estate. The greatest interest in property that a person can have.
(Webster).
 Forest Development Road and Trail. Forest roads and trails under the jurisdiction of the
Forest Service. (23 USC 101) (The term is obsolete and has been replaced with National
Forest System Road (NFSR) and National Forest System Trail (NFST))
 Forest Highway. A forest road under the jurisdiction of, and maintained by, a public
authority and open to public travel. (23 USC 101, 23 CFR 660.103)
 Forest Road. A road wholly or partly within, or adjacent to, and serving the National Forest
System which is necessary for the protection, administration, and utilization of the National
Forest System and the use and development of its resources. (23 USC 101, 23 CFR
660.103)
 Forest Road and Trail Act Easement. An easement issued by the Forest Service to a
Public Road Authority for a non-Federal-Aid road or non-Forest Highway crossing National
Forest System lands. (FSH 2709.12, 30)
 Forest Road and Trail Funds. Funds authorized or appropriated for the purpose of
carrying out the provisions of section 205 of the Act of August 27, 1958 (72 Stat. 907), as
amended; 23 U.S.C. 205. (36CFR 261.1)
 Forest Road or Trail. A road or trail wholly or partly within or adjacent to and serving the
National Forest System that the Forest Service determines is necessary for the protection,
administration and utilization of the National Forest System and the use and development
of its resources. (23 U.S.C. 101, 36 CFR 212.1, 36 CFR 251.51, 36 CFR 261.2, FSM
7705)
 Forest Trail. A trail wholly or partly within, or adjacent to, and serving the National Forest
System and which is necessary for the protection, administration, and utilization of the
National Forest System and the use and development of its resources. (FSM 2353.05,
FSH 2309.18.05)
 Forest Transportation Atlas. A display of the system of roads, trails and airfields of an
administrative unit. (36 CFR 212.1, FSM 7705)
 Forest Transportation Facility. A forest road or trail or an airfield that is displayed in a

forest transportation atlas, including bridges, culverts, parking lots, marine access facilities,
safety devices, and other improvements appurtenant to the forest transportation system.
(36 CFR 212.1, FSH 7705)

 Forest Transportation System. The system of National Forest System roads, National
Forest System Trails, and airfields on National Forest System lands. (36 CFR 212.1, FSM
7705)
 Forest Transportation System Management. Travel planning, analysis, designation of

roads, trails and areas for motor vehicle use, recordkeeping, scheduling, construction,
reconstruction, maintenance, decommissioning, and other operations undertaken to
achieve environmentally sound, safe, and cost-effective access for the use, enjoyment,
protection, administration, and management of NFS lands. (FSM 7705)
 Four-Wheel Drive Vehicle Greater Than 50 Inches in Width. An off-highway vehicle

greater than 50 inches in width that operates on four wheels and with a drive train that
allows all four wheels to receive power from the engine simultaneously. (FSM 2353.05,
FSH 2309.18.05)
 Four-Wheeled Drive Way. A National Forest System road included in the Forest
Transportation Atlas and commonly used by four-wheel drive, high clearance vehicles with
a width greater than 50 inches unless designated and managed as a trail. (FSM 2353.05)
 Functional Classification. The grouping of roads by the character of service they provide.
 Heavy Maintenance. Work usually done by highway agencies in repairing damage

normally expected from seasonal and occasionally unusual natural conditions or
occurrences. It includes work at a site required as a direct result of a disaster which can
reasonably be accommodated by a State or local road authority's maintenance, emergency
or contingency program. (23 CFR 668.103)
 Highway. The term ``highway'' includes—

(A) A road, street, and parkway,
(B) A right-of-way, bridge, railroad-highway crossing, tunnel, drainage structure, sign,
guardrail, and protective structure, in connection with a highway; and
(C) A portion of any interstate or international bridge or tunnel and the approaches
thereto, the cost of which is assumed by a State transportation department, including
such facilities as may be required by the United States Customs and Immigration
Services in connection with the operation of an international bridge or tunnel. (23 USC
101)
 Highway-Legal Vehicle. Any motor vehicle that is licensed or certified under State law for
general operation on all public roads within the State. Operators of highway-legal vehicles
are subject to State traffic law, including requirements for operator licensing. (FSM 7705)
.

 Investment Sharing. A process that:
1. Provides for acquisition, construction, and maintenance of NFS roads pursuant to an
investment sharing agreement or easement to meet mutual needs of the United States
and others for access (16 U.S.C. 535; 36 CFR 212.9(a)-(c), (e), and (f));
2. Enters into a cooperative agreement with a commercial hauler who is not a party to an
investment sharing agreement for the agency to recoup the commercial hauler’s
investment share through the commercial hauler’s contribution of funds or performance of
maintenance or reconstruction required to accommodate the commercial hauler’s use (16
U.S.C. 535); or
3. Requires a commercial hauler who is not a party to an investment sharing agreement

or a cooperative agreement to reimburse the Forest Service or, in lieu of reimbursement,
perform maintenance or reconstruction required to accommodate the commercial hauler’s
use, for the commercial hauler’s investment share (16 U.S.C. 535; 36 CFR 212.5(c) and
212.9(d)). (FSM 7730.5)
 Jurisdiction (1). The legal right or power to interpret and apply the law. Authority or
control. (Webster)
 Jurisdiction (2). The legal right to control and regulate the use of a transportation facility.
Roads on National Forest lands are under the control of the Forest Service, except for
public roads established under the Act of July 26, 1866, private roads, roads for which the
Forest Service has granted rights-of-way to private landowners or public road agencies,
and roads whose use and rights pre-date the National Forest. Other factors may affect
jurisdiction on acquired lands or easements. Review the granting document and obtain
appropriate legal opinion for these cases, when necessary. There are roads on the
transportation system where the Forest Service has limited rights of use and no jurisdiction
over the traffic, such as private road systems and State, county, or township roads. (FSH
7709.59.21)
 Jurisdiction (3). The legal right or authority to control, operate, regulate use of, maintain,
or cause to be maintained, a transportation facility, through ownership or delegated
authority. The authority to construction or maintain such a facility may be derived from fee
title, easement, written authorization, or permit from a Federal agency, or some similar
method. (23 CFR 660.103)
 Jurisdiction Over a Forest Transportation Facility. The legal right to control or regulate
use of a forest transportation facility derived from title, an easement, an agreement, or
other similar source. (FSM 7705)

 Lease. A type of special use authorization (usually granted for uses other than linear
rights-of-way) that is used when substantial capital investment is required and when
conveyance of a conditional and transferable interest in National Forest System lands is
necessary or desirable to serve or facilitate authorized long-term uses, and that may be
revocable and compensable according to its terms. (36 CFR 251.51)
 Linear Right-of-Way. A right-of-way for a linear facility, such as a road, trail, pipeline,
electronic transmission facility, fence, water transmission facility, or fiber optic cable. (36
CFR 251.51)
 Local Road (1). A road that primarily provides access to land adjacent to collector roads
over relatively short distances at low speeds. (AASHTO, 2001, A Policy on Geometric
Design of Highways and Streets)
 Local Road (2). An NFS road that connects a terminal facility with collector roads, arterial
roads, or public highways and that usually serves a single purpose involving intermittent
use. (FSM 7705)
 Low-Volume Road. A road that has an average daily traffic of 400 or less. (AASHTO,
2001, Guidelines for Geometric Design of Very Low-Volume Local Roads)
 Maintenance (1). The preservation of the entire highway, including surface, shoulders,
roadsides, structures and such traffic-control devices as are necessary for safe and efficient
utilization of the highway. (23 USC 101, 23 CFR 460.2)
 Maintenance (2). The upkeep of the entire forest transportation facility including surface
and shoulders, parking and side areas, structures, and such traffic-control devices as are
necessary for its safe and efficient utilization. (36 CFR 212.1)
 Maintenance (3). The act of keeping fixed assets in acceptable condition. It includes
preventive maintenance normal repairs; replacement of parts and structural components,
and other activities needed to preserve a fixed asset so that it continues to provide
acceptable service and achieves its expected life. Maintenance excludes activities aimed at
expanding the capacity of an asset or otherwise upgrading it to serve needs different from,
or significantly greater than those originally intended. Maintenance includes work needed to
meet laws, regulations, codes, and other legal direction as long as the original intent or
purpose of the fixed asset is not changed. (Financial Health - Common Definitions for

 Maintenance Levels. Defines the level of service provided by, and maintenance required
for, a specific road, consistent with road management objectives and maintenance criteria.
(FSH 7709.59, 62.32)
LEVEL 1. These are roads that have been placed in storage between intermittent uses.
The period of storage must exceed 1 year. Basic custodial maintenance is performed to
prevent damage to adjacent resources and to perpetuate the road for future resource
management needs. Emphasis is normally given to maintaining drainage facilities and
runoff patterns. Planned road deterioration may occur at this level. Appropriate traffic
management strategies are "prohibit" and "eliminate" all traffic. These roads are not
shown on motor vehicle use maps.
Roads receiving level 1 maintenance may be of any type, class, or construction

standard, and may be managed at any other maintenance level during the time they are
open for traffic. However, while being maintained at level 1, they are closed to vehicular
traffic but may be available and suitable for nonmotorized uses.
LEVEL 2. Assigned to roads open for use by high clearance vehicles. Passenger car
traffic, user comfort, and user convenience are not considerations. Warning signs and
traffic control devices are not provided with the exception that some signing, such as W-
18-1 “No Traffic Signs,” may be posted at intersections. Motorists should have no
expectations of being alerted to potential hazards while driving these roads. Traffic is
normally minor, usually consisting of one or a combination of administrative, permitted,
dispersed recreation, or other specialized uses. Log haul may occur at this level.
Appropriate traffic management strategies are either to:
a. Discourage or prohibit passenger cars, or
b. Accept or discourage high clearance vehicles.
LEVEL 3. Assigned to roads open and maintained for travel by a prudent driver in a
standard passenger car. User comfort and convenience are not considered priorities.
The Manual on Uniform Traffic Control Devices (MUTCD) is applicable. Warning signs
and traffic control devices are provided to alert motorists of situations that may violate
expectations.
Roads in this maintenance level are typically low speed with single lanes and turnouts.
Appropriate traffic management strategies are either "encourage" or "accept."
"Discourage" or "prohibit" strategies may be employed for certain classes of vehicles or
users.
LEVEL 4. Assigned to roads that provide a moderate degree of user comfort and
convenience at moderate travel speeds. Most roads are double lane and aggregate
surfaced. However, some roads may be single lane. Some roads may be paved and/or
dust abated. Manual on Uniform Traffic Control Devices is applicable. The most
appropriate traffic management strategy is "encourage." However, the "prohibit"
strategy may apply to specific classes of vehicles or users at certain times.

LEVEL 5. Assigned to roads that provide a high degree of user comfort and
convenience. These roads are normally double lane, paved facilities. Some may be
aggregate surfaced and dust abated. Manual on Uniform Traffic Control Devices is
applicable. The appropriate traffic management strategy is "encourage."
 Managed Use. A mode of travel that is actively managed and appropriate on a trail, based
on its design and management. (FSH 2309.18)
 Mode of Travel. A hierarchical list that includes all motorized and non-motorized land,
snow, water, and air types of travel on roads, trails, and areas. It is used to generate the
Motor Vehicle Use Maps and other map products and reports. (ATM Data Dictionary 2009)
 Motorcycle. A two-wheeled motor vehicle on which the wheels are situated in a

line, rather than side by side. (FSH 2309.18.05)
 Motor Vehicle. Any vehicle which is self-propelled, other than:

(1) A vehicle operated on rails; and
(2) Any wheelchair or mobility device, including one that is battery-powered, that
is designed solely for use by a mobility-impaired person for locomotion, and that is
suitable for use in an indoor pedestrian area. (36 CFR 212.1, 36 CFR 261.2, FSM
7705, FSH 2309.18.05)
 Motor Vehicle Use Map. A map reflecting designated roads, trails, and areas on an
administrative unit or a Ranger District of the National Forest System. (36 CFR 212.1, FSM
7705)
 Motorcycle. A two-wheeled motor vehicle on which the two wheels are not side-by-side
but in line. (FSM 2353.05, FSM 7705)
 Motorized Equipment (1). Any machine activated by a nonliving power source except
small battery-powered hand-carried devices such as flashlights, shavers, Geiger counters,
and cameras. (36 CFR 261.2)
 Motorized Equipment (2). Machines that use a motor, engine, or other nonliving power
sources. This includes, but is not limited to, such machines as chain saws, aircraft,
snowmobiles, generators, motorboats, and motor vehicles. It does not include small
battery or gas powered hand-carried devices such as shavers, wristwatches, flashlights,
cameras, stoves, or other similar small equipment. (FSM 2320.5)
 Motorized Mixed Use. Designation of an NFS road for use by both highway-legal and non-
highway-legal motor vehicles. (FSM 7705)

 National Environmental Policy Act (NEPA) procedures. The rules, policies, and
procedures governing agency compliance with the National Environmental Policy Act set
forth in 50 CFR parts 1500-1508, 7 CFR part 1b, Forest Service Manual Chapter 1950, and
Forest Service Handbook 1909.15. (36 CFR 251.51)
 National Forest System (1). As defined in the Forest Rangeland Renewable Resources
Planning Act, the ``National Forest System'' includes all National Forest lands reserved or
withdrawn from the public domain of the United States, all National Forest lands acquired
through purchase, exchange, donation, or other means, the National Grasslands and land
utilization projects administered under title III of the Bankhead-Jones Farm Tennant Act (50
Stat. 525, 7 U.S.C. 1010-1012), and other lands, waters or interests therein which are
administered by the Forest Service or are designated for administration through the Forest
Service as a part of the system. (36 CFR 212.1, 36 CFR 261.2)
 National Forest System (2). Lands and facilities administered by the Forest Service (FS)
U.S. Department of Agriculture, as set forth in the Forest and Rangeland Renewable
Resource Planning Act of 1974, as amended (16 U.S.C. 1601 note, 1600-1614). (23 CFR
660.103)
 National Forest System Land. All lands, waters, or interests therein administered by the
Forest Service. (36 CFR 251.51)
 National Forest System Road. A forest road other than a road which has been authorized
by a legally documented right-of-way held by a State, county or other local public road
authority. (36 CFR 212.1, 36 CFR 251.51, 36 CFR 261.2, FSM 7705)
 National Forest System Trail. A forest trail other than a trail which has been authorized by
a legally documented right-of-way held by a State, county or other local public road
authority. (36 CFR 212.1, 36 CFR 261.2, FSM 7705, FSM 2353.05, FSH 2309.18.05)
 National Recreation Trail. A trail that provides a variety of outdoor recreation uses in or
reasonably accessible to urban areas. (National Trail System Act of 1968, Public Law 90-
543)
 Need (1). A maintenance, capital improvement, or other programmatic or operational

requirement which can be satisfied by a single unit of work. (Financial Health - Common
Definitions for Maintenance and Construction Terms, July 22, 1998)
o Critical Need. A requirement that addresses a serious threat to public health or safety,
a natural resource, or the ability to carry out the mission of the organization. (Financial
Health - Common Definitions for Maintenance and Construction Terms, July 22, 1998)

o Emergency Need. An urgent maintenance need that may result in injury, illness, or
loss of life, natural resource, or property; and must be satisfied immediately. Emergency
needs generally require a declaration of emergency or disaster, or a finding by a line
officer that an emergency exists. (Financial Health - Common Definitions for
o Health & Safety Need. A requirement that addresses a threat to human safety and
health (e.g. violations of National Fire Protection Association 101 Life Safety Code or
appropriate Health Code) that requires immediate interim abatement and/or long-term
permanent abatement. (Financial Health - Common Definitions for Maintenance and
Construction Terms, July 22, 1998)
o Mission Need. A requirement that addresses a threat or risk to carrying out the mission
of the organization. Needs related to administration and providing services
(transportation, recreation, grazing, etc.). Needs not covered by health and safety or
natural resource protection. (Financial Health - Common Definitions for Maintenance
and Construction Terms, July 22, 1998)
o Non-Critical Need. A requirement that addresses potential risk to public or employee

safety or health, compliance with codes, standards, regulations etc., or needs that
address potential adverse consequences to natural resources or mission
accomplishment. (Financial Health - Common Definitions for Maintenance and
o Resource Protection Need. A requirement that addresses a threat or risk of damage,

obstruction, or negative impact to a natural resource. (Financial Health - Common
Definitions for Maintenance and Construction Terms, July 22, 1998)
 Non-Highway-Legal Vehicle. Any motor vehicle that is not licensed or certified under
State law for general operation on all public roads within the State. Operators of non-
highway-legal vehicles are subject to State requirements, if any, for licensing and operation
of the vehicle in question. (FSM 7705)
 Obliteration (1). To eliminate completely so as to leave no trace. (Webster)
 Obliteration (2). The reclamation and or restoration of land to resource production from
that of a transportation facility. (FSH 7709.54, no longer in print)
 Obliteration (3). To unbuild, decommission, deactivate, or dismantle a road; the denial of

use, elimination of travelway functionality, and removal of the road from the forest
development road system; return of the road corridor to resource production by natural or
designated means. (A Guide For Road Closure and obliteration in the FS, June 1996, T&D
Publication 9677 1205)

 Objective Maintenance Level. The maintenance level to be assigned at a future date
considering future road management objectives, traffic needs, budget constraints, and
environmental concerns. The objective maintenance level may be the same as, or higher or
lower than, the operational maintenance level. The transition from operational maintenance
level to objective maintenance level may depend on reconstruction or disinvestment. (FSH
7709.59, 62.3)
 Off-Highway Haul. The use of vehicles on a regular basis on NFS roads for hauling
products or commodities that exceed the maximum load, weight, length, height, or width
restrictions applicable to State or county road systems. (FSM 7730.5)
 Off-Highway Vehicle (1). Any motor vehicle designed for or capable of cross county travel
on or immediately over land, water, sand, snow, ice, marsh, swampland, or other natural
terrain. (36 CFR 212.1, FSM 2353.05, FSH 2309.18.05, FSM 7705,)
 Off-Highway Vehicle (2). Any motorized vehicle designed for or capable of cross county
travel on or immediately over land, water, sand, snow, ice, marsh, swampland, or other
natural terrain; except that term excludes (A) any registered motorboat, (B) any fire,
military, emergency or law enforcement vehicle when used for emergency purposes, and
any combat or combat support vehicle when used for national defense purposes, and (C)
any vehicle whose use is expressly authorized by the respective agency head under a
permit, lease, license, or contract. (EO 116-44 as amended by EO 11989). See also FSM
2355. 01 - Exhibit 01.
 Off-Road Vehicle. Synonymous with off-highway vehicle.
 Open to Public Travel (1). The road section is available, except during scheduled periods,
extreme weather or emergency conditions, passable by four-wheel standard passenger
cars, and open to the general public for use without restrictive gates, prohibitive signs, or
regulation other than restrictions based on size, weight, or class of registration. Toll plazas
of public toll roads are not considered restrictive gates. (23 CFR 460.2)
 Open to Public Travel (2). Except during scheduled periods, extreme weather conditions,
or emergencies, open to the general public for use with a standard passenger auto, without
restrictive gates or prohibitive signs or regulations, other than for general traffic control or
restrictions based on size, weight, or class of registration. (23 CFR 660.103)
 Operating Costs for Traffic Monitoring, Management, and Control. Includes labor
costs, administrative costs, costs of utilities and rent, and others costs associated with the
continuous operation of traffic control, such as integrated traffic control systems, incident
management programs, and traffic control centers. (23 USC 101)
 Operating Speed. The speed at which drivers are observed operating their vehicles
during free-flow conditions. (AASHTO, 2001, A Policy on Geometric Design of Highways
and Streets)

 Operational Improvement.
(A) (i) a capital improvement for installation of traffic surveillance and control equipment,
computerized signal systems, motorist information systems, integrated traffic control
systems, incident management programs, and transportation demand management
facilities, strategies, and programs, and (ii) such other capital improvement to public roads
as the Secretary may designate, by regulation; and
(B) does not include resurfacing, restoring, or rehabilitating improvements, construction of
additional lanes, interchanges, and grade separation, and construction of a new facility on a
new location. (23 USC 101)
 Operational Maintenance Level. The maintenance level currently assigned to a road

considering today's needs, road condition, budget constraints, and environmental concerns.
It defines the level to which the road is currently being maintained. (FSH 7709.59, 62.3)
 Over-Snow Vehicle. A motor vehicle that is designed for use over snow and that runs on a
track or tracks and/or a ski or skis, while in use over snow. (36 CFR 212.1, FSM 7705)
 Passenger Cars. These include passenger cars of all sizes, sport/utility vehicles,
minivans, vans and pickup trucks. (AASHTO, 2001, A Policy on Geometric Design of
 Permit (1). A special use authorization which provides permission, without conveying an
interest in land, to occupy and use National Forest System land or facilities for specified
purposes, and which is both revocable and terminable. (36 CFR 251.51)
 Permit (2). Authorization in writing by a forest officer. (36 CFR 261.2)
 Permit (3). A written license or warrant issued by one party to a second party granting the
second party permission to do some act that is not forbidden by law but is forbidden without
such license or warrant. A permit gives permission but does not vest a right. In some
States a permit may become nonrevocable after a statutory period of time. (FSM 5460.5)
 Preconstruction Engineering. All work and expense of preparing for construction or

reconstruction of a forest transportation facility including:
(1) Engineering and economic investigations, studies, and reports;
(2) Reconnaissance surveys;
(3) Preliminary surveys;
(4) Preliminary location surveys;
(5) Soils, foundations, and materials investigations, surveys, and tests;
(6) Preliminary and final designs;
(7) Preliminary and final plans, drawings, specifications, and estimates of quantities and
cost;
(8) Final location surveys staked on the ground; and
(9) Rights-of-way surveys, plans, and descriptions. (36 CFR 212.1)

 Primary Maintainer. The agency or party having primary (largest share) financial
responsibility for maintenance. (FSH 7709.58, 13)
Primitive Area. An area within the NFS classified as primitive on the effective date of
the Wilderness Act, September 3, 1964 (36 CFR 261.2, FSM 7705).
 Private Road (1). A road under private ownership authorized by easement to a private
party, or a road which provides access pursuant to a reserved or private right. (FS-643,
Roads Analysis; Informing Decisions About Managing the National Forest Transportation
System, August 1999.)
 Private Road (2). A road under private ownership authorized by an easement granted to a
private party or a road that provides access pursuant to a reserved or outstanding right.
(FSM 7705)
 Prudent Driver. In defining negligence, practically synonymous with “cautious driver”.

(Black’s Law Dictionary)
 Public Agency. Any organization with administrative or functional responsibilities which

are directly or indirectly affiliated with a governmental body of any nation, State, or local
jurisdiction. (23 CFR 635.102)
 Public Authority. A Federal, State, county, town or township, Indian tribe, municipal or
other local government or instrumentality, with authority to finance, build, operate or
maintain toll or toll-free highway facilities. (23 CFR 460.2, CFR 660.103)
 Public Lands Highway. A forest road under the jurisdiction of and maintained by a public
authority and open to public travel or any highway through unappropriated or unreserved
public lands, nontaxable Indian lands, or other Federal reservations under the jurisdiction of
and maintained by a public authority and open to public travel. (23 USC 101)
 Public Road(1). A road under the jurisdiction of and maintained by a public road authority
and open to public travel. (23 USC 101(a), 23 CFR 460.2, 23 CFR 660.103, FSM 7705)
 Public Road(2). A road that is:

1. Available, except during scheduled periods, extreme weather, or emergency
conditions;
2. Passable by four-wheel standard passenger cars; and
3. Open to the general public for use without restrictive gates, prohibitive signs, or
regulation other than restrictions based on size, weight, or class of registration. (23
U.S.C. 101(a)(27); 23 CFR 460.2(c) and 660.103). (FSM7730.5)
 Qualified Engineer. An engineer who by experience, certification, education, or license is

technically trained and experienced to perform the engineering tasks specified and is
designated by the Director of Engineering, Regional Office. (FSM 7705)

 Reconstruction. To construct again. (Webster)
 Recreational Vehicle. These include motor homes, cars with camper trailers, cars with
boat trailers, motor homes with boat trailers and motor homes pulling cars. (AASHTO,
2001, A Policy on Geometric Design of Highways and Streets)
 Rehabilitation (2). The major work required to restore the structural integrity of a bridge as
well as work necessary to correct major safety defects. (23 CFR 650.403)
 Rehabilitation (3). Renovation or restoration of an existing fixed asset or any of its

components in order to restore the functionality or life of the asset. Because there is no
significant expansion or change of purpose for the fixed asset, the work primarily addresses
deferred maintenance. (Financial Health - Common Definitions for Maintenance and
 Repair. Work to restore a damaged, broken, or worn-out fixed asset, component, or item
of equipment to normal operating condition. Repairs may be done as annual maintenance
or deferred maintenance activities. (Financial Health - Common Definitions for
 Replacement. Substitution or exchange of an existing fixed asset or component with one

having essentially the same capacity and purpose. (Financial Health - Common Definitions
for Maintenance and Construction Terms, July 22, 1998)
 Restoration. To bring back to an original state. (Webster)
 Right-of-Way (1). Land authorized to be used or occupied for the construction, operation,
maintenance and termination of a project or facility passing over, upon, under or through
such land. (36 CFR 251.51)
 Right-of-Way (2). Real property and rights therein used for the construction, operation,
maintenance of a transportation or related facility funded under title 23 of the United States
Code. (23 CFR 710.105)
 Right-of-Way (3). A privilege or right to cross over or use the land of another party for
egress and ingress such as roads, pipelines, irrigation canals, or ditches. The right-of-way
may be conveyed by an easement, permit, license, or other instrument. (FSM 5460.5)
 Road (1). A motor vehicle route over 50 inches wide, unless identified and managed as a
trail. (36 CFR 212.1, FSM 7705)

 Road and Trail 10 Percent Funds. Funds available from the permanent appropriation
``Roads and Trails for States'' under the Act of March 4, 1913 (37 Stat. 843), as amended;
16 U.S.C. 501 (36 CFR 261.1)

 Road Construction or Reconstruction. Supervising, inspecting, actual building, and
incurrence of all costs incidental to the construction or reconstruction of a road. (36 CFR
212.1, FSM 7705)
 Road Decommissioning (1). Activities that result in the stabilization and restoration of
unneeded roads to a more natural state. (36 CFR 212.1)
 Road Decommissioning (2). Activities that result in restoration of unneeded roads to a

more natural state. (FSM 7705, FSM 7734)
 Road Maintenance. Ongoing upkeep of a road necessary to maintain or restore the road
in accordance with its road management objectives. (FSM 7705, FSM 7714)
 Road Management Objectives (RMO). RMOs document the intended purpose of an

individual road in providing access to implement a land and resource management plan as
well as decisions about applicable standards for the road. RMOs should be based on
management area direction and access management objectives. RMOs contain design
criteria, operation criteria, and maintenance criteria. (FSM 7709.59.11)
 Road Subject to the Highway Safety Act. An NFS road that is open to public use in a
standard passenger car, including a road with access restricted on a seasonal basis and a
road closed during extreme weather conditions or for emergencies, but which is otherwise
open to public travel. (FSM 7705)
 Road Use Order. An order that institutes or terminates traffic rules on NFS roads (36 CFR
261.54; FSM 5330.13). (FSM 7730.5)
 Road Use Permit. A written authorization issued pursuant to Title 36, Code of Federal
Regulations, part 212, Subpart A, that allows an act or omission on an NFS road or NFS
road segment and associated transportation facilities that would otherwise be in violation of
a traffic rule in effect on the road, including:
1. Use of a closed road to access non-federal property (36 CFR 212.6(b));
2. Commercial hauling on a road where that use is otherwise restricted (36 CFR
212.9(d) and 261.54); and
3. Motor vehicle use on an NFS road that is not designated for that purpose (36 CFR
212.51(a)(8)). (FSM 7730.5)
 Roadway. The portion of a highway, including shoulders and auxiliary lanes, for vehicular
use. (AASHTO, 2001, A Policy on Geometric Design of Highways and Streets)
 Route. A road or a trail. (FSM 7705, 2350.05)
 Routine Maintenance. Work that is planned to be accomplished on a continuing basis,

generally annually or more frequently. (FSH 7709.59.60)

Other than Routine Maintenance. Work that can be deferred without loss of road
serviceability, until such time that the work can be economically or efficiently performed.
The frequency of such work is generally longer than a year. FSH 7709.59.60
 Running Speed. The speed at which an individual vehicle travels over a highway section.
 Serious Damage. Heavy, major, or unusual damage to a highway which severely impairs
the safety or usefulness of the highway or results in road closure. Serious damage must be
beyond the scope of heavy maintenance. (23 CFR 668.103)
 Service Life. The length of time that a facility is expected to provide the desired service.
(FSH 7709.56b)
 Snowmobile. An over-snow vehicle that operates on a track, uses one or more skis for
steering, and has handle-bar steering and a seat designed to be straddled by the operator.
(FSM 2353.05, FSH 2309.18.05)
 Special Use Authorization. A permit, term permit, lease, or easement which allows
occupancy, use, rights, or privileges of National Forest System land. (36 CFR 251.51, 36
CFR 261.2)
 Speed. Distance traveled divided by the time of travel. (Webster).
 State (1). Any of the 50 states, the District of Columbia, and Puerto Rico. (23 USC 101)
 State (2). Any one of the 50 states, the District of Columbia, Puerto Rico, the Virgin
Islands, Guam, and American Samoa. (23 CFR 460.2)
 State (3). Any State, the Commonwealth of Puerto Rico, and the District of Columbia (36
CFR 261.2)
 State (4). Any one of the United States, the District of Columbia, Puerto Rico or the Virgin
islands, Guam, American Samoa, or Commonwealth of the Northern Mariana Islands. (23
CFR 668.103)
 State Transportation Department (1) (STD). The State highway department,

transportation department, or other State transportation agency or commission to which title
23 of the United States Code funds are appropriated. (23 CFR 710.105)
 State Transportation Department (2). The department, commission, board or official of

any State charged by its laws with the responsibility for highway construction. (23 U.S.C.
101)

 Temporary Road or Trail. A road or trail necessary for emergency operations or
authorized by contract, permit, lease, or other written authorization that is not a forest road
or trail and that is not included in a forest transportation atlas. (36 CFR 212.1, FSM 7705)
 Terminal Facility. A transfer point between the forest transportation system and forest
resources served by the system, or between different transportation modes, including
parking areas, turnouts, boat ramps and docks, trailheads, marine access facilities, airfields
and heliports. (FSM 7705)
 Traffic Management Strategies. Options for managing traffic on NFS roads where
appropriate to control traffic. Use one or a combination of the following five strategies for
different modes of travel:
Encourage use. Encourage use consistent with the condition of the road and its
Road Management Objectives (FSH 7709.59).
Accept use. Accept, but do not encourage, use by vehicles that are suitable for the
road.
Discourage use. Discourage some or all types of motor vehicle use.
Eliminate use. Eliminate use by blocking access to the road by motor vehicles.
Prohibit use. Prohibit motor vehicle use. (FSM 7731.11)
 Traffic Rule. A restriction placed on the operation of a vehicle on a road. (FSM 7730.5)
 Traffic Service Level. Describes the significant traffic characteristics and operating
conditions of a road. (FSM 7705, FSH 7709.56, Chapter 4)
 Trail. A route 50 inches or less in width or a route over 50 inches wide that is identified and
managed as a trail. (36 CFR 212.1, FSM 2353.05, FSH 2309.18.05, FSM 7705)
 Trailhead. The transfer point between a trail and a road, water body, or airfield, which may
have developments that facilitate transfer from one mode of transportation to another.
(FSM 2353.05, FSH 2309.18.05)
 Trail Type. A category that reflects the predominant trail surface and general mode of
travel accommodated by a trail.
a. Standard Terra Trail. A trail that has a surface consisting predominantly of the ground
and that is designed and managed to accommodate use on that surface.
b. Snow Trail. A trail that has a surface consisting predominantly of snow or ice and that
is designed and managed to accommodate use on that surface.
c. Water Trail. A trail that has a surface consisting predominantly of water (but may
include land-based portages) and that is designed and managed to accommodate use
on that surface. (FSM 2353.05, FSH 2309.18.05)
 Transportation Facility Jurisdiction. The legal right to control or regulate use of a
transportation facility derived from fee title, an easement, an agreement, or other similar
method. While jurisdiction requires authority, it does not necessarily reflect ownership.
(FSM 7705)
 Travel Management Atlas. An atlas that consists of a forest transportation atlas and a
MVUM or MVUMs. (36 CFR 212.1, FSM 7705)
 Travel Route. A route, such as a county or National Forest System road, or river or trail,
that is open for use by members of the general public. (36 CFR 292.21)
 Traveled Way. The portion of the roadway used for the movement of vehicles, exclusive of
shoulders and auxiliary lanes. (AASHTO, 2001, A Policy on Geometric Design of Highways
and Streets).
 Trucks. These include single-unit, tractor-semitrailer combinations and tractor- semitrailer

in combination with additional trailers. (AASHTO, 2001, A Policy on Geometric Design of
 Unauthorized Road or Trail. A road or trail that is not a forest road or trail or a temporary
road or trail and that is not included in a forest transportation atlas. (36 CFR 212.1, FSM
2353.05, FSM 7705)
Unauthorized roads are categorized into two types and recorded in the SYSTEM linear
event in the Infra Travel Routes database. The two types are:
o Undetermined. Roads where long term purpose and need has yet to be
determined, and
o Not Needed. Roads not needed for long-term management of national forest
resources as determined through an appropriate planning document. (Travel
Routes National Data Dictionary for Roads)
 Utility Terrain Vehicle (UTV) or Side-by-Side. A type of off-highway vehicle that travels on
4 or more low-pressure tires, has a steering wheel or tiller, provides side-by-side seating,
and is of various widths. (FSH 2309.18, FSM 2353.05)
 Vehicle. Any device in, upon, or by which any person or property is or may be transported,
including any frame, chassis, or body of any motor vehicle, except devices used exclusively
upon stationary rails or tracks. (36 CFR 261.2)

 Wheelchair or Mobility Device. A device, including one that is battery-powered, that is
designed solely for use by a mobility-impaired person for locomotion; that is suitable for use
in an indoor pedestrian area; and that may be used by a person whose disability requires
its use anywhere that foot travel is permitted (Title V, sec. 507c, of the Americans With
Disabilities Act and 36 CFR 212.1).(FSM 2352.05, FSH 2309.18.05)

11 References
1. 36 CFR parts 212, 261, and 295. Administration of the Forest Development
Transportation System; Prohibitions; Use of Motor Vehicles Off Forest Service Roads,
Department of Agriculture, Washington D.C., January 12, 2001.
2. Yoder, Robert, Public Forest Service Roads Initiative, Pacific Northwest Region, Road
Managers Workshop, Portland, Or., April 18, 2000.
3. GIS Core Data Dictionary, USDA Forest Service, Washington D.C., March, 2002
(http://fsweb.wo.fs.fed.us/im/standards/gis/coredata).
4. Russell, Carol, Script for creating flattened out event table, Northern Region, USDA
Forest Service, Missoula, MT., 1999.
5. Sun, Steve, Glob Procedures for INFRA Travel Routes, Washington Office, USDA
Forest Service, Washington D.C., 2000.
6. ARC/INFO Data Management-Concepts, data models, database design, and storage,

Environmental Systems Research Institute, Inc., Redlands, CA., 1994
7. INFRA Administrators User Guide, INFRA Software Development Group, Washington,

D.C., 2000 (http://pcs27.f16.r6.fs.fed.us/infra/userguides/admin-ug.htm).
8. EM-7140-24, Guidelines for Digital Map Updates, Geometronics Service Technology

Center, Salt Lake City, UT.
References Travel Routes Data Dictionary Page: 1

12 Appendix A – Flow Charts
Figure 12-1 Road Management Options Coding Details Flow Chart
Figure 12-2 Oil, Gas, and Minerals Road Coding Flow Chart
Appendix A – Flow Charts Travel Routes Data Dictionary Page: 1

Road: Classified, Unclassified, Temporary
Values shown represent typical
database entries, and do not
Conduct Roads Analysis: May be integrated with Landscape & Watershed Analysis
apply to all situations. Please [see FSM 7712.13 – Exhibit 01] Since undetermined roads have not yet
refer to other parts of this
been evaluated for long term need, they
document for specific guidance.
Road Management Decision Process must go through roads analysis and
subsequent decision process.
Classified Roads Temporary Roads 1/ Unclassified Roads

[36 CFR 212.1 & FSM 7705] [36 CFR 212.1 & FSM 7705] [36 CFR 212.1 & FSM 7705]
System = NFSR System = “Other” 2/ 4/ System = TMP System = NOT System = UND
Status = EX Status = EX Juris = FS, “Other” 4/ Status = EX Status = EX
Juris = FS Juris = “Other” Status = EX Juris = FS Juris = FS or ?
OBJ ML = 1-5 C,D 3/ OBJ ML = OBJ ML = D 3/ OBJ ML= C or D 3/ OBJ ML=
OPER ML = 1-5 OPR ML = OPR ML = 2-5 OPER ML = OPER ML =
Service Life = C Service Life = C Service Life = S Service Life = S Service Life =
Road Management Objective
Open for use

Decommission
Restrict Use Convert to Other Uses:
- Trails
Close Levels of Treatment - Other
Put in Storage
(for 1 year or more)
Establish Full Obliteration
When no longer Revegetation Removing Fills
Blocking Drainageways & By Recontouring
needed, identify for & And
Entrance Remove Unstable & Restoring
decommissioning Waterbarring Culverts
Road Shoulders Natural Slopes
or convert to
other uses
1/ Temporary roads are not intended to be tracked in Transportation Atlas [Ref: 7711.1 (5)]. Decommissioned or Converted to
2/ Includes systems such as SH, C, L etc. Converted Road Other Use (ie Trail)
3/ All decisions after 1/12/2002 are subject to RAP. Obj_Name = ROAD Obj_Name = TRAIL
System = “Preserve” 4/ System = NFST
4/ “Other” - Denotes any valid entry from the list of values. Juris = “Preserve” Juris = FS
“Preserve” - Denotes preserve the current value. Status = DE (or CV) Status = EX
OBJ ML = “Preserve”
A converted road requires 2 Actions: Change ROAD Route Status to CV - CONVERTED OPR ML = “Preserve” Update ROAD record ...
Add new TRAIL with Trail Status = EX - EXISTING Service Life = “Preserve” Status = CV
Figure 12-1 Road Management Options (see FSM 7712.11 – Exhibit 01) – Coding Details

OIL
OIL &
& GAS
GAS ROADS
ROADS
OUTSTANDING & RESERVED RIGHTS
FOREST
FORESTPLAN
PLAN//OIL
OIL&&GAS
GASEIS
EIS
Will
Will LEASE
RAP/NEPA YES LEASE
RAP/NEPA
IsIsthis
leasing
leasing be
be
thisroad
roadneeded
neededfor
forLRMP
LRMP
implementation..
implementation.. allowed?
allowed?
PROJECT
PROJECTSPECIFIC
SPECIFICNEPA/RAP
NEPA/RAP
Identify
IdentifyConstruction
Construction&&Maintenance
Maintenancestandards
standardsforforall
allroads
roads
NO YES NO constructed.
constructed.
Determine
Determinemaintenance
maintenancepayment
paymentrates
ratesfor
forall
allroads
roadsused.
used.
DONE
DONE
Can
Canwe
weenter
enter
into
into a coopagreement
a coop agreementfor
for System
System––NFSR
NFSR
public
publicaccess?
access? Other IsIsthis
NO YES Other YES thisroad
roadneeded
needed
System
System–– RMO
RMO for
forLRMP
LRMPimplementation
implementation
Jurisdiction
Jurisdiction––FSFS other
otherthan
thanOGM?
OGM?
Service
ServiceLife
Life- -CC
NO
System
System––PP System
System––NFSR
NFSR
Other Other
Other Other Decommission NO GO
GOTO
TO EXPLORATION
System
System––OGM
OGM System
System–– Decommission EXPLORATION
Jurisdiction the
theroad PRODUCTION?
PRODUCTION? System
System––TMP
Jurisdiction––PP Jurisdiction
Jurisdiction––FSFS road TMP
Service Other
Service Life- -CC
Life Service
ServiceLife
Life––CC Other
Access System
System––OGM
Access Rights -CS
Rights - CS OGM
Jurisdiction
Jurisdiction––FSFS
Service
Service Life- -SS
Life
NO YES RMO
RMO
System System
System––NFSR
System––NFSR
NFSR NFSR
Other
Other RAP/NEPA
RAP/NEPA Other
Other
YES Well
Wellisis System
System
System–– IsIsthe
the road
roadstill needed??
stillneeded System––OGMOGM
abandoned Jurisdiction
Jurisdiction
Jurisdiction––FSFS abandoned Jurisdiction––FSFS
Service Service
Service Life- -CC
Life
ServiceLife
Life- -CC
Figure 12-2 Oil, Gas, and Minerals Road Coding Flow Chart

13 Appendix B – Retired Columns
Used in Tables:
Name: ACCESS RIGHTS RTE_LINEAR_EVENTS
Definition: Dead Linear Event - no longer used after 2007
Reference: National Forest Service Lands Program PRLS 646 (Title 36 Authority: WO
CFR 212.1 FSM 5460.5, FSM 7705, FSM 7710.5, FSH
7709.58)
Overlap: Yes
Linear Event: Yes

All Optional
Business Access Rights linear event records were converted to records in the Authorizations
Rules: Module in 2008. The Access Rights linear event is no longer used. The
AUTHORIZATIONS module may be accessed from the Road or Trail menu in IWeb
Notes:
Former Codes – no longer used
Code Description
AN - ACCESS NEEDED No legal right exists and is needed
CS - COST SHARE A supplement to a road right of way construction and use

agreement has been prepared and signed.
An interest in land owned by another party that entitles the
E - EASEMENT holder to a specific limited use or enjoyment. Will be in
ALP someday.
A right of ingress or egress granted by a government
L - LEASE authority under the terms of the lease. Will be in ALP
someday.
P – PERMIT A written license that has been issued by one party to a
second party granting permission but not vesting a right.
A right of access acquired by continuous use, known to
PR - PRESCRIPTIVE RIGHT and not contested by the landowner, in accordance with
state laws. Complete any additional information in
remarks.
A written agreement between the Forest Service and a
RA - FOREST ROAD AGREEMENT state, county or local government. (FSH 7709.58-ch13.23,
FSH 1509.11, FSM 1530)
RS – RESERVATION A right retained when property ownership was transferred
from one party to another. Will be in ALP someday.
A temporary interest in land owned by another party that
TE - TEMPORARY EASEMENT entitles the holder to a specific limited use or enjoyment for
a specific period of time.
Appendix B – Retired Columns Travel Routes Data Dictionary Page: 1

Retired Columns
Used in Tables:
RTE_BASICS
Name: MASTER_SITE
RTE_LINEAR_EVENTS
Definition: Oracle instance identifier of where the record was originally inserted.
Reference: :
Format: Unit of
Measure:
Data Type: Number Precision: 6 Scale: 0 Mandatory: No
Look Up:

All N/A
Business 1. A dead column - not used. The oracle instance number is concatenated in the CN
Rules: for the route
Notes:
Valid Codes
Code Description

Retired Columns
Used in Tables:
Name: PFSR CLASSIFICATION RTE_LINEAR_EVENTS
A Public Forest Service Road (PFSR) is a designated public road under Forest Service
Definition: jurisdiction that meets the definition of 23 U.S.C. Section 101. The PFSR classification
indicates the status of PFSR designation.
Reference: 23 U.S.C. Section 101, Process for Public Forest Service Authority: WO
Road Designation (and De-Designation) as contained in a
7700 letter from the WO to Regional Foresters 12/17/2001.
Look Up: NAME column in II_CODES Overlap: No
Linear Event: Yes

FS
Business The following criteria must be met for a road to have potential as a PFSR:
Rules:
1.) Objective Maintenance Level 3 – 5
2.) Under Forest Service Jurisdiction
3.) Provide unrestricted access (except for emergencies, seasonal snow closures, scheduled closures)
4.) Serve a compelling public transportation need
The following additional criteria must be met for a road to be designated as a PFSR
5.) Forest must coordinate with states and local road authorities before designation is formally requested
6.) Right-of-Way must be acquired before designating a road as a PFSR (Forest Service must have
jurisdiction)
Additional business rules that apply when a road segment is designated are:
7.) A road segment must be coded as designated within 1 month from the time that the Regional Forester
sends a written response back to the National Forest approving the road as a designated PFSR.
8.) The forest should use the RMO form to document additional applicable public road designation
information such as specific coordination information, contracts, agreements, etc.
9.) The date of the designation should be recorded in the record of events data (see chapter 7)
Notes: 1.) Additional data structures will be used to track project expenditures (See the INFRA Projects Module)
2.) The Forest Service was declared as a Public Road Authority on 10/16/1998 by Gloria Manning, then Acting
Deputy Chief for National Forest Systems.
3.) 23 U.S.C. 101 says in part that a public road is “Any road or street under the jurisdiction of and maintained by
a public authority and open to public travel”.
Valid Codes
Code Description
Identification and inclusion in a network, of those FS roads meeting the
criteria of a PFSR and recorded officially in the Forest Service Infra database
DSG - DESIGNATED PFSR (PFSR CLASSIFICATION). Coordination and concurrence with local
transportation agencies and FHWA - Federal Lands Highway Division has
occurred.
A road proposed by the Forest Service as a potential PFSR after determining
that the facility meets the criteria as a PFSR. Coordination and concurrence
POT - POTENTIAL PFSR with local transportation agencies and FHWA - Federal Lands Highway
Division has not occurred.

Retired Columns
Used in Tables:
Name: STATUS RTE_LINEAR_EVENTS
Definition: Dead Column - Not used
Reference: :
Format: Unit of
Measure:
Look Up:

All N/A
Business 1.) Discontinued column, do not use

Rules:
Notes:

Retired Columns
Used in Tables:
Name: TRANS_ID RTE_BASICS
Definition: Dead column - not used
Reference: :
Format: Unit of
Measure:
Look Up:

All N/A
Business 1. Discontinued column, do not use

Rules:
Notes:

TravelRoutesDataDictionary V2

Uploaded by

Copyright:

Available Formats

TravelRoutesDataDictionary V2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TravelRoutesDataDictionary V2

Uploaded by

Copyright:

Available Formats

Travel Routes

National Data Dictionary

Travel Routes Road User Board

The purpose of this document is to provide business rules, scenarios, and

For the trails Data Dictionary, refer to;

Words in Italics – Instructional comments to the reader on an action that

Introduction Travel Routes Data Dictionary Page: 1

Version Chapter Description Date

2.0 Version 2.0 included the following changes,

Change Log Travel Routes Data Dictionary Page: 1

3.1 Data Structure

Road data modules

Record of Events Access & Travel Work Items Road Maintenance

Roles: To manipulate the data in I-Web you must be granted access to

Figure 3-2 Required Roles

I1 OBJ_CLASS FK1,I1,U1 RTE_CN

3.3.1.1.1 Road Core Table (II_ROAD_CORE)

3.3.1.1.2 Road Linear Events (II_ROAD_LINEAR_EVENTS_rrff)

3.3.1.1.3 MVUM Road “snapshot” tables (II_MVUM_ROAD_ALLOW and

3.4 Spatial Component

3.4.1 Routes – Road and Trail

Distance (+/-), in dataset distance units, of

Figure 3-4. Attribute table for Road feature class

Figure 3-5 Domain for Rt_Action field

The local route number for a

Distance (+/-), in dataset distance

Area of feature in internal units Double 8 0 0 Y

Retired and obsolete columns are located in the appendix.

4.1 System /Audit Columns

Table/Column Definitions Travel Routes Data Dictionary Page: 1

Data Type: varchar2 Size: 30 Mandatory: No

Look Up: THIS_DB_INSTANCE

Table/Column Definitions Travel Routes Data Dictionary Page: 4

Format: Sequence Number & Oracle Instance Number

Data Type: varchar2 Size: 34 Mandatory Yes

Requirements for Population

Table/Column Definitions Travel Routes Data Dictionary Page: 5

Format: Sequence Number & Oracle Instance Number

Data Type: varchar2 Size: 34 Mandatory: Yes

Requirements for Population

Table/Column Definitions Travel Routes Data Dictionary Page: 6

Data Type: number Precision: 8 Scale: 4 Mandatory: Yes

Requirements for Population

6) Measure points must run in the same direction as those indicated in

Table/Column Definitions Travel Routes Data Dictionary Page: 7

Table/Column Definitions Travel Routes Data Dictionary Page: 8

Figure Table/Column Definitions-1 US Route Beginning Measure Example

Figure Table/Column Definitions-2 Route Beginning Measure Example

Table/Column Definitions Travel Routes Data Dictionary Page: 9

Definition: Additional comments or descriptive remarks.

Data Type: varchar2 Size: 2000 Mandatory: No

Requirements for Population

Table/Column Definitions Travel Routes Data Dictionary Page: 10

Figure 5.1 RTE_BASICS Table Diagram

Route Basics Table Travel Routes Data Dictionary Page: 1

Data Type: varchar2 Size: 30 Mandatory: Yes

Requirements for Population

Business 1.) Only ROUTE is used for Roads and Trails