Enhance MET tools to define map data using GIS shapefiles #1012
Labels
alert: NEED ACCOUNT KEY
Need to assign an account key to this issue
alert: NEED CYCLE ASSIGNMENT
Need to assign to a release development cycle
MET: Plotting Tools
priority: high
High Priority
requestor: Community
General Community
type: enhancement
Improve something that it is currently doing
Milestone
Describe the Enhancement
Several MET tools generate plots, including Plot-Data-Plane, Plot-Point-Obs, MODE, and Wavelet-Stat. They read static map data files bundled with the MET tarball to do so. The default map data settings and defined in the ConfigMapData file.
Over the years that static map data has caused several headaches. It eventually becomes out of date and requires updates. However, updating it is somewhat tedious. It is currently based on Natural Earth shapefiles which come in 3 different resolutions (110m, 50m, and 10m) and are updated relatively frequently. Of course, higher resolution map data makes for much larger PostScript output files which take longer to create and render.
This task it to add the option of defining map data using GIS shapefiles instead of this custom map data format. Doing so is beneficial for several reasons.
For backward compatibility, MET should continue to support the custom data file format. However, rather than distributing custom map data files, recommend that we distributed either 50m or 110m resolution shapefiles.
Time Estimate
2 days.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
No sub-issues needed.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Linked 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: