Answers are grounded in this paper and cite their sources.
Understanding the spatial and temporal patterns of holiday expressway traffic is essential for effective traffic management. This study analyzes the directional differences between inbound and outbound traffic flows on the first day of China’s 2025 National Day holiday, using 1,044,881 license plate recognition (LPR) records from the G30 Wukui section in Xinjiang, China. From these data, 462,627 origin–destination pairs between adjacent gantries were identified and aggregated into 30-min intervals. The analysis employed global and time-varying Moran’s I, Getis–Ord Gi*, and LISA statistics and introduced a directional asymmetry measure, ΔI, with bootstrap-based inference. Inbound traffic exhibited significant spatial clustering, whereas outbound traffic showed weaker clustering that was not significant at the primary 50-km specification (p = 0.064), although it was significant under seven of the eight specifications tested. Although the full-day directional asymmetry statistic ΔI was not statistically significant (p = 0.468), robust directional asymmetry was observed during the afternoon (T4) and evening (T5) return periods. A nighttime low-speed (low-flow) tendency was also observed between 00:00 and 06:00, although only a small minority of 30-min windows met the strict low-flow, low-speed criterion. An exploratory sign change in directional patterns was detected in the morning but was not statistically significant. These findings suggest that directional spatial and temporal asymmetry was pronounced in this corridor on the holiday studied and should be considered in traffic management strategies. The results also provide illustrative examples of segment-level, direction-specific, time-sensitive traveler information, although validation against operational performance indicators is still required.
No takes yet. Share an insight, caveat, or question.
Gu et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: