 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev18 [issued: 06-26-07]
-
55 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
laneWidth LaneWidth OPTIONAL,
laneAttributes LaneAttributes,
nodeList NodeList,
...
}
XML Representation:
<xs:complexType name="ReferenceLane" >
<xs:sequence>
<xs:element name="laneNumber" type="LaneNumber" />
<xs:element name="laneWidth" type="LaneWidth" minOccurs="0"/>
<xs:element name="laneAttributes" type="LaneAttributes" />
<xs:element name="nodeList" type="NodeList" />
</xs:sequence>
</xs:complexType>
Used by: This entry is used directly by one other data structure in this standard, a DF called DF_Approach
6.27 Data Frame: DF_ReferencePoint
Use: A data concept which provides a definitive and precise location in the WSG-84 coordinate systems
from which short offsets are then used to create additional data using a flat earth geonimc (sp?) project
centered from this point.. Typically used in the description of maps and intersections. .
ASN.1 Representation:
ReferencePoint ::= SEQUENCE {
-- pos PositionLocal3D,
lat Latitude, -- 4 bytes (1/8th micro degrees)
long Longitude, -- 4 bytes
elev Elevation OPTIONAL, -- 3 bytes
...
XML Representation:
<xs:complexType name="ReferencePoint" >
<xs:sequence>
<!-- pos PositionLocal3D, -->
<xs:element name="lat" type="Latitude" />
<!-- 4 bytes (1/8th micro degrees) -->
<xs:element name="long" type="Longitude" />
<!-- 4 bytes -->
<xs:element name="elev" type="Elevation" minOccurs="0"/>
<!-- 3 bytes -->
</xs:sequence>
</xs:complexType>
Used by: This entry is directly used by the following 2 other data structures in this standard (record type,
descriptive name, ASN.1, and XML name (if present) of each):
DF
<XML>, and
DF
In addition, this item may be used by data structures in other ITS standards.
Remarks: In use, all subsequent offset value are added to this point in order to determine the absolute
position to be described. In some data structures more than once ReferencePoint may be present. Data
values are interrupted in a stream fashion. That is, until a new ReferencePoint is read, the value for the last
one is used as the basis for all offset values found the same structure.
DEBATE: The elevation invented by Michael Peredo is 2 bytes long (ours is currently 3 bytes) and better,
we should drop the current DSRC on and use this one. I have left the 3 byte value here for now. Also by
encoding this as structure, we pay for two more bytes, we may just want it inserted each time as discrete