How Traffic Lights Coordinate an Intersection

TL;DR. A red light that flips to green the instant you reach it, or a red held for cross traffic that never shows up, both feel like coincidences. Neither is one. Buried in the pavement or mounted overhead is a sensor reporting to a small computer in a roadside cabinet, running a timing plan a traffic engineer wrote after studying that specific intersection, coordinated with the signals up and down the street so a driver going the speed limit can ride a "green wave" for miles. The first electric signal went up in Cleveland in 1914; the three-position signal most of the world now takes for granted came from a Black inventor's 1923 patent, sold for less than it was worth. Today the United States runs somewhere around 300,000 of these intersections, most of them still built on a legal default so simple it predates computers entirely: if the light goes dark, everyone stops.

Key takeaways

  • Traffic signals run on one of two logics: fixed-time control, which cycles through the same timing regardless of traffic, and actuated control, which uses in-pavement loop detectors or overhead cameras and radar to extend or skip a green based on who is actually there.
  • Adjacent intersections are deliberately synchronized into a "green wave," a timed offset between signals that lets a driver holding a steady speed hit consecutive greens along a corridor, planned by traffic engineers using studies of real traffic counts.
  • The world's first electric traffic signal went up in Cleveland, Ohio, in 1914, using a design patented by James Hoge. Garrett Morgan, a Black inventor in the same city, patented a real improvement in 1923: a third, intermediate position (function, not color, though it became the ancestor of today's yellow light) that cleared the intersection before cross traffic moved. He did not invent the traffic light itself.
  • Two federal frameworks make the system interoperable: the Manual on Uniform Traffic Control Devices (MUTCD) sets the rules for what signals look like and how they behave, and NTCIP, a communications standard, lets traffic controllers from different manufacturers talk to the same city network. Separately, federal accessibility rules increasingly require audible and vibrating pedestrian signals at new and rebuilt crossings.
  • In most U.S. states, a traffic signal that loses power or goes dark is, by law, an all-way stop, the same rule that would apply if the signal had never been installed. Battery backup exists at some intersections specifically to avoid ever reaching that state.
  • Red-light-running crashes killed more than 1,100 people in the U.S. in a recent year, and researchers have separately demonstrated that older networked signal systems can be remotely hijacked, not through anything exotic but through unencrypted radios and default passwords.

The moment nobody thinks about

You're the only car at the intersection. No cross traffic, no pedestrians, no reason for the light to be red except that it is, and you sit there anyway, watching an empty road, waiting for a number to run out somewhere you can't see. Or the opposite happens: you roll up to a light that turns green in the same second your front bumper crosses some invisible line, as if it had been waiting for you specifically. Both moments feel arbitrary, and both are proof that a real decision was made. Somewhere nearby, in a gray metal box about the size of a refrigerator, a controller is running a program written by a person who studied this exact intersection, counted the cars that pass through it, and decided exactly how long you would wait and why.

This is the first chapter of a different kind of hidden system than the ones before it. Food and water arrive to be consumed and disappear. A traffic signal is different: it's infrastructure you interact with dozens of times a week, that decides nothing about what you get, only when you're allowed to move, and it does that job so consistently that most people have never once asked how it decides.

The mechanism: what a light is actually deciding

Every signalized intersection runs on a controller, a specialized computer housed in a cabinet at the corner, and everything the lights above your head do traces back to a program running inside that box. The simplest version is fixed-time control: the signal cycles through the same sequence of red, yellow, and green intervals, in the same order, for the same duration, all day, regardless of how many cars are actually present. It's cheap, it requires no sensors, and it guarantees a predictable, regular gap in traffic for pedestrians and cross streets, which is part of why cities still use it on dense downtown grids where nearly every approach has cars most of the time anyway.

