Ensure test/example datasets are all CF compliant
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 11
- Avg merge
- 7h 11m
- Merged PRs (30d)
- 1
Description
We've realised that some of the dataset files we use for the documentation examples and integration testing are not actually CF compliant - so they are really not good to showcase and test on.
So we should (post merge of the #123 big revamp) review all of the datasets we use for these and ensure they are not just fully CF compliant but good exemplars for the specific visualisation case (as summarised by the titles in the form 'Example N: <title>' listing in the 'Plots by type/theme' page of the docs).
It also wouldn't hurt to increase the diversity of datasets we showcase visualisation of with cf-plot (but that could be a separate Issue).
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
Wait for the #123 revamp, then use the “Plots by type/theme” page and its “Example N: <title>” entries to identify the documentation and integration-test datasets. Review each dataset for CF compliance and whether it is a good exemplar for its visualization case. Done means all reviewed datasets meet both criteria and the integration tests still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization, documentation, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100