I have a habit that annoys every person who has ever ridden in my car. When the navigation app says “turn left in two hundred feet,” I look at the actual intersection first. I read the signs. I check whether there is a no-left-turn placard hanging under the traffic light, or a small white rectangle bolted to a pole that the GPS clearly did not account for. My passengers think this is paranoid behavior. They are wrong.
My trust in navigation apps broke a few years ago, when one told me to make a left turn across a busy intersection during rush hour. I was already drifting into the turn lane when I noticed the sign: no left turn. Not faded, not ambiguous, not partially hidden by tree branches. A perfectly clear, recently installed sign that my app had absolutely no idea existed. I would have taken that turn. The cross-traffic was heavy enough that it would not have ended well.
That experience sent me down a rabbit hole of understanding how navigation apps actually decide which turns are legal and which are not. The answer, it turns out, is messier than most people assume.
What Your Navigation App Actually Knows About an Intersection
Here is the thing most drivers do not realize: your navigation app is not reading road signs in real time. It is consulting a database. Somewhere on a server, there is a record for every intersection, every road segment, every turn lane, and that record includes metadata about what you are and are not allowed to do there. When the app calculates your route, it queries that database, checks the restrictions, and plots a path that theoretically avoids illegal maneuvers. The word “theoretically” is doing a lot of heavy lifting in that sentence.
That database is only as good as the information that went into it. And collecting turn restriction data is one of the hardest problems in digital cartography.
Think about what a turn restriction actually is. A road segment has relatively stable properties: its geometry, its name, the general direction it flows. These things change, sure, but not often. A turn restriction is different. A city traffic engineer can decide on a Monday that a particular intersection needs a no-left-turn sign, have it installed by Wednesday, and that change will not appear in any mapping database for weeks or months. Sometimes longer. The physical world updates instantly. The digital world catches up on its own schedule, and that schedule is unpredictable.
Where the Data Comes From
Map providers like Google, Apple, TomTom, and HERE assemble their road data from a patchwork of sources, and understanding how map providers actually collect road data helps explain why gaps appear. Satellite imagery can reveal lane markings and road geometry, though a satellite orbiting hundreds of miles overhead cannot read a twelve-inch sign bolted to a pole, and even fleet vehicles with roof-mounted cameras, which capture far more street-level detail, only pass through most intersections a handful of times per year. Government databases should be the gold standard. In practice, municipalities update their digital records on wildly inconsistent timelines. Some cities maintain searchable inventories of every traffic sign in their jurisdiction. Others still track changes in paper binders stacked in a back room at the public works office.
The result is a confidence gradient. The app might have rock-solid data for a major downtown corridor that gets surveyed regularly, and completely stale data for a suburban intersection three miles away where a new shopping center changed the traffic flow last spring.
The conditional restriction problem
Permanent turn restrictions are hard enough. Conditional ones are a nightmare.
Think about time-based restrictions near schools: no left turn during morning drop-off, no right turn during afternoon pickup. These are not simple yes-or-no flags in a database. They require conditional logic, time windows, day-of-week rules, and sometimes seasonal exceptions layered on top. A navigation app might correctly know that a particular turn is legal on a Saturday afternoon but have no idea that a weekly farmers’ market closes that same street every Saturday from May through October. Event-based closures, temporary construction detours, emergency road work that starts and ends within a single day: none of these fit neatly into a static database, and all of them can turn a legal instruction into an illegal one.
Then there are restrictions that depend on who you are. A sign that says “no trucks over five tons” does not affect a sedan, but the database still needs to store, categorize, and serve that information correctly. When that metadata is incomplete or miscategorized, a delivery driver following GPS directions might find themselves face-to-face with a low bridge that the app swore was not there.
Why Fixes Take So Long
Most map providers depend heavily on community reporting to catch errors, and this works better than you might expect. Google Maps and Apple Maps both offer “report a problem” tools that have expanded significantly over the years, while Waze built its entire business model around crowdsourced corrections. OpenStreetMap takes a different approach entirely, relying on volunteer mappers who physically survey their neighborhoods and update restriction data by hand. These systems catch a huge number of errors over time.
But there is a lag.
A submitted correction does not go straight into the live map. It enters a review pipeline. Depending on the provider, the type of correction, and how many other reports are in the queue, that review can take anywhere from a few days to several weeks. For a major intersection in a well-mapped city, the turnaround might be fast. For a rural road with no other reports to corroborate the change, the correction might sit in a queue for a long time. The system is biased toward caution, which makes sense: you do not want one incorrect report to change routing for millions of drivers. But that caution also means legitimate fixes sometimes move slowly.
Well-mapped cities with active contributor communities get corrections faster than areas where nobody is maintaining the data. This creates an accuracy gap that roughly mirrors the digital divide: places with more tech-engaged residents have better maps.
What you can actually do about it
If you regularly drive a route where your navigation app suggests something that does not match the signs on the road, report it. Seriously. One accurate correction from a driver who was physically at the intersection and saw the sign with their own eyes is worth more than any satellite pass or camera car drive-by. Every major mapping platform has a way to submit these corrections, and they do get processed. It just takes patience.
But the more immediate lesson is simpler: trust the signs, not the screen.
Navigation apps are routing tools, not legal authorities. If the app says turn left and the sign says no left turn, follow the sign. No traffic court in the country will accept “but my GPS told me to” as a defense. The app is offering a suggestion based on the best data it has, and sometimes that data is wrong. Your eyes are the final filter, and they should always overrule the blue line on the screen.
Why This Matters Even More for Group Travel
There is an extra wrinkle when multiple cars are following the same route. The lead driver might spot the restriction and adjust, swerving past the turn at the last second. But the second and third cars, following a few seconds behind, may already be committed. They see the lead car go straight and wonder why, or worse, they do not notice and make the turn anyway because the app still says to. A quick call over the radio helps, but a shared real-time location view showing the lead car’s corrected path lets everyone in the convoy see the adjustment as it happens, no voice call needed.
Navigation apps are extraordinary tools. They have made it possible for anyone to drive anywhere without memorizing a single road name. But they are working from a snapshot of the world that is always, to some degree, out of date. The signs on the road reflect what is actually happening right now. So when the screen and the signpost disagree, go with the sign.