MétaCan
Menu
Back to cohort
Record W2287740117 · doi:10.1016/j.trpro.2016.02.081

Logistics Sprawl in North America: Methodological Issues and a Case Study in Toronto

2016· article· en· W2287740117 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueTransportation research procedia · 2016
Typearticle
Languageen
FieldEngineering
TopicUrban and Freight Transport Logistics
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsUrban sprawlAtlantaMetropolitan areaGeographyRegional scienceCity logisticsTransport engineeringEnvironmental planningIdentification (biology)BusinessLand useEngineeringCivil engineering

Abstract

fetched live from OpenAlex

This paper focuses on the spatial patterns of freight and logistics activities in North America. The recent interest in logistics and warehousing and its impact on the urban environment has prompted research investigating the ‘sprawling’ nature of these firms. Logistics sprawl, i.e. the spatial deconcentration of logistics facilities and distribution centers in metropolitan areas has been examined for several metropolitan areas ( Dablanc and Ross, 2012 ; Dablanc 2014; Dablanc et al., 2014 ), yielding contrasting results: Atlanta and Los Angeles have experienced strong logistics sprawl between 1998 and 2008 while Seattle has not. The objective in this paper is two-fold. An additional case study (Toronto) is investigated to expand the current understanding of North American logistics sprawl and methodological issues, particularly related to facility identification and location data are discussed. An updated method for analyzing spatial patterns of logistics activity in North American cities is subsequently proposed. This updated method may then be used in the future to re-examine former case studies (Los Angeles, Atlanta, Seattle) as well as to investigate new ones.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.369
Threshold uncertainty score0.968

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.241
GPT teacher head0.414
Teacher spread0.173 · 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