Navigation bar
  Print document Start Previous page
 65 of 240 
Next page End  

SAE J2735-Draft-Rev26 [issued: 09-18-08] 
-
65 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
   vehicleCount  INTEGER (0..60000) OPTIONAL, 
   pedDetect     PedestrianDetect  OPTIONAL,
                 -- true if ANY ped are detected crossing 
                 -- the above lanes
   pedCount      INTEGER (0..60000) OPTIONAL,  
                 -- est count of peds
   ... -- # LOCAL_CONTENT
   }
XML Representation:
<xs:complexType name="MovementState" >
      <xs:sequence>
         <!-- The MovementNumber is contained in the enclosing DF. -->
         <xs:element name="movementName" type="DescriptiveName"  minOccurs="0"/>
         <!-- uniquely defines movement by nzame -->
         <xs:element name="laneCnt"  minOccurs="0">
            <xs:simpleType>
               <xs:restriction base="xs:unsignedByte">
                  <xs:minInclusive value="1"/>
               </xs:restriction>
            </xs:simpleType>
         </xs:element>
         <!-- the number of lanes to follow -->
         <xs:element name="laneSet" >
            <xs:simpleContent>
               <xs:extension base="laneSet-string" >
                  <xs:attribute name="EncodingType" use="required">
                    <xs:simpleType>
                       <xs:restriction base="xs:NMTOKEN">
                          <xs:enumeration value="base64Binary"/>
                       </xs:restriction>
                    </xs:simpleType>
                  </xs:attribute>
               </xs:extension>
            </xs:simpleContent>
         </xs:element>
         <xs:simpleType name="laneSet-string">
            <xs:restriction base="xs:base64Binary">
               <xs:minLength value="2"/>
               <xs:maxLength value="170"/>
            </xs:restriction>
         </xs:simpleType >
         <!-- each encoded as a: LaneNumber,
         the collection of lanes,  by num,
         to which this state data applies
         For the current movement State,  you may CHOICE one of the below: -->
         <xs:element name="currState" type="SignalLightState"  minOccurs="0"/>
         <!-- the state of a Motorised lane -->
         <xs:element name="pedState" type="PedestrianSignalState"  minOccurs="0"/>
         <!-- the state of a Pedestrian type lane -->
         <xs:element name="specialState" type="SpecialSignalState"  minOccurs="0"/>
         <!-- the state of a special type lane
         such as a deadicatd train lane -->
         <xs:element name="timeToChange" type="TimeToChange" />
         <!-- Roy suggests abs. time here to avoid latency issues
         and not using a time-to-live value,
         we could put out one UTC time,  then offset from it?
         Damlr still wants count-down timers,  so kept as is
         untill this is settled for good. -->
         <xs:element name="stateConfidence" type="StateConfidence"  minOccurs="0"/>
         <!-- Yellow phase time intervals
         (used for motorised vehicle lanes and pedestrian lanes)
         For the yellow Signal State,  you may CHOICE one of the below: -->
         <xs:element name="yellState" type="SignalLightState"  minOccurs="0"/>
         <!-- the next state of a
         Motorised lane -->
         <xs:element name="yellPedState" type="PedestrianSignalState"  minOccurs="0"/>
         <!-- the next state of a
         Pedestrian type lane -->
Click to Convert - Powerful PDF Converter and HTML Converter.