#2701 added support for ISMN soil moisture and temperature data in ASCII2NC. This support reads a single file in Header+Values format, and writes the data to MET's observation NetCDF file format. In reality, for a given time there are hundreds or perhaps more individual files (for each site in the ISMN) that a user would likely desire to process. The only way to do this currently is to provide a command to ASCII2NC listing each file individually.

As far as I can tell, all ISMN files that ASCII2NC supports end with .stm, so perhaps a -lookin argument like Stat-Analysis could be added so ASCII2NC can recursively search a directory for all .stm files if the -format argument specifies ismn for ASCII2NC. This would greatly increase the utility of using ISMN data with ASCII2NC.

Time Estimate

1 day (8 hours)

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2785031 DYN VEG DROUGHT

Define the Metadata

Assignee

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

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
• Need a METplus issue to update the ASCII2NC Wrapper to handle any new command line options.

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 issue
  Select: Milestone as the next official version
  Select: MET-X.Y Development project for development toward the next coordinated release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.