MétaCan
Menu
Back to cohort

Jackpine3D: A Benchmark for Evaluating 3D Spatial Database Features

2025· article· en· W7125586383 on OpenAlexaff
Mohammadmasoud Shabanijou, Zhuliang Jia, Suprio Ray, Rongxing Lu, Pulei Xiong

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicData Management and Algorithms
Canadian institutionsNational Research Council CanadaQueen's UniversityUniversity of New Brunswick
Fundersnot available
KeywordsBenchmark (surveying)Spatial databaseSuiteSpatial analysisSpatiotemporal databaseSpatial query

Abstract

fetched live from OpenAlex

In recent years, due to the advancements in 3D data technologies, and the rise in 3D spatial applications, such as metaverse and digital twins, there has been a growing interest in efficient support of 3D spatial features in database management systems (DBMS). Processing 3D spatial queries can be significantly more complex and computationally intensive than traditional 2D spatial queries. Although a few spatial database benchmarks exist, they support 2D spatial data. Hence, there is a growing need to develop a benchmark to evaluate 3D spatial features. To address the aforementioned need, we have developed Jackpine3D, a 3D spatial database benchmark. The main goal of this benchmark is to evaluate the capability of different database systems in processing 3D spatial queries. The benchmark includes a Micro benchmark suite that consists of basic 3D spatial operations, and a Macro benchmark consisting of a few real-world spatial applications. With our benchmark, we have evaluated three database systems and compared their performance. We also identify several gaps for future researchers to address.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.019
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.024
Threshold uncertainty score0.047

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.019
Meta-epidemiology (narrow)0.0030.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0040.007
Science and technology studies0.0010.001
Scholarly communication0.0030.004
Open science0.0060.003
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0040.001

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.024
GPT teacher head0.332
Teacher spread0.307 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2025
Admission routes1
Has abstractyes

Explore more

Same topicData Management and AlgorithmsFrench-language works237,207