As of July 28, 2026, recent real estate, retail, and urban redevelopment news points to a common transportation challenge: land use is changing faster than many traffic monitoring programs can measure. Mavis Tire’s planned acquisition of Pep Boys would reshape a network of automotive service locations, Batteries Plus is expanding through 30 new franchise units, and Milwaukee’s Davidson Park project has converted a former Harley-Davidson parking lot into flood-protective public space.
These stories are not primarily transportation stories, but each depends on transportation evidence. A store expansion plan, a service-center consolidation, and a parking-lot-to-park conversion all change how people move, where vehicles slow down, which corridors become busier, and which intersections absorb new demand. For engineers and planners, the question is not simply whether traffic exists. The question is whether traffic can be measured historically, spatially, and temporally with enough precision to improve mobility rather than react to congestion after it appears.
Ticon’s work begins with that distinction. A single count, a generic AADT value, or a short field survey may describe one slice of traffic. Mobility improvement requires a record of how the network behaves across days, weeks, seasons, incidents, weather, and land-use changes.
Traditional traffic data collection often relies on short observation windows. Ticon’s comparative materials note that many hardware-based approaches measure for 48 hours, equal to about 0.5% of annual time, or one week, equal to about 1.9% of annual time. Manual counting may capture only about five minutes for every hour during peak periods, roughly 1.35% of time. These approaches can be useful for specific engineering tasks, but they become fragile when traffic varies by weekday, month, season, construction activity, nearby retail demand, or special events.
Ticon’s methodology is designed around continuous historical coverage. According to the C-Site Insight Product Manual and Ticon Methodology documentation, the platform provides more than 97% road network coverage for roads of functional road class 6 and above, and 100% time coverage. It combines permanent and portable detector data, traffic counters, GPS and navigation data, connected vehicle data, GIS layers, demographics, traffic organization information, and event data. Through cross-verification, filtration, and proprietary modeling, those inputs are converted into estimates of speeds, volumes, and related traffic-flow derivatives for about 95% of roadways.
The engineering value is in both time and place. Ticon reports can represent traffic at very short road segments, up to 35 feet in some cases and about 225 feet on average, rather than averaging conditions across long road sections. Time resolution can reach five-minute intervals, and in many cases even 15-second intervals. For mobility monitoring, that difference is critical. A bottleneck at a driveway, a lane-drop, an intersection approach, or an event access point can disappear inside a mile-long average.
AADT remains a core transportation metric because it reflects the importance and use of a road segment over a year. It is widely used for planning, site selection, and transportation analysis. But AADT alone cannot explain whether a corridor fails during the morning peak, whether a retail driveway creates afternoon friction, or whether a new park shifts vehicle demand toward weekends and evenings.
In “AADT Estimation by Various Methods: Accuracy and Reliability,” Gregory Brodski and Alex Chaihorsky describe Ticon as a traffic information consolidator rather than a generic big-data provider. The distinction matters. The platform applies traffic engineering methodology and multivariate analysis together with large-scale mobility inputs. In a validation across Georgia, Nevada, and California, 695 counting points were initially selected. After excluding 28 points due to detector-based counting errors and 30 points due to GPS data gaps, 637 points remained. Because most were bidirectional, Ticon performed more than 1,200 AADT estimations.
The reported AADT performance was a median absolute percentage error of 4.78% and a relative root mean square error of 11.97%. The study states that this allows Ticon to keep expected AADT estimation error within 20% boundaries with 90% confidence. Importantly, the methodology supports similar accuracy across functional road classes 1 through 6, which makes it applicable not only to major highways but also to smaller roads where agencies and businesses often have fewer direct counts.
For traffic monitoring, the practical implication is clear: AADT should be treated as the annual baseline, not the full diagnosis. Ticon’s intraday volume work extends that baseline into daily, hourly, and sometimes 15-minute traffic estimates. In Ticon’s intraday traffic volume estimation white paper, the platform evaluates volume using parameters including road geometry, intersection geometry, road-segment connections, vehicle speed distributions, expected vehicle composition, and driver behavior under conditions such as weather, time of day, and congestion state.
Field results show why this matters. Ticon reports that median average percentage discrepancy between hourly traffic volume estimates and direct detector measurements varies between 5% and 20%, depending on the availability of infrastructure data. For 15-minute traffic flow volumes, the algorithm achieved a median absolute percentage error of 11.24%, compared with 6.5% for a pre-calibrated video detector under the same circumstances. That level of estimation supports planning questions that annual averages cannot answer, including when to retime signals, when to schedule deliveries, when to staff service operations, and when recurring congestion begins.
The Davidson Park example in Milwaukee illustrates a broader point. Redevelopment projects can reduce impervious pavement, add public space, change pedestrian activity, alter parking demand, and redirect vehicle flows. Without historical traffic monitoring, agencies may know that the project was built, but not whether mobility improved, degraded, or simply shifted to a neighboring street.
Ticon’s mobility improvement workflow addresses this by treating road networks as continuously observed systems. In “Traffic Congestion: What Works, What Doesn’t,” Ticon describes analysis of 126 signalized intersections across nine U.S. states using about 200 million data points. The research used the COVID-era reduction in traffic demand as a natural experiment. Traffic demand fell by up to 30% or more, yet delay reduction on signalized roads was often much smaller than the reduction in volume. In some cases, traffic delay changed little even when demand was reduced almost by half.
That finding is important for planners because it challenges a common assumption: less traffic does not automatically produce proportionally better mobility. Poor signal timing, saturation at critical approaches, inefficient lane allocation, and unstable progression can preserve delay even when volumes fall. Conversely, Ticon’s experience indicates that signal timing optimization alone can achieve up to 50% reduction in travel delay in suitable contexts.
This is where historical traffic data becomes an engineering tool rather than a reporting product. Ticon’s TrafficZoom and TrafficScope toolsets support speed and volume analysis, saturation analysis, level-of-service style assessment, travel delay estimation, and before-after comparisons. TrafficScope can evaluate any period within the past 10 years, allowing agencies to compare conditions before and after signal retiming, construction, corridor redesign, access changes, or ITS deployment.
A before-after study based on only a few field days risks confusing weather, weekday variation, seasonal demand, or incidents with project performance. A historical data record allows engineers to ask a more precise question: under comparable demand conditions, did the intervention reduce delay, improve speed consistency, reduce saturation, or shift congestion elsewhere?
Network mobility often fails at intersections, not midblock. For that reason, traffic monitoring must describe not only how many vehicles pass a segment, but where they go. Ticon’s turning movement estimation methodology uses multivariate analysis of GIS data, traffic events and management information, demographics, connected vehicle data, traffic organization data, location-based services, detection data, and GPS or navigation data.
The Ticon Turns white paper states that the platform estimates each turning movement demand for each 15-minute period during a 24-hour day. Depending on the request and data availability, these results can be aggregated by day of week, weekday and weekend, month, season, year, or peak and off-peak periods. That format aligns with how transportation engineers evaluate intersection operations in practice. Morning commuter demand, school dismissal traffic, Saturday retail access, and event traffic can all produce different turning patterns at the same intersection.
For land-use changes like a new service center, retail expansion, or public park, this intersection-level view is essential. A site may have acceptable total traffic volume, but an eastbound left turn into the property may overload an approach for 30 minutes each evening. A corridor may show stable AADT, while the turning demand at one signalized node grows enough to affect queue spillback. Historical turning movement monitoring makes those conditions visible before they become chronic complaints.
The phrase “traffic data” can imply certainty, but every source has limitations. Detectors fail or drift. GPS data can have spatial gaps. Location-based service data may represent people more directly than vehicles. Counters may miss unusual seasonal or event conditions. Ticon’s approach is built around cross-verification precisely because no single input is enough for reliable mobility assessment.
In “Application of Cross-Verified Multisource Data to Remediation of Inaccurate Detector Measurements,” Brodski, Stepanyan, Kozakevich, Vyazinko, and Naskidashvili describe a sequential data integration process used to clarify true traffic values when detector measurements are inaccurate. This approach is especially relevant for historical monitoring because errors can otherwise persist unnoticed and contaminate planning decisions, performance reports, or business forecasts.
For public agencies, cross-verified historical data helps prioritize limited budgets. For private operators, it reduces the risk of selecting a site based on an attractive but misleading traffic count. For engineering consultants, it provides a stronger basis for diagnosing congestion mechanisms rather than merely describing congestion symptoms.
The recent retail and service-location news also highlights another element of traffic monitoring: driver behavior. A corridor with high AADT is not automatically a good access corridor. A high-volume road where vehicles travel too fast to enter a site comfortably may produce less practical demand than a lower-volume segment where drivers slow predictably and have convenient ingress.
Ticon’s location analytics materials emphasize the use of speed and acceleration distribution patterns, lane conditions, road features, traffic organization, weather, and surrounding context. Lower speeds may indicate that drivers can maneuver into a property, but speed alone is not enough because signals, congestion, terrain, or road signs can also reduce speed. Ticon therefore applies multi-factor analysis to distinguish disturbances from stopping intent.
For mobility improvement, the same principle applies. A speed drop may indicate congestion, but it may also reflect signal control, pedestrian activity, parking maneuvers, weather, or geometric constraints. Historical monitoring allows those patterns to be separated. Engineers can identify whether a recurring slowdown is tied to commuter peaks, school activity, weekend retail demand, seasonal tourism, lane utilization, or a specific intersection approach.
The common thread across current redevelopment, retail expansion, and infrastructure planning is that mobility cannot be improved with isolated measurements. It requires historical traffic data that is accurate enough for planning, granular enough for operations, and broad enough to compare conditions over time.
Ticon’s methodology supports that requirement through year-round observation, multisource cross-verification, AADT and intraday volume estimation, 15-minute turning movement analysis, speed and congestion monitoring, saturation analysis, and before-after evaluation over historical periods reaching up to 10 years. The reported performance metrics, including 4.78% AADT MAPE, 11.97% RRMSE, 11.24% MAPE for 15-minute volumes in a field study, and expected AADT error within 20% at 90% confidence, show that traffic monitoring can move beyond approximate counts toward empirical transportation management.
For cities, that means mobility investments can be ranked by their actual contribution to delay reduction and network performance. For developers and retailers, it means locations can be evaluated by real access behavior rather than traffic volume alone. For engineers, it means the next generation of traffic data collection is not only about counting vehicles. It is about maintaining a continuous historical record of how the road network performs, why it changes, and where intervention will produce measurable improvement.
Join the network to access Ticon case studies and to receive Ticon newsletters
@2023 Ticon
