An Open Source Tool to Extract Traffic Data from Google Maps: Limitations and Challenges
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Road traffic modelling, analysis, and prediction require accurate and preprocessed spatiotemporal traffic data including measurements like traffic speed and count. Many existing and emerging surveillance systems are currently used to facilitate traffic data collection. Google Maps is a web mapping service that leverages GPS crowdsourcing to retrieve accurate traffic data verified by both the research community and industry. Google Maps facilitates APIs to provide access to this data with a paid subscription. Google Maps also make this traffic data publicly available through their web interface, but with limited features and requires further pre-processing. All existing tools to facilitate these publicly available traffic data through the Google Maps web interface is either lack essential functionalities or are proprietary. We have developed an open-source web-based data scraper tool to extract and export available traffic data from the Google Maps web interface in multiple usable formats. The tool provides a user-friendly interface that enables users to visually mark the locations of interests and to flexibly determine the required periods for data collections. Performance evaluation shows that the tool can retrieve traffic data from Google Maps in a linear time complexity with no significant computational overhead. Limitations and challenges to develop such tools are also investigated.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it