 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
108 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
note that above may be combined
to create additonal patterns
</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:unsignedInt">
<xs:minInclusive value="0"/>
<xs:maxInclusive value="12"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="dark"/>
<xs:enumeration value="green"/>
<xs:enumeration value="green flashing"/>
<xs:enumeration value="yellow"/>
<xs:enumeration value="yellow flashing"/>
<xs:enumeration value="red"/>
<xs:enumeration value="red flashing"/>
</xs:restriction>
</xs:simpleType >
</xs:union>
</xs:simpleType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Used inside the SignalState data value for each direction supported. Note that because multiple
lights can in illuminated at the same time under odd conditions, this is supported.
7.27 Data Element: DE_CrosswalkLaneAttributes
Use: The CrosswalkLaneAttributes data element relates the type of cross walk that is being described. The
term cross walk lane in this standard is generic and may include such items as a bicycle crossings and other
non-motorized uses.
ASN.1 Representation:
CrosswalkLaneAttributes ::= ENUMERATED {
noData (0), -- ('0000000000000000'B)
twoWayPath (1), -- ('0000000000000001'B)
pedestrianCrosswalk (2), -- ('0000000000000010'B)
bikeLane (4), -- ('0000000000000100'B)
railRoadTrackPresent (8), -- ('0000000000001000'B)
missing1 (16), -- ('0000000000010000'B)
pedestrianCrosswalkTypeA (32), -- ('0000000000100000'B)
pedestrianCrosswalkTypeB (64), -- ('0000000001000000'B)
pedestrianCrosswalkTypeC (128) -- ('0000000010000000'B)
} -- 1 byte
-- MUTCD provides no real "types" to use here
XML Representation:
<xs:simpleType name="CrosswalkLaneAttributes" >
<xs:annotation>
<xs:appinfo>
noData (0) -- ('0000000000000000'B)
twoWayPath (1) -- ('0000000000000001'B)
pedestrianCrosswalk (2) -- ('0000000000000010'B)
bikeLane (4) -- ('0000000000000100'B)
railRoadTrackPresent (8) -- ('0000000000001000'B)
missing1 (16) -- ('0000000000010000'B)
pedestrianCrosswalkTypeA (32) -- ('0000000000100000'B)
pedestrianCrosswalkTypeB (64) -- ('0000000001000000'B)
pedestrianCrosswalkTypeC (128) -- ('0000000010000000'B)
</xs:appinfo>
<xs:documentation>
1 byte
MUTCD provides no real &quot;types&quot; to use here