 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
75 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
ASN.1 Representation:
ValidRegion ::= SEQUENCE {
direction HeadingSlice,
-- field of view over which this applies,
extent Extent OPTIONAL,
-- the spatial distance over which this
-- message applies and should be presented
-- to the driver
area CHOICE {
shapePointSet ShapePointSet,
-- A short road segment
circle Circle
-- A point and radius
}
}
XML Representation:
<xs:complexType name="ValidRegion" >
<xs:sequence>
<xs:element name="direction" type="HeadingSlice" />
<!-- field of view over which this applies, -->
<xs:element name="extent" type="Extent" minOccurs="0"/>
<!-- the spatial distance over which this
message applies and should be presented
to the driver -->
<xs:element name="area" >
<xs:complexType>
<xs:choice>
<xs:element name="shapePointSet" type="ShapePointSet" />
<!-- A short road segment -->
<xs:element name="circle" type="Circle" />
<!-- A point and radius -->
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
Used By: This entry is used directly by one other data structure in this standard, a MSG called
MSG_TravelerInformation <ASN> <XML>. In addition, this item may be used by data structures in
other ITS standards.
Remarks: Note: Be sure to copy final form to annex text.
6.46 Data Frame: DF_VehicleComputedLane
Use: A VehicleComputedLane data structure provides lane number, lane width and lane attributes within
an approach structure for a drivable motorized vehicle lane. There is at least one ReferenceLane present
and may be zero or more ComputedLane objects as well in the enclosing Approach structure. Each
ComputedLane references a ReferenceLane found in the same intersection (using the index in which it is
found?) and an offset values to map the path of the lane.
ASN.1 Representation:
VehicleComputedLane ::= SEQUENCE {
laneNumber LaneNumber,
laneWidth LaneWidth OPTIONAL,
laneAttributes VehicleLaneAttributes OPTIONAL,
-- if not present, same as ref lane
refLaneNum LaneNumber,
-- number of the ref lane to be used
-- can reuse the lane number here
-- or for we need a new type
lineOffset DrivenLineOffset,
keepOutList NodeList OPTIONAL,
-- no stop points along the path