[Met_help] [rt.rap.ucar.edu #74310] History for problems in reading netcdf file with mode command
John Halley Gotway via RT
met_help at ucar.edu
Tue Jan 26 12:13:13 MST 2016
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
To whom it may concern,
i am trying to read a WRF-netcdf file having the following attributes
ncdump -h pr_day_WRF_h1e4_1980.nc
netcdf pr_day_WRF_h1e4_1980 {
dimensions:
x = 900 ;
y = 804 ;
time = UNLIMITED ; // (367 currently)
variables:
double lon(y, x) ;
lon:standard_name = "longitude" ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:_CoordinateAxisType = "Lon" ;
double lat(y, x) ;
lat:standard_name = "latitude" ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:_CoordinateAxisType = "Lat" ;
double time(time) ;
time:standard_name = "time" ;
time:units = "days since 1949-12-01 00:00:00" ;
time:calendar = "standard" ;
float pr(time, y, x) ;
pr:standard_name = "precipitation_flux" ;
pr:long_name = "Precipitation" ;
pr:units = "kg m-2 s-1" ;
pr:coordinates = "lon lat" ;
pr:_FillValue = 1.e+20f ;
pr:original_name = "RAINC+RAINNC" ;
pr:cell_methods = "time: mean (interval: 3 hours)" ;
:Conventions = "CF-1.4" ;
:notes = "Created with NCL script: wrfout_to_cordex.ncl
v1.2b" ;
and i am using the following command:
mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
MODEConfig_tutorial_antonio -outdir /share/home/antonio/express_hydro/ -v
where the file MODEConfig_tutorial_antonio is attached.
However i am receiving the following error message:
DEBUG 1: Default Config File:
/share/home/antonio/francesca/MET/met-5.0/share/met/config/MODEConfig_default
DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
ERROR :
ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1980.nc"
ERROR :
Any idea or suggestion?
Thank you
best regards
Antonio
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: problems in reading netcdf file with mode command
From: John Halley Gotway
Time: Tue Dec 08 10:58:10 2015
Antonio,
I see that you've used NCL to attempt to convert WRF netcdf output
into a
CF-compliant NetCDF file. Unfortunately, the result isn't readable by
the
MET software. Looking at the NetCDF header you sent, I see that it
lacks a
definition of the grid/projection on which the data resides. There's
a
CF-compliant way of defining that grid information, and I don't see it
in
your file. MET does support a special case for data that's defined on
a
lat/lon grid. However, in that case, the lat and lon variables would
only
be 1 dimension instead of 2.
So how to proceed...
(1) The best way forward is to post-process your WRFOUT files using
the
Unified Post Processor. It's GRIB output is fully supported by MET:
http://www.dtcenter.org/wrf-nmm/users/overview/upp_overview.php
(2) A second option is using the wrf_interp or p_interp utilities for
WRF-ARW output:
http://www2.mmm.ucar.edu/wrf/users/utilities/util.htm
These tools interpolate the native model output to pressure levels.
MET is
able to read data from the non-staggered variables... the mass points
instead of the vector points, i.e. wind data.
Hope that helps.
Thanks,
John
On Mon, Dec 7, 2015 at 6:08 AM, Antonio Parodi via RT
<met_help at ucar.edu>
wrote:
>
> Mon Dec 07 06:08:40 2015: Request 74310 was acted upon.
> Transaction: Ticket created by Antonio.parodi at cimafoundation.org
> Queue: met_help
> Subject: problems in reading netcdf file with mode command
> Owner: Nobody
> Requestors: Antonio.parodi at cimafoundation.org
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>
>
> To whom it may concern,
>
> i am trying to read a WRF-netcdf file having the following
attributes
>
> ncdump -h pr_day_WRF_h1e4_1980.nc
> netcdf pr_day_WRF_h1e4_1980 {
> dimensions:
> x = 900 ;
> y = 804 ;
> time = UNLIMITED ; // (367 currently)
> variables:
> double lon(y, x) ;
> lon:standard_name = "longitude" ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:_CoordinateAxisType = "Lon" ;
> double lat(y, x) ;
> lat:standard_name = "latitude" ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:_CoordinateAxisType = "Lat" ;
> double time(time) ;
> time:standard_name = "time" ;
> time:units = "days since 1949-12-01 00:00:00" ;
> time:calendar = "standard" ;
> float pr(time, y, x) ;
> pr:standard_name = "precipitation_flux" ;
> pr:long_name = "Precipitation" ;
> pr:units = "kg m-2 s-1" ;
> pr:coordinates = "lon lat" ;
> pr:_FillValue = 1.e+20f ;
> pr:original_name = "RAINC+RAINNC" ;
> pr:cell_methods = "time: mean (interval: 3 hours)"
;
>
> :Conventions = "CF-1.4" ;
> :notes = "Created with NCL script:
wrfout_to_cordex.ncl
> v1.2b" ;
>
> and i am using the following command:
>
> mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/ -v
>
> where the file MODEConfig_tutorial_antonio is attached.
>
> However i am receiving the following error message:
>
> DEBUG 1: Default Config File:
>
> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
> ERROR :
> ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1980.nc"
> ERROR :
>
> Any idea or suggestion?
>
> Thank you
>
> best regards
>
> Antonio
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #74310] problems in reading netcdf file with mode command
From: Antonio Parodi
Time: Tue Dec 08 11:35:20 2015
Hello John
thank you for your email and explanation.
If i understand properly i have to re-process all the data in case i
want to use MET...
Is it not acceptable simply to add to the files the definition of the
grid/projection on which the data resides?
Thanks
All the best
Antonio
Il 08/12/15 18:58, John Halley Gotway via RT ha scritto:
> Antonio,
>
> I see that you've used NCL to attempt to convert WRF netcdf output
into a
> CF-compliant NetCDF file. Unfortunately, the result isn't readable
by the
> MET software. Looking at the NetCDF header you sent, I see that it
lacks a
> definition of the grid/projection on which the data resides.
There's a
> CF-compliant way of defining that grid information, and I don't see
it in
> your file. MET does support a special case for data that's defined
on a
> lat/lon grid. However, in that case, the lat and lon variables
would only
> be 1 dimension instead of 2.
>
> So how to proceed...
>
> (1) The best way forward is to post-process your WRFOUT files using
the
> Unified Post Processor. It's GRIB output is fully supported by MET:
> http://www.dtcenter.org/wrf-nmm/users/overview/upp_overview.php
>
> (2) A second option is using the wrf_interp or p_interp utilities
for
> WRF-ARW output:
> http://www2.mmm.ucar.edu/wrf/users/utilities/util.htm
> These tools interpolate the native model output to pressure levels.
MET is
> able to read data from the non-staggered variables... the mass
points
> instead of the vector points, i.e. wind data.
>
> Hope that helps.
>
> Thanks,
> John
>
> On Mon, Dec 7, 2015 at 6:08 AM, Antonio Parodi via RT
<met_help at ucar.edu>
> wrote:
>
>> Mon Dec 07 06:08:40 2015: Request 74310 was acted upon.
>> Transaction: Ticket created by Antonio.parodi at cimafoundation.org
>> Queue: met_help
>> Subject: problems in reading netcdf file with mode command
>> Owner: Nobody
>> Requestors: Antonio.parodi at cimafoundation.org
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>>
>>
>> To whom it may concern,
>>
>> i am trying to read a WRF-netcdf file having the following
attributes
>>
>> ncdump -h pr_day_WRF_h1e4_1980.nc
>> netcdf pr_day_WRF_h1e4_1980 {
>> dimensions:
>> x = 900 ;
>> y = 804 ;
>> time = UNLIMITED ; // (367 currently)
>> variables:
>> double lon(y, x) ;
>> lon:standard_name = "longitude" ;
>> lon:long_name = "longitude" ;
>> lon:units = "degrees_east" ;
>> lon:_CoordinateAxisType = "Lon" ;
>> double lat(y, x) ;
>> lat:standard_name = "latitude" ;
>> lat:long_name = "latitude" ;
>> lat:units = "degrees_north" ;
>> lat:_CoordinateAxisType = "Lat" ;
>> double time(time) ;
>> time:standard_name = "time" ;
>> time:units = "days since 1949-12-01 00:00:00" ;
>> time:calendar = "standard" ;
>> float pr(time, y, x) ;
>> pr:standard_name = "precipitation_flux" ;
>> pr:long_name = "Precipitation" ;
>> pr:units = "kg m-2 s-1" ;
>> pr:coordinates = "lon lat" ;
>> pr:_FillValue = 1.e+20f ;
>> pr:original_name = "RAINC+RAINNC" ;
>> pr:cell_methods = "time: mean (interval: 3
hours)" ;
>>
>> :Conventions = "CF-1.4" ;
>> :notes = "Created with NCL script:
wrfout_to_cordex.ncl
>> v1.2b" ;
>>
>> and i am using the following command:
>>
>> mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
>> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/ -v
>>
>> where the file MODEConfig_tutorial_antonio is attached.
>>
>> However i am receiving the following error message:
>>
>> DEBUG 1: Default Config File:
>>
>> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
>> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
>> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
>> ERROR :
>> ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1980.nc"
>> ERROR :
>>
>> Any idea or suggestion?
>>
>> Thank you
>>
>> best regards
>>
>> Antonio
>>
>>
>>
>>
------------------------------------------------
Subject: problems in reading netcdf file with mode command
From: John Halley Gotway
Time: Tue Dec 08 11:45:25 2015
Antonio,
Sure, you could edit the "wrfout_to_cordex.ncl" NCL script to add in
the
CF-compliant definition... or write some other script to add more
information to it's output. Unfortunately, there are several details
to
work through. Here's the CF documentation:
http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
In the long run, I'd suggest adding a post-processing step to the end
of
your model generation scripts. And using UPP works very well for
that.
Thanks,
John
On Tue, Dec 8, 2015 at 11:35 AM, Antonio Parodi via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>
> Hello John
>
> thank you for your email and explanation.
>
> If i understand properly i have to re-process all the data in case i
> want to use MET...
>
> Is it not acceptable simply to add to the files the definition of
the
> grid/projection on which the data resides?
>
> Thanks
>
> All the best
>
> Antonio
>
> Il 08/12/15 18:58, John Halley Gotway via RT ha scritto:
> > Antonio,
> >
> > I see that you've used NCL to attempt to convert WRF netcdf output
into a
> > CF-compliant NetCDF file. Unfortunately, the result isn't
readable by
> the
> > MET software. Looking at the NetCDF header you sent, I see that
it
> lacks a
> > definition of the grid/projection on which the data resides.
There's a
> > CF-compliant way of defining that grid information, and I don't
see it in
> > your file. MET does support a special case for data that's
defined on a
> > lat/lon grid. However, in that case, the lat and lon variables
would
> only
> > be 1 dimension instead of 2.
> >
> > So how to proceed...
> >
> > (1) The best way forward is to post-process your WRFOUT files
using the
> > Unified Post Processor. It's GRIB output is fully supported by
MET:
> > http://www.dtcenter.org/wrf-
nmm/users/overview/upp_overview.php
> >
> > (2) A second option is using the wrf_interp or p_interp utilities
for
> > WRF-ARW output:
> > http://www2.mmm.ucar.edu/wrf/users/utilities/util.htm
> > These tools interpolate the native model output to pressure
levels. MET
> is
> > able to read data from the non-staggered variables... the mass
points
> > instead of the vector points, i.e. wind data.
> >
> > Hope that helps.
> >
> > Thanks,
> > John
> >
> > On Mon, Dec 7, 2015 at 6:08 AM, Antonio Parodi via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> Mon Dec 07 06:08:40 2015: Request 74310 was acted upon.
> >> Transaction: Ticket created by Antonio.parodi at cimafoundation.org
> >> Queue: met_help
> >> Subject: problems in reading netcdf file with mode command
> >> Owner: Nobody
> >> Requestors: Antonio.parodi at cimafoundation.org
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310
> >
> >>
> >>
> >> To whom it may concern,
> >>
> >> i am trying to read a WRF-netcdf file having the following
attributes
> >>
> >> ncdump -h pr_day_WRF_h1e4_1980.nc
> >> netcdf pr_day_WRF_h1e4_1980 {
> >> dimensions:
> >> x = 900 ;
> >> y = 804 ;
> >> time = UNLIMITED ; // (367 currently)
> >> variables:
> >> double lon(y, x) ;
> >> lon:standard_name = "longitude" ;
> >> lon:long_name = "longitude" ;
> >> lon:units = "degrees_east" ;
> >> lon:_CoordinateAxisType = "Lon" ;
> >> double lat(y, x) ;
> >> lat:standard_name = "latitude" ;
> >> lat:long_name = "latitude" ;
> >> lat:units = "degrees_north" ;
> >> lat:_CoordinateAxisType = "Lat" ;
> >> double time(time) ;
> >> time:standard_name = "time" ;
> >> time:units = "days since 1949-12-01 00:00:00" ;
> >> time:calendar = "standard" ;
> >> float pr(time, y, x) ;
> >> pr:standard_name = "precipitation_flux" ;
> >> pr:long_name = "Precipitation" ;
> >> pr:units = "kg m-2 s-1" ;
> >> pr:coordinates = "lon lat" ;
> >> pr:_FillValue = 1.e+20f ;
> >> pr:original_name = "RAINC+RAINNC" ;
> >> pr:cell_methods = "time: mean (interval: 3
hours)" ;
> >>
> >> :Conventions = "CF-1.4" ;
> >> :notes = "Created with NCL script:
> wrfout_to_cordex.ncl
> >> v1.2b" ;
> >>
> >> and i am using the following command:
> >>
> >> mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
> >> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/
> -v
> >>
> >> where the file MODEConfig_tutorial_antonio is attached.
> >>
> >> However i am receiving the following error message:
> >>
> >> DEBUG 1: Default Config File:
> >>
> >>
> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
> >> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
> >> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
> >> ERROR :
> >> ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1980.nc"
> >> ERROR :
> >>
> >> Any idea or suggestion?
> >>
> >> Thank you
> >>
> >> best regards
> >>
> >> Antonio
> >>
> >>
> >>
> >>
>
>
>
------------------------------------------------
Subject: problems in reading netcdf file with mode command
From: Antonio Parodi
Time: Tue Dec 15 11:49:03 2015
Dear John
now the metadata read as it follows, where i highlighted in bold the
added fields with the help of my colleague Francesca (cc)
dimensions:
x = 900 ;
y = 804 ;
time = UNLIMITED ; // (366 currently)
variables:
double lon(y, x) ;
lon:standard_name = "longitude" ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:_CoordinateAxisType = "Lon" ;
double lat(y, x) ;
lat:standard_name = "latitude" ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:_CoordinateAxisType = "Lat" ;
double time(time) ;
time:standard_name = "time" ;
time:units = "days since 1949-12-01 00:00:00" ;
time:calendar = "standard" ;
float pr(time, y, x) ;
pr:standard_name = "precipitation_flux" ;
pr:long_name = "Precipitation" ;
pr:units = "kg m-2 s-1" ;
pr:coordinates = "lon lat" ;
pr:_FillValue = 1.e+20f ;
pr:original_name = "RAINC+RAINNC" ;
pr:cell_methods = "time: mean (interval: 3 hours)" ;
*pr:level = "A12" *;
// global attributes:
:CDI = "Climate Data Interface version 1.5.5
(http://code.zmaw.de/projects/cdi)" ;
:history = "Sun Nov 29 00:13:11 2015: cdo daysum
pr_3hr_WRF_h1e4_1979.nc pr_day_WRF_h1e4_1979.nc\nWed Sep 16 21:02:20
2015: cdo -f nc4 -z zip -b 32 seltimestep,2/2921
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/pr_fullyear_c1979_1979.nc
/galileo/home/userexternal/jvonhard/scratch/postproc/h1e4/pr/3hr/pr_3hr_WRF_h1e4_1979.nc\nWed
Sep 16 21:00:00 2015: cdo cat
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197901_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197902_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197903_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197904_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197905_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197906_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197907_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197908_pr.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197909_pr.nc\nFri
Sep 11 15:05:24 2015: cdo splitvar
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197901.nc
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197901_\nFri
Sep 11 11:43:13 2015: cdo -b 64 cat
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_00:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_03:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_06:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_09:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_12:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_15:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_18:00:00.nc
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_21:00:00.nc"
;
:institution = "Institute fo Atmospheric Sciences and
Climate - CNR" ;
:Conventions = "CF-1.4" ;
:notes = "Created with NCL script:
wrfout_to_cordex.ncl
v1.2b" ;
:created_by = "Jost von Hardenberg -
j.vonhardenberg at isac.cnr.it" ;
:title = "wrfpost.nc" ;
:product = "output" ;
:CORDEX_domain = "EUR-11" ;
:project_id = "CORDEX" ;
:rcm_version_id = "v3.4.1" ;
:model_id = "WRF" ;
:institute_id = "ISAC-CNR" ;
:driving_experiment_name = "evaluation" ;
:driving_model_ensemble_member = "r1i1p1" ;
:driving_model_id = "ERAINT" ;
:driving_experiment = "ERA-INTERIM,evaluation,r1i1p1"
;
:experiment_id = "evaluation" ;
:experiment = "Evaluation run with reanalysis
forcing" ;
:creation_date = "Tue Oct 15 21:19:06 CEST 2013" ;
:contact = "j.vonhardenberg at isac.cnr.it" ;
:CDO = "Climate Data Operators version 1.5.5
(http://code.zmaw.de/projects/cdo)" ;
* :MET_version = "V5.0" ;**
** :Projection = "LatLon" ;**
** :delta_lat = "0.037 degrees" ;**
** :delta_lon = "0.037 degrees" ;**
** :Nlat = "900 grid_points" ;**
** :Nlon = "804 grid_points" ;**
** :lon_ll = "-7.7514" ;**
** :lat_ll = "31.3724" ;
*}
Still i am having the followin error message: do you have any idea?
antonio at drihm:~/express_hydro$
/share/home/antonio/francesca/MET/met-5.0/bin/mode
pr_day_WRF_h1e4_1979_BK.nc pr_day_WRF_h1e4_1979_BK.nc
MODEConfig_tutorial_antonio -outdir /share/home/antonio/express_hydro/
-v 1000
DEBUG 1: Default Config File:
/share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_None".
ERROR :
ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1979_BK.nc"
ERROR :
thanks
All the best
Antonio
Il 08/12/15 19:45, John Halley Gotway via RT ha scritto:
> Antonio,
>
> Sure, you could edit the "wrfout_to_cordex.ncl" NCL script to add in
the
> CF-compliant definition... or write some other script to add more
> information to it's output. Unfortunately, there are several
details to
> work through. Here's the CF documentation:
>
> http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
>
> In the long run, I'd suggest adding a post-processing step to the
end of
> your model generation scripts. And using UPP works very well for
that.
>
> Thanks,
> John
>
>
>
>
>
> On Tue, Dec 8, 2015 at 11:35 AM, Antonio Parodi via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>>
>> Hello John
>>
>> thank you for your email and explanation.
>>
>> If i understand properly i have to re-process all the data in case
i
>> want to use MET...
>>
>> Is it not acceptable simply to add to the files the definition of
the
>> grid/projection on which the data resides?
>>
>> Thanks
>>
>> All the best
>>
>> Antonio
>>
>> Il 08/12/15 18:58, John Halley Gotway via RT ha scritto:
>>> Antonio,
>>>
>>> I see that you've used NCL to attempt to convert WRF netcdf output
into a
>>> CF-compliant NetCDF file. Unfortunately, the result isn't
readable by
>> the
>>> MET software. Looking at the NetCDF header you sent, I see that
it
>> lacks a
>>> definition of the grid/projection on which the data resides.
There's a
>>> CF-compliant way of defining that grid information, and I don't
see it in
>>> your file. MET does support a special case for data that's
defined on a
>>> lat/lon grid. However, in that case, the lat and lon variables
would
>> only
>>> be 1 dimension instead of 2.
>>>
>>> So how to proceed...
>>>
>>> (1) The best way forward is to post-process your WRFOUT files
using the
>>> Unified Post Processor. It's GRIB output is fully supported by
MET:
>>> http://www.dtcenter.org/wrf-
nmm/users/overview/upp_overview.php
>>>
>>> (2) A second option is using the wrf_interp or p_interp utilities
for
>>> WRF-ARW output:
>>> http://www2.mmm.ucar.edu/wrf/users/utilities/util.htm
>>> These tools interpolate the native model output to pressure
levels. MET
>> is
>>> able to read data from the non-staggered variables... the mass
points
>>> instead of the vector points, i.e. wind data.
>>>
>>> Hope that helps.
>>>
>>> Thanks,
>>> John
>>>
>>> On Mon, Dec 7, 2015 at 6:08 AM, Antonio Parodi via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> Mon Dec 07 06:08:40 2015: Request 74310 was acted upon.
>>>> Transaction: Ticket created by Antonio.parodi at cimafoundation.org
>>>> Queue: met_help
>>>> Subject: problems in reading netcdf file with mode command
>>>> Owner: Nobody
>>>> Requestors: Antonio.parodi at cimafoundation.org
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310
>>>>
>>>> To whom it may concern,
>>>>
>>>> i am trying to read a WRF-netcdf file having the following
attributes
>>>>
>>>> ncdump -h pr_day_WRF_h1e4_1980.nc
>>>> netcdf pr_day_WRF_h1e4_1980 {
>>>> dimensions:
>>>> x = 900 ;
>>>> y = 804 ;
>>>> time = UNLIMITED ; // (367 currently)
>>>> variables:
>>>> double lon(y, x) ;
>>>> lon:standard_name = "longitude" ;
>>>> lon:long_name = "longitude" ;
>>>> lon:units = "degrees_east" ;
>>>> lon:_CoordinateAxisType = "Lon" ;
>>>> double lat(y, x) ;
>>>> lat:standard_name = "latitude" ;
>>>> lat:long_name = "latitude" ;
>>>> lat:units = "degrees_north" ;
>>>> lat:_CoordinateAxisType = "Lat" ;
>>>> double time(time) ;
>>>> time:standard_name = "time" ;
>>>> time:units = "days since 1949-12-01 00:00:00"
;
>>>> time:calendar = "standard" ;
>>>> float pr(time, y, x) ;
>>>> pr:standard_name = "precipitation_flux" ;
>>>> pr:long_name = "Precipitation" ;
>>>> pr:units = "kg m-2 s-1" ;
>>>> pr:coordinates = "lon lat" ;
>>>> pr:_FillValue = 1.e+20f ;
>>>> pr:original_name = "RAINC+RAINNC" ;
>>>> pr:cell_methods = "time: mean (interval: 3
hours)" ;
>>>>
>>>> :Conventions = "CF-1.4" ;
>>>> :notes = "Created with NCL script:
>> wrfout_to_cordex.ncl
>>>> v1.2b" ;
>>>>
>>>> and i am using the following command:
>>>>
>>>> mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
>>>> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/
>> -v
>>>> where the file MODEConfig_tutorial_antonio is attached.
>>>>
>>>> However i am receiving the following error message:
>>>>
>>>> DEBUG 1: Default Config File:
>>>>
>>>>
>> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
>>>> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
>>>> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
>>>> ERROR :
>>>> ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1980.nc"
>>>> ERROR :
>>>>
>>>> Any idea or suggestion?
>>>>
>>>> Thank you
>>>>
>>>> best regards
>>>>
>>>> Antonio
>>>>
>>>>
>>>>
>>>>
>>
>>
------------------------------------------------
Subject: problems in reading netcdf file with mode command
From: John Halley Gotway
Time: Wed Dec 16 10:45:12 2015
Antonio,
I see that you added the following global attributes to your NetCDF
file to
define the grid information:
* :MET_version = "V5.0" ;**
** :Projection = "LatLon" ;**
** :delta_lat = "0.037 degrees" ;**
** :delta_lon = "0.037 degrees" ;**
** :Nlat = "900 grid_points" ;**
** :Nlon = "804 grid_points" ;**
** :lon_ll = "-7.7514" ;**
** :lat_ll = "31.3724" ;
Unfortunately, you're mixing NetCDF file formats here MET won't be
able to
read the file.
MET can read 3 different formats of NetCDF files:
(1) The output of the pinterp (or wrf_interp) utility for WRF-ARW
data.
(2) Gridded CF-compliant NetCDF files where the grid is defined as
prescribed by the CF-convention.
(3) Gridded MET NetCDF files which look like the output of the MET
pcp_combine tool.
You're mixing formats (2) and (3) here. If you'd like to stick with
the
CF-convention, try defining that grid in the CF way:
http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
Or you could switch to making it look like the NetCDF output of the
MET
tools, but that's a very limited format which isn't as general as the
CF-convention.
Ultimately, I'd still recommend post-processing your WRF output with
UPP
which creates GRIB files which MET handles well.
Thanks,
John
On Tue, Dec 15, 2015 at 11:49 AM, Antonio Parodi via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>
> Dear John
>
> now the metadata read as it follows, where i highlighted in bold the
> added fields with the help of my colleague Francesca (cc)
>
> dimensions:
> x = 900 ;
> y = 804 ;
> time = UNLIMITED ; // (366 currently)
> variables:
> double lon(y, x) ;
> lon:standard_name = "longitude" ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:_CoordinateAxisType = "Lon" ;
> double lat(y, x) ;
> lat:standard_name = "latitude" ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:_CoordinateAxisType = "Lat" ;
> double time(time) ;
> time:standard_name = "time" ;
> time:units = "days since 1949-12-01 00:00:00" ;
> time:calendar = "standard" ;
> float pr(time, y, x) ;
> pr:standard_name = "precipitation_flux" ;
> pr:long_name = "Precipitation" ;
> pr:units = "kg m-2 s-1" ;
> pr:coordinates = "lon lat" ;
> pr:_FillValue = 1.e+20f ;
> pr:original_name = "RAINC+RAINNC" ;
> pr:cell_methods = "time: mean (interval: 3 hours)"
;
> *pr:level = "A12" *;
>
> // global attributes:
> :CDI = "Climate Data Interface version 1.5.5
> (http://code.zmaw.de/projects/cdi)" ;
> :history = "Sun Nov 29 00:13:11 2015: cdo daysum
> pr_3hr_WRF_h1e4_1979.nc pr_day_WRF_h1e4_1979.nc\nWed Sep 16 21:02:20
> 2015: cdo -f nc4 -z zip -b 32 seltimestep,2/2921
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> pr_fullyear_c1979_1979.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/postproc/h1e4/pr/3hr/pr_3hr_WRF_h1e4_1979.nc\nWed
> Sep 16 21:00:00 2015: cdo cat
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197901_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197902_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197903_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197904_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197905_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197906_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197907_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197908_pr.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197909_pr.nc\nFri
> Sep 11 15:05:24 2015: cdo splitvar
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/
> wrfpost_c1979_197901.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/tmpdir_wrfout/tmpdir_h1e4/chunk1979/1979/wrfpost_c1979_197901_\nFri
> Sep 11 11:43:13 2015: cdo -b 64 cat
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_00:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_03:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_06:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_09:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_12:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_15:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_18:00:
> 00.nc
>
>
/galileo/home/userexternal/jvonhard/scratch/wrfpost/h1e4/he79/post/d02/197901/wrfpost_d02_1979-
01-01_21:00:
> 00.nc"
> ;
> :institution = "Institute fo Atmospheric Sciences
and
> Climate - CNR" ;
> :Conventions = "CF-1.4" ;
> :notes = "Created with NCL script:
wrfout_to_cordex.ncl
> v1.2b" ;
> :created_by = "Jost von Hardenberg -
> j.vonhardenberg at isac.cnr.it" ;
> :title = "wrfpost.nc" ;
> :product = "output" ;
> :CORDEX_domain = "EUR-11" ;
> :project_id = "CORDEX" ;
> :rcm_version_id = "v3.4.1" ;
> :model_id = "WRF" ;
> :institute_id = "ISAC-CNR" ;
> :driving_experiment_name = "evaluation" ;
> :driving_model_ensemble_member = "r1i1p1" ;
> :driving_model_id = "ERAINT" ;
> :driving_experiment = "ERA-
INTERIM,evaluation,r1i1p1" ;
> :experiment_id = "evaluation" ;
> :experiment = "Evaluation run with reanalysis
forcing" ;
> :creation_date = "Tue Oct 15 21:19:06 CEST 2013" ;
> :contact = "j.vonhardenberg at isac.cnr.it" ;
> :CDO = "Climate Data Operators version 1.5.5
> (http://code.zmaw.de/projects/cdo)" ;
> * :MET_version = "V5.0" ;**
> ** :Projection = "LatLon" ;**
> ** :delta_lat = "0.037 degrees" ;**
> ** :delta_lon = "0.037 degrees" ;**
> ** :Nlat = "900 grid_points" ;**
> ** :Nlon = "804 grid_points" ;**
> ** :lon_ll = "-7.7514" ;**
> ** :lat_ll = "31.3724" ;
> *}
>
> Still i am having the followin error message: do you have any idea?
>
> antonio at drihm:~/express_hydro$
> /share/home/antonio/francesca/MET/met-5.0/bin/mode
> pr_day_WRF_h1e4_1979_BK.nc pr_day_WRF_h1e4_1979_BK.nc
> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/
> -v 1000
> DEBUG 1: Default Config File:
>
> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_None".
> ERROR :
> ERROR : Trouble reading forecast file "pr_day_WRF_h1e4_1979_BK.nc"
> ERROR :
>
> thanks
>
> All the best
>
> Antonio
>
>
> Il 08/12/15 19:45, John Halley Gotway via RT ha scritto:
> > Antonio,
> >
> > Sure, you could edit the "wrfout_to_cordex.ncl" NCL script to add
in the
> > CF-compliant definition... or write some other script to add more
> > information to it's output. Unfortunately, there are several
details to
> > work through. Here's the CF documentation:
> >
> >
> http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
> >
> > In the long run, I'd suggest adding a post-processing step to the
end of
> > your model generation scripts. And using UPP works very well for
that.
> >
> > Thanks,
> > John
> >
> >
> >
> >
> >
> > On Tue, Dec 8, 2015 at 11:35 AM, Antonio Parodi via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
> >>
> >> Hello John
> >>
> >> thank you for your email and explanation.
> >>
> >> If i understand properly i have to re-process all the data in
case i
> >> want to use MET...
> >>
> >> Is it not acceptable simply to add to the files the definition of
the
> >> grid/projection on which the data resides?
> >>
> >> Thanks
> >>
> >> All the best
> >>
> >> Antonio
> >>
> >> Il 08/12/15 18:58, John Halley Gotway via RT ha scritto:
> >>> Antonio,
> >>>
> >>> I see that you've used NCL to attempt to convert WRF netcdf
output
> into a
> >>> CF-compliant NetCDF file. Unfortunately, the result isn't
readable by
> >> the
> >>> MET software. Looking at the NetCDF header you sent, I see that
it
> >> lacks a
> >>> definition of the grid/projection on which the data resides.
There's a
> >>> CF-compliant way of defining that grid information, and I don't
see it
> in
> >>> your file. MET does support a special case for data that's
defined on
> a
> >>> lat/lon grid. However, in that case, the lat and lon variables
would
> >> only
> >>> be 1 dimension instead of 2.
> >>>
> >>> So how to proceed...
> >>>
> >>> (1) The best way forward is to post-process your WRFOUT files
using the
> >>> Unified Post Processor. It's GRIB output is fully supported by
MET:
> >>> http://www.dtcenter.org/wrf-
nmm/users/overview/upp_overview.php
> >>>
> >>> (2) A second option is using the wrf_interp or p_interp
utilities for
> >>> WRF-ARW output:
> >>> http://www2.mmm.ucar.edu/wrf/users/utilities/util.htm
> >>> These tools interpolate the native model output to pressure
levels.
> MET
> >> is
> >>> able to read data from the non-staggered variables... the mass
points
> >>> instead of the vector points, i.e. wind data.
> >>>
> >>> Hope that helps.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On Mon, Dec 7, 2015 at 6:08 AM, Antonio Parodi via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> Mon Dec 07 06:08:40 2015: Request 74310 was acted upon.
> >>>> Transaction: Ticket created by
Antonio.parodi at cimafoundation.org
> >>>> Queue: met_help
> >>>> Subject: problems in reading netcdf file with mode
command
> >>>> Owner: Nobody
> >>>> Requestors: Antonio.parodi at cimafoundation.org
> >>>> Status: new
> >>>> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310
> >>>>
> >>>> To whom it may concern,
> >>>>
> >>>> i am trying to read a WRF-netcdf file having the following
attributes
> >>>>
> >>>> ncdump -h pr_day_WRF_h1e4_1980.nc
> >>>> netcdf pr_day_WRF_h1e4_1980 {
> >>>> dimensions:
> >>>> x = 900 ;
> >>>> y = 804 ;
> >>>> time = UNLIMITED ; // (367 currently)
> >>>> variables:
> >>>> double lon(y, x) ;
> >>>> lon:standard_name = "longitude" ;
> >>>> lon:long_name = "longitude" ;
> >>>> lon:units = "degrees_east" ;
> >>>> lon:_CoordinateAxisType = "Lon" ;
> >>>> double lat(y, x) ;
> >>>> lat:standard_name = "latitude" ;
> >>>> lat:long_name = "latitude" ;
> >>>> lat:units = "degrees_north" ;
> >>>> lat:_CoordinateAxisType = "Lat" ;
> >>>> double time(time) ;
> >>>> time:standard_name = "time" ;
> >>>> time:units = "days since 1949-12-01
00:00:00" ;
> >>>> time:calendar = "standard" ;
> >>>> float pr(time, y, x) ;
> >>>> pr:standard_name = "precipitation_flux" ;
> >>>> pr:long_name = "Precipitation" ;
> >>>> pr:units = "kg m-2 s-1" ;
> >>>> pr:coordinates = "lon lat" ;
> >>>> pr:_FillValue = 1.e+20f ;
> >>>> pr:original_name = "RAINC+RAINNC" ;
> >>>> pr:cell_methods = "time: mean (interval: 3
hours)"
> ;
> >>>>
> >>>> :Conventions = "CF-1.4" ;
> >>>> :notes = "Created with NCL script:
> >> wrfout_to_cordex.ncl
> >>>> v1.2b" ;
> >>>>
> >>>> and i am using the following command:
> >>>>
> >>>> mode pr_day_WRF_h1e4_1980.nc pr_day_WRF_h1e4_1980.nc
> >>>> MODEConfig_tutorial_antonio -outdir
/share/home/antonio/express_hydro/
> >> -v
> >>>> where the file MODEConfig_tutorial_antonio is attached.
> >>>>
> >>>> However i am receiving the following error message:
> >>>>
> >>>> DEBUG 1: Default Config File:
> >>>>
> >>>>
> >>
> /share/home/antonio/francesca/MET/met-
5.0/share/met/config/MODEConfig_default
> >>>> DEBUG 1: Match Config File: MODEConfig_tutorial_antonio
> >>>> DEBUG 1: Merge Config File: MODEConfig_tutorial_antonio
> >>>> ERROR :
> >>>> ERROR : Trouble reading forecast file
"pr_day_WRF_h1e4_1980.nc"
> >>>> ERROR :
> >>>>
> >>>> Any idea or suggestion?
> >>>>
> >>>> Thank you
> >>>>
> >>>> best regards
> >>>>
> >>>> Antonio
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #74310] problems in reading netcdf file with mode command
From: Antonio Parodi
Time: Wed Dec 16 16:28:14 2015
Hello
i don't see any information for gridded data at this link
http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
where am i wrong?
thanks
All the best
Antonio
Il 16/12/15 18:45, John Halley Gotway via RT ha scritto:
> If you'd like to stick with the
> CF-convention, try defining that grid in the CF way:
>
> http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
------------------------------------------------
Subject: problems in reading netcdf file with mode command
From: John Halley Gotway
Time: Wed Dec 16 16:55:36 2015
Antonio,
Since you're dealing with a lat/lon grid, try switching from writing
2-dimesional lat/lon variables to 1-dimensional. Listed below is an
example of a CF-compliant NetCDF file that MET reads well. Notice
that the
data variable (edr) has an attribute named "grid_mapping" which lists
the
name of the variable which defines it... in this case, that variable
is
also named grid_mapping.
In that CF document, the definitions of grid mappings can be found in
Appendix F.
Hope this helps.
John
netcdf gtg_obs_forecast.20130827.i12.f06 {
dimensions:
lat = 361 ;
lon = 720 ;
z = 26 ;
name_len = 32 ;
time = 1 ;
variables:
int grid_mapping ;
grid_mapping:grid_mapping_name = "latitude_longitude"
;
grid_mapping:semi_major_axis = 6371000. ;
grid_mapping:inverse_flattening = 0 ;
double time(time) ;
time:long_name = "forecast time" ;
time:units = "seconds since 1970-1-1" ;
time:axis = "T" ;
double forecast_reference_time ;
forecast_reference_time:long_name = "reference time" ;
forecast_reference_time:units = "seconds since 1970-1-
1" ;
int forecast_period ;
forecast_period:units = "seconds" ;
double lat(lat) ;
lat:units = "degrees_north" ;
lat:long_name = "latitude coordinate" ;
lat:standard_name = "latitude" ;
lat:_CoordinateAxisType = "Lat" ;
double lon(lon) ;
lon:units = "degrees_east" ;
lon:long_name = "longitude coordinate" ;
lon:standard_name = "longitude" ;
lon:_CoordinateAxisType = "Lon" ;
double z(z) ;
z:standard_name = "altitude" ;
z:long_name = "flight_level" ;
z:units = "feet" ;
z:positive = "up" ;
z:axis = "Z" ;
int field_id ;
field_id:long_name = "field indentification number" ;
char field_name(name_len) ;
field_name:long_name = "field name" ;
float edr(time, z, lat, lon) ;
edr:units = "m^(2/3) s^-1" ;
edr:long_name = "Median eddy dissipation rate" ;
edr:coordinates = "lat lon" ;
edr:_FillValue = -9999.f ;
edr:grid_mapping = "grid_mapping" ;
// global attributes:
:Conventions = "CF-1.4" ;
:Originating_center = "NCAR" ;
:Product_Status = "Experimental Products" ;
:Product_Type = "Forecast/Uninitialized Analysis" ;
:DataType = "GRID" ;
:DatasetLocation = "" ;
}
On Wed, Dec 16, 2015 at 4:28 PM, Antonio Parodi via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=74310 >
>
> Hello
>
> i don't see any information for gridded data at this link
>
>
> http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
>
>
> where am i wrong?
>
> thanks
>
> All the best
>
> Antonio
>
> Il 16/12/15 18:45, John Halley Gotway via RT ha scritto:
> > If you'd like to stick with the
> > CF-convention, try defining that grid in the CF way:
> >
> >
> http://cfconventions.org/Data/cf-conventions/cf-conventions-
1.6/build/cf-conventions.html
>
>
>
------------------------------------------------
More information about the Met_help
mailing list