[Met_help] [rt.rap.ucar.edu #82155] History for NetCDF CF-Compliance

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

In our initial development of the QPF Verification System for the NWS, our
group in NOAA/NWS/MDL is building a prototype viewer and hope to use the
viewer to demonstrate capabilities in an upcoming requirements review with
the NWS. The reason for stating this is the NetCDF output generated by the
MET tools are not CF-compliant, and we were hoping to use the NetCDF files
in the prototype viewer which requires CF-compliant files.

In an earlier exchange with John Gotway, he said using a script to reformat
the existing MET NetCDF output to follow CF conventions would be pretty
straight-forward with the longer term goal of MET producing them directly.

In summary, the aforementioned requirements review is in mid-October and we
were wondering if we could obtain the script soon. If not, there is a work
around so that we could still use the prototype viewer in the review. We
are willing to be testers for the CF-compliance ensuring the encoding works.

Thanks for your consideration in this matter,

Brad Diehl


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: NetCDF CF-Compliance
From: John Halley Gotway
Time: Thu Sep 28 15:40:38 2017

Brad,

Thanks for laying out the issues we discussed last week.  Please
correct me
if I'm wrong, but I believe you're operating on a single domain.  Am I
correct in recalling that it's the URMA domain?

If the domain remains fixed, modifying the NetCDF output files from
MET to
make them CF-compliant should be pretty straight-forward.  Handling
one
domain should be pretty easy... but handling all possible domains is
the
difficult part that will take some development.

Three questions:
(1) Am I correct in thinking that we only need to handle a single
domain
definition?
(2) If so, can you define which one?
(3) Are there any requirements for the scripting language?  Using nco
tools
(like ncatted)?  Python? R?
What's the preference?

Thanks,
John Halley Gotway



On Thu, Sep 28, 2017 at 2:15 PM, Brad Diehl - NOAA Federal via RT <
met_help at ucar.edu> wrote:

>
> Thu Sep 28 14:15:21 2017: Request 82155 was acted upon.
> Transaction: Ticket created by brad.diehl at noaa.gov
>        Queue: met_help
>      Subject: NetCDF CF-Compliance
>        Owner: Nobody
>   Requestors: brad.diehl at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82155 >
>
>
> In our initial development of the QPF Verification System for the
NWS, our
> group in NOAA/NWS/MDL is building a prototype viewer and hope to use
the
> viewer to demonstrate capabilities in an upcoming requirements
review with
> the NWS. The reason for stating this is the NetCDF output generated
by the
> MET tools are not CF-compliant, and we were hoping to use the NetCDF
files
> in the prototype viewer which requires CF-compliant files.
>
> In an earlier exchange with John Gotway, he said using a script to
reformat
> the existing MET NetCDF output to follow CF conventions would be
pretty
> straight-forward with the longer term goal of MET producing them
directly.
>
> In summary, the aforementioned requirements review is in mid-October
and we
> were wondering if we could obtain the script soon. If not, there is
a work
> around so that we could still use the prototype viewer in the
review. We
> are willing to be testers for the CF-compliance ensuring the
encoding
> works.
>
> Thanks for your consideration in this matter,
>
> Brad Diehl
>
>

------------------------------------------------