data definitions & schemas - tripcheck

70
TripCheck Traveler Information Portal (TTIP) Data Definitions & Schemas

Upload: others

Post on 29-May-2022

8 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Data Definitions & Schemas - TripCheck

TripCheck Traveler Information Portal

(TTIP)

Data Definitions amp Schemas

Data Definitions

TransPort ODOT TTIP i copy 2016 ODOT

Revision History

Date Version Description Author

12142005 10 Initial draft of document DH

1132009 11 Grammar changes and clarification of data types and definitions

JWG

232011 12 Add TTIP Local Entry (TLE) data types SH

6202011 13 Expand ODOT Severity Codes GH

03042015 14 Document maintenance AA

06182015 15 Correct RWISxml schema JB

2102016 16 Update entire document JB

262018 17 Update CRMS definitions CM

4162019 18 Update TLE to new amp improved definition JB

File Name TTIP Data Definitionsdoc

Revision Version 18

Revised Date 4162019 31000 PM

Data Definitions

TransPort ODOT TTIP ii copy 2016 ODOT

Table of Contents

1 INTRODUCTION 1

11 Charter 1 12 System Description 1 13 Intended Audience 1 14 Document Organization 1

2 LOCATION INFORMATION 3

21 LatitudeLongitude data 3 22 Mile point vs mile post 3

3 DATA SOURCES 4

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS 7

41 Schema Table Format 7 42 Closed Circuit TV ndash Inventory - updated July 2015 8 43 Dynamic Message Sign (DMS) 12

431 DMS Inventory - updated July 2015 12 432 DMS Status - updated July 2015 14 433 DMS Inventory ndash Statewide - updated July 2015 16 434 DMS Status - Statewide - updated July 2015 17

44 Event Information 20 441 Events - updated July 2015 20 442 Local Events - updated July 2015 27

45 Incident Information - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

46 Highway Trucking Restrictions - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

47 Parking Lot Information 31 471 Portland Airport Parking Lot ndash updated Jan 2016 31 472 Multnomah Falls Parking Lot - updated Jan 2016 31

48 Traffic Speed Sensor 34 481 Traffic Speed Sensor ndash Inventory - updated Jan 2016 34 482 Traffic Speed Sensor ndash Status - updated Jan 2016 36

49 Road and Weather Information 40 491 Road and Weather Conditions (info gathered manually) - updated July 2015 40 492 Road Weather Info Sys (info gathered via automated weather stations) -

updated June 2015 43 410 Portland State University (PSU) 48

4101 PSU ndash Inventory - updated Jan 2016 48 4102 PSU ndash MFP - updated Jan 2016 49 4103 PSU ndash DACRegion1Ramps - updated Nov 2015 51 4104 PSU ndash DACRegion2Ramps - updated Nov 2015 53

411 Data Acquisition (DAC) 55 4111 DAC ndash Eugene - updated Jan 2016 55 4112 DAC ndash Portland - updated Jan 2016 56

412 Travel Time (TT) 57 4121 TT - DCU Inventory - updated Jan 2016 57 4122 TT - DC Traversals - updated Jan 2016 58 4123 TT - Segment Inventory - updated Jan 2016 59 4124 TT - Segment Calculations - updated Jan 2016 60

413 Classified Length amp Speed (CLS) 61 4131 CLS - Inventory - updated Jan 2016 61

Data Definitions

TransPort ODOT TTIP iii copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016 62 4133 CLS - Length ndash updated Jan 2016 62

APPENDIX 64

A Acronyms 64 B AGENCY NAMING REFERENCES 65 C Message Wrapper Example (using LinkStatus) 65

Data Definitions

TransPort ODOT TTIP Page 1 copy 2016 ODOT

1 INTRODUCTION

11CHARTER

The TripCheck Traveler Information Portal (TTIP) is the result of a joint project sponsored by TransPort a Portland based consortium of regional traffic management agencies and the Oregon Department of Transportation TTIP is part of a larger regional plan to improve Center-to-Center traffic communication and Center-to-Traveler communication

12SYSTEM DESCRIPTION

The TripCheck Traveler Information Portal allows transportation and emergency service agencies to share view access and display multi-modal real-time transportation and incident information This focus on the quick and easy exchange of information is intended to speed emergency response and help operating agencies better understand their system management options It tends to allow for a broad regional view of traffic situations rather than a small centralized view Even smaller agencies can have access to a much broader span of information about traffic events that might affect their local operations

In addition this non-sensitive information is being made available to Information Service Providers (ISPs) who might use innovative broadcast wireless and Internet media to distribute information to the traveling public

Over the past few years a number of standards have been developed for presenting transportation information by several national and international standards bodies There is a significant amount of overlap between the standards so that when combined they provide a homogenous view of various types of traffic management data

This portal is based upon those standards for data access and sharing

13 INTENDED AUDIENCE

There are two groups of TTIP users the first is public agencies involved in transportation and public safety The second is Information Service Providers (ISPs) researchers and others with an interest in dissemination of information to the public

This document is intended for an Agency or an ISP who would like to become a consumer of ATIS information from the TripCheck Traveler Information Portal

Anyone who reads this document should be familiar with basic traffic terms and hardware They should also have a reasonable understanding of XML and the various standard schema definitions

14 DOCUMENT ORGANIZATION

This document consists of four sections and the appendices The first section provides a basic description of the data exchange portal

Section 2 outlines the process for accessing the various types of TTIP data via an http call once you have completed an ISP logon request and received your notification of completion

Section 3 tabulates the contributing agencies and the data they provide Data coming from an agency must conform to the standard format and be content that is acceptable for public release For instance no personal information or things such as fatality information would be provided

Section 4 discusses the different traffic terms equipment and processes which are in place to develop the initial traffic information amp provides a general schema layout for each data type that can be requested For specific information on the different allowable field contents or codes please refer to the appropriate standards from the links provided in Section 2 For the specific TTIP XML document format please download sample XML files and Schemas on the TTIP website for ISPs

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 2: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP i copy 2016 ODOT

Revision History

Date Version Description Author

12142005 10 Initial draft of document DH

1132009 11 Grammar changes and clarification of data types and definitions

JWG

232011 12 Add TTIP Local Entry (TLE) data types SH

6202011 13 Expand ODOT Severity Codes GH

03042015 14 Document maintenance AA

06182015 15 Correct RWISxml schema JB

2102016 16 Update entire document JB

262018 17 Update CRMS definitions CM

4162019 18 Update TLE to new amp improved definition JB

File Name TTIP Data Definitionsdoc

Revision Version 18

Revised Date 4162019 31000 PM

Data Definitions

TransPort ODOT TTIP ii copy 2016 ODOT

Table of Contents

1 INTRODUCTION 1

11 Charter 1 12 System Description 1 13 Intended Audience 1 14 Document Organization 1

2 LOCATION INFORMATION 3

21 LatitudeLongitude data 3 22 Mile point vs mile post 3

3 DATA SOURCES 4

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS 7

41 Schema Table Format 7 42 Closed Circuit TV ndash Inventory - updated July 2015 8 43 Dynamic Message Sign (DMS) 12

431 DMS Inventory - updated July 2015 12 432 DMS Status - updated July 2015 14 433 DMS Inventory ndash Statewide - updated July 2015 16 434 DMS Status - Statewide - updated July 2015 17

44 Event Information 20 441 Events - updated July 2015 20 442 Local Events - updated July 2015 27

45 Incident Information - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

46 Highway Trucking Restrictions - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

47 Parking Lot Information 31 471 Portland Airport Parking Lot ndash updated Jan 2016 31 472 Multnomah Falls Parking Lot - updated Jan 2016 31

48 Traffic Speed Sensor 34 481 Traffic Speed Sensor ndash Inventory - updated Jan 2016 34 482 Traffic Speed Sensor ndash Status - updated Jan 2016 36

49 Road and Weather Information 40 491 Road and Weather Conditions (info gathered manually) - updated July 2015 40 492 Road Weather Info Sys (info gathered via automated weather stations) -

updated June 2015 43 410 Portland State University (PSU) 48

4101 PSU ndash Inventory - updated Jan 2016 48 4102 PSU ndash MFP - updated Jan 2016 49 4103 PSU ndash DACRegion1Ramps - updated Nov 2015 51 4104 PSU ndash DACRegion2Ramps - updated Nov 2015 53

411 Data Acquisition (DAC) 55 4111 DAC ndash Eugene - updated Jan 2016 55 4112 DAC ndash Portland - updated Jan 2016 56

412 Travel Time (TT) 57 4121 TT - DCU Inventory - updated Jan 2016 57 4122 TT - DC Traversals - updated Jan 2016 58 4123 TT - Segment Inventory - updated Jan 2016 59 4124 TT - Segment Calculations - updated Jan 2016 60

413 Classified Length amp Speed (CLS) 61 4131 CLS - Inventory - updated Jan 2016 61

Data Definitions

TransPort ODOT TTIP iii copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016 62 4133 CLS - Length ndash updated Jan 2016 62

APPENDIX 64

A Acronyms 64 B AGENCY NAMING REFERENCES 65 C Message Wrapper Example (using LinkStatus) 65

Data Definitions

TransPort ODOT TTIP Page 1 copy 2016 ODOT

1 INTRODUCTION

11CHARTER

The TripCheck Traveler Information Portal (TTIP) is the result of a joint project sponsored by TransPort a Portland based consortium of regional traffic management agencies and the Oregon Department of Transportation TTIP is part of a larger regional plan to improve Center-to-Center traffic communication and Center-to-Traveler communication

12SYSTEM DESCRIPTION

The TripCheck Traveler Information Portal allows transportation and emergency service agencies to share view access and display multi-modal real-time transportation and incident information This focus on the quick and easy exchange of information is intended to speed emergency response and help operating agencies better understand their system management options It tends to allow for a broad regional view of traffic situations rather than a small centralized view Even smaller agencies can have access to a much broader span of information about traffic events that might affect their local operations

In addition this non-sensitive information is being made available to Information Service Providers (ISPs) who might use innovative broadcast wireless and Internet media to distribute information to the traveling public

Over the past few years a number of standards have been developed for presenting transportation information by several national and international standards bodies There is a significant amount of overlap between the standards so that when combined they provide a homogenous view of various types of traffic management data

This portal is based upon those standards for data access and sharing

13 INTENDED AUDIENCE

There are two groups of TTIP users the first is public agencies involved in transportation and public safety The second is Information Service Providers (ISPs) researchers and others with an interest in dissemination of information to the public

This document is intended for an Agency or an ISP who would like to become a consumer of ATIS information from the TripCheck Traveler Information Portal

Anyone who reads this document should be familiar with basic traffic terms and hardware They should also have a reasonable understanding of XML and the various standard schema definitions

14 DOCUMENT ORGANIZATION

This document consists of four sections and the appendices The first section provides a basic description of the data exchange portal

