Papers › Wi-Fi Wardriving Studies Must Account for Important Statistical Issues
Wi-Fi Wardriving Studies Must Account for Important Statistical Issues
Edward J Oughton, Julius Kusuma, Thibault Peyronel, Jon Crowcroft
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
Knowledge of Wi-Fi networks helps to guide future engineering and spectrum policy decisions. However, due to its unlicensed nature, the deployment of Wi-Fi Access Points is undocumented meaning researchers are left making educated guesses as to the prevalence of these assets through remotely collected or passively sensed measurements. One commonly used method is referred to as `wardriving` essentially where a vehicle is used to collect geospatial statistical data on wireless networks to inform mobile computing and networking security research. Surprisingly, there has been very little examination of the statistical issues with wardriving data, despite the vast number of analyses being published in the literature using this approach. In this paper, a sample of publicly collected wardriving data is compared to a predictive model for Wi-Fi Access Points. The results demonstrate several statistical issues which future wardriving studies must account for, including selection bias, sample representativeness and the modifiable areal unit problem.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections