Enhance TC-RMW to reorder the dimensions of the NetCDF output to store the gridded dimensions last #2523
Closed
8 of 21 tasks
Labels
MET: Tropical Cyclone Tools
priority: high
High Priority
requestor: METplus Team
METplus Development Team
type: enhancement
Improve something that it is currently doing
Milestone
Describe the Enhancement
During development for MET #2168, it was noted that the NetCDF output generated by the TC-Diag tool should order the NetCDF output dimensions as time, lat, lon. The python diagnostics code expects the dimensions to be ordered in this way. I also see this convention in WRF files:
And in SWPC NetCDF output files:
While the CF-convention does NOT force an order for the dimensions, the earlier COARDS convention does, as described in this section. And it is generally encouraged to considered to continue with this ordering for compatibility with existing tools, such as
ncview
.This task is to reorder the dimensions of the NetCDF output from the
tc_rmw
tool to list the range and azimuth dimensions last. So change...FROM:
double TMP(range, azimuth, pressure, track_point) ;
TO:
double TMP(track_point, pressure, range, azimuth) ;
Time Estimate
4 hours.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
None needed
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
TC-Diag project 2770043
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Thanks @bikegeek for finding the code to generate TCRMW plots in METplotpy:
https://github.com/dtcenter/METplotpy/blob/develop/metplotpy/contributed/tc_rmw/plot_fields.py
Its reads in data via read_tcrmw in the tc_utils.py:
https://github.com/dtcenter/METplotpy/blob/develop/metplotpy/contributed/tc_rmw/tc_utils.py
These will need to be updated.
Enhancement Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
The text was updated successfully, but these errors were encountered: