 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev26 [issued: 09-18-08]
-
66 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
<xs:element name="yellTimeToChange" type="TimeToChange" minOccurs="0"/>
<xs:element name="yellStateConfidence" type="StateConfidence" minOccurs="0"/>
<!-- below items are all optinal based on use and context
some are used only for ped lans -->
<xs:element name="vehicleCount" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedShort">
<xs:maxInclusive value="60000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="pedDetect" type="PedestrianDetect" minOccurs="0"/>
<!-- true if ANY ped are detected crossing
the above lanes -->
<xs:element name="pedCount" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:unsignedShort">
<xs:maxInclusive value="60000"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- est count of peds -->
<xs:element name="localMovementState" type="local:MovementState" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_SignalPhaseAndTimingMessage (SPAT) <ASN> <XML>. In addition, this item may be used
by data structures in other ITS standards.
Remarks: Note that the value given for the time to change will vary in many actuated signalized
intersection based on the sensor data received during the phase. The data transmitted always reflects the
then most current time value. Therefore, as an example, in a phase which may vary from 15 to 25 seconds
of duration based on observed traffic flows, a time to change value of 15 seconds might be transmitted for
many seconds on end (as many as 10 seconds) followed by decreasing values as the time runs out. During
this entire period of time, the yellow time would also be sent. The time to change element can be regarded
as a guaranteed minimum value of the time that will be elapse unless a preemption event occurs.
6.29 Data Frame: DF_NodeList
Use: The NodeList data structure provides the sequence of signed offset values for determining the Xs
and Ys (and, possibly Width or Zs when present) using the then current ReferencePoint and NodeConfih
objects to build a path for the enclosing ReferenceLane relating to a lane in the current intersection.
ASN.1 Representation:
NodeList ::= SEQUENCE (SIZE(1..64)) OF Offsets
-- RefPointID was removed because in practice,
-- you do not seem to need it and sending another ref point
-- is shorter then having the index each time
XML Representation:
<xs:complexType name="NodeList" >
<xs:sequence minOccurs="1" maxOccurs="64">
<xs:element name="node" type="Offsets" />
</xs:sequence>
</xs:complexType>
Used By: This entry is directly used by the following 7 other data structures in this standard (record type,
descriptive name, ASN.1, and XML name (if present) of each):
DF
DF
DF
 |