MétaCan
Menu
Back to cohort
Record W2155291540 · doi:10.3138/carto.47.3.1112

Considering Risk Locations When Defining Perturbation Zones for Geomasking

2012· article· en· W2155291540 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCartographica The International Journal for Geographic Information and Geovisualization · 2012
Typearticle
Languageen
FieldSocial Sciences
TopicHuman Mobility and Location-Based Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsPerturbation (astronomy)Cluster analysisComputer sciencePopulationData miningAlgorithmArtificial intelligencePhysics

Abstract

fetched live from OpenAlex

Geomasking techniques are commonly used to mask the true location information of cases by introducing noise into location data. This study seeks to improve the spatially adaptive random perturbation (SARP) geomasking method by using the actual distribution of the residential addresses (or “risk location”) rather than the people (or “risk population”) to define a perturbation zone. The procedure used in the study also employs a “donut-shaped” perturbation zone, rather than the traditional “pancake-shaped” zone, when displacing a case. The effectiveness of the proposed geomasking methods is assessed in terms of their potential to control for location re-engineering and their ability to maintain the point patterns embedded in the real distribution. The authors conclude that SARP geomasking using the distribution of actual street addresses protects privacy more effectively than geomasking based on population size; the different SARP techniques do not significantly change the clustering patterns on a global level, but the geomasked data tend to be more clustered than the real case distribution.

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.004
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.892
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0030.000
Scholarly communication0.0010.002
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.019
GPT teacher head0.317
Teacher spread0.298 · 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