Study guide

2.3 SPaT and MAP Message Structure under SAE J2735

IMSA Traffic Signal Senior Field Technician Level III Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Adaptive Signal Control Technology (ASCT) & Modern Systems

1.1 ASCT Architecture & Operational Principles 1.2 Model-Based vs. Rule-Based ASCT Algorithms 1.3 ASCT Detection Layout & System Health Monitoring 1.4 Central Traffic Management Systems (ATMS) & Architecture

2 Chapter 2: Connected Vehicles (V2X), ITS Integration & Emerging Technologies

2.1 Connected Vehicle V2X Architecture & the 5.9 GHz Safety Spectrum 2.2 Roadside Unit Installation, GNSS Timing & SCMS Security 2.3 SPaT and MAP Message Structure under SAE J2735 2.4 Controller-to-RSU Interface, CV Applications & MAP Field Verification 2.5 Preemption vs. Priority and Transit Signal Priority Strategies 2.6 TSP Detection Architectures, Conditional Priority & Freight Priority 2.7 Automated Traffic Signal Performance Measures (ATSPMs)

3 Chapter 3: MUTCD Signal Warrants & Justification Studies

3.1 Traffic Studies & Engineering Data Collection 3.2 Vehicular Volume Warrants (Warrants 1, 2, and 3) 3.3 Pedestrian, School Crossing, and Network Warrants (Warrants 4, 5, and 8) 3.4 Coordinated, Crash Experience, Grade Crossing, and PHB Warrants (Warrants 6, 7, and 9)

4 Chapter 4: MUTCD Signal Equipment, Display & Visibility Standards

4.1 Signal Face Arrangements & MUTCD Lens Sizing 4.2 LED Optics, Backplates & Optical Shielding 4.3 Number of Signal Faces, the 20-Degree Placement Envelope & Sight Distance 4.4 Signal Face Mounting Heights, Lateral Offset & Distance from the Stop Line 4.5 Flashing Yellow Arrow Operation & Yellow Trap Elimination 4.6 Pedestrian Signal Displays, Countdown Modules, Interval Timing & APS 4.7 Bicycle Signal Faces & MUTCD Flashing Operation

5 Chapter 5: Advanced Traffic Detection Technologies & Configuration

5.1 Video Image Detection & Microwave Radar Detection 5.2 Thermal, Acoustic & Magnetometer Detection Technologies 5.3 Inductive Loop Physics, Geometry & Conductor Standards 5.4 Multi-Loop Arrays, Lead-In Cable & Pull-Box Splicing 5.5 Detector Testing, Tuning, Megohmmeter Diagnostics & Troubleshooting

6 Chapter 6: Traffic Communications & Fiber Optic Networks

6.1 Optical Waveguide Physics, Fiber Types & OSP Cable Construction 6.2 Optical Connectors, Polish Geometries & Redundant ITS Ring Topologies 6.3 Fiber Splicing, Optical Testing & Link Loss Budgets 6.4 Managed Industrial Ethernet in Traffic Cabinets 6.5 Copper, Twisted-Pair & Wireless Communications Media

7 Chapter 7: Actuated Phasing, Ring-Barrier Structure & Dual-Ring Operations

7.1 NEMA Dual-Ring Phasing, Barriers & Phase Compatibility 7.2 Lead-Lag Left Turns, the Yellow Trap & Signal Overlaps 7.3 Actuated Phase Parameters, Minimum Green, Passage Time & Termination 7.4 Recall Modes, Volume-Density Control & Parameter Diagnostics 7.5 Yellow Change & Red Clearance Interval Kinematics 7.6 Dilemma Zones, Pedestrian Interval Equations & a Full Field Calculation

8 Chapter 8: Coordinated Arterial Timing & Preemption Systems

