datahub-transportation-gov/2014-its-world-congress-connected-vehicle-test-bed-3trh-hz5x
 
Readme
Updated 5 months ago
Indexed 16 hours ago

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

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.Intersection Situation Data (ISD) data set communicates MAP and signal phase and timing (SPaT) information. MAP information communicates an intersection’s location (latitude and longitude), elevation, and geometric features such as approaches and lane configuration. SPaT data communicates the (current) state of the intersection’s signal indication(s). The data is composed of discrete Row Groups. A Row Group is a collection of (approximately 3-4) consecutive rows with common attribute.

NOTE: All Extra Files are attached in 2014 ITS World Congress Connected Vehicle Test Bed Demonstration Vehicle Situation Data

Columns

NameSocrata field nameColumn name in sgr mountData typeDescription
spat_timestamp_dayspat_timestamp_dayspat_timestamp_dayNumberDay when the SPaT message was generated in GMT.
map_int_approach_idmap_int_approach_idmap_int_approach_idNumberThis field contains a unique index value for an approach or egress in an intersection for the convenience of human users. It is typically used along with an optional human readable string name for the object.
map_layerTypemap_layertypemap_layertypeTextThis field specifies the type of information found in a layer of a geographic map fragment (such as an intersection). For the ISD dataset, this data element takes only one value: “intersectionData”
map_int_approach_drivingLanes_nodeListmap_int_approach_drivinglanes_nodelistmap_int_approach_drivinglanes_nodelistTextThis field contains the sequence of signed offset values for determining the Xs and Ys (and, possibly Width or Zs when present) using the current intersection position to build a path for the enclosing reference lane relating to a lane in the current intersection. Please consult page 77 of the SAE J2735 Standard for more information.
dialogIDdialogiddialogidTextThis field contains the ID of the type of data being transmitted. In this instance all entries will be “intersectionSitDataDep” indicating that intersection situation data (ISD) is being transmitted / presented here.
spat_timestamp_monthspat_timestamp_monthspat_timestamp_monthNumberMonth when the SPaT message was generated in GMT.
bundleNumberbundlenumberbundlenumberNumberThis field contains the bundle number of the ISD message
spat_timestamp_secondspat_timestamp_secondspat_timestamp_secondNumberSecond when the SPaT message was generated in GMT.
map_int_idmap_int_idmap_int_idTextThis field contains an ID (number) that globally and uniquely defines an intersection within a country or region. Assignment rules for this value are established elsewhere and may use regional assignment schemas that vary.
map_msgIDmap_msgidmap_msgidTextThe msgID is a data element used in each message to define which type of message follows from the message set defined by this Standard. This data element is always the first value inside the message and is used to tell the receiving application how to interpret the remaining bytes (i.e. what message structure has been used). For the ISD dataset, this data element takes only one value: “mapData”
serviceRegion_nwCorner_longserviceregion_nwcorner_longserviceregion_nwcorner_longNumberThis field contains the longitude of the northwest corner of the rectangle that the SDW presides over, expressed in 1/10th integer microdegrees. The value 1800000001 shall be used when unavailable.
map_int_approach_namemap_int_approach_namemap_int_approach_nameTextThis field contains an optional human readable name for the approach lanes to the intersection.
spat_int_idspat_int_idspat_int_idTextThe unique ID number for the SPaT message.
map_int_namemap_int_namemap_int_nameTextThis field contains an optional human readable name for the intersection.
map_msgCntmap_msgcntmap_msgcntNumberThis field contains a sequence number within a stream of messages with the same msgID and from the same sender. A sender may initialize this element to any value in the range 0-127 when sending the first message with a given msgID, or if the sender has changed identity since sending the most recent message with that msgID. Two further use cases exist when the sender has not changed identity: When the rest of the message content to be sent changes, the msgCnt shall be set equal to one greater than the value used in the most recent message sent with the same msgID. When the message content has not changed, the msgCnt is not changed. For this element the value after 127 is zero. The receipt of a non-sequential msgCnt value (from the same sending device and message type) implies that one or more messages from that sending device may have been lost, unless msgCnt has been reinitialized due to an identity change
map_int_refPoint_latmap_int_refpoint_latmap_int_refpoint_latNumberThis field contains the latitude of a reference point at the described intersection, expressed in 1/10th integer microdegrees. The value 900000001 shall be used when unavailable.
mapint_approaches_approach_drivingLanesmapint_approaches_approach_drivinglanesmapint_approaches_approach_drivinglanesNumberThis field contains the width of a lane in in centimeters. The maximum value would be a lane of over 327 centimeters.
map_crcmap_crcmap_crcTextThis attribute is a two byte data element calculated over the payload bytes of the message (starting with the initial sequence and ending with the last data element before the CRC itself and including all tag, length, and values bytes found in between). It is always placed as the very last data element in the message. The generating polynomial used is the "CRC-CCITT" commonly expressed as x16 + x12 + x5 + 1. An initial seed value of zero shall be used. Note that because the first byte of every DSRC message is never zero (it is 0x30), framing errors due to incorrectly clocking initial zero values cannot occur. Note that the MSB byte is always transmitted first, following the typical ASN bytes order. When a well formed DSRC message (including its last two bytes holding the CRC value) is decoded and input to the CRC process, the resulting CRC should always be the value zero.
spat_timestamp_yearspat_timestamp_yearspat_timestamp_yearNumberYear when the SPaT message was generated in GMT.
map_int__approach_drivingLanes_laneNumbermap_int__approach_drivinglanes_lanenumbermap_int__approach_drivinglanes_lanenumberNumberThis field contains a unique index value for a lane used to refer to that lane by other objects in the intersection map data structure. Lanes may be ingress (inbound traffic) or egress (outbound traffic) in nature, as well as barriers and other types of specialty lanes. All lanes are numbered. The laneNumber, in conjunction with the intersections_id, forms a regionally unique way to address a specific lane in that intersection.
spat_int_states_timeToChangespat_int_states_timetochangespat_int_states_timetochangeNumberThis attribute specifies the time remaining, in tenths of a second, before the signal phase will change to the next phase. The maximum time remaining is 12000 (120.0 seconds = 2 minutes). 0 indicates no time remaining. A special value of 12001 indicates indefinite time remaining (greater than 2 minutes) and a special value of 12002 indicates an unknown amount of time remaining.
serviceRegion_seCorner_latserviceregion_secorner_latserviceregion_secorner_latNumberThis field contains the latitude of the southeast corner of the rectangle that the SDW presides over, expressed in 1/10th integer microdegrees. The value 900000001 shall be used when unavailable
timeToLivetimetolivetimetoliveTextThis field contains the time remaining before the ISD message expires. This field is enumerated as follows: 0 – 1 minute, 1 – 30 minutes, 2- one day, 3 – one week, 4 – one month, 5 – one year
spat_int_states_stateConfidencespat_int_states_stateconfidencespat_int_states_stateconfidenceTextThis field describes the confidence of the current signal phase and its estimated time values. Values are enumerated as follows: 0 – unknownEstimate, 1 – minTime, 2- maxTime, 3 - timeLikelyToChange
spat_timestamp_hourspat_timestamp_hourspat_timestamp_hourNumberHour when the SpaT message was generated in GMT.
serviceRegion_nwCorner_latserviceregion_nwcorner_latserviceregion_nwcorner_latNumberThis field contains the latitude of the northwest corner of the rectangle that the SDW presides over, expressed in 1/10th integer microdegrees. The value 900000001 shall be used when unavailable.
requestIDrequestidrequestidTextThis field contains the ID (number) of the ISD message.
spat_int_statusspat_int_statusspat_int_statusNumberThis attribute contains the Advance Traffic Controller status information on the intersection. Data is encoded in hexadecimal. Converting the hexadecimal to binary gives an 8 bit unsigned integer with bits 76543210. Each bit has value 0 or 1 and indicates whether or not a condition is present at an intersection. For the ISD dataset, this data element takes only one value: {0} which indicates the intersection is operating normally.
serviceRegion_seCorner_longserviceregion_secorner_longserviceregion_secorner_longNumberThis field contains the longitude of the southeast corner of the rectangle that the SDW presides over, expressed in 1/10th integer microdegrees. The value 1800000001 shall be used when unavailable.
spat_int_states_yellStateConfidencespat_int_states_yellstateconfidencespat_int_states_yellstateconfidenceTextThis field describes the confidence of the yellow signal phase and its estimated time values. Values are enumerated as follows: 0 – unknownEstimate, 1 – minTime, 2- maxTime, 3 - timeLikelyToChange
spat_timestamp_minutespat_timestamp_minutespat_timestamp_minuteNumberMinute when the SPaT message was generated in GMT.
spat_int_states_currStatespat_int_states_currstatespat_int_states_currstateTextThis attribute defines the current state of a particular known movement and depends on the type of lane that the currState applies to.
spat_int_states_laneSetspat_int_states_lanesetspat_int_states_lanesetTextThis attribute represents movement within lanes at an intersection. Data is provided in hexadecimal. Each movement/lane pair is provided as a double-octet (four character) hex string. The first two characters represent the movement, while the last two characters represent the lane. The movement is obtained by converting the hexadecimal value to an 8 bit binary string with bits 76543210. A movement is present with a logical 1 for any given bit. Bit 0 represents straight motion, bit 1 represents a left turn, bit 2 represents a right turn, and bit 3 represents a U-turn. No other bits are used. For example, a laneSet string of 0x0703 has the movement characters 07, which are written as 00000111 in binary. Bits 0, 1, and 2 are in the logical 1 position, indicating straight, left, and right movement. The string has lane characters 03 which directly indicate lane 3. Therefore, a laneSet of 0x0703 indicates straight/left/right movement on lane 3. There is no limit to the number of movement lane/pairs possible. For example, a laneSet of 0x08040302 indicates a U-Turn on lane 4 (with movement string 00001000 in binary) and straight/left on lane 2 (with movement string 00000011 in binary). Values in decimal should be converted back to the full binary bit string in order to interpret the laneSet field.
mapData_int_refPoint_longmapdata_int_refpoint_longmapdata_int_refpoint_longNumberThis field contains the longitude of a reference point at the described intersection, expressed in 1/10th integer microdegrees. The value 1800000001 shall be used when unavailable.
seqIDseqidseqidTextThis 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.
map_int_approach_drivingLanes_laneAttributesmap_int_approach_drivinglanes_laneattributesmap_int_approach_drivinglanes_laneattributesNumberThe laneAttributes data element relates the allowed (possible) movements from a motorized vehicle lane. Note that in practice these values may be further restricted by vehicle class, local regulatory environment and other changing conditions. There are 17 enumerated values for the Lane Attributes data element.
Upstream Metadata