Re: [thredds] catalog of multiple Thredds catalogs [SEC=UNCLASSIFIED]

• To: Frank Erjiang Fu <F.Fu@xxxxxxxxxx>
• Subject: Re: [thredds] catalog of multiple Thredds catalogs [SEC=UNCLASSIFIED]
• From: Michael McDonald <mcdonald@xxxxxxxxxxxxx>
• Date: Mon, 9 May 2016 08:31:12 -0400

On Mon, May 9, 2016 at 12:28 AM, Frank Erjiang Fu <F.Fu@xxxxxxxxxx> wrote:
>
> Is it possible to create a Thredds dataset to link another Thredds dataset? I 
> don’t remember where I read it can be done.
>
> For example, Thredds 1 has datasets A and B, Thredds 2 has datasets C and D. 
> I would like to have Thredds 3 which has datasets A and C from Thredds 1 and 
> Thredds 2.


I think I understand what you are trying to do. You can use the
following "netcdf location=" to reference a remote/local OPeNDAP
dataset within another dataset. We use this method to create
smaller/managable (1 year) datasets with "like" variables and then
union together each individual 1-year var dataset into a higher level
dataset with all vars combined. Just use "dods://" to wherever the
OPeNDAP URL is. We then take it one step more & union those yearly
datasets into another higher level dataset to include multiple years
of data in another dataset.

<netcdf location="dods://...">

e.g.,
<netcdf location="dods://tds.hycom.org/thredds/dodsC/GLBa0.08/latest/2d"/>


http://tds.hycom.org/thredds/GLBa0.08/latest.html


I talk in more detail about this here,
http://www.unidata.ucar.edu/mailing_lists/archives/thredds/2013/msg00457.html


note: We changed the hostname "localhost" to "tds.hycom.org" (our
DNS-RR pool of THREDDS servers) so that our OPeDAP queries are better
load balanced.


-- 
Michael McDonald
Florida State University

• Follow-Ups:
  • Re: [thredds] catalog of multiple Thredds catalogs [SEC=UNCLASSIFIED]
    • From: Frank Erjiang Fu

• References:
  • [thredds] catalog of multiple Thredds catalogs [SEC=UNCLASSIFIED]
    • From: Frank Erjiang Fu