8.1 Arterial Progression Principles & Actuated-Coordinated Operation 8.2 Time-Space Diagrams, Lead-Lag Sequencing & Transition Troubleshooting 8.3 Emergency Vehicle Preemption Technologies & Execution Sequence 8.4 Railroad Preemption Interconnects & Warning Time Calculations

9 Chapter 9: Electrical Codes, Grounding, Surge Protection & Power Distribution

9.1 NEC Articles, Underground Cover & Raceway Fill 9.2 Conductor Ampacity, Derating & NESC Overhead Clearances 9.3 Grounding, Bonding & Ground Resistance Testing 9.4 Transient Overvoltage, Surge Protective Devices & Cabinet Lightning Protection 9.5 Battery Backup Systems, Battery Chemistries & AC Branch Circuit Voltage Drop 9.6 Basic Electrical & Electronic Fundamentals for Signal Technicians

10 Chapter 10: NEMA TS1, TS2 & ATC Cabinet Architecture

10.1 NEMA TS1 vs. TS2 Architecture, SDLC Bus & BIUs 10.2 Malfunction Management Units (MMU) vs. Conflict Monitors (CMU) 10.3 Model 170/2070, ATC Architecture, Load Switches & Flashers

11 Chapter 11: Project Oversight, Quality Assurance, Maintenance & Troubleshooting

11.1 Civil, Raceway & Pole Construction Inspection Milestones 11.2 IMSA Cable Specifications, Cable Pulling, Acceptance Testing & As-Builts 11.3 Systematic Cabinet Troubleshooting & Diagnostic Instrumentation 11.4 Electrical Safety, Arc Flash Protection & Work Zone Traffic Control

2.3 SPaT and MAP Message Structure under SAE J2735

Key Takeaways Explain This Topic AI

SAE J2735 defines the message set; SPaT carries current phase state and time-to-change, and MAP carries the lane-level geometry the SPaT states refer to. Neither is useful without the other.

SPaT timing fields express minimum and maximum end times rather than a single countdown, because an actuated phase can gap out early or extend to max — a technician who reads them as a fixed countdown will misdiagnose a healthy broadcast.

MAP encodes approach and lane nodes as offsets from a reference point, so a MAP built from a stale or mis-georeferenced base map produces lane-level errors that no amount of controller tuning will correct.

SPaT and MAP are broadcast continuously at roughly 10 Hz, so any interruption in the controller-to-RSU data path is visible to vehicles within a fraction of a second.

Last updated: September 2026

2.3 SPaT and MAP Message Structure under SAE J2735

Note

IMSA Level III Examination Focus : Mastery of SAE J2735 message sets is essential for advanced signal technicians. You must know how the Advanced Transportation Controller (ATC) communicates with the Roadside Unit (RSU), how NEMA signal phases map to J2735 SignalGroupID values, how geometric node points define intersection approaches, and how in-vehicle safety algorithms process phase countdowns.

Connected intersection operations rely on standardized, machine-readable data streams that broadcast the physical layout and immediate operational state of traffic signals. The Society of Automotive Engineers ( SAE ) codified these data structures in the SAE J2735 Dedicated Short Range Communications (DSRC) / V2X Message Set Dictionary . Among the various messages defined in J2735, the two most critical infrastructure-generated payloads are Signal Phase and Timing (SPaT) and MAP (Intersection Geometry) .

The SAE J2735 Message Family Overview

The SAE J2735 standard establishes a shared syntactic and semantic vocabulary for all connected vehicle participants. Messages are formatted using Abstract Syntax Notation One ( ASN.1 ) and encoded using Unaligned Packed Encoding Rules ( UPER ) to minimize packet size over the air.

Message Type Full Designation Transmission Source Standard Broadcast Frequency Primary Operational Payload

SPaT Signal Phase and Timing Infrastructure (RSU) 10 Hz (100 ms) Current phase displays, interval countdowns (MinEndTime, MaxEndTime), active preempt/priority states

MAP Intersection Geometry Infrastructure (RSU) 1 Hz (1,000 ms) or on change 3D reference anchor point, approach lane centerlines, lane connections, stop bar locations, crosswalks

BSM Basic Safety Message Vehicle (OBU) 10 Hz (100 ms) Vehicle kinematics: latitude, longitude, elevation, speed, heading, acceleration, brake system status

TIM Traveler Information Message Infrastructure (RSU) Event-based / 1 Hz Dynamic speed limits, work zone warnings, road closures, curve speed advisories

PSM Personal Safety Message Vulnerable Road User 10 Hz (100 ms) Pedestrian / cyclist position, heading, velocity, device operational mode

SRM Signal Request Message Priority Vehicle (OBU) 1 to 5 Hz on approach Request for transit priority or emergency preemption (ETA, route, vehicle class)

SSM Signal Status Message Infrastructure (RSU) 1 to 2 Hz / Ack Controller status response to SRM (priority granted, queued, rejected)

SPaT Message Internal Structure & Data Elements

The SPaT message describes the real-time operational status of every signal phase and crosswalk movement associated with an intersection. It answers the question: "What color is each movement displaying right now, and when is it expected to change?" +-----------------------------------------------------------------------------+

  • | SPaT MESSAGE ASN.1 HIERARCHICAL TREE |
  • +-----------------------------------------------------------------------------+
  • | SPaT (Root) |
  • | └── intersections: IntersectionStateList |
  • | └── IntersectionState |
  • | ├── id: IntersectionReferenceID (Region ID + Intersection ID) |
  • | ├── revision: MsgCount (0 - 127 roll-over counter) |
  • | ├── status: IntersectionStatusObject |
  • | | ├── manualControlIsEnabled |
  • | | ├── stopTimeIsActivated |
  • | | ├── failureFlash / conflictFlash |
  • | | └── preemptIsActive / tspIsActive |
  • | ├── moy: MinuteOfTheYear (0 - 527,040) |
  • | ├── timeStamp: DSecond (0 - 59,999 milliseconds in the minute) |
  • | └── states: MovementList |
  • | └── MovementState (Repeated for each NEMA Phase/Overlap) |
  • | ├── movementName: Descriptive Text |
  • | ├── signalGroup: SignalGroupID (1 - 255) |
  • | └── state-time-speed: MovementEventList |
  • | └── MovementEvent |
  • | ├── eventState: MovementPhaseState |
  • | └── timing: TimeChangeDetails |
  • | ├── minEndTime: TimeMark |
  • | ├── maxEndTime: TimeMark |
  • | ├── likelyTime: TimeMark |
  • | └── confidence: TimeIntervalConfidence |
  • +-----------------------------------------------------------------------------+
  • Critical SPaT Data Fields

IntersectionReferenceID : Uniquely identifies the physical intersection across regional networks using a combination of a 16-bit RoadRegulatorID (jurisdiction) and a 16-bit IntersectionID .

IntersectionStatusObject : A 16-bit bitmap reporting real-time cabinet status flags, including whether the intersection is running under time-of-day coordination, manual police control, preemption override, or MMU conflict flash.

SignalGroupID : An 8-bit integer (1 to 255) representing a distinct signalized movement. In standard North American deployments, SignalGroup IDs 1 through 8 map directly to standard NEMA TS2 Phases 1 through 8 , while IDs 9 through 16 designate pedestrian phases or phase overlaps (e.g., SignalGroup 10 = Phase 2 Pedestrian; SignalGroup 14 = Overlap A).

MovementPhaseState : An enumeration defining the exact instantaneous optical display:

protected-Movement-Allowed : Solid Green ball or arrow.

movement-Clearance : Solid Yellow change interval.

stop-And-Remain : Solid Red display.

permissive-Movement-Allowed : Flashing Yellow Arrow (FYA) or permissive green ball with yielding rules.

caution-Conflicting-Traffic : Yellow flashing operation.