Actuated control is the more common approach at suburban and lower-volume intersections, and it's the reason a red light with no cross traffic in sight still sometimes makes you wait: the detector serving that direction hasn't seen you yet, or it has, and the signal is still finishing a minimum interval it's legally required to hold. The classic detector is an inductive loop, a coil of wire cut into a shallow slot in the pavement and sealed over; a car parked or rolling over it slightly disturbs the coil's electromagnetic field, and the change registers at the controller as a vehicle present at that approach. Newer intersections increasingly use overhead video cameras or radar units instead, which do the same job (report presence, count vehicles, sometimes classify them) without cutting into the asphalt or needing repair every time a utility crew digs up the street. An actuated controller uses those inputs to extend a green for a lane that's still filling with cars, cut a green short once traffic clears, or skip a phase entirely if no one ever calls for it.

The unit of work at any signal is a phase: one non-conflicting set of movements (through traffic on the main street, say, or a protected left turn) that gets the right-of-way at the same time. A cycle is one full pass through every phase at an intersection, and cycle length is how long that whole loop takes, commonly somewhere between 60 and 120 seconds at a typical signal, longer at busier ones. Controllers organize phases using a "ring and barrier" structure: certain phases are grouped so they can run in parallel without conflicting (opposing through movements, for instance), while a "barrier" separates groups of phases that must never be green at once (a north-south through movement and an east-west through movement). None of this is visible from the driver's seat, but it's the actual logic being executed every time the light changes.

Pedestrians get their own half of this system: a signal head, usually showing a walking figure and an upraised hand, that runs on the same phase and cycle logic as the vehicle signals, plus, at many corners, a pedestrian push button that either calls a walk phase that wouldn't otherwise run or simply confirms that a pedestrian is present and ready. Newer or retrofitted crossings increasingly include accessible pedestrian signals (APS), which add audible tones and a vibrating arrow on the push button housing so a person who is blind or has low vision can tell, without seeing the display at all, when the walk interval starts and which direction it covers.

Don't be confused: "actuated" is not the same thing as "smart." An actuated signal only reacts to what's happening at its own corner, extending or skipping its own phases based on its own detectors. It has no idea what's happening at the next intersection, let alone across the city. A signal using adaptive control, covered later in this chapter, is a different and considerably newer category: a system that continuously recalculates timing for a whole corridor or network based on real-time conditions everywhere in it, not just the corner it sits on.

The complete journey: one signal becomes a corridor

A single intersection's controller only has to solve its own local problem, but a city's traffic doesn't move corner by corner, it moves along streets, and that's the reason most drivers experience traffic signals as a system in the first place, whether they can articulate it or not: hit one green light on a major road and, if you hold roughly the speed limit, the next few lights turn green just as you arrive too.

That effect, commonly called a green wave, isn't luck. Traffic engineers set each signal along the corridor to turn green at a specific time offset from a shared master clock, and that offset is calculated directly from the travel time between intersections at a chosen progression speed (often set at or slightly under the posted limit, not the speed most drivers actually drive). A platoon of cars leaving one green light arrives at the next intersection just as its own green begins, and the effect repeats down the line for as many signals as the coordination plan covers. This kind of signal timing work is done using traffic studies: engineers count vehicles by direction and time of day, sometimes over multiple days, and use that data to set cycle lengths, offsets, and the split of green time between competing approaches. Designed well, it measurably reduces stops, delay, and fuel use; agencies that have gone through and retimed aging signal plans have documented double-digit percentage drops in travel time and delay on the corridors involved.

Above the level of any one corridor sits a traffic management center (TMC), a facility, often shared across an entire city or region, where operators watch live camera feeds and real-time signal data from hundreds or thousands of intersections at once. A TMC can retime a corridor for a football game or a parade, clear a green-light path ahead of an ambulance or a VIP motorcade, or manually override a stuck signal reported by a driver before a technician ever reaches the site. It's the layer where "one intersection" becomes "one city's traffic," and it's staffed continuously in most major metro areas precisely because traffic conditions change faster than any fixed timing plan can fully anticipate.

Who keeps it running

A traffic light is not a fixture, it's a small department's worth of ongoing work. Traffic engineers design the timing plans in the first place, running the vehicle counts and delay studies that decide cycle length, phase order, and how a corridor's signals should be offset from one another, and revisiting those plans as development changes what an intersection actually sees. Signal technicians are the people who physically keep the hardware alive: replacing failed bulbs or LED modules, recalibrating detectors that have drifted out of adjustment, splicing wiring damaged by utility work or a crash, and responding, often at odd hours, when a signal reported as "dark" or "flashing" turns out to need someone standing in the intersection with a laptop plugged into the cabinet. TMC operators watch the citywide picture and adjust in real time. And when a signal fails outright, often it's a police officer or a public works crew who arrives first, not to fix the electronics but to physically direct traffic through the intersection until a technician restores it, standing in for the exact function the signal itself normally performs.

That last detail points at a legal fact most drivers never learn until they need it: in most U.S. states, a traffic signal that is dark, unlit on every approach, or stuck flashing an ambiguous signal is, by statute, to be treated as an all-way stop. Washington State's law is typical: when a signal has lost power entirely or isn't displaying red, yellow, or green on any approach, drivers must treat the intersection as if stop signs controlled every direction. New York and Michigan have equivalent rules. It's a rule that predates the electronics it now applies to: it's simply what the law would already require if the signal had never been built there, and it's the reason officers direct traffic at a dead intersection rather than waiting, because until the signal is restored, that four-way-stop default is the only legal right-of-way rule in force.

Where this came from

Before any of this existed, intersections in growing early-20th-century cities were controlled by police officers standing on raised platforms, manually waving traffic through with hand signals or a simple two-color paddle, a solution that worked only as long as a trained person was physically present at every busy corner around the clock.

The first fix was electric but still simple. On August 5, 1914, the intersection of Euclid Avenue and East 105th Street in Cleveland, Ohio, got what's credited as the world's first electric traffic signal, four pairs of red and green lights, one at each corner, based on a design patented by James Hoge. A police officer in a nearby booth threw a manual switch to change the lights, and the system was wired so that conflicting greens (two directions moving at once) were physically impossible to select, an improvement over an officer's judgment alone. It even included a buzzer to warn drivers a change was coming.

What that 1914 system still lacked was a way to clear cars already inside the intersection before opposing traffic got the green. That gap is where Garrett Morgan enters the story, and it deserves to be told accurately rather than flattened into "the man who invented the traffic light," a claim that overstates his actual contribution and undersells what it really was. Morgan was born in Kentucky in 1877 to formerly enslaved parents, moved to Cleveland as a young man, and built a career and a business as a self-taught inventor with no formal engineering education, first in sewing-machine repair, later in safety equipment: in 1916, he used a smoke hood of his own design to help rescue survivors trapped after an explosion in a water-intake tunnel beneath Lake Erie. In 1923, the U.S. Patent Office granted him patent 1,475,024 for a three-position traffic signal. Electric signals already existed by then, including Hoge's; what didn't exist in most of them was a true intermediate position, and Morgan's design added exactly that, a hand-cranked signal that could hold all directions of traffic stopped at once before releasing any single direction, giving vehicles already inside the intersection time to clear it. That intermediate function is the direct ancestor of the modern yellow light. Morgan sold the rights to General Electric for $40,000 (well over half a million dollars today), a real sale of a real, useful patent, though one that also meant he never captured the patent's long-term value once GE incorporated the idea into the electric signals that followed.

Don't be confused: Garrett Morgan improved the traffic signal, he didn't invent it. Manually switched electric signals, including Hoge's Cleveland installation, predate Morgan's patent by nearly a decade, and other inventors were experimenting with three-position designs around the same period. What Morgan actually holds, cleanly and verifiably, is a 1923 U.S. patent for a specific, working three-position mechanism that solved a real safety problem: clearing an intersection before opposing traffic entered it. That's a genuine and underappreciated contribution on its own. It doesn't need the inflated version of the story to matter.

Pedestrian-specific signals came later, emerging through the 1930s as cities experimented with dedicated "walk" indications alongside vehicle lights, and were gradually formalized into the same national manual that governs vehicle signals today. The bigger structural leap came decades after that: in June 1963, Toronto brought online what's credited as the world's first full-scale, real-time computer traffic control system, using a general purpose digital computer to take input from vehicle detectors across a network of signals and adjust timing automatically rather than through manual switches or standalone mechanical timers. That's the direct ancestor of every coordinated, computer-managed signal network running today, including the green waves and traffic management centers described above.

Standards and coordination that make it interoperable

None of this works as a system unless every agency, contractor, and equipment manufacturer building a piece of it agrees on the same rules. In the United States, that document is the Manual on Uniform Traffic Control Devices (MUTCD), issued by the Federal Highway Administration. It specifies what colors and shapes a signal must use, how signals must be timed and sequenced, where and how pedestrian signals and push buttons must be installed, and dozens of other details, and by federal law it applies to every public road open to travel, not just federal highways. Without it, a red light in one state could mean something subtly different from a red light in another.

A second, less visible standard solves a different problem: getting equipment from competing manufacturers to speak the same language. NTCIP, the National Transportation Communications for Intelligent Transportation System Protocol, is a family of communication standards that lets a traffic management center run signal controllers, message signs, and sensors built by entirely different companies as one coordinated network, rather than locking a city into a single vendor's proprietary system for the life of every controller it ever buys.

A third layer covers accessibility rather than traffic behavior. The Public Right-of-Way Accessibility Guidelines (PROWAG), finalized by the U.S. Access Board in 2023 under the authority of the Americans with Disabilities Act, require that accessible pedestrian signals, audible tones and a vibrating arrow, be installed at every new or substantially altered signalized crossing, closing a long gap in which a sighted pedestrian and a blind pedestrian effectively had access to different amounts of information at the same intersection.

Keeping it working

Maintenance here is a mix of small routine tasks and periodic, bigger overhauls. Signal indications have moved almost entirely from incandescent bulbs to LEDs, which last far longer, use a fraction of the electricity, and (a real if counterintuitive downside) produce so little waste heat that in heavy snow some LED signal heads can no longer melt accumulating snow off their own lenses the way old incandescent bulbs incidentally did, occasionally requiring a separate fix. Loop detectors and cameras need periodic calibration, since a loop that's drifted out of tune can miss a motorcycle or a bicycle entirely, and a camera detector can be thrown off by glare, shadows, or a repaving project that changes lane positions. Controller firmware gets software updates the same way any networked computer does, and cities are expected to revisit and retime signal timing plans on some kind of regular schedule (a few years is a common interval), since traffic patterns shift as neighborhoods grow, businesses open and close, and driving habits change.

Backup power is its own maintenance category. Many, though not all, intersections have a battery backup system, a bank of batteries in or near the cabinet that keeps the signal running for several hours after a power outage rather than going dark immediately. Agencies typically prioritize which intersections get this equipment based on traffic volume, history of frequent local outages, and whether the intersection sits on a route to a hospital or other critical facility, since backup batteries and the LED indications they're paired with cost real money per intersection and can't be installed everywhere at once.

When it breaks

The most common failure is mundane and brief: a storm, a car striking a signal pole, or a routine utility outage knocks out power, and the intersection goes dark until either backup batteries kick in or a crew restores power and, if needed, physically resets the controller. This is exactly the everyday scenario the all-way-stop default exists for, and it's why officers or public works crews sometimes stand in an intersection directing traffic by hand, the same job Cleveland's officer performed from a control booth in 1914, just without the switch.

The more unsettling failure mode is digital. In 2014, computer science researchers at the University of Michigan, working with permission from a Michigan road agency, examined a networked traffic signal system controlling nearly 100 intersections and found it vulnerable in almost the simplest ways possible: the wireless radios linking controllers together sent data unencrypted, the controllers still used default factory usernames and passwords, and a debug port inside the roadside cabinet was physically reachable by anyone who could open the box. Using those three weaknesses together, the team demonstrated they could take control of the signals across the whole tested network, an outcome they engineered carefully to avoid any actual danger to drivers, and published as a direct warning that "connected" traffic infrastructure was being deployed faster than it was being secured. It remains one of the clearest documented demonstrations that a traffic signal network's weakest link is rarely the signal itself.

Separate from any hacking, the more routine and far deadlier failure is human: drivers running red lights. In a recent year, red-light-running crashes killed more than 1,100 people in the United States and injured over 140,000 more, and roughly half of those killed weren't the driver who ran the light at all, they were passengers, pedestrians, cyclists, or occupants of the vehicle that got hit. Automated red-light camera enforcement measurably reduces this: studies have found double-digit percentage drops in fatal red-light-running crashes in cities that run camera programs, and a documented rise in the same crash rate in cities that later shut their programs down, even though camera programs themselves have become politically contested and many U.S. communities have discontinued them in recent years over cost, enforcement, and public-acceptance concerns.

The scale of it

Estimates vary by methodology and year, but the United States operates somewhere in the range of 300,000 signalized intersections, a 2026 nationwide inventory effort puts the figure at just over 303,000, while other federal and academic counts in recent years have landed anywhere from roughly 270,000 to 330,000. Whichever exact number you take, it implies an enormous, continuously running, mostly invisible layer of computing and human oversight: hundreds of thousands of controllers each executing a locally tailored timing plan, feeding data up to traffic management centers that, in a large city, may be watching camera feeds and signal status from more than a thousand intersections simultaneously, and a workforce of engineers and technicians revisiting those plans on an ongoing cycle rather than setting them once and walking away.

Trade-offs and what's next

The clearest frontier is adaptive signal control, systems like SCOOT and SCATS (each running in hundreds of cities worldwide) that go a step beyond actuated control by continuously recalculating timing across a whole network based on real-time traffic data, rather than reacting only at a single intersection or following a timing plan set months earlier. Where it's been deployed well, adaptive control has shown meaningful reductions in delay compared to fixed or simply actuated signals, though it's also more expensive to install and maintain, and it depends on the same sensors and networked communication that made the 2014 Michigan vulnerabilities possible in the first place, which is why security has become as central to newer deployments as raw performance.

A related push is connected vehicle technology, or vehicle-to-infrastructure (V2I) communication, in which a signal broadcasts its current and upcoming timing directly to equipped vehicles, letting a car warn its driver that a green is about to end or, eventually, adjust its own speed to arrive on a green rather than a red. It depends on a large enough share of vehicles on the road actually carrying the equipment to be worth building for, which is part of why it remains a pilot-scale technology in most of the country rather than a default feature of daily driving.

Inside individual intersections, one of the more contested design choices is whether a left turn gets its own protected phase (a dedicated arrow, no oncoming traffic to watch for) or a permissive one, where turning drivers must find their own gap in oncoming traffic. Protected phases measurably reduce left-turn and pedestrian crashes at a given corner, but they add time to the cycle, which takes green time away from other movements and can make overall delay worse; research on real intersections has found the safety picture more mixed than either side of the debate usually claims; a bit of one crash type goes down, a different one can rise elsewhere in the same intersection. Traffic engineers weigh that trade-off corner by corner rather than applying one rule everywhere, based on turning volumes, crash history, and how much pedestrian traffic the crossing actually carries.

Further out, autonomous vehicles raise a stranger question than "can a computer drive," namely whether an intersection full of self-driving cars still needs a traffic light aimed at humans at all. Researchers have proposed adding a fourth signal color, sometimes called a "white phase," that would activate only once enough connected autonomous vehicles are approaching an intersection, telling human drivers simply to follow the car ahead of them while the vehicles themselves negotiate the crossing directly with each other. It's still a research proposal rather than deployed technology, but it points at a real long-term possibility: a traffic signal built primarily to coordinate machines rather than people, a genuine departure from every system described in this chapter so far, all of which exist to make a decision legible to a human being sitting in a driver's seat.

Back to the intersection

The next time a light turns red with no cross traffic anywhere in sight, that emptiness isn't proof the system failed, it's usually proof a detector somewhere hasn't finished its minimum interval, or that a fixed-time plan written for the whole day's average traffic doesn't happen to match this particular quiet minute. And the next time a green arrives just as you reach it, that's not chance either: it's an offset a traffic engineer calculated between this signal and the last one, tuned to a progression speed, running inside a controller descended, in a fairly direct line, from a manually thrown switch in a Cleveland control booth in 1914 and a hand-cranked patent drawing from 1923. The light changes. Almost nothing about when it changes is random.

The leap: what it replaced, and the work behind it

Before the signal, an intersection was a negotiation, and the currency was nerve. When the Model T put cars in ordinary hands in the 1920s, American streets that had belonged to pedestrians, streetcars, horses, and children playing filled up with fast metal, and nobody had worked out the rules yet. The result was carnage that reads as unbelievable now. In 1924, motor vehicles killed about 23,600 people in the United States, and in the 1920s roughly 60 percent of those killed were children under nine. Cities grieved in public: Baltimore put up a monument in 1921 "in memory of the 130 children whose lives were sacrificed by accident" that single year, and in a 1922 New York safety parade, 1,054 children marched to stand for the number killed the year before. The only traffic control at a busy corner was a police officer on a platform, waving his arms, present as long as a human could stand there and no longer.

The signal replaced that officer with a machine that never got tired, and the size of the safety gain is easiest to see per mile driven. In 1923 the U.S. death rate was about 18.65 deaths for every 100 million miles driven; today it is around 1.1, a drop of roughly 94 percent, achieved even as Americans drove vastly more. Signals are only one piece of that, alongside seatbelts and better cars, but the coordinated intersection is a load-bearing piece, and it does not run itself. The United States operates on the order of 300,000 signalized intersections, each one a small computer running a timing plan a traffic engineer wrote after counting real cars, kept alive by signal technicians who splice wiring at odd hours and by traffic-management-center operators watching thousands of corners at once. It is a permanent job, not a finished one.

Here is what it buys your ordinary day. In 2024 the average American driver made about 2.44 trips and covered roughly 31 miles a day; across the country that adds up to something like 232 billion trips a year. Almost every one of them crosses signals you never consciously register, each quietly deciding whose turn it is so two streams of traffic don't try to occupy the same square of asphalt. The morning it fails, you feel it fast. A dark signal legally becomes an all-way stop, which is why a single blacked-out downtown intersection can back traffic up for blocks until a public works crew stands in the middle of it doing, by hand, the exact job the light was doing: the same job Cleveland's officer did from a booth in 1914, just without the switch. The light that turns green as you arrive is not luck; it is a person's calculation, running in a gray box nobody looks at, standing in for a job no human could do around the clock.

Real-world examples and recent developments

The systems and companies below are real, named pieces of the traffic signal world introduced earlier in this chapter.

  • ATSAC (Automated Traffic Surveillance and Control), Los Angeles Department of Transportation (launched 1984): built to manage traffic around the Coliseum for that year's Olympic Games, when it controlled 118 signals; it now runs more than 4,850 of the city's traffic signals from a central control room, and LADOT is upgrading it again ahead of the 2028 Olympics. LADOT, ATSAC
  • Surtrac, built by Rapid Flow Technologies (first deployed 2012): a decentralized adaptive signal system developed at Carnegie Mellon University by researcher Stephen Smith, first installed on nine intersections in Pittsburgh's East Liberty neighborhood; an evaluation of that initial deployment found a 25 percent cut in travel time and a 40 percent cut in wait time. Carnegie Mellon University, on Surtrac
  • Miovision (Kitchener, Ontario): a traffic technology company whose camera-based video detection and Miovision Adaptive signal control system are installed at intersections across North America, replacing or supplementing inductive loop detectors with computer vision. Miovision, TrafficLink video detection
  • Yunex Traffic (formerly Siemens Intelligent Traffic Systems): a global traffic signal manufacturer and operator that in 2024 won a ten-year, roughly 200-million-pound contract with Transport for London to install and maintain traffic signal equipment across 21 London boroughs. ITS International, on the London contract

