WarwickCIM/OSMdashboard

consider retrieving changesets info from OSM-hasthag-explorer

Open

#37 opened on Sep 3, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)R (1 fork)auto 404
enhancementhelp wantedpriority-high

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

So far, data about changesets is pulled by from querying OSM's API in two steps:

  1. First, we pull all the changesets made by a list of users with get_contributors_changesets()
  2. Then, for every changeset, we get all their details with get_changesets_details()

All of this is done in here: https://github.com/WarwickCIM/OSMdashboard/blob/main/inst/templates/dashboard_groups/data_retrieval.R (until issue #11 is implemented).

This process takes a lot of time and is resource hungry. Ideally we could pull this data from https://github.com/WarwickCIM/OSM-hasthag-explorer (if that was a service).

Contributor guide

Research direction
Start by reading the current data retrieval code in `inst/templates/dashboard groups/data retrieval.R` to understand how changesets are fetched. Then explore the OSM hasthag explorer repository to see if it provides any service or API. Consider the feasibility of using it and outline the steps needed to integrate it into OSMdashboard.
Tech stack
r
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitRREST APIs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40