| 4 | | TWP_NAME | TWP_NAME | Identifies the name of the township where the DESTAPE event is located, if applicable. | OTS/RIGIS | Indicates if the DESTAPE event is located within a township. | Based on the location of a DESTAPE feature. | Based on the geometry of the road segment or from other source information the RIMS user assigns the appropriate code value. | In the ODOT Enterprise Warehouse this field displays the township name. In the RIMS Road Inventory/Mashup the field is displayed as a concatenation of Township Name, County Code, and Township Number. | N/A | N/A | N/A | Varchar(50) | A complete list of these codes is in Appendix B - Township Numbers and FIPS Codes. | |
| 4 | | TWP_FIPS_CD | N/A | Federal Information Processing System (FIPS) code that uniquely identifies which township the DESTAPE event is located, if applicable. | OTS/RIGIS | Identifies the township FIPS code where a roadway segment is located. | Assigned by the National Institute of Standards and Technology | | The township FIPS is not coded in DESTAPE but is calculated and populated in the ODOT Enterprise Data Warehouse.
| N/A | N/A | N/A | Char(5) | A complete list of coces is in Appendix B - Township Numbers and FIPS Codes. | |
| 4 | | STREET_SUFFIX_CD | ST_X | Part of the posted street name and identifies the named street suffix if applicable. For example: Crossroads Blvd. | OTS/RIGIS | Descriptive characteristic of the posted street name. | Publication 28, Postal Addressing Standards | Postal Explorer (usps.com) | | May be used in conjuction with Street Name Prefix, Street Name, and Suffix when applicable. | N/A | N/A | N/A | Varchar(4) | A complete list of these codes is in Appendix D - Street Name Suffixes and Descriptions. | |
| 4 | | STREET_NAME | ST_NAME | A familiar designation for a route. | OTS/RIGIS | For tracking information by a specific route and is helpful when a route number is not known. | Source could be from RIMS, project plans, or information received from outside sources. | | May be used in conjunction with Street Name Prefix, Street Name Suffix, and Street Direction Code when applicable. | N/A | (9) Route/Street Name | (9) Route/Street Name | Varchar(50) | | |
| 4 | | STREET_DIR_SUFFIX_CD | ST_2X | Part of the posted street name and identifies the named street direction if applicable. Example: Main St SW | OTS/RIGIS | Descriptive characteristic of the posted street name. | Source could be from RIMS, project plans, or information received from outside sources. | | May be used in conjunction with Street Name Prefix, Street Name, and Suffix when applicable | N/A | N/A | N/A | Varchar(2) | Code=Description N=North E=East S=South W=West NE=Northeast NW=Northwest SE=Southeast SW=Southwest | |
| 4 | | STREET_PREFIX_DIR_CD | ST_PRE | Identifies the named street direction, if applicable. | OTS/RIGIS | Descriptive characteristics of the posted direction of the street name. | Plans, imagery, or other jurisdictional sources. | | | N/A | | N/A | Varchar(1) | Code=Description
N=North
S=South
E=East
W=West
| |
| 4 | | STL_NBR | N/A | Calculated logpoint for routes that traverse multiple counties. | OTS/RIGIS | Identifies a statewide logpoint for a given DESTAPE event. | Generated using route geometry and county based logpoints from the RIMS database | Code in decimal format to the nearest thousandth of a mile. | Geometry and logpoints from the county based DESTAPE events are used to calculate the statewide logpoints for the same event and are published in the ODOT Enterprise Data Warehouse. | N/A | N/A | N/A | Numeric(7,3) | | |
| 4 | | ROUTE_NBR | RT | Number convention for identifying a route. | State System=Director of Transportation, County/Township=County Engineer, Municipal=OTS assigns, Other=OTS assigns | Positions 7-11 of the NLF_ID code, used by business units and information systems across ODOT to organize and manage processes and information | RIMS user derives from roadway changes communicated through Director’s Journal, County Commissioners, Township Trustees, or Office of Technical Services. | | Each state system route number is unique within Ohio. Local roadways are unique within each county. Route numbers are always five digits and zeropadded. For example, RIMS stores the route number for Interstate 71 as 00071 and the route number for State Route 161 as 00161. | Item 17 Route Number | (8) Route Number | (8) Route Number | Char(5) | Route numbers may contain letters, numbers, or special characters. | |
| 2, 3 | | STL_END_NBR | N/A | The terminus point for a given section of road that is rounded to three decimal
places after the zero. This identifies the state traversal measures independent of
the county measures.
| OTS/RIGIS | For identifying the ending point of a section for spatial referencing purposes at
the statewide level.
| Calculated using the originating location of a route within the state.
| | These measures are continuous across the entire state without resetting to zero
at the county border. The traversal is relative to the entire state boundary as
opposed to the county boundary and corresponds conceptionally to the state
milepost. The code is in decimal format to the nearest thousandth of a mile.
| N/A | N/A | N/A | Numeric(8,3) | | |
| 2, 3 | | STL_BEGIN_NBR | N/A | The point of origin for a given section of road that is rounded to three decimal places after the zero. This identifies the state traversal measures independent of the county measures.
| OTS/RIGIS | For identifying the beginning point of a section for spatial referencing purposes at the statewide level.
| Calculated using the originating location of a route within the state.
| | These measures are continuous across the entire state without resetting to zero at the county border. The traversal is relative to the entire state boundary as opposed to the county boundary and corresponds conceptionally to the state milepost. Code in decimal format to the nearest thousandth of a mile.
| N/A | N/A | N/A | Numeric(8,3) | | |
| 4 | | SPEC_DESC_IND | GOES | This identifies on which side of the road the feature is located.
| OTS/RIGIS | For use in locating features associated with the route. | Based on the location of a DESTAPE feature. | | This item is only coded when the Record Type Code (RECORD_TYPE_CD) is I or C. For example: If a corporation boundary or an intersection is only on the left side of the road then the code will be L indicating left. | N/A | N/A | N/A | Varchar(1) | Code=Description L=Left R=Right I=Interchange Blank | |
| 2, 3, 4 | | | N/A | The field contains the shape of the geometry for the section of a route. | OTS/RIGIS | Shows the geometry of a route segment. | | | Coordinates represented in NAD 832 Ohio State Plan South geographic projection. | N/A | N/A | N/A | Geometry | | |
| 4 | | SEQUENCE _NBR | SEQ | A code that allows for multiple events to occur at the same logpoint. | OTS/RIGIS | Differentiates between recorded events happening at the same location. | Based on the location of a DESTAPE feature. | | The numeric order 1-9 is applied based on the importance of the event. For example, leave records must be SEQ = 4 and re-enter records must be SEQ = 5. End of route records must be SEQ = 9. | N/A | N/A | N/A | Varchar(1) | Numeric 1-9. A complete list of these codes is in Appendix K - DESTAPE Record Type Codes. | |
| 4 | | ROAD_DIRECTION_CODE | TEND | Identifies a change from the predominant direction for a route segment. | OTS/RIGIS | Identifies when a route segment travels in a direction different than the coded predominant direction. | Based on the geometry of the route segment. | | This is only coded when a route segment direction is different than the predominate route direction (INV_DIRECTION_CD). | N/A | N/A | N/A | Varchar(1) | Code=Description N=North S=South E=East W=West | |
| 4 | | RECORD_TYPE_CD | TYPE_ | Records the type of event that occurs at a given location. | OTS/RIGIS | Identifies the type of event at a given location. | Based on the location of a DESTAPE feature. | | Appendix K gives further requirements for the description text used with the Record Type Code. | N/A | N/A | N/A | Varchar(1) | A complete list of these codes is in Appendix K - DESTAPE Record Type Codes. | |
| 2, 3, 4 | | PERP_YEAR_NBR | N/A | Identifies the calendar year the data was published. | OTS/RIGIS | Identifies the calendar year the data was published.
| | | | BeginDate | N/A | N/A | Number(4,0) | Four-digit calendar year (e.g., 2020)
| |
| 4 | | OBJECTID | OBJECTID | This field is unique key to this table and is created as part of any registered table by Esri. | OTS/RIGIS | Unique identifier for each record. | | | | N/A | N/A | N/A | int | | |
| 2, 3, 4 | | CARDINALITY_CD | N/A | Roadways should be inventoried in the predominant direction from south to
north and west to east.
| OTS/RIGIS | Position 14 of the NLF_ID code. Differentiates between single and dual carriageway routes.
| RIMS user derives from business rules to identify route as cardinal or non-cardinal.
| | On a divided highway such as an interstate there would be two inventories, one for each direction of the highway. Both inventories shall be inventoried in the cardinal direction (i.e., south to north and west to east.) Cardinal designation can be used for either a single or dual carriageway following the cardinal direction. Non-cardinal designation shall only be used on a divided route where the route does not follow a cardinal direction.
| N/A | N/A | N/A | Char(1) | Code=Description
C=Cardinal
N-Non-cardinal
| |
| 2, 4 | | ROUTE_EXTENSION_CD | RT_X | Defines a specified characteristic of a state transportation facility. Each character has a specific meaning. | OTS/RIGIS | Position 13 of the NLF_ID code. It assigns a descriptive qualifier to a route.
| RIMS user derives from Director's Journal and/or OTS.
| | Utilized for State System routes (IR, US, SR) with one exception. Exception: “P” is used for proposed state and off-state system routes. | N/A | N/A | N/A | Char(1) |
Code=Description *=Default A=Alternate B=Bypass C=Connector route D=Directional Alternate (1st within county) E=East Bound F=Directional Alternate (2nd within county) G=Directional Alternate (3rd within county) I=Interchange Roadway J=Waiting for final disposition (abandonment or transfer) K=Turnpike N=North Bound P=Proposed (not built) S=South Bound
| |
| 2, 3, 4 | | ROUTE_SUFFIX_CD | N/A | This field has legacy meaning from ODOT’s Local Roadway System Database and is only used on an off-state system route. It is an extension of the Route Number
(ROUTE_NBR). It has no specific meaning.
| OTS/RIGIS | Position 12 of the NLF_ID code. Differentiates ‘mainline’ routes from ‘child’ routes or is used to differentiate routes that would otherwise have the same
number.
| RIMS user derives from roadway changes communicated through County
Engineers, or other sources.
| Based on provided source information, RIMS user assigns appropriate system
code value.
| This could be a number, letter, or special character—asterisk (*) is the default value and represents no suffix.
Examples:
For CR1, positions 7-12 for County Route 1 in Stark County are coded as 00001* For CR1A, positions 7-12 for Stark County Route 1A are coded as 00001A
| N/A | N/A | N/A | Char(1) | Asterisk (*) is the default value where no route suffix is assigned. Otherwise, the
value is an alphanumeric or a special character.
| |
| 2, 3, 4 | | ROUTE_TYPE_CD | DESG | Basic transportation grouping or system that the facility belongs to providing additional detail about the route system.
| OTS/RIGIS | Position 5-6 of NLF_ID code, used by business units and information systems across ODOT to organize and manage processes and information.
| RIMS user derives from roadway changes communicated through Director’s Journal, County Engineers, or other sources.
| |
Route Type further indicates the primary ownership of the route segment with some exceptions. For some business purposes there are routes assigned an NLF_ID of County or Township when situated within a municipal boundary. Because they reside inside a city boundary, they are municipal routes even when assigned a ROUTE_TYPE of CR or TR. ODOT tracks this information using a combination of fields including MILEAGE_CLASS and MUNI_CODE_LEFT and/or MUNI_CODE_RIGHT. For example, if a route assigned as Route Type CR is located within a municipal boundary it will be coded as MILEAGE_CLASS = 2 and the MUNI_CODE_LEFT and MUNI_CODE_RIGHT will be populated.
| N/A | N/A | N/A | Char(2) | Code=Description
AC=Army Corps of Engineers AR=U.S. Army Roads BK=Bike Route (Trail) CN=Connecting Road CR=County Road DD=Department of Defense Road DE=Department of Energy DR=Driveway FR=Forest Road FW=National Fish and Wildlife Road IR Interstate MR=Municipal Street NA=NASA Road NP=National Park Service Road NR=Natural Resources Road (Park Road) NV=U.S. Navy Road PL=Parking Lot RA=Ramp RE=Rest Area Entry/Exit RR=Railroad Track SP=Emergency Vehicle Turnaround (Spur) SR State Route TR=Township Road US=United States Route WS=Weigh Station Entry/Exit
| |
| 2, 3, 4 | | COUNTY_CD | COUNTY_CODE | The standard ODOT three letter abbreviation of Ohio's county names. | OTS/RIGIS | Position 2-4 of the NLF_ID code, used by business units and information systems across ODOT to organize and manage processes and information.
| RIMS user determines county assignment based on segment geometry location within the ODOT county boundary polygon. | | | Item 63 County Code | (2) Coundy Code | N/A | Char(3) | A complete list of these codes is in Appendix A - County Attribute Values and Codes.
| |
| 2, 3, 4 | | JURISDICTION_CD | JURIS | Identifies the primary legal authority of a transportation facility.
| OTS/RIGIS | Position 1 of the NLF_ID code, used by business units and information systems across ODOT to organize and manage processes and information.
| RIMS user derives from roadway changes communicated through the Director's Journal, County Engineers, or other sources.
| Based on provided source information, RIMS user assigns appropriate system code value.
| Jurisdiction indicates the primary ownership of the route segment with some exceptions. For some business purposes there are routes assigned an NLF_ID of County (C) or Township (T) when situated within a municipal boundary. Because they reside inside a city boundary, they are municipal routes even when assigned a Jurisdiction of C or T. ODOT tracks this information using a combination of fields including MILEAGE_CLASS and MUNI_CODE_LEFT and/or MUNI_CODE_RIGHT. For example, if a route assigned as Jurisdiction C is located within a municipal boundary it will be coded as MILEAGE_CLASS = 2 and the MUNI_CODE_LEFT and MUNI_CODE_RIGHT will be populated. | N/A | N/A | N/A | Char(1) | Code=Description
C=County
F=Federal
M=Municipal
P= Private
S=State
T=Township | |
| 2, 3, 4 | | NLF_ID | N/A | The Network Linear Feature ID (NLF_ID) combines seven components from the county network that describe administrative and other characteristics related to a route line. This is the primary key field which allows ODOT’s graphic roadway network geometric segments to be linked to business data attributes.
| OTS/RIGIS | NLF_ID is the basis for identifying unique roadway segments in ODOT’s geospatial geometric map layers. It is the key field that ties roadway graphics to all ODOT business data attributes that can be displayed on a map.
| System aggregation of multiple fields within RIMS.
| RIMS user determines based on business requirements.
| | Route ID | N/A | N/A | Char(14) | The following is a breakdown of the seven components by position in the code string:
Position 1 Jurisdiction Code (JURISDICTION_CD): Primary legal authority of transportation facility:
Code=Description S=State
C =County
T=Township
M=Municipal
F=Federal
P=Private
Positions 2-4 County Code (COUNTY_CD): Standard ODOT three letter abbreviation of Ohio’s county names. A complete list of these codes is in Appendix A - County Attribute Values and Codes.
Example: ADA - Adams, ALL - Allen, ASD - Ashland, etc. Positions 5-6 Route Type Code (ROUTE_TYPE_CD): Basic transportation grouping or system that the facility belongs to: Code=Description AC=Army Corp of Engineers
AR=U.S. Army Roads
BK=Bike Route (Trail)
CN=Connecting Road CR=County Road
DD=Department of Defense Road
DE=Department of Energy
FR=Forest Road
FW=National Fish and Wildlife Road
IR=Interstate
MR=Municipal Street
NA=NASA Road
NP=National Park Service Road (Federal Park Road)
NR=Natural Resources Road (State Park Road)
NV=U.S. Navy Road
RA=Ramp
RE =Rest Area Entry/Exit
RR Railroad Track
SP=Emergency Vehicle Turnaround (Spur)
SR=State Route
TR=Township Road
US=United States Route
WS=Weigh Station Entry/Exit
Positions 7-11 Route Number (ROUTE_NBR): The Director of Transportation, County Commissioners, Township Trustees, or Office of Technical Services (OTS) assign transportation route identifications. Each state system route number is unique within Ohio. Local roadways are unique within each county. Route numbers are always five digits and zero-padded. For example, RIMS stores the route number for Interstate 71 as 00071 and the route number for State Route 161 as 00161.
Position 12 Route Suffix Code (ROUTE_SUFFIX_CD): This field has legacy meaning from ODOT’s Local Roadway System Database and is only used on an off-state system route. It is an extension of the Route Number (ROUTE_NBR). It has no specific meaning. Its purpose is to differentiate routes that would otherwise have the same number. This could be a number, letter, or special character—asterisk (*) is the default value and represents no suffix. Examples: - For CR1, positions 7-12 for County Route 1 in Stark County are coded as 00001*
- For CR1A, positions 7-12 for Stark County Route 1A are coded as 00001A
Position 13 Route Extension Code (ROUTE_EXTENSION_CD): Defines a specified characteristic of a state transportation facility. Each character has a specific meaning: Code=Description *=Default (a regular route with no special qualifier)
A Alternate
B Bypass
C Spur or connector
D Directional alternate (1st within a county)
F Directional alternate (2nd within a county)
G Directional alternate (3rd within a county)
I Interchange roadway
J Waiting for final disposition (abandonment or transfer)
K Turnpike
N Northbound
P Proposed (not built) This code is an exception and can be used on an off- state system route to designate a proposed route
S Southbound
T Temporary route
X Express lanes
Position 14 Cardinality Code (CARDINALITY_CD): Roadways in Ohio are usually inventoried in the predominant route direction, from south to north and west to east. On a divided highway, there would be two NLF_IDs, one for each direction of the roadway. Both routes are inventoried with logpoints shown in the cardinal direction (e.g., south to north and west to east.) - The Cardinality Code (CARDINALITY_CD) is C when the route is south to north and west to east.
- The Cardinality Code (CARDINALITY_CD) is N when the route does not follow a cardinal direction.
| |
| 4 | | MUNI_NAME | N/A | Identifies the name of the municipality where the DESTAPE event is located if applicable. | OTS/RIGIS | Identifies the name of the municipality where the DESTAPE event is located if applicable. | RIMS Database, municipal boundary polygon. | Based on the geometry of the road segment or from other source infomration the RIMS user assigns the approrpriate code value. | | N/A | N/A | N/A | Varchar(50) | A complete lsit of these codes is in Appendix C - Municipality and FIPS Codes.
| |
| 4 | | MUNI_FIPS_CD | N/A | The Federal Information Processing System (FIPS) code uniquely identifies which municipality the DESTAPE event is located in, if applicable. | OTS/RIGIS | Identifies the Municipal FIPS code for a roadway segment. | Assigned by the National Institute of Standards and Technology | | The Municipal FIPS is not coded in DESTAPE but is calculated and populated in the ODOT Enterprise Data Warehouse. | N/A | N/A | N/A | Char(5) | A complete list of these codes is in Appendix C - Municipality and FIPS Codes. | |
| 4 | | LONGITUDE_NBR | N/A | Longitude is a geographic coordinate that specifies the east-west position of a point on the surface of the earth. | OTS/RIGIS | identifies the location of a DESTAPE event along the LRS or allows the mapping of a DESTAPE event without an LRS. | | Coded as Decimal Degrees. For example: -83.679376. | | N/A | N/A | N/A | Numeric(9,6) | | |
| 4 | | LATITUDE _NBR | N/A | Latitude is a geographic coordinate that specifies the north-south position of a point on the surface of the Earth. | OTS/RIGIS | Identifies the location of a DESTAPE event along the LRS or allows the mapping of a DESTAPE event without an LRS. | | Coded as decimal degrees. For example, 38.946969. | | N/A | N/A | N/A | Numeric(8,6) | | |
| 4 | | INV_DIRECTION_CD | DIR | The predominant direction of the route.
| OTS/RIGIS | This direction is determined by looking at the overall direction of a route as it
travels through the state. For instance, US33 in Fairfield County goes mostly
southbound but the direction code is east as US33 is eastbound throughout the
state.
| Project plans and imagery.
| Based on the geometry of the route. | Since this is the predominant direction of the route the direction code cannot change. Refer to the Tendency Code (road direction, tendency), for segments that may be different than the predominant direction. | N/A | NA | N/A | Varchar(1) | Code=Description
N =North
S=South
E=East
W=West
| |
| 2, 3, 4 | | DISTRICT_NBR | D_DISTRICT_ID | thie ODOT District in which the section of the route is located. | OTS/RIGIS | Allows user to determine the district to which a segment of roadway belongs. | RIMS user derives from ODOt District Boundary File.
| RIMS user determines district assignment based on segment geometry. | | N/A | (3) Highway District | N/A | Numeric(2,0) | Code=Value 1=District 1 - Lima
2=District 2 - Bowling Green
3=District 3 - Ashland
4=District 4 - Akron
5=District 5 - Jacksontown
6=District 6 - Delaware
7=District 7 - Sidney
8=District 8 - Lebanon
9=District 9 - Chillicothe
10=District 10 - Marietta
11=District 11 - New Philadelphia
12=District 12 - Garfield Heights
| |