[Thread Prev][Thread Next][Index]

Re: Grib



Adam,

A good suggestion. Thank you. As a first cut, I have added the text of the email from Joe and a link to the scripts to the FAQ-o-matic documentation.

Roland

Adam Baxter wrote:

Guys,
Thank you for your help and quick responses. I greatly appreciate it.
You might want to add some of this to your documentation, however. It doesn't mention anything about GDS and that was my main guide for setting LAS up.
Just a suggestion,
Adam Baxter

Joe Mclean wrote:

Hi Adam,
You and I had some e-correspondance back around December 21. You wrote that you have GDS servers at nomads.ncdc.noaa.gov:9090 and nomads.ncdc.noaa.gov:9091. The LAS documentation concerning adding gridded data at http://ferret.pmel.noaa.gov/LASdoc/serve/cache/16.html will guide you through the process of configuring LAS for these datasets, just use the GDS OPeNDAP URL instead of a file name for the dataset url attribute and for running addXml.pl
Joe

Roland Schweitzer wrote:

Adam,

The most straight forward way to use LAS with grib files is to use some "middle-ware" to handle the translation from grib to netCDF on-the-fly.

In my opinion the best tool for this job (there are certainly others) is the GrADS Data Server (http://grads.iges.org/grads/gds/gds.html). You install GrADS and GDS and configure GDS to serve your grib files. Clients (like LAS) that want to interact with these data will be able to do so using the netCDF API as if the files were actually stored in netCDF even though they will remain in grib. There is some overhead, but the process in efficient enough to work with LAS.

Roland

Adam Baxter wrote:

Hello,
I've been searching through the LAS documentation and I haven't found any information on how to point LAS at grib files. The documentation describes how to convert our grib files into NetCDF, but with gigs of data that's not really possible.
Any suggestions?

Adam Baxter








[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement