Update Gulf of Mexico refs to Gulf of America
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 16
- Forks
- 15
- Avg merge
- 1h 39m
- Merged PRs (30d)
- 6
Description
I see 4 references to Gulf of Mexico https://ioos.github.io/ioos_code_lab/search.html?q=of+mexico.
| notebook | existing text | updated text |
|---|---|---|
| https://ioos.github.io/ioos_code_lab/content/code_gallery/data_access_notebooks/2017-09-09-hurricane_irma.html | Below we have a station in Naples, FL along the Gulf of Mexico. | Below we have a station in Naples, FL along the Gulf Coast. |
| https://ioos.github.io/ioos_code_lab/content/code_gallery/data_access_notebooks/2017-11-30-rerddap.html | Gulf of Mexico Coastal Ocean Observing System (GCOOS) | Gulf of America Coastal Ocean Observing System (GCOOS) |
| https://ioos.github.io/ioos_code_lab/content/code_gallery/data_access_notebooks/2022-11-23_pyobis_example.html | There is a reference in the 4th response cell. | Can we simplify and remove the response table? |
https://ioos.github.io/ioos_code_lab/content/code_gallery/data_access_notebooks/2017-06-12-NCEI_RA_archive_history.html -> This is tricky because we are using that text string to search NCEI. I don't know if NCEI has/will update their records to reflect this change. We can test and see what happens.
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
Start with the search results and the three listed notebook pages, then inspect the fourth notebook, 2017-06-12-NCEI_RA_archive_history.html, to verify whether the NCEI query still works with the existing text. Confirm each reference and the response table change before updating the notebooks; done means the requested wording is addressed without breaking the NCEI search.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100