Re: Re: GMU WCS Server supports netCDF output

• To: "yliu5@xxxxxxx" <yliu5@xxxxxxx>
• Subject: Re: Re: GMU WCS Server supports netCDF output
• From: Denis Nadeau <denis.nadeau@xxxxxxxxx>
• Date: Thu, 25 Aug 2005 19:22:43 -0400

Hi,
I tried to write some code to read grid_mapping as stipulate in Appendix F.

But, I got some problems with the example file RUC.nc.  
Lambert_Conformal_projection did not have a standard_parallel #2 variable, and 
I did not know how to convert it to OGR. (The code is comment out at th e end 
of netcdfdataset.cpp for futur implementation. )

Regards,
Denis

---------- Message transf=E9r=E9 ----------
From: yliu5@xxxxxxx
To: warmerdam@xxxxxxxxx
Date: Thu, 25 Aug 2005 16:07:43 -0400
Subject: Re: GMU WCS Server supports netCDF output
Hi Frank,

I believe the file is correct. Please refer to CF conventions document at

http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html

Chapter 5.6 and Appendix F.

Actually the data is in UTM projection, but I can't find how to specify
UTM in netCDF. So I used Transverse Mercator instead. Is there any other way

to specify projections?

There are two variables called xdim and ydim. From them you can get the
x-coordinate and y-coordinate of every pixel. Therefore we can get anything
we want such as the offset, origin, etc. And also there are lat/lon
variables storing the lat/lon of every pixel. That makes the netCDF file
much larger than the original HDF-EOS file. If you have any better idea to
avoid those unnecessary variables, please let me know. Thanks.

Regards,
Yang Liu
LAITS,GMU

• Follow-Ups:
  • Re: GMU WCS Server supports netCDF output
    • From: John Caron

• References:
  • Fwd: Re: GMU WCS Server supports netCDF output
    • From: yliu5