The Mechanics of SPaT Timing Parameters

The timing block within each MovementEvent provides the critical predictive countdown values, encoded as a TimeMark in units of tenths of a second (100 ms) from the top of the current hour (0 to 35,999 tenths of a second): Current Hour Second = TimeMark 10 \text{Current Hour Second} = \frac{\text{TimeMark}}{10} Current Hour Second = 10 TimeMark ​

MinEndTime : The earliest possible time at which the current phase state can terminate. For a green phase, this represents the expiration of the programmed Minimum Green plus any active pedestrian service intervals. For a yellow phase, it represents the exact end of the fixed yellow change clearance.

MaxEndTime : The latest possible time at which the current phase state can terminate under continuous vehicle extension. In actuated operations, this correlates to the phase Maximum Green (Max 1 or Max 2) or the coordination Force-Off point .

LikelyTime : An advanced controller-generated prediction of when the phase will terminate based on historical gap-out behavior, volume-density settings, or adaptive progression algorithms.

Confidence : A statistical probability score (0 to 15 scale) reflecting how reliably the controller expects the phase to terminate at the LikelyTime .

MAP Message Internal Structure & Geometric Modeling

While SPaT describes dynamic signal timing, the MAP message provides the static physical canvas upon which those timing displays operate. A vehicle cannot interpret a SPaT message without having the intersection's MAP message loaded into memory. +-----------------------------------------------------------------------------+

  • | MAP MESSAGE GEOMETRIC TOPOLOGY |
  • +-----------------------------------------------------------------------------+
  • | |
  • | Approach 1 (Ingress) Approach 2 (Egress) |
  • | [Lane 1: Left Turn] ──> ConnectsTo (SignalGroup 1) ──> [Lane 20] |
  • | [Lane 2: Thru Lane] ──> ConnectsTo (SignalGroup 2) ──> [Lane 21] |
  • | [Lane 3: Right Turn] ──> ConnectsTo (SignalGroup 2) ──> [Lane 22] |
  • | |
  • | \ Stop Line Bar / |
  • | \======================================================/ |
  • | \ / |
  • | \ (Intersection Reference Point) / |
  • | \ Anchor: Lat / Long / Elev / |
  • | \ (+) / |
  • | \ / |
  • | \===========================================/ |
  • | Pedestrian Crosswalk |
  • | (SignalGroup 10) |
  • +-----------------------------------------------------------------------------+
  • Core MAP Data Components

Intersection Reference Point (Anchor Point) : The geodetic focal point of the intersection, defined using the WGS-84 coordinate reference system . Latitude and longitude are specified to a resolution of one-tenth of a microdegree (0.0000001°) , providing a horizontal geographic precision of approximately 1.1 centimeters . Elevation is defined with a precision of 10 centimeters above sea level.

Approach & Lane Definitions : Roadways entering the intersection are designated as Ingress Approaches , while departing roadways are Egress Approaches . Each travel path within an approach is assigned a unique 8-bit LaneID (1 to 255).

Lane Nodes and Delta Offsets : Rather than storing full 64-bit geographic coordinates for every point along a lane, MAP messages define lanes using a series of sequential Node Offsets relative to the previous node. Each node contains delta offsets: ( Δ X , Δ Y , Δ Z ) (\Delta X, \Delta Y, \Delta Z) ( Δ X , Δ Y , Δ Z ) specified in centimeters. This vector string forms the precise 3D centerline and curvature of each travel lane.

Stop Line Bar Coordinates : The final node of an ingress lane vector defines the physical location of the pavement stop bar.

ConnectsTo & Maneuvers : This is the critical functional link between MAP and SPaT. The ConnectsTo data block defines:

Which egress lane can be reached from this ingress lane.

The permitted maneuver ( maneuverStraightAllowed , maneuverLeftAllowed , maneuverRightAllowed , maneuverUTurnAllowed ).

The specific SignalGroupID governing that turning path .