Efren Serra wrote:
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.
My money would be on duplication, the RDBMS would want to completly
store the Coverage would it not?
(Your arrow goes both ways in your diagram).
That said you may have more luck keeping the searchable metadata in your
RDBMS, and running a file cache
on the side to store the actual rasters. If you hide it behind an API it
would be identical in use to storing the
coverages in the RDBMS, and would be much less risk then taking on an
RnD task.
Question for coverage types, I was working on the GeoTools RnD Page the
other day, updating its status & timelines.
Are you still content with the targets (Early next Year = January right
now), and descriptions there?
Jody
-------------------------------------------------------
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
