From: Efren S. <efr...@me...> - 2005-12-02 18:02:41
|
Rob, 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, ...) 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. v/r, Efren -----Original Message----- From: geo...@li... [mailto:geo...@li...]On Behalf Of Woolf, A (Andrew) Sent: Thursday, December 01, 2005 12:32 AM To: Rob Atkinson; efr...@me... Cc: Alexander Petkov; Norman Barker; geo...@li...; Dietmar Muller; Keiran Millard; geotools-devel; Amit Parashar Subject: RE: [Geoserver-devel] Re: [Geoserver-users] netcdf - wcs resource Hi Rob, > am currently trying to organise some effort to get a major > new geotools enhancement (Complex features) into the > Geoserver head, and the WCS support is an obvious target to > try to roll in. Would be grateful if you can identify any > issues, futher development work required to roll that in, and > also if any committed effort for this can be rolled into my > project plan as in-kind support. This sort of in-kind support > will help make the case for the bits of cash we are chasing > to support UI upgrades for the new stuff etc. Usual story - really want this, but no effort to put in... :-( > Is there a UI config for the new WCS stuff? If not, what > needs to be done? If you stick with a small subset (perhaps one) of netCDF conventions you can imagine a netCDF collection 'scanner' that picks out e.g. spatiotemporal metadata defined by those conventions across the fileset, and presents additional configurable options in a GUI. We're working on this in NERC DataGrid for CSML - rather than geoserver config - generation. > In general - we have two requirements in the medium term: > 1) auto-configure WCS for a catalogue of NetCDF files, to > support subsetting actions easily having found a netCDF file > in a catalogue In most atmos/ocean use cases you don't want file-level discovery. You want the aggregated (timeseries) dataset. > 2) be able to subset (in a single WCS call) from collections > of netCDF files across both spatial and temporal dimensions. Yep. > Also, there are many netCDF conventions - what is the > expected level of support and configurability? The 'CF' conventions for atmos/ocean data are the canonical standard: http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html though (as far as I'm aware) not implemented in full *anywhere*. However, an incremental approach can be taken - e.g. starting with independent spatiotemporal coord vbls (http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html#grid_ex1), then sorting 'auxiliary coord vbls' (http://www.cgd.ucar.edu/cms/eaton/cf-metadata/CF-1.0.html#grid_ex2) etc... A large amount of deployed met/ocean netCDF is covered by a small subset of CF. ------------------------------------------------------- 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_idv37&alloc_id865&op=ick _______________________________________________ Geoserver-devel mailing list Geo...@li... https://lists.sourceforge.net/lists/listinfo/geoserver-devel |