NetCDFWriter

Open
#289 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

The payload names no files, tests or entry points, only the NetCDF project site and a user request for optional automated QA/QC flagging. Before any code, a newcomer would need to find the project's existing writer components and decide what a NetCDF output should contain and how flags would be stored, which is a design question for maintainers. Done would mean an agreed specification and a maintainer decision on scope, not a patch.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

https://www.unidata.ucar.edu/software/netcdf/

User request: "possibly with some automated QA/QC flagging."

Dominant language
Python
Stars
57
Forks
30
Avg merge
3h 14m
Merged PRs (30d)
56

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OceanDataTools/openrvdas

All issues in OceanDataTools/openrvdas

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.