Recent developments

  • Google's Project Green Light (expanding through 2024 and 2025): an AI system that mines Google Maps driving data to recommend signal timing changes, which city engineers then review and apply themselves; Boston's rollout alone covered 114 intersections across 20 neighborhoods and reported up to a 33 percent cut in unnecessary stops at some of them. Boston.gov, on the Project Green Light expansion
  • USDOT National V2X Deployment Plan (released August 2024): a federal plan setting targets for vehicle-to-infrastructure technology, aiming for 20 percent of the National Highway System and 25 percent of signalized intersections in the top 75 U.S. metro areas to carry V2X equipment by 2028, rising toward full National Highway System coverage roughly a decade later. FHWA, on the National V2X Deployment Plan

Glossary

Signal phase. One set of non-conflicting movements at an intersection (such as through traffic on the main street) that receives the right-of-way at the same time.

Cycle length. The total time a signal takes to run through every one of its phases once before repeating.

Fixed-time control. A signal timing approach that repeats the same sequence and duration of phases regardless of actual traffic present.

Actuated control. A signal timing approach that uses detectors, such as inductive loops or cameras, to extend, shorten, or skip phases based on real-time vehicle or pedestrian presence.

Inductive loop detector. A coil of wire embedded in the pavement that senses a vehicle passing over or resting on it by detecting the disturbance in its electromagnetic field.

Green wave. A deliberately timed offset between consecutive signals along a corridor that lets a vehicle traveling at a set progression speed encounter a series of green lights.

Traffic management center (TMC). A facility where operators monitor and adjust traffic signals and camera feeds across many intersections in real time, often citywide.

Accessible pedestrian signal (APS). A pedestrian signal that adds audible tones and a vibrating arrow to its push button so a person who is blind or has low vision can tell when and in which direction to cross.

MUTCD (Manual on Uniform Traffic Control Devices). The FHWA standard governing the design, placement, and timing of traffic signals and other traffic control devices on U.S. public roads.

NTCIP. A family of communications standards that lets traffic signal controllers and related equipment from different manufacturers operate together on the same network.

Adaptive signal control. A more advanced control method, such as SCOOT or SCATS, that continuously recalculates signal timing across a network of intersections based on real-time traffic conditions rather than a fixed plan.

Vehicle-to-infrastructure (V2I). Wireless communication between vehicles and roadway infrastructure, such as a traffic signal broadcasting its timing directly to equipped cars.

Protected left turn. A left-turn signal phase with its own dedicated green arrow and no conflicting oncoming traffic, as opposed to a permissive turn where the driver must find a gap.

Sources and notes

Open questions

  • Exact counts of U.S. signalized intersections vary by tens of thousands depending on the source and methodology, from roughly 270,000 to 330,000; treat 300,000 as a working figure, not an exact census.
  • How much of the vehicle fleet needs connected-vehicle (V2I) equipment before the technology delivers benefits large enough to justify widespread infrastructure investment is still an open, actively studied question.
  • The long-term security posture of networked, adaptive, and connected signal systems, and how consistently older, unpatched controllers get upgraded after vulnerabilities like the 2014 Michigan case are found, remains an unevenly documented, evolving picture across U.S. agencies.

Next, the light is only useful because of what's underneath it. How asphalt roads are built and repaired 👉