[Go-essp-tech] PCMDI URLs in CMOR generated NetCDF

[Karl Taylor]

Hi Stephen,

I think the idea was that the baseURL would point to a catalog that 
would provide the "address?" of  the actual location of the data.  PCMDI 
(and I would think all the gateways) might want copies of the gridspec 
files (which will be tiny compared to most of the data files).  So the 
URL could point to PCMDI's copy, or possibly to the originating copy, 
but that would seem to be more complicated.

The purpose of the attribute is to point the user to somewhere where 
he/she can obtain the gridspec files.

I'm not sure I followed your alternative suggestion. If you think the 
above is inferior, please try again to explain your alternative.

thanks,
Karl


stephen.pascoe at stfc.ac.uk wrote:
> The Hadley centre has noticed that NetCDF coming out of CMOR contain
> gridspec files pointing to PCMDI.  For instance:
>  
> ts:associated_files =
> "baseURL:http://*cmip-pcmdi.llnl.gov/CMIP5/dataLocation
> gridspecFile:gridspec_Amon_HadCM3_esmControl_r0_fx.nc
> cellAreaFile:cellArea_Amon_HadCM3_esmControl_r0_fx.nc
> cellVolumeFile:cellVolume_Amon_HadCM3_esmControl_r0_fx.nc" ;
>
> Is it intended that gridspec files will be held centrally like this?  I
> had thought they would be collocated with the data.  If these baseURL
> fields should point to the datanode how can they be configured in CMOR?
> It would make sense for them to be a DRS URL with a configurable
> hostname.
>
> Cheers,
> Stephen.
>
>  
> ---
> Stephen Pascoe  +44 (0)1235 445980
> British Atmospheric Data Centre
> Rutherford Appleton Laboratory
>