110 likes | 244 Views
Interoperability Options. ESIP Federation: 6 January 2005. OGC OPeNDAP. . . This set of slides is the result of one part of the Workshop portion of the Data Access/Transport Protocols track of the ESIP Meeting. The moderator And note taker was James Gallagher.
E N D
Interoperability Options ESIP Federation: 6 January 2005 OGC OPeNDAP This set of slides is the result of one part of the Workshop portion of the Data Access/Transport Protocols track of the ESIP Meeting. The moderator And note taker was James Gallagher.
Options: OPeNDAP WFSOPeNDAP WCSWFS OPeNDAP WCS OPeNDAP
OPeNDAP -> WCS • One case of interop experiment to be proposed to OGC
Options: OPeNDAP WCS • Adopt OPeNDAP as a WKB • Will not be very useful to many users; not what they expect • Develop an OPeNDAP+WCS superset • Conceptual level mismatch makes this impractical. • Build an OPeNDAP WCS gateway • Best choice: Still serve ODAP comm, WCS comm can access data.
Long-term view • Abstract: build abstract model using existing things (Common Data Model: NetCDF4, HDF5, DAP4) • Includes interaction patterns • Build concrete example based on existing components • OPeNDAP/WCS
Ancillary Data Server 2. Ancillary data. May be in separate location Or in OPeNDAP or THREDDS 1. WCS Request WCS OPeNDAP Gateway 3. (Repeat as necessary) 5. Data Request 8. WCS Response OPeNDAP Server 6. Response 4. Construct OPeNDAP Data Request using e.g., GetCoverage & Ancillary data 7. Convert OPeNDAP Data into Requested Data Encoding Format, e.g. HDF, netCDF, … Figure from George Percivall, Drawn by Jose Garcia.
Containers In WCS some semantic metadata is required and there is the possibility of adding additional metadata - free.
Other protocols • ADDE • DiGIR • ESML • Similar/analogous to DAP’s DAS/DDS