
Recent development news points to a familiar transportation challenge. In Colorado, Firestone City Centre is preparing for a 128,000-square-foot Target within a 140-acre mixed-use project. Near Boston, Brookfield Properties and New England Development have acquired the former South Weymouth Naval Air Station site with plans that include 6,500 housing units and 2 million square feet of retail and commercial space. These projects are not just real estate stories. They are future traffic systems in formation.
For planners, engineers, retailers, and municipalities, the question is not simply whether these developments will generate more trips. They will. The harder question is where, when, by whom, in which direction, and under what operating conditions those trips will appear. That is where historical traffic data, continuous traffic monitoring, and precise traffic data collection become essential for mobility improvement.
Ticon’s work starts from a practical transportation engineering premise: average traffic volume alone is not enough. Annual Average Daily Traffic, or AADT, is useful because it reflects the relative importance of a roadway and supports planning, site evaluation, and network monitoring. But major developments change mobility at a finer scale than an annual average can describe. A new anchor store, residential district, logistics node, or infrastructure resilience project affects morning peaks, weekend shopping periods, school traffic, freight exposure, turning movements, and seasonal demand in different ways.
In AADT Estimation by Various Methods: Accuracy and Reliability, Gregory Brodski and Alex Chaihorsky describe Ticon as a traffic information consolidator that combines traffic engineering methodology, multivariate analysis, and relevant large-scale mobility sources. In a validation across Georgia, Nevada, and California, Ticon evaluated 695 counting points, rejected 28 due to detector-counting errors and 30 due to GPS-data gaps, then performed more than 1,200 estimations across the remaining 637 mostly bidirectional points. The reported AADT performance was a median average percentage error of 4.78 percent and a relative root mean square error of 11.97 percent, supporting expected volume-estimation error within 20 percent at 90 percent confidence.
That level of quantified uncertainty matters because traffic monitoring is not only about collecting more observations. It is about knowing how much trust to place in the estimate. A 48-hour tube count can capture a temporary condition, a holiday anomaly, or a weather-affected weekday. A one-week count is better, but it still represents only about 1.9 percent of the year. Ticon’s methodology is designed around year-round observation, cross-verification of multiple independent sources, and high spatial resolution, allowing analysts to identify unusual intra-day, intra-week, monthly, and seasonal changes rather than treating them as background noise.
This is especially important for mixed-use sites. A development such as Firestone City Centre will not produce a single traffic pattern. A large-format retailer may drive weekend and afternoon peaks, restaurants may extend activity into evening hours, multifamily housing may add recurring commuter demand, and nearby complementary retailers may create chained trips. Similarly, a 6,500-unit redevelopment near Boston will likely generate both residential access trips and regional commercial trips, with effects distributed across multiple municipalities and feeder roads. Historical traffic data allows each of these demand components to be compared against predevelopment baselines.
Ticon’s intraday traffic volume methodology extends this analysis beyond AADT. The platform estimates traffic volumes at hourly levels and, where supported by data availability, 15-minute bins. Its intraday estimation approach considers road geometry, intersection geometry, segment connectivity, speed distributions, expected vehicle composition, driver behavior, weather, time of day, and congestion state. For traffic signal management, corridor operations, retail staffing, and congestion diagnosis, these shorter intervals are often more useful than daily averages.
The distinction is straightforward. A road with acceptable AADT may still fail during 30 minutes of concentrated left-turn demand into a shopping center. A corridor may appear healthy over the year while showing recurring Friday afternoon saturation. A proposed driveway may look adequate until vehicle classification shows a higher truck share than expected. Mobility improvement depends on detecting these patterns before they become operating failures.
Ticon’s approach to traffic data collection reflects that need for detail. The platform consolidates and cross-verifies information from sources including permanent and portable traffic detectors, traffic counters, GPS data, connected-vehicle data, GIS information, demographics, traffic organization data, events, and other relevant inputs. The resulting dataset supports coverage of more than 97 percent of roads at Functional Road Class 6 and above, with 100 percent time coverage. After filtration and processing, Ticon estimates speeds, volumes, and derived performance metrics for about 95 percent of roadways, including short road segments up to 35 feet, with an average segment length of about 225 feet, and time intervals down to 5 minutes, or in many cases 15 seconds.
For traffic engineers, that combination of spatial and temporal resolution changes the monitoring problem. Instead of asking whether traffic is “up” or “down” near a new development, analysts can ask which links experience new delay, which approaches approach saturation, whether queues are likely to spill back, how truck exposure changes by time of day, and whether the network’s actual performance matches planning assumptions.
Ticon’s virtual transportation model is built for this kind of evaluation. It can rank road sections by traffic delay, saturation degree, total driver time loss, and each section’s contribution to area-wide mobility. For before-and-after analysis, delay can be used as the comparison metric. For congestion analysis, travel time delay and saturation degree can identify where demand is exceeding operational capacity. For site-related analysis, traffic volume and speed distributions help distinguish high-volume roads that are accessible from high-volume roads where vehicles are moving too fast or too congested to support safe and convenient access.
Turning movement estimation adds another layer. In Ticon Turns: Verification of Accuracy, Ticon describes a methodology that estimates left, through, and right-turn demand for each 15-minute period across a 24-hour day. Results can be aggregated by day of week, weekdays and weekends, month, season, year, peak period, or off-peak period. The validation compared Ticon turning-movement estimates with portable detector measurements collected by an independent organization at two three-leg and two four-leg intersections in Maine. For large mixed-use projects, this kind of directional information is often the difference between a generic trip-generation estimate and a usable access-management plan.
Historical data also improves impact analysis because it separates recurring behavior from temporary disruption. A resilience project, a major construction phase, a new anchor tenant, or a road closure can change traffic patterns in ways that are not visible from short-duration counts. Ticon’s impact-analysis framework emphasizes year-round observations and cross-verification precisely because partial time coverage, one-size-fits-all assumptions, and failure to account for external factors can produce inaccurate volume estimates and poor business or engineering decisions.
Retail trip generation research illustrates the point. The Convenience Store Trip Generation study in Ticon’s knowledge base examined 26 stores in Knox County, Tennessee, using 24-hour driveway counts and adjacent street traffic counts. It introduced variables beyond store size, including adjacent road traffic volumes, dwelling units in the market area, and competition with other development. The study also treated pass-by trips as trips influenced by the traffic volume on adjacent roads, while home-based trips were evaluated through a market-area accessibility index based on dwelling units and travel time. In other words, the built environment and the transportation network must be modeled together.
The same principle applies to today’s mixed-use projects. A 140-acre retail and residential center is not only a destination. It is an accessibility field shaped by adjacent volumes, competing destinations, driveway placement, peak-hour directional flows, nearby households, travel times, and the probability that a traveler will stop. A former naval air station converted into housing and commercial space is not only a land-use change. It is a new set of daily origins and destinations imposed on an existing regional network.
For municipalities, historical traffic monitoring supports better phasing. If a development is delivered over several years, traffic conditions can be measured before, during, and after each major phase. Engineers can compare observed changes against projected trip generation, identify whether mitigation is working, and adjust signal timing, access control, or lane assignment before congestion becomes normalized. For retailers and developers, the same information supports site access decisions, staffing, inventory planning, and revenue forecasting based on real traffic fluctuations rather than average exposure.
The practical lesson is that mobility improvement does not come from a single count or a single forecast. It comes from a monitored feedback loop: collect traffic data continuously, cross-check it against independent sources, estimate volumes and speeds at the right temporal and spatial resolution, compare current conditions with historical baselines, and translate the findings into operational changes.
As large mixed-use developments, retail anchors, and resilience investments continue to reshape local networks in 2026, the transportation question will become more precise. Not “how much traffic will this create,” but “how will this change network performance by segment, interval, movement, and vehicle type?” Historical traffic data gives engineers the baseline. Traffic monitoring shows the change as it occurs. Ticon’s methodology connects both into a practical framework for mobility improvement.