Section 2 outlines the process for accessing the various types of TTIP data via an http call once you have completed an ISP logon request and received your notification of completion

Section 3 tabulates the contributing agencies and the data they provide Data coming from an agency must conform to the standard format and be content that is acceptable for public release For instance no personal information or things such as fatality information would be provided

Section 4 discusses the different traffic terms equipment and processes which are in place to develop the initial traffic information amp provides a general schema layout for each data type that can be requested For specific information on the different allowable field contents or codes please refer to the appropriate standards from the links provided in Section 2 For the specific TTIP XML document format please download sample XML files and Schemas on the TTIP website for ISPs

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 3: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP ii copy 2016 ODOT

Table of Contents

1 INTRODUCTION 1

11 Charter 1 12 System Description 1 13 Intended Audience 1 14 Document Organization 1

2 LOCATION INFORMATION 3

21 LatitudeLongitude data 3 22 Mile point vs mile post 3

3 DATA SOURCES 4

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS 7

41 Schema Table Format 7 42 Closed Circuit TV ndash Inventory - updated July 2015 8 43 Dynamic Message Sign (DMS) 12

431 DMS Inventory - updated July 2015 12 432 DMS Status - updated July 2015 14 433 DMS Inventory ndash Statewide - updated July 2015 16 434 DMS Status - Statewide - updated July 2015 17

44 Event Information 20 441 Events - updated July 2015 20 442 Local Events - updated July 2015 27

45 Incident Information - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

46 Highway Trucking Restrictions - NOTE The file containing this data Incdxml is described in the lsquoeventsrsquo section (section 441) 30

47 Parking Lot Information 31 471 Portland Airport Parking Lot ndash updated Jan 2016 31 472 Multnomah Falls Parking Lot - updated Jan 2016 31

48 Traffic Speed Sensor 34 481 Traffic Speed Sensor ndash Inventory - updated Jan 2016 34 482 Traffic Speed Sensor ndash Status - updated Jan 2016 36

49 Road and Weather Information 40 491 Road and Weather Conditions (info gathered manually) - updated July 2015 40 492 Road Weather Info Sys (info gathered via automated weather stations) -

updated June 2015 43 410 Portland State University (PSU) 48

4101 PSU ndash Inventory - updated Jan 2016 48 4102 PSU ndash MFP - updated Jan 2016 49 4103 PSU ndash DACRegion1Ramps - updated Nov 2015 51 4104 PSU ndash DACRegion2Ramps - updated Nov 2015 53

411 Data Acquisition (DAC) 55 4111 DAC ndash Eugene - updated Jan 2016 55 4112 DAC ndash Portland - updated Jan 2016 56

412 Travel Time (TT) 57 4121 TT - DCU Inventory - updated Jan 2016 57 4122 TT - DC Traversals - updated Jan 2016 58 4123 TT - Segment Inventory - updated Jan 2016 59 4124 TT - Segment Calculations - updated Jan 2016 60

413 Classified Length amp Speed (CLS) 61 4131 CLS - Inventory - updated Jan 2016 61

Data Definitions

TransPort ODOT TTIP iii copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016 62 4133 CLS - Length ndash updated Jan 2016 62

APPENDIX 64

A Acronyms 64 B AGENCY NAMING REFERENCES 65 C Message Wrapper Example (using LinkStatus) 65

Data Definitions

TransPort ODOT TTIP Page 1 copy 2016 ODOT

1 INTRODUCTION

11CHARTER

The TripCheck Traveler Information Portal (TTIP) is the result of a joint project sponsored by TransPort a Portland based consortium of regional traffic management agencies and the Oregon Department of Transportation TTIP is part of a larger regional plan to improve Center-to-Center traffic communication and Center-to-Traveler communication

12SYSTEM DESCRIPTION

The TripCheck Traveler Information Portal allows transportation and emergency service agencies to share view access and display multi-modal real-time transportation and incident information This focus on the quick and easy exchange of information is intended to speed emergency response and help operating agencies better understand their system management options It tends to allow for a broad regional view of traffic situations rather than a small centralized view Even smaller agencies can have access to a much broader span of information about traffic events that might affect their local operations

In addition this non-sensitive information is being made available to Information Service Providers (ISPs) who might use innovative broadcast wireless and Internet media to distribute information to the traveling public

Over the past few years a number of standards have been developed for presenting transportation information by several national and international standards bodies There is a significant amount of overlap between the standards so that when combined they provide a homogenous view of various types of traffic management data

This portal is based upon those standards for data access and sharing

13 INTENDED AUDIENCE

There are two groups of TTIP users the first is public agencies involved in transportation and public safety The second is Information Service Providers (ISPs) researchers and others with an interest in dissemination of information to the public

This document is intended for an Agency or an ISP who would like to become a consumer of ATIS information from the TripCheck Traveler Information Portal

Anyone who reads this document should be familiar with basic traffic terms and hardware They should also have a reasonable understanding of XML and the various standard schema definitions

14 DOCUMENT ORGANIZATION

This document consists of four sections and the appendices The first section provides a basic description of the data exchange portal

Section 2 outlines the process for accessing the various types of TTIP data via an http call once you have completed an ISP logon request and received your notification of completion

Section 3 tabulates the contributing agencies and the data they provide Data coming from an agency must conform to the standard format and be content that is acceptable for public release For instance no personal information or things such as fatality information would be provided

Section 4 discusses the different traffic terms equipment and processes which are in place to develop the initial traffic information amp provides a general schema layout for each data type that can be requested For specific information on the different allowable field contents or codes please refer to the appropriate standards from the links provided in Section 2 For the specific TTIP XML document format please download sample XML files and Schemas on the TTIP website for ISPs

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 4: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP iii copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016 62 4133 CLS - Length ndash updated Jan 2016 62

APPENDIX 64

A Acronyms 64 B AGENCY NAMING REFERENCES 65 C Message Wrapper Example (using LinkStatus) 65

Data Definitions

TransPort ODOT TTIP Page 1 copy 2016 ODOT

1 INTRODUCTION

11CHARTER

The TripCheck Traveler Information Portal (TTIP) is the result of a joint project sponsored by TransPort a Portland based consortium of regional traffic management agencies and the Oregon Department of Transportation TTIP is part of a larger regional plan to improve Center-to-Center traffic communication and Center-to-Traveler communication

12SYSTEM DESCRIPTION

The TripCheck Traveler Information Portal allows transportation and emergency service agencies to share view access and display multi-modal real-time transportation and incident information This focus on the quick and easy exchange of information is intended to speed emergency response and help operating agencies better understand their system management options It tends to allow for a broad regional view of traffic situations rather than a small centralized view Even smaller agencies can have access to a much broader span of information about traffic events that might affect their local operations

In addition this non-sensitive information is being made available to Information Service Providers (ISPs) who might use innovative broadcast wireless and Internet media to distribute information to the traveling public

Over the past few years a number of standards have been developed for presenting transportation information by several national and international standards bodies There is a significant amount of overlap between the standards so that when combined they provide a homogenous view of various types of traffic management data

This portal is based upon those standards for data access and sharing

13 INTENDED AUDIENCE

There are two groups of TTIP users the first is public agencies involved in transportation and public safety The second is Information Service Providers (ISPs) researchers and others with an interest in dissemination of information to the public

This document is intended for an Agency or an ISP who would like to become a consumer of ATIS information from the TripCheck Traveler Information Portal

Anyone who reads this document should be familiar with basic traffic terms and hardware They should also have a reasonable understanding of XML and the various standard schema definitions

14 DOCUMENT ORGANIZATION

This document consists of four sections and the appendices The first section provides a basic description of the data exchange portal

Section 2 outlines the process for accessing the various types of TTIP data via an http call once you have completed an ISP logon request and received your notification of completion

Section 3 tabulates the contributing agencies and the data they provide Data coming from an agency must conform to the standard format and be content that is acceptable for public release For instance no personal information or things such as fatality information would be provided

Section 4 discusses the different traffic terms equipment and processes which are in place to develop the initial traffic information amp provides a general schema layout for each data type that can be requested For specific information on the different allowable field contents or codes please refer to the appropriate standards from the links provided in Section 2 For the specific TTIP XML document format please download sample XML files and Schemas on the TTIP website for ISPs

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 5: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP Page 1 copy 2016 ODOT

1 INTRODUCTION

11CHARTER

The TripCheck Traveler Information Portal (TTIP) is the result of a joint project sponsored by TransPort a Portland based consortium of regional traffic management agencies and the Oregon Department of Transportation TTIP is part of a larger regional plan to improve Center-to-Center traffic communication and Center-to-Traveler communication

12SYSTEM DESCRIPTION

The TripCheck Traveler Information Portal allows transportation and emergency service agencies to share view access and display multi-modal real-time transportation and incident information This focus on the quick and easy exchange of information is intended to speed emergency response and help operating agencies better understand their system management options It tends to allow for a broad regional view of traffic situations rather than a small centralized view Even smaller agencies can have access to a much broader span of information about traffic events that might affect their local operations

In addition this non-sensitive information is being made available to Information Service Providers (ISPs) who might use innovative broadcast wireless and Internet media to distribute information to the traveling public

Over the past few years a number of standards have been developed for presenting transportation information by several national and international standards bodies There is a significant amount of overlap between the standards so that when combined they provide a homogenous view of various types of traffic management data

This portal is based upon those standards for data access and sharing

13 INTENDED AUDIENCE

There are two groups of TTIP users the first is public agencies involved in transportation and public safety The second is Information Service Providers (ISPs) researchers and others with an interest in dissemination of information to the public

This document is intended for an Agency or an ISP who would like to become a consumer of ATIS information from the TripCheck Traveler Information Portal

Anyone who reads this document should be familiar with basic traffic terms and hardware They should also have a reasonable understanding of XML and the various standard schema definitions

14 DOCUMENT ORGANIZATION

This document consists of four sections and the appendices The first section provides a basic description of the data exchange portal

Section 2 outlines the process for accessing the various types of TTIP data via an http call once you have completed an ISP logon request and received your notification of completion

Section 3 tabulates the contributing agencies and the data they provide Data coming from an agency must conform to the standard format and be content that is acceptable for public release For instance no personal information or things such as fatality information would be provided

Section 4 discusses the different traffic terms equipment and processes which are in place to develop the initial traffic information amp provides a general schema layout for each data type that can be requested For specific information on the different allowable field contents or codes please refer to the appropriate standards from the links provided in Section 2 For the specific TTIP XML document format please download sample XML files and Schemas on the TTIP website for ISPs

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 6: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP Page 2 copy 2016 ODOT

Appendix A contains supplemental information about acronyms contained in this document Appendix B exhibits specific codes used in Agency name and IDfields in the various record types Appendix C exhibits a sample reply wrapper for requested data

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 7: Data Definitions & Schemas - TripCheck

Data Definitions

TransPort ODOT TTIP Page 3 copy 2016 ODOT

2 LOCATION INFORMATION

21 LATITUDELONGITUDE DATA

