Navigation bar
  Print document Start Previous page
 55 of 303 
Next page End  

SAE J2735-Draft-Rev29 [issued: 12-11-08] 
-
55 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
               ApproachObject,      
                                  -- data about one or more approaches 
                                  -- (lane data is found here)
   preemptZones SEQUENCE (SIZE(1..32)) OF 
               SignalControlZone OPTIONAL, 
                                  -- data about one or more
                                  -- preempt zones 
   priorityZones SEQUENCE (SIZE(1..32)) OF 
               SignalControlZone OPTIONAL,    
                                  -- data about one or more 
                                  -- priority zones
   ... 
   }
XML Representation:
<xs:complexType name="Intersection" >
      <xs:sequence>
         <xs:element name="name" type="DescriptiveName"  minOccurs="0"/>
         <xs:element name="id" type="IntersectionID" />
         <!-- a gloablly unique value,
         the upper bytes of which may not
         be sent if the context is known -->
         <xs:element name="refPoint" type="ReferencePoint"  minOccurs="0"/>
         <!-- the reference from which subsequent
         data points are offset untill a new
         point is used. -->
         <xs:element name="refInterNum" type="IntersectionID"  minOccurs="0"/>
         <!-- present only if this is a computed
         intersection instance -->
         <xs:element name="orientation" type="Heading"  minOccurs="0"/>
         <!-- present only if this is a computed
         intersection instance -->
         <xs:element name="laneWidth" type="LaneWidth"  minOccurs="0"/>
         <!-- reference width used by subsequent
         lanes until a new width is given -->
         <xs:element name="type" type="IntersectionStatusObject"  minOccurs="0"/>
         <!-- data about the intersection type -->
         <xs:element name="approaches" >
            <xs:complexType>
               <xs:sequence minOccurs="1" maxOccurs="32">
                  <xs:element name="approache" type="ApproachObject" />
                  <!-- data about one or more approaches (lane data is found here) -->
               </xs:sequence>
            </xs:complexType>
         </xs:element>
         <xs:element name="preemptZones"  minOccurs="0">
            <xs:complexType>
               <xs:sequence minOccurs="1" maxOccurs="32">
                  <xs:element name="preemptZone" type="SignalControlZone" />
                  <!-- data about one or more preempt zones -->
               </xs:sequence>
            </xs:complexType>
         </xs:element>
         <xs:element name="priorityZones"  minOccurs="0">
            <xs:complexType>
               <xs:sequence minOccurs="1" maxOccurs="32">
                  <xs:element name="priorityZone" type="SignalControlZone" />
                  <!-- data about one or more priority zones -->
               </xs:sequence>
            </xs:complexType>
         </xs:element>
      </xs:sequence>
</xs:complexType>
In addition, this item may be used by data structures in other ITS standards.
Remarks: Note that refInterNum and orientation are only present when a computed intersection is being
described (a concept similar to a computed  vehicle lane).  The preemptZones and priorityZones are used to
relate signal preempt and priority zones to specific request values.