[Go-essp-tech] esg publisher, thredds and netcdf attributes

[Bob Drach]

Hi Stephen,

See

http://esg-pcmdi.llnl.gov/internal/metadata/sample_per_variable_1.xml/view

for an annotated sample schema. It's probably the closest to what you  
are asking for. Yes it would be useful to have an XSD document that  
defined which parts of the THREDDS schema ESG actually uses. Also keep  
in mind that the catalog structure may well continue to evolve. In  
particular there is a request from the LAS folks to combine the  
variable-specific aggregations into larger union aggregations to cut  
down on the number of datasets LAS has to track.

Bob

On Jun 9, 2010, at 4:17 AM, <stephen.pascoe at stfc.ac.uk> wrote:

>
> I understood from yesterday's ESGF telco that Bob and Anne are already
> working on the datanode's THREDDS XML in the context of  
> replication.  I
> think we need to document the format of the THREDDS XML as served by  
> ESG
> datanodes.  We should also document which bits of the ESG architecture
> depend on this format.  For instance, if we changed the format what
> would break?
>
> What Bryan is getting at is some means of identifying properties like
> tracking_id as the CMOR tracking_id.  I expect this could be done in
> many ways from just tagging the properties with an authority to
> embedding arbitrary XML inside <metadata> elements.  This is why we  
> need
> to know what depends on the current format.
>
> Is this something we could put together with input from the rest of  
> ESGF
> or does it exist already?
>
> Cheers,
> Stephen.
>
>
> ---
> Stephen Pascoe  +44 (0)1235 445980
> British Atmospheric Data Centre
> Rutherford Appleton Laboratory
>
> -----Original Message-----
> From: go-essp-tech-bounces at ucar.edu
> [mailto:go-essp-tech-bounces at ucar.edu] On Behalf Of Bryan Lawrence
> Sent: 09 June 2010 10:13
> To: Bob Drach
> Cc: go-essp-tech at ucar.edu
> Subject: [Go-essp-tech] esg publisher, thredds and netcdf attributes
>
> Hi Bob
>
> As you know, we're in the process of building a tool to parse the
> thredds catalogs produced by esg-publisher.
>
> We're sitting in a meeting looking at the Thredds XML.
>
> At the moment there are dataset properties which reflect attributes  
> from
> the files, and some which come from esg-publisher. From the point of
> view of automatically consuming these catalogs, we can't tell the
> difference between these attributes.
>
> For example, the checksum information we presume comes from esg-
> publisher, and the tracking-id from internal attributes file.
>
> Is it possible in Thredds to distinguish between these things? It's
> pretty important for unpicking the origin of the information which
> appears in the catalog.
>
> Thanks
> Bryan
>
> --
> Bryan Lawrence
> Director of Environmental Archival and Associated Research (NCAS/ 
> British
> Atmospheric Data Centre and NCEO/NERC NEODC) STFC, Rutherford Appleton
> Laboratory Phone +44 1235 445012; Fax ... 5848;
> Web: home.badc.rl.ac.uk/lawrence
> _______________________________________________
> GO-ESSP-TECH mailing list
> GO-ESSP-TECH at ucar.edu
> http://*mailman.ucar.edu/mailman/listinfo/go-essp-tech
> -- 
> Scanned by iCritical.
>