Some information is classified as Point and some as Segment Point data has a single latlong pair and Segment data has a beginning and ending latitudelongitude pair Remember that roadways are not always straight lines and the segment pairs only define a beginning and ending point not the shape or path of the roadway between This is especially true for long segments so attempting to interpolate a midpoint on the segment may be impossible or at least highly inaccurate

22 MILE POINT VS MILE POST

There is a small distinction to be made between these two Data is reported in an MP field but the content is more determined by the context than the description Generally most traffic devices signs etc that are designed and installed are defined to the hundredth even the thousandth of a mile while mileposts are set at the time a highway is constructed When a turn is shortened or lengthened the mileposts within the curve may be reset but the highway mileage is said to be the same and is never changed

An engineer or construction supervisor will specify a mile point for an event or beginning and end of an event area such as road construction

The casual observer calling into 911 or a police officer who reports his location at an accident scene usually gives Incident milepost While the difference may not be significant in the context of the big picture it is good to keep this in mind when trying to zoom in on a specific location

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 8: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 4 copy 2016 ODOT

3 DATA SOURCES

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT

CRMS (read

from system

memory)

TmddLinkInventory

TmddLinkStatus

Vehicle Detection

Station (VDS)

Inventory 24

hour

Status 2

minute

Vehicle Detection Station (VDS) data may

have multiple loops TTIP only provides the

mainline loop information

ODOT

WSDOT

ODOT

NUCLEUS

TmddDMSInventory

TmddDMSStatus

TmddDMSInventory-

SW

TmddDMSStatus-SW

Dynamic

Message Sign

(DMS)

Inventory 24

hour

Status 2

minute

ODOT SCAN AtisWeatherInformati

on(rwis)

Road Weather

Information

System

(Automatic

collection of

data)

15 minute

The ODOT Remote Weather Information

System (RWIS) provides automated weather

collection from a number of fixed locations

within the state of Oregon Not all defined

information is available from every station

ODOT HTCIS AtisWeatherInformati

on(rw)

Road Weather

(Manual

collection of

data)

15 minute

Road Weather (RW) ndash During winter months

ODOT maintenance crews provide daily

RoadWeather reports for our mandatory road

reporting stations Mandatory road reporting

stations are pre-defined road segments that

experience frequent winter weather impacts

Crews provide reports five times per day and

at other times when conditions change

significantly The daily reporting times are

approximately 400 AM 700 AM 1000 AM

330 PM and 830 PM Actual reporting times

can vary depending on crew availability and

the locations they are working

ODOT HTCIS AtisEventInformation

Event (planned

closures

construction)

2 minute

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 9: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 5 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT HTCIS AtisIncidentInformatio

n Incident 2 minute

ODOT TLE TLE (TripCheck Local

Entry) Local Events 2 minute

TripCheck Local Events

ODOT

HTCIS

(Highway

Travel

conditions

information

system)

AtisIncidentInformatio

n

Highway

Trucking

restrictions

2 minute

ODOT HCSS TmddcCTVInventory Cameras Inventory 24

hour

The CCTV Inventory data provides the URL of

the current snapshot Some images carry

overlayed weather information

ODOT CRMS

TmddpsuInventory

TmddDACEugene

Tmdd DACPortland

Tmdd

DACRegion1Ramps

Tmdd

DACRegion2Ramps

Traffic Speed

Sensor

Inventory 24

hour

Status 2

minute

DAC (Data Acquisition Components) collecting VOS

(Volume occupancy and speed) detector

data

ODOT HMFP Mfparking

PSUMFP

Parking lot

informationStat

us Plus All data

related to

parking lot

Inventory 24

hour

Status 2

minute

ODOT Travel Time

TravelTime

TTDcuInventory

TTDcuTraversals

TTSegInventory

TTSegmentCalcs

Segment

BlueTooth and

routes

information

Inventory 24

hour

Status 2

minute

PSU and WSDOT are the primary receiver of

data

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 10: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 6 copy 2016 ODOT

Provider Source Database

Basis Schema Data Content Update Frequency

Additional information

ODOT CLS CLSinventory

CLSlengthbindata

CLSspeedbindata

Inventory 24

hour

Status 10

minute

Length amp Speed data

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 11: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 7 copy 2016 ODOT

4 TRAVELER INFORMATION DATA DEFINITIONS AND SCHEMAS

Each type of Traveler Information data is available as a separate XML document Once a consumer is signed up to pull data from the portal any desired feed is accessible The following sections outline the different data types available on the portal

41 SCHEMA TABLE FORMAT

The following table defines the standards based schemas which contain the traveler information the format and the logic behind the individual data fields

Data Field Description Data Type Data Unit Null Value

Blank

The field name from the schema Business (Traffic Center) definition for the field String Integer

Decimal

DateTime Txt

Num Fixed

Float etc

KmHr

Celsius

Inch foot

1˚Cels etc

Most fields

are Metric

empty

-1

1011

None

any

value

that

signifie

s an

error

conditi

on etc

Can data

element

be blank

YN

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 12: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 8 copy 2016 ODOT

42 CLOSED CIRCUIT TV ndash INVENTORY - UPDATED JULY 2015

(Corresponding xml file cctvInventoryxml)

Closed Circuit Television or CCTV can be provided in a number of formats but generally they fall into one of two categories still or motion Motion video is often referred to as streaming There are a number of technologies that will provide this format Streaming video does require a significant amount of bandwidth and server resources so is not provided here at this time There are also a number of formats available to provide still images that are updated on some regular frequency

Currently TTIP provides an inventory of all available cameras along with an Internet URL that can be used to access the specific still camera image This inventory is updated every 24 hours even though the source database may only be modified infrequently The images are updated on the source server about once every 2-20 minutes depending on the specific camera 5 minutes is the average update interval

These images are preprocessed and include the required ODOT accreditation along with local weather information if available from an automated weather station in the vicinity Often these two devices will be at the same roadside facility Some cameras are fixed and some may be movable and zoom-able by the local traffic agency A latitudelongitude pair is provided but may not be the exact location

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Close Caption TV - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the

request for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 13: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 9 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 14: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 10 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags are

repeated for each of the

multiple camera images

included in the file

ltcCTVInventorygt

ltorganization-informationgt

ltorganization-idgt

ltorganization-idgt

ltorganization-namegt

ltorganization-namegt

ltorganization-informationgt

ltdevice-idgtltdevice-idgt

ltdevice-namegt

ltdevice-namegt

ltlocationgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltlocationgt

ltcctv-imagegtltcctv-imagegt

ltcctv-urlgtltcctv-urlgt

ltcctv-othergt ltcctv-othergt

ltnode-idgtltnode-idgt

ltroute-designator gt

ltlast-update-timegt

ltdategt ltdategt

lttimegt lttimegt

ltlast-update-timegt

ltcCTVInventorygt

organization id

organization id Example 1002

Organization name

Organization name Example ODOT

Device id Example 277

Device name

Example AstoriaUS101MeglerBrNB

Geolocation Point (in micro degrees)

Latitude Example 44075040

Longitude Example -122117431

CCTV Image type EX jpeg

CCTV image URL Example

httpwwwTripCheckcomroadcams

camsAstoriaUS101MeglerBrNB_pid392

jpg

text description of the camera location

Example US101 at Astoria - ODOT District

Office

Node id Example 009

Start amp end XML tag

DateTime image was last updated

Example date 20110123

Example time 123456

End XML tag

End XML tag

Integer

String

Integer

String

Decimal 6

decimal places

Decimal 6

decimal places

Text

Text

String

Numeric

NA

DateTime

ltyyyymmddgt

lthhmmssgt

NA

NA

N

N

N

N

N

N

N

N

N

N

Y

N

N

N

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 15: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 11 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 16: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 12 copy 2016 ODOT

43 DYNAMIC MESSAGE SIGN (DMS)

431 DMS Inventory - updated July 2015

