1. M E E T I N G F E D E R A L R E Q U I R E M E NT S F O R
M A P P I N G A L L P U B L I C R O A D S
All Roads Network of Linear-
Referenced Data

2. Overview
 What is the All Roads Network of
Linear-Referenced Data (ARNOLD)?
 Why is FHWA Requiring an All
Roads Network?
 How Many Centerline Miles does
ITD Certify Each Year?
 What does ITD Already Have?
 What is ITD Working On?
 What is Needed to Meet Federal
Requirements?
 If ARNOLD becomes the unified
transportation layer, how do we
build one GIS layer?

3. What is the All Roads Network (ARNOLD)?
BACKGROUND
• Long-held desire by state and federal agencies to build a unified
network of roads, as explored in Transportation for the Nation (TFTN).
• The data system is now in place at FHWA to handle the data through
the Highway Performance Monitoring System (HPMS).
• The Governmental Affairs Office identified redundancies in geospatial
data between federal and local agencies.
REQUIREMENTS
• FHWA memo sent August 2012 requires all states to provide:
• Line work and LRS data for all public roads.
• Dual carriageway line work for divided roads.
• Due June 15, 2014 per memo, but ITD submitting June 15, 2015.

4. Why is FHWA Requiring ARNOLD?
MAP-21
• Federal legislation requires all accidents be locatable.
23 CFR 460
• This federal code requires all states and U.S. territories certify public road
mileage in order to receive apportioned Safety funds. ARNOLD will provide
validation of the mileage being provided by the states.
NEEDS OF FHWA AND OTHER AGENCIES
• There is a strong desire to make all bridges locatable.
• ITD’s understanding is that FHWA is working with the U.S. Census Bureau
to make the HPMS GIS layer the base for U.S. Census maps.
• Governmental Affairs Office (GAO) identified a need to reduce duplication
of geospatial efforts among governmental agencies.

5. State-wide Public RoadsState-wide Public Roads
Breakdown of Public
Roads
Breakdown of Public
Roads
Including federal lands
roads, Idaho certifies
approximately 48,000
centerline miles of
roadway each year.
The following are public
road centerline miles
by category:
 Federal: 8,000 miles
 ITD: 5,000 miles
 Local agencies &
Counties: 29,000
 Other: 6,000 miles
Approximately How Many Public Roads are in Idaho?

6. What does ITD Already Have?
 ITD Roads Layer
 Dataset includes complete State Highway System (SHS) roads, functionally
classed roads, federal-aid roads and many rural local roads.
 Additional categories of roads currently being added to the layer include urban
and city roads, federal agency roads and other roads.
 A new linear referencing system (Agile Assets’ Network Manager)
that maintains the geometry as a routable dataset (stores m-values)
of the SHS and improved local public roads and associated event
data.
 Mature process for maintenance and upkeep of SHS.
 Local Road Inventory program: Mature and collaborative process
with LHTAC, counties (44) and local highway districts (57) to
maintain improved local public roads. Mandated by Idaho State
Code for certification by ITD’s Director and the Governor. Formal
process through which local funds are apportioned to locals.
 Edge-matching of existing ITD data is complete.

7. What is ITD Working On?
 Developing a process to meet federal mandate by June 2015.
 Incorporating geometry for Idaho cities into Network
Manager. LHTAC supplied this data for most rural cities and
a few urban cities.
 Ongoing improvement of accuracy of our GIS data in the
Local Road Inventory Program. All but 2 local highway
districts/county road and bridge departments have approved
the updated geometry.
 Collaborating with the Transportation TWG to explore the
potential integration of ARNOLD and the Unified
Transportation Layer into a single GIS dataset.

8. What Does ITD Need to Meet Federal Mandate?
 Road geometry for some small cities with a population
between 5,000 – 50,000.
 Road geometry for state agencies (example: Idaho Parks
and Recreation).
 Road geometry for some large urban areas with a
population greater than 50,000.
 Definitions for dual carriageways and divided highways,
standardized for SHS and local roads.
 Model for maintaining city, state agency and other road
data in Network Manager.
 Processes for building and maintaining addressing data.

9. Items to Reconcile if ARNOLD data becomes the
Unified Transportation Layer?
 Process to build and maintain data: Will ITD be responsible or
perhaps a web application can be deployed?
 ITD’s current LRM is Segment Codes and Milepoints. Need to
create a process for entities outside the Agency to work within that
framework to create new geometry and maintain existing data.
 ITD road geometry compared to county GIS Department-
maintained geometry: Is the county geometry “good enough” to
meet state and federal requirements? Who has authority to supply
this data?
 Incorporation of and integration with Idaho State Police geometry.
 Standardization of core attributes.
 E-911 needs—requirement for addressing on private roads?
 Conflict resolution process: How do we resolve which geometry to
use if involved parties can’t agree?

10. W E N D Y B A T E S
G I S M A N A G E R
( 2 0 8 ) 3 3 2 - 7 8 8 9
W E N D Y . B A T E S @ I T D . I D A H O . G O V
M A R G A R E T P R I D M O R E
H P M S C O O R D I N A T O R
( 2 0 8 ) 3 3 4 - 8 2 2 1
M A R G A R E T . P R I D M O R E @ I T D . I D A H O . G O V
ITD Contacts