Recent city technology leadership moves, including San Antonio’s appointment of a new Chief Information Officer, reflect a broader municipal reality in 2026: urban mobility is now as much an information challenge as an infrastructure challenge. Cities are expected to improve travel reliability, support economic activity, reduce emissions, and justify public spending, often without the budget or time required for major roadway reconstruction.
That is why bottleneck identification has become a priority for smart city programs. The key question is no longer simply, “Where is traffic slow?” A more useful question is, “Where does the road network fail to accommodate demand, why does it fail there, and what level of intervention is justified?” Ticon’s traffic analytics platform is designed around precisely this question.
Urban congestion is visible, but its causes are not always obvious. A queue at one intersection may be caused by insufficient downstream capacity, poor signal coordination several blocks away, turning movement imbalance, access friction from driveways, a lane drop, or recurring event traffic. Treating the visible queue without diagnosing the network mechanism can lead to expensive interventions with limited impact.
Ticon’s research illustrates why this distinction matters. In the study “Impact of Traffic Volume Variations on Travel Delays as Illustrated by Pandemic Period Data,” G. Brodski, A. Stepanyan, T. Kozakevich, I. Vyazinko, and A. Naskidashvili analyzed 196,891,570 data points across 126 road sections in nine eastern U.S. states over a two-year period. The road sections ranged from 400 to 3,500 meters. The study found that reduced traffic demand did not consistently translate into proportional delay reduction. In some cases, even a 54% decrease in travel demand produced little change in delay.
For municipalities, this finding is important. It suggests that bottlenecks are not only a function of volume. They are also a function of traffic control quality, intersection design, turning demand, network connectivity, and the way congestion propagates through corridors. In practical terms, simply restricting demand or widening a road is not always the best first response.
Traditional traffic analysis often begins with counts, spot speeds, and field observations. These remain useful, but they can miss the temporal and spatial detail needed to rank bottlenecks across a whole urban network. Ticon’s methodology consolidates multiple traffic information sources, including permanent and portable detectors, traffic counters, GPS data, connected vehicle data, GIS information, demographics, traffic organization data, events, and other sources.
This matters because bottleneck identification requires coverage, not just snapshots. Ticon provides near-complete road network coverage, more than 97% of roads at Functional Road Class 6 and above, and 100% time coverage. Through cross-verification, filtration, and proprietary processing, Ticon produces estimates of speeds, volumes, and derived performance measures for 95% of roadways. The platform supports high spatial resolution, down to short road segments of up to 35 feet, with about 225 feet on average, and time resolution as fine as 5 minutes, in many cases up to 15 seconds.
That granularity changes the workflow. Instead of looking at a few congested locations, engineers can evaluate how an entire corridor behaves during morning peaks, school dismissal, weekend retail peaks, special events, seasonal demand shifts, or construction detours. A bottleneck becomes a measurable network condition, not merely a complaint hotspot.
For intervention planning, traffic volume alone is not enough. A high-volume road may operate well if capacity and signal control are adequate. A moderate-volume intersection may create severe delay if left-turn demand is underestimated or signal timing is poorly matched to actual flow.
Ticon’s TrafficZoom and TrafficScope tools are built to combine several layers of analysis:
• Speed and volume analysis, to understand demand and operating conditions.
• Saturation analysis, to identify where demand approaches or exceeds practical capacity.
• Level of Service calculations for streets and road sections.
• Street and intersection performance ranking, to prioritize the most consequential locations.
• Network Bandwidth Utilization, to assess how effectively the network accommodates current demand.
• Travel delay and cumulative traffic delay, to quantify user impact and compare alternatives.
The practical value is prioritization. Cities can distinguish between locations where signal timing optimization may be enough and locations where geometric redesign, turn-lane changes, access management, or larger capital work may be necessary.
Many urban bottlenecks are intersection problems. A corridor may show low speeds, but the root cause can be a dominant left-turn movement, an undersupplied through movement, or a heavy right turn conflicting with pedestrians and transit stops. This is why turning movement estimation is central to evidence-based intervention planning.
Ticon’s turning movement methodology estimates each turning movement for each 15-minute period across a full 24-hour day. Results can be aggregated by day of week, weekday versus weekend, month, season, year, peak period, or off-peak period. This allows planners to see not only whether an intersection is congested, but which movement creates the operational constraint and when it occurs.
For example, a morning peak bottleneck driven by inbound left turns may need a different treatment than a weekend bottleneck driven by retail access and right-turn queues. Without turning movement detail, both may appear as the same red segment on a speed map. With turning movement analytics, they become distinct engineering problems.
Bottleneck identification is not an academic exercise. It guides public spending, contractor selection, signal retiming programs, ITS deployment, and capital improvement plans. If the input data are coarse or biased, cities may overbuild in one location while ignoring a higher-impact constraint nearby.
Join the network to access Ticon case studies and to receive Ticon newsletters
@2023 Ticon
