MétaCan
Menu
Back to cohort
Record W3121525777 · doi:10.1177/0361198120986169

Understanding Google Location History as a Tool for Travel Diary Data Acquisition

2021· article· en· W3121525777 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueTransportation Research Record Journal of the Transportation Research Board · 2021
Typearticle
Languageen
FieldSocial Sciences
TopicHuman Mobility and Location-Based Analysis
Canadian institutionsDalhousie UniversityConcordia University
Fundersnot available
KeywordsData collectionTRIPS architectureTravel behaviorComputer sciencePhoneMobile phoneSample (material)Location dataTransport engineeringExpansiveTravel surveyEngineeringWorld Wide WebTelecommunicationsStatistics

Abstract

fetched live from OpenAlex

Understanding human mobility within urban settings is fundamental for urban and transport planning. Travel demand modeling and planning typically rely on data that are collected from large-scale household travel surveys (i.e., origin–destination surveys) and compiled into single- or multiple-day travel diaries. The laborious task of collecting these data has left traditional methods with numerous limitations, resulting in significant trade-offs in regard to accuracy, sample size, and study duration, while also being vulnerable to reporting and transcription error. Rising mobile phone ownership has provided opportunities to acquire expansive cellular network data from service providers and location-based service data through smartphone applications. At the same time, the Google Maps smartphone application provides built-in infrastructure that can passively collect detailed location information from user smartphone devices. The resulting data are known as Google location history (GLH). To better understand the potential of these data offerings in transportation modeling and planning, GLH data passively collected from five different smartphones following prescribed itineraries over 12 days was evaluated. As 51% of 934 locations and 32% of 888 trips were matched to the pre-determined travel diary data, it was determined that GLH data does not currently appear to be an adequate tool for travel diary data collection. On average, locations that were missed by GLH were shorter (mean of 355 s), whereas locations that were identified were longer (mean of 762 s).

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 imitation

Not 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.

metaresearch head score (Codex)0.015
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.386
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0150.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0020.001
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.

Opus teacher head0.344
GPT teacher head0.442
Teacher spread0.097 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it