Using crowdsourced spatial data from Flickr vs. PPGIS for understanding nature's contribution to people in Southern Norway
Bibliographic record
Abstract
Abstract Crowdsourced data can provide spatially explicit data on the contribution of nature to people. Spatial information is essential for effectively managing the diverse relationships that people have with nature, but the potential and limits of using crowdsourcing data to generate maps for conservation purposes need further research. Passive crowdsourcing tools include social media platforms where photos and user‐generated tags are shared among users, whereas active crowdsourcing, such as public participatory geographic information system (PPGIS), provides an online platform for mapping place attributes such as values, experiences and preferences. In this study, we assess the spatial information gained through using Flickr (a photo sharing platform) and PPGIS (an online mapping platform) platforms for conservation planning to understand differences and similarities on the spatial distribution of values captured by the two platforms, and to identify what environmental and infrastructure variables correlate best with the distribution of values. We test these tools in Southern Norway including protected areas and the surrounding zones. We analysed non‐spatial (using chi‐square and Spearman rank correlation) and spatial (using clustering, Maxent and distribution overlap) data to identify differences between the two datasets and the values represented therein. We found large differences in spatial distribution using these two datasets, with Flickr data concentrated outside the protected areas and near roads, whereas PPGIS provided more fine‐scale data on diverse values in locations inaccessible by roads within the protected areas. Flickr can be used for generating regional scale data of scenic landscapes or routes, but PPGIS performs better for management of nature qualities appreciated by different user groups within protected areas. We discuss the pros and cons of using each data source and when each dataset is more suitable to be used in protected area management. A free Plain Language Summary can be found within the Supporting Information of this article.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.006 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".