NASA-IMPACT / NASA-IMPACT/veda-data
Rename yearly NO2 collection from OMI_trno2-COG to no2-yearly
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9m
- Merged PRs (30d)
- 1
Description
We currently have three NO2 products in our catalog:
no2- monthly datano2-monthly-difference- monthly anomaly (difference from some baseline)OMI_trno2-COG- yearly data
They present the same type of property (NO2 concentrations), just different derived products. Would it make sense to rename the OMI_trno2-COG collection to no2-yearly or so, to harmonize the naming pattern between the three?
We would need to update it in VEDA Earthdata Dashboard and the EO Dashboard, but I think that is easy enough to do.
Acceptance criteria
- Renamed
OMI_trno2-COGtono2-yearly
Contributor guide
No contributing guide indexed for this repository
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
Start with the collection references in the VEDA Earthdata Dashboard and app/src/scripts/generate_files.py around line 171 in the EO Dashboard. Trace all uses of OMI_trno2-COG before changing the name, then verify that both dashboards use no2-yearly and that the acceptance criterion is satisfied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100