 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
62 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
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
<XML>, and
DF
<XML>, and
DF
<XML>, and
DF
<XML>, and
DF
<XML>, and
DF
<XML>, and
DF
In addition, this item may be used by data structures in other ITS standards.
Remarks: When describing a path, the first node is the one closest to the intersection for the lane or the
beginning point in a roadway segment. Typically, this is located on the stop line for approaches. Safety
applications can use this to identify their stop line without having to consult the Intersection Message. For
egresses, the first node indicates where the lane begins.
When the node list used to describe "non stopping areas" in a path (such as a stripped do not block area or a
railroad crossing) then the offsets are taken in paired sets. The first offset provides the start of the area to
be avoided, while the 2nd offset provides the end of that area. The path is presumed to follow the same
linear path described by the node list for the lane.
Subsequent nodes provide points further and further away along the lane's driven line. Include as many as
necessary to characterize lane curvature "within tolerance."
6.29 Data Frame: DF_Offsets
Use: The Offsets data structure provides one set of of signed offset values for determining the Xs and Ys
(and, possibly Zs when present) using the then current ReferencePoint and NodeConfih objects to build a
single point in a path for the enclosing ReferenceLane relating to a lane in the current intersection.
ASN.1 Representation:
Offsets ::= SEQUENCE {
xOffset INTEGER (-32767..32767),
yOffset INTEGER (-32767..32767),
zOffset INTEGER (-32767..32767) OPTIONAL,
width LaneWidth OPTIONAL
-- all in signed values where