Description: This field indicates the type and number of points at which traffic is allowed to enter or exit a roadway. Access control is on primary roads only and is obtained from the color‑coded map provided by the Office of Maintenance.
Description: The All Systems Annual Oversize Permit is an annual permit that allows for unlimited trips on all State, US and Interstate routes as well as approved city/county roads for loads which are categorized unde rthe following maximum dimensions:Maximum Dimensions for Legal Loads:Length: 120’Width: 16’Height: 15’ 5”Gross Weight: 80,000 poundsAxle Weight: 20,000 pounds per axleAt certain dimensions within the allowed limits there are requirements to contact Motor Carrier Services (MCS) for route approval on all State, US and Interstate routes:120' long x 12' 5" wide x 13' 10" high - unlimited distance - no routing required120' long x 14' 6" wide x 15' 5" high - movement restricted to 50 mile radius unless the route continues on at least 4-lane roads or trip routes are obtained from Motor Carrier Services120' long x 16' wide x 15' 5" high - trip routes must be obtained75' long x 12' 5" wide x 14' 6" high - maximum dimensions for hauling hayCarriers are required to check with local officials when traveling on county roads or city streets for bridge embargo, detour, road embargo and vertical clearance information. Contact information for individual routes is available by clicking on the route.
Service Item Id: 3631ba14238a446dbb17495be2d4cdba
Copyright Text: Iowa Department of Transportation,
Description: Contains records on construction year, aggregate type and source location, pavement type, surface type, layer types and widths (base, subsurface, surface) construction year and project information (where available)
Description: This field is used on municipal or urban road segments and indicates the right of way cost group code in the following manner for all road systems:Rural/Agricultural on Both Sides (Lowest Cost)Low CostAverage CostHigh Cost
Description: Highway helper assigned patrol routes in the State of Iowa. Highway helper vehicles can be dispatched from these routes to other off-route areas, but these are the assigned patrol areas.
REGION
(
type: esriFieldTypeInteger, alias: REGION
, Coded Values:
[1: Des Moines/Ames]
, [2: Cedar Rapids/Iowa City]
, [3: Council Bluffs]
, ...2 more...
)
Description: Within the extent of all Federal-aid eligible roads, a random selection of roadway sections is used to represent various attributes at a system-wide level for the purposes of assessing the performance and condition of the network. This process helps to reduce any burden that may be imposed on the States to perform data collection to meet their HPMS reporting requirements. These sections of the network are referred to as Sample Panel sections. Moreover, the Sample Panel sections are selected randomly and are intended to give a statistically valid representation of the State's road network. Due to the structure of the HPMS data model, the States are not required to extract the Sample Panel data items, as long as the data in their submittal covers the Sample Panel. States are encouraged to submit their entire dataset for each data item. FHWA will dynamically assign values to the Sample Panel sections, using the data provided by the States. This should help to lessen the data processing burden on States that are currently collecting more than the minimum coverage.
Description: The Infrastructure Condition Evaluation (ICE) layer is based on the result of merging seven different criteria using a linear overaly process that includes Iowa DOT's in-house Roadway Asset Management System (RAMS) and Pavement Management Information System (PMIS).
CORRIDOR_ID
(
type: esriFieldTypeSmallInteger, alias: CORRIDOR_ID
, Coded Values:
[470: 470 - I-380 terminus to IA 27]
, [471: 471 - IA 3 to US 75]
, [472: 472 - US 218 to IA 3]
, ...471 more...
)
Description: Lane type based on characteristics described by the Federal Highway Administration (FHWA), Highway Performance Monitoring System (HPMS) according to allowed traffic behavior in the lane.
Description: This field indicates the left side or inside shoulder material type for all road systems using the Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) criteria.
Description: This field indicates a maintenance contract with a city or county. The Office of Maintenance-Programs is responsible for keeping this information current. This is used for primary and institutional roads.
Description: This field is used to identify the Maintenance District number. The District is assigned by the Office of Maintenance-Programs. This is used on primary and institutional roads. Districts 1‑6
Description: The characteristics of the median on all road sections are entered using the following criteria. If median has a curb, the curb is placed on the inside shoulder. A barrier is .152 meters or more. A painted median is not considered a median.
Description: This code indicates the width of the median between the edges of traffic lanes recorded to the nearest foot. This field is applicable for all road systems.
Description: Total number of lanes on the route according to criteria established by the Federal Highway Administration (FHWA) Highway Performance Monitoring System (HPMS) criteria.
PARKING_TYPE
(
type: esriFieldTypeInteger, alias: PARKING_TYPE
, Coded Values:
[1: NO PARKING IS POSTED]
, [2: PARALLEL ONE SIDE - NO PARKING OTHER SIDE]
, [3: PARALLEL ONE SIDE - DIAGONAL OTHER SIDE]
, ...6 more...
)
Description: This layer has been retired form use in 2025 - The Commercial Industrial Network has been moved to the layer Commercial Network in RAMS. This field is a five‑level classification for use in planning and programming for the primary road system. The Office of Systems Planning is responsible for providing the data for this field.
Description: A level crossing, or grade crossing, is an intersection where a railway line crosses a road or path at the same level, as opposed to the railway line crossing over or under using a bridge or tunnel.
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
LT1PASSMOV
(
type: esriFieldTypeInteger, alias: I.22. LESS THAN 1 PASSENGER TRAIN PER DAY
, Coded Values:
[1: LESS THAN ONE PER DAY]
, [2: ONE OR MORE PER DAY]
)
PASSCNT
(
type: esriFieldTypeInteger, alias: I.22. AVERAGE PASSENGER TRAIN COUNT PER DAY
)
DEVELTYPID
(
type: esriFieldTypeInteger, alias: I.23. TYPE OF LAND USE
, Coded Values:
[11: OPEN SPACE]
, [12: RESIDENTIAL]
, [13: COMMERCIAL]
, ...5 more...
)
XINGADJ
(
type: esriFieldTypeInteger, alias: I.24. IS THERE AN ADJACENT CROSSING
, Coded Values:
[1: YES]
, [2: NO]
)
DAYTHRU
(
type: esriFieldTypeInteger, alias: II.1.A. TOTAL DAY THRU TRAINS
)
NGHTTHRU
(
type: esriFieldTypeInteger, alias: II.1.B. TOTAL NIGHT THRU TRAINS
)
TOTALSWT
(
type: esriFieldTypeInteger, alias: II.1.C. TOTAL SWITCHING TRAINS
)
TOTALLTR
(
type: esriFieldTypeInteger, alias: II.1.D. TOTAL TRANSIT TRAINS
)
LT1MOV
(
type: esriFieldTypeInteger, alias: II.1.E. CHECK IF LESS THAN ONE MOVEMENT PER DAY
, Coded Values:
[1: LESS THAN ONE MOVEMENT PER DAY]
, [2: ONE OR MORE MOVEMENT PER DAY]
)
WEEKTRNMOV
(
type: esriFieldTypeInteger, alias: II.1.E. HOW MANY TRAINS PER WEEK
)
YEARTRNMOV
(
type: esriFieldTypeInteger, alias: II.2. YEAR OF TRAIN COUNT DATA
)
MAXTTSPD
(
type: esriFieldTypeInteger, alias: II.3.A. MAXIMUM TIMETABLE SPEED
)
TRAFICLN
(
type: esriFieldTypeString, alias: IV.1. NUMBER OF CROSSING LANES, length: 2
)
TRAFLNTYPE
(
type: esriFieldTypeInteger, alias: IV.1. TYPE OF CROSSING LANES
, Coded Values:
[1: ONE WAY TRAFFIC]
, [2: TWO WAY TRAFFIC]
, [3: DIVIDED TRAFFIC]
)
Description: provides localized, but consistently placed points of reference from which to measure a linear location. The reference post LRM uses the mileposts along the primary routes. Note that the LRS does not allow using the post values as a representation of accumulated distance; this subsystem applies the posts and relative offsets to locate events. For example, the accumulated distance of 10.06 is not the same location as reference post 10, offset 6 miles.
Description: This field designates the difference between mainline and non‑mainline road sections, and designates other normal roadway uses. (This field is applicable only to primary roads.)
Color: [0, 0, 0, 255] Background Color: N/A Outline Color: N/A Vertical Alignment: bottom Horizontal Alignment: left Right to Left: false Angle: 0 XOffset: 0 YOffset: 0 Size: 10 Font Family: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
HISTORICAL_SIGNIFICANCE
(
type: esriFieldTypeInteger, alias: HISTORICAL_SIGNIFICANCE
, Coded Values:
[1: 1 - BRIDGE IS ON NATIONAL REGISTER OF HISTORICAL PLACES]
, [2: 2 - BRIDGE IS ELIGIBLE FOR NATIONAL REGISTER OF HISTORICAL PLACES]
, [3: 3 - BRIDGE IS POSSIBLY ELIGIBLE FOR NATIONAL REGISTER OF HISTORICAL PLACES]
, ...2 more...
)
MAINT_DESCRIPTION
(
type: esriFieldTypeString, alias: MAINT_DESCRIPTION, length: 1
, Coded Values:
[L: L - LEFT BRIDGE SB_WB LANE OF TWIN BRIDGES]
, [R: R - RIGHT BRIDGE NB_EB LANE OF TWIN BRIDGES]
, [S: S - SINGLE BRIDGE ON NORMAL ROADWAY]
, ...6 more...
)
Description: This layer contains items such as Culver Inlets, Sign Supports, Light Masts, Walls that are needed for the bridge office to add projects related to the Misc Structures to PPMS
TOLL_CHARGED
(
type: esriFieldTypeInteger, alias: TOLL_CHARGED
, Coded Values:
[1: TOLL CHARGED IN ONE DIRECTION ONLY]
, [2: TOLL CHARGED IN BOTH DIRECTIONS]
, [3: NO TOLL CHARGED]
)
TOLL_AUTHORITY
(
type: esriFieldTypeInteger, alias: TOLL_AUTHORITY
, Coded Values:
[70: FRANK E. BAUER BRIDGE]
, [71: FORT MADISON BRIDGE]
, [80: BELLEVUE BRIDGE]
, ...3 more...
)
TOLL_TYPE
(
type: esriFieldTypeInteger, alias: TOLL_TYPE
, Coded Values:
[1: THIS SECTION HAS TOLL LANES BUT NOT SPECIAL TOLLS (E.G. HOT LANES)]
, [2: THIS SECTION HAS HOT LANES]
, [3: THIS SECTION HAS OTHER SPECIAL TOLLS]
)
Description: Coded only for Des Moines, Council Bluffs and Davenport urban areas with a population of 200,000 or more people. The purpose of this data item is to identify the general character of the land surrounding each road segment. The process of doing so, however, must fully recognize that "pure" delineations are the exceptions rather than the rule. This field is applicable to all road systems.
Description: The calibration points establish route segment beginning and ending references along a RAMS route in miles that allows RAMS to interpolate measurements along a route.
Service Item Id: 3631ba14238a446dbb17495be2d4cdba
Copyright Text: Iowa Department of Transportation, Analytics Bureau
Description: The centerline geometry provides a base geometry for all event layers to exist as a representation of a surface route in the RAMS database.
Service Item Id: 3631ba14238a446dbb17495be2d4cdba
Copyright Text: Iowa Department of Transportation, Analytics Bureau
Description: The network feature class contains the route features for use in the ALRS. These routes have attributes, geometry that comes from the centerline feature class, and calibration that comes from the calibration point feature class. Combined these elements constitute a route with a LRM that can be used to locate events on that route. Each route should have a unique route identifier, called a routeID. This routeID can be a single field or a concatenation of multiple fields. If the network will use a concatenated routeID, all the fields that compose the routeID should be present in the network feature class, in addition to the routeID field.
Description: The network feature class contains the route features for use in the ALRS. These routes have attributes, geometry that comes from the centerline feature class, and calibration that comes from the calibration point feature class. Combined these elements constitute a route with a LRM that can be used to locate events on that route. Each route should have a unique route identifier, called a routeID. This routeID can be a single field or a concatenation of multiple fields. If the network will use a concatenated routeID, all the fields that compose the routeID should be present in the network feature class, in addition to the routeID field.
Description: The network feature class contains the route features for use in the ALRS. These routes have attributes, geometry that comes from the centerline feature class, and calibration that comes from the calibration point feature class. Combined these elements constitute a route with a LRM that can be used to locate events on that route. Each route should have a unique route identifier, called a routeID. This routeID can be a single field or a concatenation of multiple fields. If the network will use a concatenated routeID, all the fields that compose the routeID should be present in the network feature class, in addition to the routeID field.
Description: The network feature class contains the route features for use in the ALRS. These routes have attributes, geometry that comes from the centerline feature class, and calibration that comes from the calibration point feature class. Combined these elements constitute a route with a LRM that can be used to locate events on that route. Each route should have a unique route identifier, called a routeID. This routeID can be a single field or a concatenation of multiple fields. If the network will use a concatenated routeID, all the fields that compose the routeID should be present in the network feature class, in addition to the routeID field.
Description: The network feature class contains the route features for use in the ALRS. These routes have attributes, geometry that comes from the centerline feature class, and calibration that comes from the calibration point feature class. Combined these elements constitute a route with a LRM that can be used to locate events on that route. Each route should have a unique route identifier, called a routeID. This routeID can be a single field or a concatenation of multiple fields. If the network will use a concatenated routeID, all the fields that compose the routeID should be present in the network feature class, in addition to the routeID field.