MétaCan
Menu
Back to cohort
Record W2059398928 · doi:10.1080/13658811003702147

An ontology-based framework for geospatial clustering

2010· article· en· W2059398928 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

VenueInternational Journal of Geographical Information Systems · 2010
Typearticle
Languageen
FieldComputer Science
TopicData Management and Algorithms
Canadian institutionsUniversity of ReginaUniversity of Calgary
Fundersnot available
KeywordsGeospatial analysisOntologyCluster analysisComputer scienceGeographyInformation retrievalData scienceData miningCartographyArtificial intelligence

Abstract

fetched live from OpenAlex

Geospatial clustering is an important topic in knowledge discovery research and geospatial information systems. However, current clustering research emphasizes the development of more efficient and effective clustering methods without paying much attention to domain knowledge and users' goals during the clustering process. Making better use of geospatial and clustering knowledge to select proper methods and datasets will help achieve clustering results that better meet users' requirements. In this article, we present the GEO_CLUST framework for performing geospatial clustering. The framework consists of the GeoCO ontology for geospatial clustering and the ontology reasoner reasoning mechanism. The GeoCO ontology is used to represent geospatial and clustering domain knowledge. The ontology reasoner uses classification and decomposition techniques to specify users' tasks. Using the framework, users can identify the appropriate geospatial data and clustering method based on their specific goals. To demonstrate the framework, two case studies on finding population density clusters in Western Canada and locating five hospitals in South Carolina are discussed. The results show that the framework can select the proper datasets and clustering methods with respect to users' goals.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.899
Threshold uncertainty score0.890

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0010.004
Open science0.0020.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.012
GPT teacher head0.291
Teacher spread0.279 · 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