Replace italics below with details for this issue.

Describe the Enhancement

Provide a description of the enhancement request here.

From dtcenter/METplus#1705
The IODA input has "station_ob@MetaData" variable instead of msg_tyoe@MetaData variable which contains the message types.

The name of the message type variable is configured at metadata_map ("message_type" key). The current setting is "msg_type". It will be convenient adding "station_ob" into metadata_map for message_type.

The sample IODA file exists at seneca:/d1/personal/kalb/ioda/raob_all_v1_20201215T1200Z.nc4

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

4 hours

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2799992 - NRL

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 PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

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 Linked 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.