Map builder draw it, get valid J2735
5 of 5 free decodes left today — create a free account for 500/dayHow MAP works. A MAP message describes an intersection as a reference point plus lanes; each lane is a list of nodes stored as centimeter offsets (first node from the reference point, then from the previous node). For ingress lanes the first node sits at the stop bar and the list runs away from the intersection, so vehicles can match their position to a lane as they approach. Connections (connectsTo) tie an ingress lane to the egress lane it feeds and carry the signalGroup that SPaT reports timing for. Read more: MAP guide · How MAP links to SPaT.
How TIM works. A Traveler Information Message carries an advisory, sign or work-zone notice for a geographic region over a time window. The region is an anchor point plus a path of offsets (or a circle / polygon) with a 16-bit heading mask that says which direction of travel it applies to; the content is a list of ITIS phrase codes and short text. The newer J2945/4 RSM describes a work zone in structured fields (speed limit, lane status) instead. Read more: TIM guide · MAP guide.
Corridor batches. RSUs broadcast one message per store-and-repeat row, and a long work zone or speed zone usually needs one TIM or RSM per segment of road (each path is limited to 63 nodes and a few hundred meters of useful offset range). Draw the corridor once, pick a segment length and a template, and the builder generates a numbered series with sequential packetID/msgCnt, encodes them in one call, and can push them to one or several of your RSUs. Read more: TIM guide · NTCIP 1218 push.
1Reference point not set
The intersection's reference point — usually the center of the intersection. Every lane node is measured from it. Click the button and then the map, or type coordinates.
2Lanes 0 lanes
Draw each lane from the stop bar outward. Click the first node where the lane meets the intersection (node 1, shown in yellow), then click along the lane center line away from it; double-click or press Enter to finish. J2735 orders ingress nodes away from the reference point; egress lanes start at the intersection too. Drag nodes to adjust, click a midpoint to insert, right-click a node to delete.
Lane
3Connections & signal groups 0
A connection says “traffic in ingress lane A may continue into egress lane B” and names the signalGroup whose SPaT state controls that movement. Click Add by clicking, then an ingress lane and an egress lane on the map, or pick them below.
4Intersection & message
Output MapData (messageId 18) · PSID 0xE0000017
The UPER hex is what every NTCIP 1218 RSU accepts (rsuMsgRepeatPayload / rsuMsgRepeatPayload2, bare MessageFrame, the RSU signs it). Controller and RSU vendors (Econolite, Q-Free/Intelight, Trafficware, Yunex, Commsignia, Kapsch, Danlaw) load the same hex or a GeoJSON/XML intermediate through their own tools.
↓Import an existing MAP
Paste MAP hex (bare UPER, or a WSMP/1609.2 frame) or MessageFrame JSON. The lanes are rebuilt on the map from their node offsets and become fully editable; node encodings are preserved so an unchanged lane re-encodes to the same bytes.
💾Project
1Region not drawn
Click along the road in the direction of travel; the first point is the anchor. Double-click or Enter to finish.
2Frame & content
Sign position = the anchor point.
| Lane | Closed | Offset (m) |
|---|
Output TravelerInformation (31) / RoadSafetyMessage (33) · PSID 0x8003
The UPER hex is what every NTCIP 1218 RSU accepts (rsuMsgRepeatPayload / rsuMsgRepeatPayload2, bare MessageFrame, the RSU signs it). Controller and RSU vendors (Econolite, Q-Free/Intelight, Trafficware, Yunex, Commsignia, Kapsch, Danlaw) load the same hex or a GeoJSON/XML intermediate through their own tools.
↓Import an existing TIM
Paste TIM hex or JSON; the region path is rebuilt on the map (path and circle regions) and the frame fields are filled in.
💾Project
1Corridor not drawn
Draw the corridor center line in the direction of travel, or import a GeoJSON LineString / CSV of points. The line is cut into segments; each segment becomes one message anchored at its first point.
2Message template
Batch output
| # | Message | Anchor | Nodes | Bytes | Status |
|---|
Each message is a bare UPER MessageFrame for one NTCIP 1218 store-and-repeat row. Encoding a batch costs one quota unit per 10 messages.