[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Serving local netCDF files though DODS

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: Serving local netCDF files though DODS
  • Date: Thu, 04 Nov 2004 13:08:10 -0700
John,

Thanks for the info.

James

On Thu, 2004-11-04 at 12:18, John Caron wrote:
> James Gallagher wrote:
> 
> >On Wed, 2004-11-03 at 17:30, Tennessee James Leeuwenburg wrote:
> >  
> >
> >>I am able to server local netCDF files from the current version of the 
> >>Thredds server. I have been struggling to get remote files working, so 
> >>my understanding may be flawed, but as far as I can tell, this is how 
> >>things work.
> >>
> >>Thredds uses a "service" to work out how to fetch your data. Each data 
> >>set has a "service" which you specify by "name" which says how the data 
> >>should be fetched. You can have a "NetCDF" serviceType for NetCDF data, 
> >>or "DODS" for data fetched from a DODS server. The "base" for local 
> >>netCDF files should point to a directory on your filesystem, including 
> >>any trailing "/".
> >>    
> >>
> >
> >Thanks for the info. I've set up several Aggregation Servers, but always
> >using OPeNDAP servers, never using local netCDF files. One question: the
> >"base"; that pathname is usually relative in the examples I've seen.
> >Relative to what?
> >
> >James
> >  
> >
> reletive to the catalog URL.
-- 
__________________________________________________________________________
   James Gallagher                                         OPeNDAP, Inc.
   address@hidden                         http://www.opendap.org
   Voice/Fax: 406.723.8663