Thank you for your response.  This is our current state of affairs, where
MBL (Metoc Broker Language), JMBL (Joint Metoc Broker Language):

+-> MBL <-+ +-> ... | | |
Client(s) <--+-> JMBL     <-+--> File Encoding Cache  <--+-> IEEE format
w/header data source

                        |              |    (GRIB, netCDF, ...)     |
+-> GML <-+ +-> RDBMS with GIS
support (Orcale Spatial, PostgreSQL + PostGIS, ...)

Sorry - I'm not really sure I understand this.. Maybe text wrapping has destroyed it, but it not obvious. Maybe its a notation I'm not familiar withj.


I was wondering, when providing netCDF support for WCS, whether the RDBMS
with GIS support would store metadata pertinent to the netCDF file or
whether it would have to duplicate the existing data in the netCDF file in
the RDBMS with GIS support.  Thank you.

I would think that, in general, catalogs need to extract metadata from "extrinsic objects" into a series of metadata slots to support discovery and interpretation before incurreing the expense (time, bandwidth, computing resources, possibly economic) of accessing the data object.

The exact set of metadata slots, and the usage of controlled vocabularies within them is the tricky bit of course. This is "infrastructure design" and in itself ought to be standardised. The main thing missing is the lack of infrastructure projects willing to look deeper than traditional "descriptive metadata" into these sort of issues, so there is a bit of a vacuum as to what this common solution would look like.

So, to attack that particular problem I'd look at the areas of commonality across metadata for gridded data formats, and map this into a flexible ebRIM structure, using ISO terminology where possible. I'd be tempted to start looking with JPEG2000 format as probably the most comprehensive starting point (but I'm not claiming to be an expert in this!)

Rob A

v/r,
Efren

Efren:

There shouldn't be any need to duplicate the data in the netCDF file.

Alex




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to