MétaCan
Menu
Back to cohort
Record W4405800240 · doi:10.3390/architecture5010001

Re-(De)fined Level of Detail for Urban Elements: Integrating Geometric and Attribute Data

2024· article· en· W4405800240 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

VenueArchitecture · 2024
Typearticle
Languageen
FieldEngineering
Topic3D Modeling in Geospatial Applications
Canadian institutionsUniversity of Manitoba
FundersNational University of Singapore
KeywordsComputer scienceGeography

Abstract

fetched live from OpenAlex

The level of detail (LOD) differentiates multi-scale representations of virtual 3D city models; however, the LOD tends to relay primarily the geometric details of buildings. When the LOD extends to other datasets, such as vegetation, transportation, terrain, water bodies, and city furniture, their LODs are not as clearly defined. Despite the general acceptance of this categorization, existing LOD formats also neglect non-geometric attributes. Integrating geometric and attribute data enables geometrically accurate and data-rich 3D models, ensuring that representations are as accurate as possible and that analyses contain as much information as possible. This paper proposes a family of LOD definitions considering both geometric and attribute data based on the geometric complexity and difficulty of obtaining, archiving, processing, and distributing the data. These definitions are intended to apply to all datasets by determining divisions in the LOD typically experienced across urban 3D model elements and their associated datasets, including buildings, vegetation, roads, relief, water bodies, and city furniture. Universally applicable definitions for datasets allow individuals to recreate studies or representations of 3D models to ensure the relevant data are present. These definitions also assist data providers in evaluating their data infrastructure and further strategizing and prioritizing updates or upgrades.

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: Methods · Consensus signal: none
Teacher disagreement score0.827
Threshold uncertainty score0.409

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.082
GPT teacher head0.300
Teacher spread0.218 · 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