2014 ITS World Congress Connected Vehicle Test Bed Demonstration Traveler Situation Data

datahub.transportation.gov | Last Updated 1 May 2024

During 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

Tags: intelligent transportation systems (its), its joint program office (jpo), 2014 its world congress (itswc) connected vehicle (cv) test bed demonstration, traveler situation data (tsd), connected equipment, application message, field test, detroit, michigan, map, signal phase and timing (spat), arterial, connected vehicle message, its world congress

This dataset has the following 26 columns:

Column NameAPI Column NameData TypeDescriptionSample Values
dialogIDdialogidtextThis 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.
seqIDseqidtextThis 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.
requestIDrequestidtextThis field contains the ID (number) of the TSD.
recordCountrecordcountnumberThis field contains the total number of records received in the TSD query, summed across all bundles.
asdBundles_bundleCountasdbundles_bundlecountnumberThis field contains the number of bundles in the TSD.
asdBundles_bundleNumberasdbundles_bundlenumbernumberThis field contains the sequence number in a bundle of TSDs
asdBundles_bundleIdasdbundles_bundleidtextThis field contains the ID (number) of a bundle.
asdBundles_asdRecords_broadcastInst_biTypeasdbundles_asdrecords_broadcastinst_bitypetextThis 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
asdBundles_asdRecords_broadcastInst_biPsidasdbundles_asdrecords_broadcastinst_bipsidnumberThis field contains the ID (number) of the broadcast.
asdBundles_asdRecords_broadcastInst_biPriorityasdbundles_asdrecords_broadcastinst_biprioritynumberThis 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).
asdBundles_asdRecords_broadcastInst_biTxModeasdbundles_asdrecords_broadcastinst_bitxmodetextThis field contains the transmission mode of the broadcast message. For the TSD dataset, this data element takes only one value: {alternating}
asdBundles_asdRecords_broadcastInst_biTxChannelasdbundles_asdrecords_broadcastinst_bitxchanneltextThis field contains the transmission channel of the broadcast message. Possible values are chControl, chService, and ch172, 174,176, 178, 780, 182, and 184.
asdBundles_asdRecords_broadcastInst_biTxIntervalasdbundles_asdrecords_broadcastinst_bitxintervalnumberThis field contains the time interval at which to transmit message snapshots, in 1/10th integer seconds.
asdBundles_asdRecords_broadcastInst_biDeliveryStart_yearasdbundles_asdrecords_broadcastinst_bideliverystart_yearnumberThis field contains the year in which the message should become available to vehicles
asdBundles_asdRecords_broadcastInst_biDeliveryStart_monthasdbundles_asdrecords_broadcastinst_bideliverystart_monthnumberThis field contains the month in which the message should become available to vehicles
asdBundles_asdRecords_broadcastInst_biDeliveryStart_dayasdbundles_asdrecords_broadcastinst_bideliverystart_daynumberThis field contains the day in which the message should become available to vehicles
asdBundles_asdRecords_broadcastInst_biDeliveryStart_hourasdbundles_asdrecords_broadcastinst_bideliverystart_hournumberThis field contains the hour in which the message should become available to vehicles
asdBundles_asdRecords_broadcastInst_biDeliveryStart_minuteasdbundles_asdrecords_broadcastinst_bideliverystart_minutenumberThis field contains the minute in which the message should become available to vehicles
asdBundles_asdRecords_broadcastInst_biDeliveryStop_yearasdbundles_asdrecords_broadcastinst_bideliverystop_yearnumberThis field contains the year in which the message should stop being available to vehicles.
asdBundles_asdRecords_broadcastInst_biDeliveryStop_monthasdbundles_asdrecords_broadcastinst_bideliverystop_monthnumberThis field contains the month in which the message should stop being available to vehicles.
asdBundles_asdRecords_broadcastInst_biDeliveryStop_dayasdbundles_asdrecords_broadcastinst_bideliverystop_daynumberThis field contains the day in which the message should stop being available to vehicles.
asdBundles_asdRecords_broadcastInst_biDelievryStop_hourasdbundles_asdrecords_broadcastinst_bidelievrystop_hournumberThis field contains the hour in which the message should stop being available to vehicles.
asdBundles_asdRecords_broadcastInst_biDelievryStop_minuteasdbundles_asdrecords_broadcastinst_bidelievrystop_minutenumberThis field contains the minute in which the message should stop being available to vehicles.
asdBundles_asdRecords_broadcastInst_biSignatureasdbundles_asdrecords_broadcastinst_bisignaturetextThis field contains information on whether the message has been signed.
asdBundles_asdRecords_broadcastInst_biEncryptionasdbundles_asdrecords_broadcastinst_biencryptiontextThis field contains information on whether the message is encrypted.
asdBundles_asdRecords_advisoryMessageasdbundles_asdrecords_advisorymessagetextThis 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.