future iteration: add a [year] column to the remoteness index.
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 0
- Avg merge
- 34m
- Merged PRs (30d)
- 4
Description
As this data can/will change over time (even if only small changes), should include a year column to make sure we use the right data for the right year.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Locate the remoteness index data and the code that creates or consumes it, then determine how the year should be represented for changing data. Done means the index includes a year column that identifies the correct data year without breaking existing use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100