Skip to content

Handle expected no input for ascii2nc and point2grid #1630

@georgemccabe

Description

@georgemccabe

Based on discussion in this MET Help ticket: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=98329

Describe the Enhancement

Logan (NOAA) would like to process data with ascii2nc that occasionally has no obs data, which is expected. When this is the case, we would like ascii2nc to write out a file with no observations in it. This could be a configurable setting in case other users prefer the tool to skip writing a file if no data is present.

The data is then passed into point2grid. It is unclear how point2grid would react to an empty input file. We should also investigate what is needed to handle this situation in that application as well.

Time Estimate

Estimate the amount of work required here.
1 day.

Sub-Issues

No sub-issues required.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2791541

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required: John HG
  • Select scientist(s) or no scientist required: Logan

Labels

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

Projects and Milestone

  • Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
  • Select milestone to next major version milestone 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), Project(s), Milestone, and Linked issues
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Close this issue.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions