2014 ITS World Congress Connected Vehicle Test Bed Demonstration Traveler Situation Data
datahub.transportation.gov | Last Updated 1 May 2024During the 2014 ITS World Congress a demonstration of the connected vehicle infrastructure in the City of Detroit was conducted. The test site included approximately 14 intersections around Detroit’s COBO convention center and involved 9 equipped vehicles. Traveler Situation Data (TSD) was obtained from the data warehouse, and not the data clearinghouse. Only 19 messages were obtained from our query as the current mode of operation of the Test Bed is that the warehouse only contains a few static messages, which are meant to serve as a proxy for future operation in which query submissions will only return message(s) relevant to the context in which the query was submitted. The messages that returned per a query submission communicates a pertinent advisor message which is in part contextualized by location and content. NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data
This dataset has the following 26 columns:
Column Name | API Column Name | Data Type | Description | Sample Values |
---|---|---|---|---|
dialogID | dialogid | text | This field contains the ID of the type of data being transmitted. In this instance all entries will be “advSitDatDistRSE” indicating that traveler situation data (TSD) is being transmitted / presented here. | advSitDatDistRSE view top 100 |
seqID | seqid | text | This field communicate the message content type. All entries in this instance will be “data” indicating that the data portion of the transmitted message is presented. | data view top 100 |
requestID | requestid | text | This field contains the ID (number) of the TSD. | 5.45E+04 5.45E+08 5.45E+06 5.45E+07 5.45E+10 view top 100 |
recordCount | recordcount | number | This field contains the total number of records received in the TSD query, summed across all bundles. | 19 17 12 14 5 view top 100 |
asdBundles_bundleCount | asdbundles_bundlecount | number | This field contains the number of bundles in the TSD. | 2 1 view top 100 |
asdBundles_bundleNumber | asdbundles_bundlenumber | number | This field contains the sequence number in a bundle of TSDs | 2 1 view top 100 |
asdBundles_bundleId | asdbundles_bundleid | text | This field contains the ID (number) of a bundle. | F93AFF66 735C803B DCF469ED 45F80BAF 94E35A3E view top 100 |
asdBundles_asdRecords_broadcastInst_biType | asdbundles_asdrecords_broadcastinst_bitype | text | This field contains the type of broadcast message. For the TSD dataset, this data element takes only one value: {tim}, since this data file is communicating TSDs | tim view top 100 |
asdBundles_asdRecords_broadcastInst_biPsid | asdbundles_asdrecords_broadcastinst_bipsid | number | This field contains the ID (number) of the broadcast. | 8003 view top 100 |
asdBundles_asdRecords_broadcastInst_biPriority | asdbundles_asdrecords_broadcastinst_bipriority | number | This field contains the priority of the broadcast message, presented in an 8 bit binary string. The 5 least significant bits are reserved (and set to 0). A priority of all zeros is used for routing messages such as roadside signage where not displaying the message to the driver is only of modest impact. A value of 111xxxxx indicates a message of the highest priority. Other priorities are set according to local conventions. Values in decimal should be converted back to the 8 bit binary string and interpreted as described above. For example, a value of 32 is 00100000 in binary and corresponds to a broadcast priority of 1 (low). | 32 view top 100 |
asdBundles_asdRecords_broadcastInst_biTxMode | asdbundles_asdrecords_broadcastinst_bitxmode | text | This field contains the transmission mode of the broadcast message. For the TSD dataset, this data element takes only one value: {alternating} | alternating view top 100 |
asdBundles_asdRecords_broadcastInst_biTxChannel | asdbundles_asdrecords_broadcastinst_bitxchannel | text | This field contains the transmission channel of the broadcast message. Possible values are chControl, chService, and ch172, 174,176, 178, 780, 182, and 184. | ch178 view top 100 |
asdBundles_asdRecords_broadcastInst_biTxInterval | asdbundles_asdrecords_broadcastinst_bitxinterval | number | This field contains the time interval at which to transmit message snapshots, in 1/10th integer seconds. | 1 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStart_year | asdbundles_asdrecords_broadcastinst_bideliverystart_year | number | This field contains the year in which the message should become available to vehicles | 2014 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStart_month | asdbundles_asdrecords_broadcastinst_bideliverystart_month | number | This field contains the month in which the message should become available to vehicles | 8 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStart_day | asdbundles_asdrecords_broadcastinst_bideliverystart_day | number | This field contains the day in which the message should become available to vehicles | 30 26 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStart_hour | asdbundles_asdrecords_broadcastinst_bideliverystart_hour | number | This field contains the hour in which the message should become available to vehicles | 22 18 19 20 17 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStart_minute | asdbundles_asdrecords_broadcastinst_bideliverystart_minute | number | This field contains the minute in which the message should become available to vehicles | 32 30 1 28 3 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStop_year | asdbundles_asdrecords_broadcastinst_bideliverystop_year | number | This field contains the year in which the message should stop being available to vehicles. | 2014 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStop_month | asdbundles_asdrecords_broadcastinst_bideliverystop_month | number | This field contains the month in which the message should stop being available to vehicles. | 9 view top 100 |
asdBundles_asdRecords_broadcastInst_biDeliveryStop_day | asdbundles_asdrecords_broadcastinst_bideliverystop_day | number | This field contains the day in which the message should stop being available to vehicles. | 7 3 view top 100 |
asdBundles_asdRecords_broadcastInst_biDelievryStop_hour | asdbundles_asdrecords_broadcastinst_bidelievrystop_hour | number | This field contains the hour in which the message should stop being available to vehicles. | 22 18 19 20 17 view top 100 |
asdBundles_asdRecords_broadcastInst_biDelievryStop_minute | asdbundles_asdrecords_broadcastinst_bidelievrystop_minute | number | This field contains the minute in which the message should stop being available to vehicles. | 32 30 1 28 3 view top 100 |
asdBundles_asdRecords_broadcastInst_biSignature | asdbundles_asdrecords_broadcastinst_bisignature | text | This field contains information on whether the message has been signed. | TRUE view top 100 |
asdBundles_asdRecords_broadcastInst_biEncryption | asdbundles_asdrecords_broadcastinst_biencryption | text | This field contains information on whether the message is encrypted. | FALSE view top 100 |
asdBundles_asdRecords_advisoryMessage | asdbundles_asdrecords_advisorymessage | text | This field contains a complete TIM according to the SAE J2735 Standard which is based on a tag-length-value structure of the ASN.1 BER-DER formatted data. To provide insight into decoding these entries the following table will present the breakdown of a single message and summarize each of its components. As one will see in the table below, critical to decoding these entries in the translation of the ITIS codes into their meaning. To translate these codes user are advised to consult the SAE J2540 Standard. TIM messages, which are contained in this *_advisoryMessage field is comprised of three parts: Part I is header, Part II is common anchor, Part III is content, all of them are colored coded in the table below. Additionally, in the table below data element are shown in two colors, blue is for data type and red is data name. | 3081D88001108109000000000008281401A481C33081C0800102A11BA119A0108004193AAFF98104CE80E578820200B48102000C820102820207DE8303055C8084027D00850102A6108004193AB1DD8104CE80EA03820200B58702016E880100A93930378002000CA231A02F820100A32A040405F5035C0404037BFF4B04040763FA8C0404047FFE15040402A9FFB1040403080047040404F7027BAA3AA0383006A004800235293006A0048002010C3006A004800231053006A004800222113006A0048002010C3006A004800231183006A0048002221185022052 3081BA8001108109000000000009021402A481A53081A2800102A11BA119A0108004193AE6728104CE802F3E820200B88102000C820102820207DE8303055C8084027D00850102A6108004193AE8DF8104CE80353E820200B78702016E880100A91B30198002000CA213A011820100A30C040407AD044D040405F0033EAA3AA0383006A004800235293006A0048002010C3006A004800231103006A004800222113006A0048002010C3006A004800231283006A0048002221185029123 3081BD8001108109000000000009021404A481A83081A5800102A11BA119A0108004193B278A8104CE80672A820200B881020078820102820207DE8303055C8084027D00850102A6108004193B25048104CE80613A820200B88702016EA921301F80020078A219A017820100A3120404FB05FD140404F7F0FB410404F4FBF98BAA3AA0383006A004800235293006A0048002010C3006A004800231283006A004800222113006A0048002010C3006A004800231383006A0048002221185028596 3081D58001108109000000000008281403830101A481BD3081BA800102A11BA119A0108004193A7E7E8104CE802FB3820200B38102008A820102820207DE83030556E084027D00850102A6108004193A79CD8104CE802F2B820200B38702016E880100A93330318002008AA22BA029820100A3240404FFCCFA610404013DFAA904040131FF22040401F1FFDB040401DB00AE040405090357AA3AA0383006A0048002352A3006A0048002010C3006A004800231043006A004800222113006A0048002010C3006A004800231183006A004800222118502DF7F 308182800110810900000046485F494345830101A46B3069800102A11BA119A0108004195428CB8104CE4539B68202025C8102FFFF820102820207DE83030530A784027D00850102A610800419542EAA8104CE454A108202025C8702099C880100A91230108002FFFFA20AA008A3060404294C01A0AA0AA0083006A0048002171885020000 view top 100 |