(Corresponding xml file dmsInventoryxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Inventory file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request

for this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 17: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 13 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

N N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 18: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 14 copy 2016 ODOT

432 DMS Status - updated July 2015

(Corresponding xml file dmsStatusxml)

A Dynamic Message Sign (DMS) is a roadside sign that comes in a variety of sizes and shapes and may even be portable Most provide a number of lines and varying widths However the DMS information provided here is restricted to fixed signs with known latlong positions They have three lines per message and are restricted to two messages which alternate Motorists are generally unable to read anything more than this with normal traffic flow

TTIP provides an inventory of active signs every 24 hours Each sign has a unique ID Every 2 minutes a status message is produced which contains the message ID current sign status and contents of the message fields

The DMS Status file only provides signs located in the Portland Metro area and also includes signs located in Vancouver Washington Contains the active message being displayed on a specific sign

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from the Current DateTime

Example 2138034503

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data Example 2138034503

Integer N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

DateTime

ltyyyymmd

dgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 19: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 15 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmd

dgt

lthhmmssgt

N

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1 gt

ltphase1Line2 gt

ltphase1Line3 gt

ltphase2Line1 gt

ltphase2Line2 gt

ltphase2Line3 gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example TEST

Current status of the device In service unavailable

etc Example in service

Message 1 line 1 Empty field

Message 1 line 2 Empty field

Message 1 line 3 Empty field

Message 2 line 1 Empty field

Message 2 line 2 Empty field

Message 2 line 3 Empty field

Numeric

Text

Text

Text

Text

Text

Text

Text

Text

N

N

N

Y

Y

Y

Y

Y

Y

NA

NA

NA

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 20: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 16 copy 2016 ODOT

433 DMS Inventory ndash Statewide - updated July 2015

(Corresponding xml file dmsInventory-SWxml)

This XML file contains a list of signs located throughout the State of Oregon It does not include signs located in other states

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

DMS (Statewide) - Inventory

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 21: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 17 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListInventorygt

ltdmsInventorygt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltpointLocationgt

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegt

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltdmsInventorygt

Id Unique id for dms device Example 1

Issuing Agency Example ODT3

Location Name Example VMS I-5 NB at Wilsonville

C201A17

Geolocation (in micro degrees)

Latitude Example 44075040

Longitude Example -122751220

Numeric

Text

Numeric 6

decimal place

Numeric 6

decimal place

N

ltdmsListInventorygt

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

434 DMS Status - Statewide - updated July 2015

(Corresponding xml file dmsStatus-SWxml)

This XML file contains the message being displayed on signs located throughout the State of Oregon at the given time

Data Field Description Data Type Data Unit Null Example

Blank

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 22: Data Definitions & Schemas - TripCheck

Data Definitions

ODOT TTIP Page 18 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Dynamic Message Sign (Statewide) - Status

XML Begin Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

String

String

N

N

N

N

ltmessageIDgt

ltmessageIDgt

Hash generated from theCurrentDateTime

Example 2138034503

Integer Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that containes the request for

this data

Example 2138034503

Integer Ex

4294967295

N

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

ltlocalResponseGroupgt

The time the inventory was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 19 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

Note the following tags

are repeated for each of

the multiple DMS devices

included in the file

ltdmsListDeviceStatusgt

ltdmsDeviceStatusgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

ltdms-device-statusgt

ltdms-device-statusgt

ltdmsCurrentMessagegt

ltphase1Line1gt

ltphase1Line1gt

ltphase1Line2gt

ltphase1Line2gt

ltphase1Line3gt

ltphase1Line3gt

ltphase2Line1gt

ltphase2Line1gt

ltphase2Line2gt

ltphase2Line2gt

ltphase2Line3gt

ltphase2Line3gt

ltdmsCurrentMessagegt

ltdmsDeviceStatusgt

ltdmsListDeviceStatusgt

Id Unique id for dms device Example 1

Issuing Agency

Example ODOT

Device Status

Example in service

Current Message

Example TRAVEL TIME TO

Example OR217 10MIN

Example 99E VIA I205 16MIN

Numeric

Text

Text

N N N

ltlocalResponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

File end XML tags NA

Data Definitions

ODOT TTIP Page 20 copy 2016 ODOT

44 EVENT INFORMATION

441 Events - updated July 2015

(Corresponding xml file Incdxml)

Link Events are defined as planned ODOT activities along a roadway often the events represent construction projects An event may be posted just minutes before it happens or perhaps days or weeks before it is scheduled to begin An event usually has a defined end date

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Information Response XML Tag NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

Agency Identifier

Example usordot

Agency unique name

Example ODOT

Text see

Agency table

na N

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime Integer - Ex

4294967295

N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data

Integer ndash Ex

4294967295

N

lttimeStampgt

ltdategtltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Reply Time stamp ndash date and time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

ltresponseGroupgt

The time the data was retrieved

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 21 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseGroupgt

lteventsgt

lteventgt

ltheadgt

ltidgtltidgt

Business system generated number

Example 160495

integer NY

ltupdateTimegt

ltdategt ltdategt

lttimegt lttimegt

ltupdateTimegt

ltheadgt

Date the information was last manually updated

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

State highway name

locationName Example TUALITAN VALLEY

Text N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

Route

LinkName ExampleORE8

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

Internal (state) highway number

Example idAlpha 29

Integer N

ltoffset1gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset1gt

Event Starting Milepoint

miDec Example 1128

Marker example ORE8 Hillsboro

Numeric Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltmarkergtltmarkergt

ltoffset2gt

Event Ending Milepoint

miDec Example 1466

Marker example ORE8 Cornelius

Numeric Miles N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferenceLinkgt

North south east west Text N

Data Definitions

ODOT TTIP Page 22 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltstartPointgt

Geolocation Link start (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltdisplayPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltdisplayPointgt

Geolocation Link display (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltendPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltendPointgt

Geolocation Link end (in micro degrees)

Latitude Example 45506750

Longitude Example -122961090

Numeric 6

decimal place

N

ltPointGeometrygt

ltPointGeometrygt

ltlineGeometry gt

PointGeometry Example

POINT (-136879659262 57016548421)

Numeric 6

decimal place

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

N

lttypeEventgt

ltroadworkgtltroadworkgt

lttypeEventgt

TypeKind of Event

Roadwork Example road construction

Text N

ltseveritygtltseveritygt None minor major etc Text N

ltdescriptiongt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltdescriptiongt

ShortHeadline description of event Text Y

ltadvicegt

lttextgt

lttextgt

hellip

lttextgt

lttextgt

ltadvicegt

More extensive event information Text Y

Data Definitions

ODOT TTIP Page 23 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltaffectedLanes gt

empty field Text Y

ltstartTimegt

ltdategt ltdategt

lttimegt lttimegt

ltstartTimegt

Expected start time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltclearTimegt

ltdategt ltdategt

lttimegt lttimegt

ltclearTimegt

Expected end time

Example date 20110123

Example time 123456

ltyyyymmddgt

lthhmmssgt

Y

ltschedule gt

lttailgt

XML tags NA

Y

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category codes

Tag odotCategoryID

Value Examples (see description of ID values below)

A

C

CH

CV

H

I

M

T

W

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Event Category code descriptions

Tag odotCategoryDescript

Value Examples (description of codersquos above)

CrashHazard

Construction Work

Cancelled Herbicide Application

Commercial Vehicle Information

Herbicide Application

Information

Maintenance Work

Traffic Congestion

Weather Impact

Text N

Data Definitions

ODOT TTIP Page 24 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggtlttaggt

ltValuegtltValuegt

ltentrygt

Off Highway codes

Tag Example odotOffHwyCD

Value Examples (see description of CD values below)

FR

OF

OR

RA

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Off Highway code descriptions

Tag odotOffHwyDescript

Value Examples (description of CDrsquos above)

Frontage Road

Off Ramp

On Ramp

Rest Area

None

Text N

ltentrygt

lttaggt lttaggt

ltValuegt ltValuegt

ltentrygt

Severity codes

Tag odotSeverityID

Value Examples (see description of ID values below)

0

1

2

3

4

5

6

7

8

Numeric N

Data Definitions

ODOT TTIP Page 25 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Severity code descriptions

Tag odotSeverityDescript

Value Examples (description of IDrsquos above)

Informational only

Estimated delay lt 20 minutes

Estimated delay of 20 minutes - 2 hours

Estimated delay of 2 hours or greater

Closure

Seasonal Closure

Unconfirmed

No to Minimum Delay

Closure with Detour

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Direction of travel NS = north to south

Tag Highwaydirection

Value Examples

NS

SN

WE

EW

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Initials of data entry person

Tag recorderinitials

Value Example VR

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency name

Tag Publicontact

Value Example Central TOC

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

Responsible agency phone number

Tag Publicontactphone

Value Example (503) 731-8247

Text N

ltentrygt

lttaggt lttaggt

ltValuegtltValuegt

ltentrygt

URL for additional information

Tag Infourl

Value Example wwwtvhwypavingorg

Text None Y

Data Definitions

ODOT TTIP Page 26 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttailgt

lteventgt

lteventgt

hellip

lteventgt

ltlinkgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 27 copy 2016 ODOT

442 Local Events - updated July 2015

(Corresponding xml file incd-tlexml)

Local events are defined as activities on local roadways reported by local jurisdictions (cities or counties) These events can be planned such as construction or reports of crashes (unplanned incidents) or weather events

Output field Description Type UnitStandard

Error MO

IncidentTLE The information content describing an entry from the TLE website

Data frame M

Organization-Information

The information content describing an organization information for a single organization

Data frame 33163 - TMDD

M

Organization-Id Identifier organization-resource-identifier (IA5String(SIZE(132)))

34168 - TMDD

-1 M

Organization-Name Name organization-resource-name(IA5String(SIZE(1128)))

34169 - TMDD

blank O

Last-Update-Time Date of last update DateTime ISO 8601 blank O

Incidents Data Frame

Incident Data Frame

Id incident identifier organization-resource-identifier (IA5String(SIZE(132)))

-1 M

LocationDesription locationDesription (IA5String (SIZE(11024)))

-1 M

Data Definitions

ODOT TTIP Page 28 copy 2016 ODOT

Type TypeId

1 (Hazard)

2 (Construction

3 (Information)

4 (WeatherHazard)

5 (Detour)

6 (Vehicle Restriction)

7 (Crash)

(IA5String(SIZE(150)))

-1 M

Impact Specifies the level of importance of the incident TLE event impactName

impactId

1 = None

2 = Low

3 = Moderate

4 = High

5 = Closed

(IA5String(SIZE(140)))

-1 M

HeadLine TLE headline (IA5String( SIZE(1256)))

Comments Incident comments (IA5String( SIZE(11024)))

blank O

CreateTime Time the TLE incident was created ISO 8601 -1 M

EventStart Time the incident started ISO 8601 -1 M

EventEnd Time the incident ended ISO 8601 blank O

startLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

Data Definitions

ODOT TTIP Page 29 copy 2016 ODOT

endLat The geographic latitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLatitudelcnt (INTEGER

(-900000000 900000001))

tenth of a micro degree SAE J2266

-1 M

startLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

endLong The geographic longitude of a node expressed in integer microdegrees with reference to the horizontal datum specified by horizontalDatum

GlobalLogitudelcnt (INTEGER (-1800000000 1800000001))

tenth of a micro degree SAE J2266

-1 M

geometryWkt Markup language for representing vector geometry objects on a map

OpenGISreg Simple Features Access (SFA) also called ISO 19125

-1 M

SourceAgency Identifies the organization from which the information was sourced

The reference name must be a maximum of either 10 capital letters or 12 lowercase letters

gt= 1 char

-1 M

ContactEmail TLE contact email (IA5String( SIZE(1256)))

-1 M

ContactName TLE contact name (IA5String( SIZE(1100)))

-1 M

ContactOrganization TLE contact organization (IA5String( SIZE(1100)))

-1 M

ContactPhone TLE contact phone (IA5String( SIZE(116)))

-1 M

Data Definitions

ODOT TTIP Page 30 copy 2016 ODOT

Direction Transform(IsBirectional)=BOTH_DIRECTIONS ONE_DIRECTION

(IA5String(SIZE(120)))

-1 M

updateTime Date of last update to the TLE incident ISO 8601 blank O

45 INCIDENT INFORMATION - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE lsquoEVENTSrsquo SECTION

(SECTION 441)

(Corresponding xml file Incdxml)

Incidents are defined as unplanned ODOT activities along a roadway An example is a vehicle accident that has closed on or more lanes Usually the Incident is reported after it happens Throughout the Incident the incident end time will be updated as estimates become available

46 HIGHWAY TRUCKING RESTRICTIONS - NOTE THE FILE CONTAINING THIS DATA INCDXML IS DESCRIBED IN THE

lsquoEVENTSrsquo SECTION (SECTION 441)

(Corresponding xml file Incdxml)

Trucking Restrictions describe highway conditions that may impact the travel route for commercial trucks Restrictions are typically related to the trucking vehiclersquos weight and dimensions (length height width) An example of the limitation could be applicable to trucks in situations for temporary bridge building where weightheightwidth restrictions may apply

Data Definitions

ODOT TTIP Page 31 copy 2016 ODOT

47 PARKING LOT INFORMATION

471 Portland Airport Parking Lot ndash updated Jan 2016

(Corresponding xml file PDXparkingxml)

Note Portland Airport parking lot information has been removed from TTIP We intend to include this data again once the Portland Airport parking system is back online

In the past traveling via plane usually meant showing up at airport parking and driving up and down long lanes of parked cars looking for that elusive parking slot Many parking structures had multiple floors with no indication whether it was full or not Today many parking structures have become automated with vehicle sensors so that individual stalls may be sensed and counted Eventually these will contain flashing lights to notify a traveler of availability even at a distance Now with this new technology it is possible to go onto the Internet and access parking garage statistics for a given airport so you will know which garage to go to and your chances of finding an available slot The data often includes the number of total slots per garage number available and a percentage of full

472 Multnomah Falls Parking Lot - updated Jan 2016

(Corresponding xml file Mfparkingxml)

Multnomah Falls Parking was added to the portal in 2014

Multnomah Falls parking lot is an ODOT property located near Multnomah Falls The falls have an easy driving access from Portland OR on I-84 The parking lot is situated at a five minutesrsquo walk off of I-84 Because of the easy access and the prime location the parking lot has a potential to fill up quickly resulting in delays and accidents on I-84 The XML file provides both a numerical percentage full and a descriptive percentage full value

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Information Response Multnomah Falls Parking XML Tag

Data Definitions

ODOT TTIP Page 32 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltagencyNamegt

ltperson gt

ltsendergt

ltmessageIDgt

ltmessageIDgt

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

Start amp End XML Tag

A hash generated from the CurrentDateTime

Message ID Ex 4294967295

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

Text

Integer

DateTime

ltyyyymmddgt

lthhmmssgt

na Y

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

The time the data was retrieved

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

ltparkingLotsgt

ltparkingLotgt

ltheadgt

ltidgtltidgt

Business system generated number

- ID Example 781503

integer Y

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

ltheadgt

Reply Time stamp ndash date and time

- Date Example 20160115

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

Y

Data Definitions

ODOT TTIP Page 33 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlocationgt

ltlocationNamegt

ltlocationNamegt

ltlatitudegt

ltlatitudegt

ltlongitudegt

ltlongitudegt

ltlocationgt

location Name Ex Multnomah Falls Parking

Geolocation Point (in micro degrees) Latitude Example 44075040

Longitude Example -122751220

Text

Decimal 6

decimal place

Decimal 6

decimal place

Y

N

N

ltpercentFullgt

ltpercentFullgt

PercentFull

Example 15

Integer N

ltpercentFullMessagegt

ltpercentFullMessagegt

PercentFullMessage

Example Parking lot 15 full

Text N

ltparkingLotgt

ltparkingLotsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA N

Data Definitions

ODOT TTIP Page 34 copy 2016 ODOT

48 TRAFFIC SPEED SENSOR

481 Traffic Speed Sensor ndash Inventory - updated Jan 2016

(Corresponding xml file linkInventoryxml)

A traffic Link is defined as a segment of roadway bounded by a beginning and ending point It is permissible to define a single point link where that point defines something such as a bridge overpass or traffic sensor

A link point will usually only contain a single latlong pair or a single location identifier or name

A Link may be further defined by anything that happens on or near that segment of road Within the end points a number of things can be specified that define the roadway itself restrictions to travel on the roadway existing events and incidents and even weather

Standard codes and phrases are used to ensure consistency from one system to the next Links may also be defined such that they overlap other segments or are a subset of another link

The end points may be defined in a number of ways including latlong pairs cross streets mileposts and even on and off ramps Often some or all of these are included to provide flexibility towards the end-use of the information The latlong pair may be used to place the information on a map but the milepost information may be present so a motorist can place it on the actual roadway

Defining information may be general enough that it covers the entire link such as weather conditions In other cases it may be so specific as to define a certain lane or lanes on the roadway Perhaps an Incident such as a highway accident will only affect a single lane or just the shoulder

On a divided highway there may be a separate set of link information for each direction of travel with its own descriptive information such as on-off ramps and mile-point or milepost and latlong end points In some cases the defining information will also include an elevation which is important when you wish to determine which level you are on when different highways transect However this is not common at this time

The lane-numbering pattern is

Direction of Travel Right Shoulder

Lane 3

Lane 2

Lane 1

Direction of Travel Left Shoulder

Median

Direction of Travel Left Shoulder

Lane 1

Lane 2

Lane 3

Direction of Travel Right Shoulder

Not all roadways have shoulders medians or multiple lanes but the general numbering will always apply

Data Definitions

ODOT TTIP Page 35 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS) Inventory

Start XML Tags

NA

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request

for this data

Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

DateTime

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltlocationgt

ltpointLocationgt

ltpointNamegt

ltpointNamegt

Point Name Example Zoo (2R387) to EB US 26 Text

Data Definitions

ODOT TTIP Page 36 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltlinearReferencePointgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkIdgt

ltidAlphagtltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

idAlpha - Example 15 Text Y

ltoffsetgt

ltmiDecgtltmiDecgt

ltoffsetgt

Mile Point

Example 7221

decimal mile N

lttravelDirectiongt

lttravelDirectiongt

ltlinearReferencePointgt

Highway segment travel direction ndash Example north

south east west

Text N

ltgeoLocationPointgt

ltlatitudegtltlatitudegt

ltlongitudegtltlongitudegt

ltgeoLocationPointgt

Geolocation Point (in micro degrees)

Latitude Example 45426850

Longitude Example -122751220

Decimal 6

decimal place

micro

degrees

N

ltpointLocationgt

ltlocationgt

ltlinkgt

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

482 Traffic Speed Sensor ndash Status - updated Jan 2016

(Corresponding xml file linkStatusxml)

There are a number of methods for counting vehicles on the roadway Uses for the information include future expansion planning determining traffic volumes for highway funding adjusting speeds for safety purposes and determining transportation patterns

Some new applications involve looking at historical traffic pattern along with weather accidents and other impacting information in an attempt to forecast future travel times and alternate travel routes

Terms that are used with these devices are Speed Density and Occupancy

Data Definitions

ODOT TTIP Page 37 copy 2016 ODOT

Speed the average speed of all vehicles over a measured area for a given time This can be calculated from the density and occupancy For an in-depth discussion see httpwwwsinicaedutw~jdsJDS-159pdf

Density the vehicle concentration per kilometer

Occupancy the proportion of time () in which something is on the loop

Some of the more common ways to gather real-time information include

Pneumatic tubes a rubber hose which is placed across the highway to measure axles crossing a certain point on a highway These are primarily used on low speed roads for temporary counting surveys This will give axle counts but most will not give speeds

Bending plate a weight pad attached to a metal plate embedded in the road to measure axle weight and speed It is an expensive device and requires alteration to the road bed This is most often used close to truck weigh stations to weigh on the fly

Inductive loop a wire embedded in the road in a square formation that creates a magnetic field as metal passes over it A roadside counting device then processes the received pulses Some sensors have single loops and gather only occupancy and density Some sensors have double loops spaced a known distance apart so that they can calculate average speeds along with occupancy and density

Radar newer devices use radar to look at individual lanes to give exact real time speeds and counts

Video Cameras programs are being written to compare video frames to determine speed and occupancy information These will provide inexpensive ways to provide information but are still in their infancy

Bluetooth Data Collection Units (DCUs) gather the hashed and coded MAC Address timestamp from Bluetooth enabled devices as vehicles pass by The timestamps collected by different DCUs are compared and used to calculate the travel time for a route

Whatever the method of gathering the data the VDS information will be consistently reported here as the actual calculated or smoothed data as transmitted from the providing agency

The inductive loop is most common in Oregon for real-time highway speed measurement Often there will be an associated highway loop and an on-ramp loop The average highway speed will be used to meter the vehicles allowed to enter the ramp Generally these measurements are provided in short time segments of 20-30 seconds and should have little variability from one reading to the next when traffic is free flowing Generally only the highway loop will be reported here

For city streets there may be one or more loops in an intersection to determine how long the queue is when a light is red There may also be another loop several hundred feet from the intersection to attempt to gather speed information during a green light There are significant calculations which the loop controller must perform to provide representative numbers These readings will generally be calculated and smoothed over a period of from five to fifteen minutes to minimize the effect of stop and go traffic

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt

ltmessageHeadergt

Traffic Speed Sensor (VDS)Status

Start XML Tags

NA

Data Definitions

ODOT TTIP Page 38 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltsendergt

ltagencyIdentifiergt

ltagencyIdentifiergt

ltagencyNamegt

ltAgencyNamegt

ltsendergt

Sender info

- Agency Identifier - Example usordot

- Agency unique name - Example ODOT

Text na Y

ltmessageIDgt

ltmessageIDgt

A hash generated from the CurrentDateTime

Example 2130151525

Integer N

ltresponseTogt

ltresponseTogt

Identifies the message that contained the request for

this data Example 2130151525

Integer Y

lttimeStampgt

ltdategt

lttimegt

lttimeStampgt

Reply Time stamp ndash date and time

- Date Example 20160114

- Time Example 15152500

ltyyyymmddgt

lthhmmssgt

N

ltmessageHeadergt End XML tag NA

ltresponseGroupsgt ltresponseGroupgt

Start XML tags NA

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the status was retrieved

- Date Example 20160114

- Time Example 151525

ltyyyymmddgt

lthhmmssgt

ltlinksgt

ltlinkgt

ltheadgt

ltidgtltidgt

ltissuingAgencygt

ltissuingAgencygt

ltheadgt

- ID - Example ODTR1ST1001

- Issuing Agency - Example Reg1TMOC

Text

Text

Y

ltdelaygtltdelaygt Delay time for travel along a particular link Added to

fre-flow travel time for the link

Example -1

Integer Seconds

Max

-1 Y

ltspeedgtltspeedgt Average speed over the interval

Example 74

Integer KMhr -1 Y

ltdensitygtltdensitygt

Vehicle concentration per kilometer of the link

Example -1

Integer Vehicles per

km

-1 Y

Data Definitions

ODOT TTIP Page 39 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltoccupancygt

ltoccupancygt

ltlinkgt

Occupancy is the percent of time a given point on the

roadway is occupied by a vehicle

Example 14

Decimal Percent

Max

inclusive

100

-1 Y

ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

Data Definitions

ODOT TTIP Page 40 copy 2016 ODOT

49 ROAD AND WEATHER INFORMATION

Road Weather Information may be gathered manually by an ODOT employee visually inspecting the road weather conditions or automatically via system devices installed along the roadway that automatically collect and report weather information The Automated and Manually reported data is provided in two separate XML files

491 Road and Weather Conditions (info gathered manually) - updated July 2015

(Corresponding xml file rwxml)

During the Fall and Winter months ODOT crews inspect the impact that weather is having on road surface conditions The road weather conditions are reported several times per day during inclement weather The reports are posted manually to a central database Any significant changes are radioed to the office where it can be used to upgrade the status right away While the road weather reports are reliable at the time reported they become less accurate as time goes by These are generally not updated after 830 PM and before 4 AM

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information Manually collected

ltmessageHeadergt

ltsendergt

ltagencyIdentifiergt

ltagencyNamegt

ltsendergt

ltmessageIDgt

ltmessageIDgt

ltresponseTogt

ltresponseTogt

lttimeStampgt

ltdateltdategt

lttimegtlttimegt

lttimeStampgt

ltmessageHeadergt

Agency Identifier

Agency unique name

A hash generated from the CurrentDateTime

Identifies the message that contained the request for

this data

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

String

String

Integer ndash Ex

4294967295

Integer ndash Ex

4294967295

DateTime

ltyyyymmddgt

lthhmmssgt

na N

N

N

N

N

N

N

ltresponseGroupsgt ltresponseGroupgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

The time the weather information was retrieved DateTime

ltyyyymmddgt

lthhmmssgt

N

Data Definitions

ODOT TTIP Page 41 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltweatherReports gt

ltweatherReport gt

ltheadgt

ltidgt ltidgt

Business system generated number

Example 170

Integer N

ltupdateTimegt

ltdategtltdategt

lttimegtlttimegt

ltupdateTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltexpiryTimegt

ltdategtltdategt

lttimegtlttimegt

ltexpiryTimegt

Reply Time stamp ndash date and time

Date ndash example 20160115

Time ndash example 111526

DateTime

ltyyyymmddgt

lthhmmssgt

N

ltonExpirygt

ltonExpirygt

ltheadgt

Instruction on Expiry

Example Discard

String N

ltlocationgt

ltlocationNamegt

ltlocationNamegt

Location Name

Example MT BACHELOR

String N

ltlinkLocationgt

ltlinearReferenceLinkgt

ltrefOrImplicitTypegt

ltlinkgt

ltlinkNamegt

ltlinkNamegt

The route where the RW station is located

Example HWY372

Text N

ltlinkIdgt

ltidAlphagt

ltidAlphagt

ltlinkIdgt

ltlinkgt

ltrefOrImplicitTypegt

The state highway where the RW station is located Text N

ltoffset1gt

ltmiDecgtltmiDecgt

ltoffset1gt

Starting Milepoint Numeric 3 dec Miles N

ltoffset2gt

ltmiDecgtltmiDecgt

ltoffset2gt

Ending Milepoint Numeric 3 dec Miles N

Data Definitions

ODOT TTIP Page 42 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

lttravelDirectiongt

ltlinearReferenceLinkgt

Empty field Text Y

ltgeoLocationLinkgt

ltstartPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link start (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltstartPointgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltendPointgt

ltlatitudegt

ltlatitudegt

Geolocation Link end (in micro degrees)

Latitude Example 44075040

Numeric 6

decimal place

Y

ltlongitudegt

ltlongitudegt

ltendPointgt

ltgeoLocationLinkgt

ltlinkLocationgt

ltlocationgt

Longitude Example -122751220

Numeric 6

decimal place

Y

ltcurrTempgt

ltcurrTempgt

current temperature Integer 1˚ Celsius 1001 Y

lthighTempgt

lthighTempgt

high temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltlowTempgt

ltlowTempgt

low temperature in last 24 hours Integer 1˚ Celsius 1001 Y

ltskyConditionsgt ltweatherConditionsgt

ltweatherConditionsgt

ltskyConditionsgt

See schema Example overcast

String Y

ltsnowDepthgt

ltsnowDepthgt

Current depth of unpacked snow on driving surface Integer Centimeter 3001 Y

ltsnowOffRoadgt

ltsnowOffRoadgt

Current depth of unpacked snow off driving surface Integer Centimeter 3001 Y

ltdrivingRestrictionsgt

ltdrivingRestrictionsgt

Winter driving restrictions Example Carry chains or traction tires

Text Y

Data Definitions

ODOT TTIP Page 43 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltpavementConditionsgt

ltpavementConditiongt

ltpavementConditiongt

ltpavementConditionsgt

Pavement Condition Example bare pavement

Text Y

ltfurtherTextgt Start amp End XML Tags NA Y

ltweatherReport gt

ltweatherReportsgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End XML Tags NA

492 Road Weather Info Sys (info gathered via automated weather stations) - updated June 2015

(Corresponding xml file rwisxml)

Automatic weather stations provide weather at a given point alongside a given roadway Since the station exists in a single location it might not reflect the actual conditions of the road surface in the entire vicinity especially if there are large variations in tree coverage and elevation However they are generally reliable and provide real-time information The standard measurements are reported in metric scales and will require translation to US measurements

Data Field Description Data Type Data Unit Null Example

Blank

ltinformationResponsegt Road and Weather Information automatically

collected XML Tag N

ltmessageHeadergt

Agency Identifier Text see Agency

table na N ltsendergt

ltagencyIdentifiergt

ltagencyNamegt Agency unique name Text N

ltsendergt

ltmessageIDgt

A hash generated from the CurrentDateTime

Integer max

Example is

4294967295

N ltmessageIDgt

Data Definitions

ODOT TTIP Page 44 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltresponseTogt Identifies the message that contained the request

for this data

Integer max

Example is

4294967295

N

ltresponseTogt

lttimeStampgt

Reply Time stamp ndash date and time

N

ltdategt ltyyyymmddgt

lttimegt lthhmmssgt

lttimeStampgt

ltmessageHeadergt

ltresponseGroupsgt

The time the weather information was retrieved

ltyyyymmddgt

N

ltresponseGroupgt lthhmmssgt

ltheadgt

ltupdateTimegt

ltdategt

lttimegt

ltupdateTimegt

ltheadgt

ltweatherReports gt

RWIS Site ID number

Example 24000 integer N

ltweatherReport gt

ltheadgt

ltidgt ltidgt

ltupdateTimegt Reply Time stamp ndash date and time N

Data Definitions

ODOT TTIP Page 45 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdategt ltdategt ltyyyymmddgt

lttimegtlttimegt lthhmmssgt

ltupdateTimegt

ltheadgt

ltlocationgt Location name

Text N ltlocationNamegt Example Bend Parkway North Canal (US 97 MP

135)

ltlocationNamegt

ltpointLocationgt

Geolocation Point (in micro degrees)

Latitude Example 44075040

Decimal 5

decimal places N

ltgeoLocationPointgt

ltlatitudegt

ltlatitudegt

ltlongitudegt

Longitude Example -122117431 Decimal 5

decimal places N

ltlongitudegt

ltgeoLocationPointgt

ltpointLocationgt

ltlocationgt

ltcurrTempgtltcurrTempgt current temperature Decimal(41) 1˚ Celsius 1001 Y

ltvisibilitygtltvisibilitygt Surface visability Decimal(41) 1 meter 1000001 Y

ltwindDirectiongt Compass direction north south east west

northwest etc Text Y

ltwindDirectiongt

Data Definitions

ODOT TTIP Page 46 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltwindSpeedgt Wind speed (based on 2 minute sensor collection

average) Decimal(41)

1 meter

second 65535 Y

ltwindSpeedgt

ltwindDirectionGustgt

ltwindDirectionGustgt

Compass direction north south east west

northwest etc Text Y

ltwindSpeedGustgt

ltwindSpeedGustgt

Wind Gust speed (based on 2 minute sensor

collection average) Decimal(41)

1 meter

second 65535 Y

ltprecipitationgt None Yes Rain Snow Mixed Upper Lower Both

Light Light Freezing Freezing Rain Sleet Hail

Lens Dirty No Com Fault Initialized Other

Unidentified Unknown Frozen No Data (251) No

Data (252) No Data (253) No Data (254) No Data

Text No Data Y ltprecipitationgt

lthumiditygt Relative humidity Text xxx 101 Y

lthumiditygt

ltfreezePointgt Temperature at which surface solution will freeze Decimal(41) 1 ˚Celsius 1001 Y

ltfreezePointgt

ltrainRategt

The rainfall rate in tenths of grams per square

meter per second (for rain this is approximately to

036mmhr)

Decimal(52) 036mmhr 65535 Y

Data Definitions

ODOT TTIP Page 47 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltrainRategt

ltprecipSituationgt 6 standard situations (other unknown

noPrecipitation unidentifiedSlight

unidentifiedModerate unidentifiedHeavy) ltorgt No

Data

Text

No Data

Y ltprecipSituationgt

ltsurfaceWaterDepthgt Depth of water on the roadway surface - NOTE a

value of NaN (Not a Number) is returned when the

water depth sensor returns an invalid value

Integer Millimeter 255 Y ltsurfaceWaterDepthgt

ltTempgt

ltsurfaceTemperature1gt

ltsurfaceTemperature1gt

Pavement surface temperature Variable number of

entries determined by number of sensors at the

specified location

surfaceTemperature1 surfaceTemperature2 etc

Decimal(41) 1˚ Celsius 1001 Y

ltTempgt

ltpressuregt

ltpressuregt Barometric pressure Decimal(41) 1 millibar 65535 Y

ltdewPointgt

ltdewPointgt Dewpoint temperature Decimal(41)

1 ˚

Celsius 1001 Y

ltweatherReport gt

End XML Tags NA

ltweatherReports gt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

Data Definitions

ODOT TTIP Page 48 copy 2016 ODOT

410 PORTLAND STATE UNIVERSITY (PSU)

4101 PSU ndash Inventory - updated Jan 2016

(Corresponding xml file psuInventoryxml )

This XML file was created for Portland State University and contains the combined inventory of the Data Acquisition Components (DAC) devices located in Eugene and the Portland Metro area

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltJurisdictionIDgt

ltJurisdictionIDgt

Jurisdiction Id

Example 1

Integer

ltJurisdictionNamegt

ltJurisdictionNamegt

Jurisdiction Name

Example REGION 1

String

ltStationIDgt

ltStationIDgt

Station Id

Example 2

Integer

ltRampsgt

ltRamps gt

Ramps

Example10002

String

ltDetectorsgt

ltDetectorsgt

Detectors

Example 1=1000022=100003

String

ltHighwayNamegt

ltHighwayNamegt

Highway Name

Example OR-217

String

ltLocationNamegt

ltLocationNamegt

Location name

Example NB 72nd (2R348) to NB OR 217

String

ltLatitudegt

ltLatitudegt Geolocation Point (in micro degrees) Latitude Example 44075040

Decimal 5

decimal places

ltLongitudegt

ltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122751220

Decimal 5

decimal places

ltMilePointgt

ltMilePointgt Mile Point

Example 661

Decimal Miles N

ltLinkDirectiongt

ltLinkDirectiongt

Link Direction Example N

Text

ltLanesgt

ltLanesgt

Lanes Example 2

Integer

ltProtocolgt

ltProtocolgt

Protocal

Example NTCIP

String

Data Definitions

ODOT TTIP Page 49 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt

End XML tags NA

4102 PSU ndash MFP - updated Jan 2016

(Corresponding xml file PSUMFPxml )

This XML file was created for Portland State University and contains a complete dataset for the Multnomah Falls parking lot including data related to all the gates status

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt

Start XML Tags NA

ltLOT_SUM_IDgt

ltLOT_SUM_IDgt

Example 1286228 Integer

ltLOT_CAP_PCT_NOgt

ltLOT_CAP_PCT_NOgt

Example 13 Integer

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

ltGATE_STAT_ CLOSE_THRSHLD_NOgt

Example 100 Integer

ltGATE_STAT_ OPEN_THRSHLD_NOgt

ltGATE_STAT_ OPEN_THRSHLD_NOgt

Example 85 Integer

ltCAR_CNT_DAY_NOgt

ltCAR_CNT_DAY_NOgt

Example 37 Integer

ltCUR_CAR_CNT_NOgt

ltCUR_CAR_CNT_NOgt Example 25 Integer

ltGATE_SYS_STAT_NOgt

ltGATE_SYS_STAT_NOgt Example 9 Integer

ltBLK_OUT_SIGN_POS_NOgt

ltBLK_OUT_SIGN_POS_NOgt Example 1 Integer

ltGATE_1_ALM_NOgt

ltGATE_1_ALM_NOgt Example 0 Integer

ltGATE_2_ALM_NOgt

ltGATE_2_ALM_NOgt Example 0 Integer

ltGATE_3_ALM_NOgt

ltGATE_3_ALM_NOgt Example 0 Integer

Data Definitions

ODOT TTIP Page 50 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltGATE_4_ALM_NOgt

ltGATE_4_ALM_NOgt Example 0 Integer

ltBOS_1_STAT_ALM_NOgt

ltBOS_1_STAT_ALM_NOgt Example 0 Integer

ltBOS_2_STAT_ALM_NOgt

ltBOS_2_STAT_ALM_NOgt Example 0 Integer

ltBOS_3_STAT_ALM_NOgt

ltBOS_3_STAT_ALM_NOgt Example 0 Integer

ltBOS_4_STAT_ALM_NOgt

ltBOS_4_STAT_ALM_NOgt Example 0 Integer

ltGATE_1_STAT_POS_NOgt

ltGATE_1_STAT_POS_NOgt Example 2 Integer

ltGATE_2_STAT_POS_NOgt

ltGATE_2_STAT_POS_NOgt Example 2 Integer

ltGATE_3_STAT_POS_NOgt

ltGATE_3_STAT_POS_NOgt Example 2 Integer

ltGATE_4_STAT_POS_NOgt

ltGATE_4_STAT_POS_NOgt Example 2 Integer

ltGATE_1_DTCTR_FAIL_ALM_NOgt

ltGATE_1_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_ALM_NOgt

ltGATE_2_DTCTR_FAIL_ALM_NOgt Example 12 Integer

ltGATE_3_DTCTR_FAIL_ALM_NOgt

ltGATE_3_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_ALM_NOgt

ltGATE_4_DTCTR_FAIL_ALM_NOgt Example 0 Integer

ltGATE_1_DTCTR_FAIL_CD_NOgt

ltGATE_1_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_2_DTCTR_FAIL_CD_NOgt

ltGATE_2_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_3_DTCTR_FAIL_CD_NOgt

ltGATE_3_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltGATE_4_DTCTR_FAIL_CD_NOgt

ltGATE_4_DTCTR_FAIL_CD_NOgt Example 0 Integer

ltMAN_STAT_CDgt

ltMAN_STAT_CDgt Example 1 Integer

Data Definitions

ODOT TTIP Page 51 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTOCS_SENT_FLGgt

ltTOCS_SENT_FLGgt Example false

String

ltNOTFCTN_SENT_IND_NOgt

ltNOTFCTN_SENT_IND_NOgt Example1

Integer

ltHTCIS_SENT_FLGgt

ltHTCIS_SENT_FLGgt Example false

String

ltUD_DTTMgt

ltUD_DTTMgt Example 2015-02-05T08512998-

0800

DateTime

ltUD_USER_IDgt

ltUD_USER_IDgt Example ODOTpa331

String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4103 PSU ndash DACRegion1Ramps - updated Nov 2015

(Corresponding xml file DACRegion1Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 1 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML tag

NA NA NA NA

ltdevice-status-headergt Start XML tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

Data Definitions

ODOT TTIP Page 52 copy 2016 ODOT

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML tag NA NA NA NA

ltmetered-lane-listgt Start XML tag

NA NA NA NA

ltmetered-lanegt Start XML tag

NA NA NA NA

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

Data Definitions

ODOT TTIP Page 53 copy 2016 ODOT

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

4104 PSU ndash DACRegion2Ramps - updated Nov 2015

(Corresponding xml file DACRegion2Rampsxml )

This XML file contains ramp data collected by our Central Ramp Metering System for all ramps in ODOT Region 2 Traffic Jurisdiction

Data Field Description Data Type Data Unit Null Example Blank

ltramp-meter-status-itemgt Start XML Tag

NA NA NA NA

ltdevice-status-headergt Start XML Tag

NA NA NA NA

ltdevice-idgt ltdevice-idgt Ramp ID Integer Identifier NA N

ltdevice-statusgt ltdevice-statusgt Percentage of Device Operation Decimal Percent NA N

ltcenter-idgt ltcenter-idgt ODOT Jurisdiction (Region) number Integer Identifier NA N

ltresponse-plan-idgt ltresponse-plan-idgt Not used at this time Integer NA N

ltlast-comm-timegt ltlast-comm-timegt Timestamp of the data collected DateTime NA N

ltdevice-status-headergt End XML Tag

NA NA NA NA

ltmetered-lane-listgt Start XML Tag

NA NA NA NA

ltmetered-lanegt Start XML Tag

NA NA NA NA

Data Definitions

ODOT TTIP Page 54 copy 2016 ODOT

ltmeter-implemented-actiongt ltmeter-implemented-actiongt Current action of the Ramp Controller Integer Enumerated Value NA N

ltimplemented-meter-command-sourcegt ltimplemented-meter-command-sourcegt Current source of ramp metering control Integer Enumerated Value NA N

ltmeter-implemented-rategt ltmeter-implemented-rategt Current rate of the ramp meter Integer Vehicleshourlane NA N

ltmeter-requested-actiongt ltmeter-requested-actiongt Ramp Controller action requested by central system Integer Enumerated Value NA N

ltmeter-requested-rategt ltmeter-requested-rategt Metering rate requested by central system Integer Vehicleshourlane NA N

ltmetered-lane-vehicle-countgt ltmetered-lane-vehicle-countgt

Number of vehicles that came down the ramp in a 20 second period denoted by the last-comm-time Integer Vehicles20 seconds NA N

ltmetered-lanegt End XML tag

NA NA NA NA

ltmetered-lane-listgt End XML tag

NA NA NA NA

ltmainline-flow-rategt ltmainline-flow-rategt Volume rate of associated mainline station Integer Vehicles20 seconds NA N

ltmainline-vehicle-occupancygt ltmainline-vehicle-occupancygt Occupancy value of the mainline stations Integer Percent NA N

ltmainline-vehicle-speedgt ltmainline-vehicle-speedgt

Average speed of vehicles in a 20 second period at the mainline station Integer MPH NA N

ltramp-meter-status-itemgt End XML tag NA NA NA NA

Data Definitions

ODOT TTIP Page 55 copy 2016 ODOT

411 DATA ACQUISITION (DAC)

4111 DAC ndash Eugene - updated Jan 2018

(Corresponding xml file DACEugenexml)

Data Acquisition Components (DAC) Lane Detector data located in ODOT Regions 2-5

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Eugene

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-gt

ltstation-idgt

Unique Identifier of the Detector Station

Example 22

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1001741

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 6 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 8 (percent)

Integer

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 59 (mph)

Integer

Data Definitions

ODOT TTIP Page 56 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

4112 DAC ndash Portland - updated Jan 2018

(Corresponding xml file DACPortlandxml)

Data Acquisition Components (DAC) Lane Detector data located in the Portland Metro area (ODOT Region 1)

Data Field Description Data Type Data Unit Null Example

Blank

ltns2detectorDataObject

xmlnsns2=httpodotgovgt Data Acquisition Component - Portland

NA

ltdetector-data-itemgt

ltdetector-listgt

ltdetector-data-detailgt

Start XML Tags NA

ltstation-idgtltstation-idgt Unique Identifier of the Detector Station

Example 2

Integer

ltdetector-idgt

ltdetector-idgt Unique Identifier of the Lane Detector with lane

number Example 1000021

String

ltdetection-time-stampgt

ltdetection-time-stampgt The time the detector data was measured

Example 2015-02-05T085240000-0800

DateTime

ltvehicle-countgt

ltvehicle-countgt The volume of vehicles per 20 second sample

Example 11 (veh20-sec)

Integer

ltvehicle-occupancygt

ltvehicle-occupancygt Detector Occupancy (percentage of 20 second

sample the detector was active)

Example 17 (percent)

Integer

Data Definitions

ODOT TTIP Page 57 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltdetector-reliabilitygt

ltdetector-reliabilitygt Percentage of time the detector was relaiable

during the 20 second sample

Example 100 (percent)

Integer

ltvehicle-speedgt

ltvehicle-speedgt Average speed of vehicles during the 20 second

sample Example 48 (mph)

Integer

ltdetector-data-detailgt

ltdetector-listgt

ltdetector-data-itemgt

ltns2detectorDataObjectgt

End XML Tags NA

412 TRAVEL TIME (TT)

4121 TT - DCU Inventory - updated Jan 2016

(Corresponding xml file TTDcuInventoryxml)

Travel Time Data Collection Unit for the vehicles containing BlueTooth device

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tag NA

ltDcuIDgtltDcuIDgt Example 467 Integer ltDcuNamegtltDcuNamegt Example 99W I-5 String ltLatitudegt ltLatitudegt Geolocation Point (in micro degrees)

Latitude Example 44075040 decimal

ltLongitudegtltLongitudegt Geolocation Point (in micro degrees)

Longitude Example -122117431

decimal

ltHighwaygtltHighwaygt Example 99W String

Data Definitions

ODOT TTIP Page 58 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltRoadwayNumbergt

ltRoadwayNumbergt

Example 1 String

ltMilePointgtltMilePointgt Example 758 Decimal ltLocationTypegt

ltLocationTypegt

Example Intersection ltorgt FreeFlowingTraffic String

ltIsActivegt ltIsActivegt Example false String ltTablegt

ltNewDataSetgt End XML Tags

NA

4122 TT - DC Traversals - updated Jan 2016

(Corresponding xml file TTDcuTraversalsxml)

Bluetooth stations along the road that capture the traversal as the time taken for a vehicle to travel from one station (sensor) to the next

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltTraversalIDgt

ltTraversalIDgt

Example 141866424 Integer

ltSegmentIDgtltSegmentIDgt Example 2303 Integer ltTraversalEndDateTimegt

ltTraversalEndDateTimegt

Example 2015-02-05T085027-0800 DateTime

ltTraversalTravelDateTimegt

ltTraversalTravelDateTimegt

Example22 Integer

ltDataSourceNamegt

ltDataSourceNamegt

Example ODOT String

ltTravesalSubmittedDateTimegt

ltTravesalSubmittedDateTimegt

Example 2015-02-05T08524175-

0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 59 copy 2016 ODOT

4123 TT - Segment Inventory - updated Jan 2016

(Corresponding xml file TTSegInventoryxml)

Inventory of devices that collect vehicle data for a given segment Includes location information and the parameters used for calculating the average travel time

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt Start XML Tag NA ltTablegt Start XML Tag NA ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltStationIDgtltStationIDgt Example ODTR1ST3100 String ltSegmentNamegt

ltSegmentNamegt

Example I-205 NB Prosperity Park String

ltSegmentTypegt

ltSegmentTypegt

Example 2 Integer

ltSegmentLengthgt

ltSegmentLengthgt

Example 14572 Integer

ltMinimumLanesReportinggt

ltMinimumLanesReportinggt

Example 05 Decimal

ltCalculationThresholdgt

ltCalculationThresholdgt

Example 30 Integer

ltCalculationPeriodgt

ltCalculationPeriodgt

Example 2 Integer

ltMinimumSamplesgt

ltMinimumSamplesgt

Example 3 Integer

ltSegmentMaximumFiltergt

ltSegmentMaximumFiltergt

Example 9936 Integer

ltSegmentMinimumFiltergt

ltSegmentMinimumFiltergt

Example 132 Integer

ltStandardDeviationSamplesgt

ltStandardDeviationSamplesgt

Example 15 Integer

ltStandardDeviationMultipliergt

ltStandardDeviationMultipliergt

Example 196 Decimal

ltUseStandardDeviationFiltergt

ltUseStandardDeviationFiltergt

Example true String

Data Definitions

ODOT TTIP Page 60 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltIsActivegtltIsActivegt Example true String

ltTablegt

ltNewDataSetgt End XML Tags

NA

4124 TT - Segment Calculations - updated Jan 2016

(Corresponding xml file TTSegmentCalcsxml)

The calculated average travel time for a specific segment

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags

NA

ltSegmentIDgtltSegmentIDgt Example 2107 Integer ltSegmentCalcTimegt

ltSegmentCalcTimegt

Example 2016-01-13T1544358-

0800

DateTime

ltSegmentTravelTimegt

ltSegmentTravelTimegt

Example 47 Integer

ltCalcVariancegt

lt CalcVariance gt

Example 22050420168067206 Decimal

ltCalcConfidenceIntervalgt

lt CalcConfidenceInterval gt

Example 20465144746094763 Decimal

ltStdDeviationCalcSamplesRemovedgt

ltStdDeviationCalcSamplesRemoved gt

Example 5 Integer

ltStdDeviationFitlerValuegt

ltStdDeviationFitlerValue gt

Example 24599865549667122 Decimal

ltExceededMaxFiltergt

ltExceededMaxFilter gt

Example 0 Integer

ltBelowMinFiltergt

lt BelowMinFilter gt

Example 1 Integer

Data Definitions

ODOT TTIP Page 61 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltTablegt

ltNewDataSetgt End XML Tags

NA

413 CLASSIFIED LENGTH amp SPEED (CLS)

The Classified Length and Speed module is a data collector used to collect length and speed data to publish to the TTIP Server Data is collected through web services on Automated Traffic Controllers (ATCs) All data is aggregated into Length and Speed classifications that are defined in the CLS Inventory file by detector station Each length and speed aggregate represents 20 seconds of data collection

4131 CLS - Inventory - updated Jan 2016

(Corresponding xml file clsinventoryxml)

List classifications for length and speed and which detector station they belong to

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltStationIDgtltStationIDgt ID of detctor station Example 7 Numeric ltTypegtltTypegt Type of clasification lsquoLengthrsquo or lsquoSpeedrsquo Text ltBinNumbergtlt BinNumber gt The ID of the bin classification Example

3 Numeric Number

lt BinNumberDescriptiongt

ltBinNumberDescriptiongt

The classification aggregate value If this

is for length this will be in feet If it is

speed it will be in mph Example 30

Numeric Feet or MPH

ltConfigureTimegt

ltConfigureTimegt

The time at which the classfication was

configured Example 2016-01-

05T1429090228548-0800

DateTime

ltTablegt

ltNewDataSetgt End XML Tags

NA

Data Definitions

ODOT TTIP Page 62 copy 2016 ODOT

4132 CLS - Speed - updated Jan 2016

(Corresponding xml file clsspeedbindataxml)

Speed data aggregated by speed classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular speed classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric ltBNgtltBNgt BIN - ID of Speed Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XM End XML Tags

NA

4133 CLS - Length ndash updated Jan 2016

(Corresponding xml file clslengthbindataxml)

Length data aggregated by length classification for each detector station The Bin Count represents the number of vehicles that passed the detector station in a 20 second period that fall into that particular length classification

Data Field Description Data Type Data Unit Null Example

Blank

ltNewDataSetgt

ltTablegt Start XML Tags NA

ltSIDgtltSIDgt Station ID Example 7 Numeric ltLNgtltLNgt Lane - Right most lane is 1 Numeric

Data Definitions

ODOT TTIP Page 63 copy 2016 ODOT

Data Field Description Data Type Data Unit Null Example

Blank

ltBNgtltBNgt BIN - ID of Length Classification unique

to detector station Example 1

Numeric

ltBCgtltBCgt BIN count - Number of cars that are in

that classification during 20 second

collection cycle Example 5

Numeric

ltDTgtltDTgt End time of aggregate sample Example

2016-01-11T130601-0800

DateTime

ltTablegt

ltNewDataSetgt XMEnd XML Tags

NA

Data Definitions

ODOT TTIP Page 64 copy 2016 ODOT

APPENDIX

A ACRONYMS

CCTV Closed Circuit Television Cameras

DAC Data Acquisition Component

DMS Dynamic Message Signs

ISP Internet Service Provider

ITS Intelligent Transportation System

ODOT Oregon Department of Transportation

RW Road Weather ndash Manually entered weather information (Manual data collection)

RWIS Remote Weather Information System (Automated data collection)

TLE TripCheck Local Entry ndash for local (non ODOT) events

TTIP TripCheck Traveler Information Portal

VOS Volume Occupancy and Speed

WSDOT Washington State Department of Transportation

XML Extensible Markup Language

Data Definitions

ODOT TTIP Page 65 copy 2016 ODOT

B AGENCY NAMING REFERENCES

Agency Identifier External Agency Name Agency Name Issuing Agency

usordot Oregon Department of Transportation

ODOT State of Oregon REG1TMOC ODOT Region 1 Portland

Reg1TMOC same as Agency Name ODT2 ODOT Region 2 Salem

usorportlandpdx Port of Portland Portland International Airport

PDX

usorportlanddot City of Portland

C MESSAGE WRAPPER EXAMPLE (USING LINKSTATUS)

Request Response

- ltinformationResponsegt

- ltmessageHeadergt

- ltsendergt

ltagencyIdentifiergtusordotltagencyIdentifiergt

ltagencyNamegtODOTltagencyNamegt

ltsendergt

ltmessageIDgt1138212969097ltmessageIDgt

ltresponseTogt2131101608ltresponseTogt

- lttimeStampgt

ltdategt20060125ltdategt

lttimegt10160900lttimegt

lttimeStampgt

ltmessageHeadergt

- ltresponseGroupsgt

- ltresponseGroupgt

- ltheadgt

- ltupdateTimegt

ltdategt20060125ltdategt

lttimegt101520lttimegt

ltupdateTimegt

ltheadgt

- ltlinksgt

Standard encoding message Data provider is ODOT Message ID from Datetime hash Message date ndash 01252006 Message time = 101609 AM Portal update Date Portal update Time Link records follow

Data Definitions

ODOT TTIP Page 66 copy 2016 ODOT

Link Status - ltlinkgt

- ltheadgt

ltidgtODTR1ST1001ltidgt

ltissuingAgencygtReg1TMOCltissuingAgencygt

ltheadgt

ltdelaygt-1ltdelaygt

ltspeedgt122ltspeedgt

ltdensitygt-1ltdensitygt

ltoccupancygt7ltoccupancygt

ltlinkgt

Link record 1 Link id or name Region 1 TMOC of ODOT Delay is unavailable Speed in KMH Density is unavailable The point is occupied 7 of the time End of Link 1

Request Tail ltlinksgt

ltresponseGroupgt

ltresponseGroupsgt

ltinformationResponsegt

End of Link records

Page 23: Data Definitions & Schemas - TripCheck
Page 24: Data Definitions & Schemas - TripCheck
Page 25: Data Definitions & Schemas - TripCheck
Page 26: Data Definitions & Schemas - TripCheck
Page 27: Data Definitions & Schemas - TripCheck
Page 28: Data Definitions & Schemas - TripCheck
Page 29: Data Definitions & Schemas - TripCheck
Page 30: Data Definitions & Schemas - TripCheck
Page 31: Data Definitions & Schemas - TripCheck
Page 32: Data Definitions & Schemas - TripCheck
Page 33: Data Definitions & Schemas - TripCheck
Page 34: Data Definitions & Schemas - TripCheck
Page 35: Data Definitions & Schemas - TripCheck
Page 36: Data Definitions & Schemas - TripCheck
Page 37: Data Definitions & Schemas - TripCheck
Page 38: Data Definitions & Schemas - TripCheck
Page 39: Data Definitions & Schemas - TripCheck
Page 40: Data Definitions & Schemas - TripCheck
Page 41: Data Definitions & Schemas - TripCheck
Page 42: Data Definitions & Schemas - TripCheck
Page 43: Data Definitions & Schemas - TripCheck
Page 44: Data Definitions & Schemas - TripCheck
Page 45: Data Definitions & Schemas - TripCheck
Page 46: Data Definitions & Schemas - TripCheck
Page 47: Data Definitions & Schemas - TripCheck
Page 48: Data Definitions & Schemas - TripCheck
Page 49: Data Definitions & Schemas - TripCheck
Page 50: Data Definitions & Schemas - TripCheck
Page 51: Data Definitions & Schemas - TripCheck
Page 52: Data Definitions & Schemas - TripCheck
Page 53: Data Definitions & Schemas - TripCheck
Page 54: Data Definitions & Schemas - TripCheck
Page 55: Data Definitions & Schemas - TripCheck
Page 56: Data Definitions & Schemas - TripCheck
Page 57: Data Definitions & Schemas - TripCheck
Page 58: Data Definitions & Schemas - TripCheck
Page 59: Data Definitions & Schemas - TripCheck
Page 60: Data Definitions & Schemas - TripCheck
Page 61: Data Definitions & Schemas - TripCheck
Page 62: Data Definitions & Schemas - TripCheck
Page 63: Data Definitions & Schemas - TripCheck
Page 64: Data Definitions & Schemas - TripCheck
Page 65: Data Definitions & Schemas - TripCheck
Page 66: Data Definitions & Schemas - TripCheck
Page 67: Data Definitions & Schemas - TripCheck
Page 68: Data Definitions & Schemas - TripCheck
Page 69: Data Definitions & Schemas - TripCheck
Page 70: Data Definitions & Schemas - TripCheck