Skip to content

Enhance ASCII2NC to support IABP/IPAB Arctic and Antarctic drifting buoy observations #2654

@JohnHalleyGotway

Description

@JohnHalleyGotway

Describe the Enhancement

This enhancement request arose via GitHub discussion dtcenter/METplus#2312. Please see this comment from that discussion for more information about the IABP/IPAB Arctic and Antarctic drifting buoy observation dataset.

Some details to note:

  • Dataset description: https://iabp.apl.uw.edu/data.html
  • Sample data: https://iabp.apl.uw.edu/WebData/
  • The data is stored in one ASCII file per buoy. So each file many contain months or years of data for each buoy.
  • Enhance ASCII2NC to read this data source.
  • In particular, extract the meteorological observations of temperature and pressure (along with any others).

Also enhance ASCII2NC to filter data by time. Currently, ASCII2NC can compute time summaries through the config file but cannot filter the input data by time. Recommend adding valid_beg and valid_end config options to support by time. pb2nc already supports this using the obs_window config option or -valid_beg and -valid_end command line options.

This will provide flexibility in how ASCII2NC is run to process the data. Users many want the input/output files the same with each file containing all obs for a single buoy. Or they may want to extract obs from all the buoys for some time window (e.g. daily or monthly perhaps). Filtering by time provides that option.

Could also consider filtering in space by supporting the mask config option, but that's not explicitly needed for this data. This feature request moved to #2754.

Time Estimate

3 days?

Sub-Issues

Consider breaking the enhancement down into sub-issues.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2784543 NOAA R2O METp SW2

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Select component(s)
  • Select priority
  • Select requestor(s)

Projects and Milestone

  • Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
  • Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

Enhancement Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of develop.
    Branch name: feature_<Issue Number>_<Description>
  • Complete the development and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into develop.
    Pull request: feature <Issue Number> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issues
    Select: Repository level development cycle Project for the next official release
    Select: Milestone as the next official version
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions