[Met_help] [rt.rap.ucar.edu #88069] History for Format for netcdf forecast files
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 9 12:07:12 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I want to evaluate forecasts, whose files are written in netcdf.
When I test with my netcdf forecast files, it does nor work and I get
warnings like:
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "F
ileType_NcCF".
DEBUG 4: NcCfFile::open() -> could not extract valid time from the "time"
variable.
DEBUG 4: NcCfFile::open() -> could not extract valid time from file name.
DEBUG 4: NcCfFile::open() -> could not extract init time from the
"forecast_reference_time" variable
DEBUG 4: NcCfFile::open() -> could not extract init time from file name.
Could you provide me an example of netcdf file which can be read by MET ?
Thanks
*Blandine L'Hévéder*
Météo - Océan -Climat
blandine.lheveder at gmail.com
tel. 06 62 53 32 37
https://fr.linkedin.com/in/blandine-l-heveder-493171a9
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Format for netcdf forecast files
From: John Halley Gotway
Time: Fri Dec 07 09:26:02 2018
Blandine,
I see that you have some NetCDF files that are not currently readable
by
MET. MET *should* be able to read NetCDF files which follow the
Climate
Forecast convention (i.e. CF-compliant NetCDF). In addition, MET is
able
read it own output NetCDF file format.
You have 2 choices here...
(1) You could reformat your NetCDF files into a format that MET can
read.
(2) Or, if you're using met-8.0, you could write a python script which
reads your data and associated metadata and passes it to the MET tools
via
memory.
If you aren't dealing with very much data and reformatting isn't a big
hurdle, then I'd recommend option (1).
If you do have a lot of data and reformatting is not realistic, then
option
(2) would provide a way forward.
Here's the website for the NetCDF CF-conventions:
http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html
And here's a list of examples of running python scripts to read data
and
pass it to MET:
https://dtcenter.org/met/users/downloads/analysis_scripts.php
Just let me know if you have additional questions.
Thanks,
John Halley Gotway
On Fri, Dec 7, 2018 at 6:27 AM Blandine Lheveder via RT
<met_help at ucar.edu>
wrote:
>
> Fri Dec 07 06:27:10 2018: Request 88069 was acted upon.
> Transaction: Ticket created by blandine.lheveder at gmail.com
> Queue: met_help
> Subject: Format for netcdf forecast files
> Owner: Nobody
> Requestors: blandine.lheveder at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88069 >
>
>
> Hi,
>
> I want to evaluate forecasts, whose files are written in netcdf.
> When I test with my netcdf forecast files, it does nor work and I
get
> warnings like:
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "F
> ileType_NcCF".
> DEBUG 4: NcCfFile::open() -> could not extract valid time from the
"time"
> variable.
> DEBUG 4: NcCfFile::open() -> could not extract valid time from file
name.
> DEBUG 4: NcCfFile::open() -> could not extract init time from the
> "forecast_reference_time" variable
> DEBUG 4: NcCfFile::open() -> could not extract init time from file
name.
>
> Could you provide me an example of netcdf file which can be read by
MET ?
>
> Thanks
>
> *Blandine L'Hévéder*
> Météo - Océan -Climat
>
> blandine.lheveder at gmail.com
> tel. 06 62 53 32 37
> https://fr.linkedin.com/in/blandine-l-heveder-493171a9
>
>
------------------------------------------------
Subject: Format for netcdf forecast files
From: Blandine Lheveder
Time: Thu Dec 13 10:39:50 2018
Hi John,
Thanks for your response.
I have tried to write the netcdf files in a CF-compliant mode and to
mimic
the output files of pcpcombine .
The header of my netcdf forecast file (which I want to test in MET) is
the
following:
netcdf temperature_at_2m_forMET {
dimensions:
time = UNLIMITED ; // (1 currently)
lat = 455 ;
lon = 644 ;
variables:
float air_temperature(lat, lon) ;
air_temperature:valid_time_ut = "1544562000" ;
air_temperature:init_time_ut = "1544526000" ;
air_temperature:valid_time = "20181211_210000" ;
air_temperature:init_time = "20181211_110000" ;
air_temperature:long_name = "air_temperature_at_2m" ;
air_temperature:units = "degK" ;
float lat(lat, lon) ;
lat:standard_name = "latitude" ;
lat:units = "degrees_north" ;
lat:long_name = "latitude" ;
float lon(lat, lon) ;
lon:standard_name = "longitude" ;
lon:units = "degrees_east" ;
lon:long_name = "longitude" ;
float time(time) ;
time:valid_time_ut = "1544562000" ;
time:valid_time = "20181211_210000" ;
float forecast_reference_time(time) ;
forecast_reference_time:init_time_ut = "1544526000" ;
forecast_reference_time:init_time = "20181211_110000" ;
}
Is the name of the variable correct for air temperature at 2m ?
In the point_stat process, MET doesn't recognize
- the variable name and put air_temperature(*,*) (with (*,*) being
the
level)
- the valid_time and put : valid time: 19700101_000000
Could you please help me ?
Thanks a lot
Blandine
*Blandine L'Hévéder*
Météo - Océan -Climat
blandine.lheveder at gmail.com
tel. 06 62 53 32 37
https://fr.linkedin.com/in/blandine-l-heveder-493171a9
Le ven. 7 déc. 2018 à 17:26, John Halley Gotway via RT
<met_help at ucar.edu>
a écrit :
> Blandine,
>
> I see that you have some NetCDF files that are not currently
readable by
> MET. MET *should* be able to read NetCDF files which follow the
Climate
> Forecast convention (i.e. CF-compliant NetCDF). In addition, MET is
able
> read it own output NetCDF file format.
>
> You have 2 choices here...
> (1) You could reformat your NetCDF files into a format that MET can
read.
> (2) Or, if you're using met-8.0, you could write a python script
which
> reads your data and associated metadata and passes it to the MET
tools via
> memory.
>
> If you aren't dealing with very much data and reformatting isn't a
big
> hurdle, then I'd recommend option (1).
> If you do have a lot of data and reformatting is not realistic, then
option
> (2) would provide a way forward.
>
> Here's the website for the NetCDF CF-conventions:
>
>
> http://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-
conventions.html
>
> And here's a list of examples of running python scripts to read data
and
> pass it to MET:
> https://dtcenter.org/met/users/downloads/analysis_scripts.php
>
> Just let me know if you have additional questions.
>
> Thanks,
> John Halley Gotway
>
>
> On Fri, Dec 7, 2018 at 6:27 AM Blandine Lheveder via RT
<met_help at ucar.edu
> >
> wrote:
>
> >
> > Fri Dec 07 06:27:10 2018: Request 88069 was acted upon.
> > Transaction: Ticket created by blandine.lheveder at gmail.com
> > Queue: met_help
> > Subject: Format for netcdf forecast files
> > Owner: Nobody
> > Requestors: blandine.lheveder at gmail.com
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=88069 >
> >
> >
> > Hi,
> >
> > I want to evaluate forecasts, whose files are written in netcdf.
> > When I test with my netcdf forecast files, it does nor work and I
get
> > warnings like:
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "F
> > ileType_NcCF".
> > DEBUG 4: NcCfFile::open() -> could not extract valid time from the
"time"
> > variable.
> > DEBUG 4: NcCfFile::open() -> could not extract valid time from
file name.
> > DEBUG 4: NcCfFile::open() -> could not extract init time from the
> > "forecast_reference_time" variable
> > DEBUG 4: NcCfFile::open() -> could not extract init time from file
name.
> >
> > Could you provide me an example of netcdf file which can be read
by MET ?
> >
> > Thanks
> >
> > *Blandine L'Hévéder*
> > Météo - Océan -Climat
> >
> > blandine.lheveder at gmail.com
> > tel. 06 62 53 32 37
> > https://fr.linkedin.com/in/blandine-l-heveder-493171a9
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list