GALEON :: OGC Huntsville, 2006-mar-08 IUB GALEON Status Update Huntsville, 2006-mar-08 Peter Baumann, Ivan Delchev International University Bremen, rasdaman GmbH

2 GALEON :: OGC Huntsville, 2006-mar-08 Implementation Work Project Goal: Implement WCS server that stores NetCDF data within a standard relational database, using the rasdaman toolkit Architecture: Client stub- for inhouse testing Java servlet - translate WCS request into rasdaman query language; pipe result from rasdaman to client rasdaman - evaluate query, package result PostgreSQL-maintain data in BLOBs Implemented by CS students, mainly Ivan Delchev Neither them, nor me, with geo education; GML coords/CRS! Great Guinean pigs: Ran into virtually any misunderstanding you can have

3 GALEON :: OGC Huntsville, 2006-mar-08 Findings Some issues WCS w/o semantics definition: Any coverage values returned ok as long as metadata fit We use XML + SOAP/WSDL, however, clients sometimes want KVP, sometimes XML, sometimes both; abandon KVP in OGC? Current status Imports NetCdf, delivers JPEG, BMP, TIFF, PNG Limited interop with Cadcorp, UniFlorence clients (thanks to both for their help!) List of change requests and issues, phrased against WCS 1.1 draft Paperware: 8-page coverage response description (now Section 10.4 in WCS 1.1) 12 editorial change requests to WCS semantic change requests to WCS issues (4 solved meantime, 6 pending, 1 to be written)[ Ivan Delchev ]

4 GALEON :: OGC Huntsville, 2006-mar-08 Most Recent Issue: SOAP SOAP IUB using Xerces + Axis (Jakarta tool for SOAP service implementation) Schema-based transparent marshalling and unmarshalling Axis SOAP Service Style Variants: RPC (default): SOAP "section 5" encoding Document: no encoding (eg, no multiref object serialization) Wrapped: like Document, but with "unwrapping" of objects Message: "raw" - arbitrary XML in SOAP Envelope w/o type mapping / data binding Q: Obviously a source of incompatibility – should WCS (and other OGC standards) fix service style?

5 GALEON :: OGC Huntsville, 2006-mar-08 Summary Implementation continues, to achieve full interoperability Resource issue due to lack of funding, piggybacking with TA job GALEON extremely helpful for WCS 1.1 Even independently from NetCDF - discussions stipulated within WCS.RWG, many change requests incorporated in WCS 1.1