MétaCan
Menu
Back to cohort
Record W4220652580 · doi:10.3390/land11040475

An Overview of Fractal Geometry Applied to Urban Planning

2022· article· en· W4220652580 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueLand · 2022
Typearticle
Languageen
FieldEngineering
TopicUrban Design and Spatial Analysis
Canadian institutionsUniversity of Waterloo
FundersSocial Sciences and Humanities Research Council of Canada
KeywordsFractalUrban planningFractal dimensionContext (archaeology)NormativeComputer scienceCitizen journalismFractal analysisFunction (biology)Regional scienceData scienceGeographySociologyMathematicsPolitical scienceCivil engineeringArchaeologyEngineeringWorld Wide WebLaw

Abstract

fetched live from OpenAlex

Since computing advances in the last 30 years have allowed automated calculation of fractal dimensions, fractals have been established as ubiquitous signatures of urban form and socioeconomic function. Yet, applications of fractal concepts in urban planning have lagged the evolution of technical analysis methods. Through a narrative literature review around a series of “big questions” and automated bibliometric analysis, we offer a primer on fractal applications in urban planning, targeted to urban scholars and participatory planners. We find that developing evidence demonstrates linkages between urban history, planning context, and urban form and between “ideal” fractal dimension values and urban aesthetics. However, we identify gaps in the literature around findings that directly link planning regulations to fractal patterns, from both positive and normative lenses. We also find an increasing trend of most literature on fractals in planning being published outside of planning. We hypothesize that this trend results from communication gaps between technical analysts and applied planners, and hope that our overview will help to bridge that gap.

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.000
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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.263
Threshold uncertainty score0.483

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.025
GPT teacher head0.244
Teacher spread0.219 · 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