NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Pauline, Yep the DLWriter is part of it but I think Ted's approach can be captured as well due to the flexibility of netcdf-java. Configuring the metadata is still a big issue yes and its the same issue faced for example when harvesting metadata from services like OGC WMS/WCS. Lots of approaches there but I like the ability of thredds/netcdf-java to create catalogues, inherit metadata etc - it seems to me to be a flexible starting place for developing data-specific apps that read such a catalog and create a new catalog with the metadata configured. More on this once we prove the concept on a few collections :-) Cheers, Simon ________________________________________ From: Pauline Mak [Pauline.Mak@xxxxxxxxxxx] Sent: Tuesday, 14 April 2009 8:47 AM To: Ted Habermann Cc: Pigot, Simon (CMAR, Hobart); rsignell@xxxxxxxxx; thredds@xxxxxxxxxxxxxxxx; Peter.Blain@xxxxxxxxxxx; NGDC Geospatial; Erin Robinson Subject: Re: What would the ISO metadata look like? Hi Ted, I think what Simon is referring to is the THREDDS DLWriter (see http://www.unidata.ucar.edu/projects/THREDDS/tech/reference/DigitalLibraries.html). This assumes that you will have well configured metadata for the datasets as defined here: http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/DL.html. One of the output of the DLWriter is DIF, and some work has been done on converting DIF to ISO19115 (Marine Profile) and ANZLIC documents. I was forwarded an email from Dave Connell and have attached it to this message. As for what the ISO document will look like, you'll have to refer to the spec (hours of fun!) You can also have a look at the Bluenet MEST (http://bluenet.its.utas.edu.au/geonetwork/srv/en/main.home) - I think this is an older version (right Simon?). Anyhow, all the records in there are in ISO19115, so it might give you an idea on what your dataset should look like. I think the big question is, how do we configure the metadata in the first place. Cheers, -Pauline. Ted Habermann wrote: > Simon et al., > > This is the second response inspired by the recent THREDDS discussion. > This one is more ISO focused. Assume that you connected to a THREDDS > Server and were ready to write an ISO metadata record. What would you > actually write? I have been trying to figure this one out for awhile and > submitted this question to EDEN. I would, of course, be interested in > you answer as well as this is a very common THREDDS Server case. > > Thanks, > Ted > > > The grids are: > Attributes > Analysis Temperature: The latest Sea Surface Temperature calculated > based on the previous analysis temperature, weighted according to its > reliability, combined with a weighted average of current observations > within a surrounding area which is determined according to the grid > point's gradient. > > Average Gradient: The average of the gradients in all four directions > (N, S, E, W) from the grid intersection. > > Gradient X+, X-, Y+, Y-: Gradients in various Directions. > > Physiographic Descriptor: The land/sea tag indicating whether a grid > intersection is a land or sea point. > > land_binary_mask (CF name for Physiographic Descriptor): X_binary_mask > has 1 where condition X is met, 0 elsewhere. 1 = land, 0 = sea. > > Ice Field: Percent sea ice for 50 km SST field. > > Number Observations: Number of Observations - The total number of > current obser! vations u e new temperature for the grid intersection. > > Age Recent Observation: Age of Most Recent Observation - The age, in > hours from the time of last analysis, of the most recent observation > used to determine the new temperature for a grid intersection. > > Reliability: New reliability associated with the new temperature, based > on the previous reliability combined with the weighted reliability of > all observations used in the last analysis. > > Class 1 Coverage: Class 1 Temporal Coverage - Set of bits (0-15) of > which bit 1 is set to 1 for each analysis which included observations > with a reliability greater than or equal to a specific minimum > reliability considered as class 1. Bit 0 always remains a 0, and all > bits are shifted right during each analysis ! leaving b reliability > observations are used for a grid intersection. > > Spatial Covariance X+, X-, Y+, Y-: The distance in grid units from the > grid intersection to the nearest land mass in a given direction. > > Climatological Temperature: Independent Grid Temperature - The average > sea surface temperature of a grid intersection for a particular month > over a number of years, taken from the global climatology file. > > ==== Ted Habermann =========================== > Enterprise Data Systems Group Leader > NOAA, National Geophysical Data Center > V: 303.497.6472 F: 303.497.6513 > "If you want to go quickly, go alone. > ! If gether" > Old Proverb > ==== Ted.Habermann@xxxxxxxx > <mailto:Ted.Habermann@xxxxxxxx> ================== > > ------------------------------------------------------------------------ > > -- Pauline Mak ARCS Data Services Ph: (03) 6226 7518 Email: pauline.mak@xxxxxxxxxxx Jabber: pauline.mak@xxxxxxxxxxx http://www.arcs.org.au/ TPAC Email: pauline.mak@xxxxxxxxxxx http://www.tpac.org.au/
thredds archives: