Ticket #650 (closed issue: wontfix)

Opened 14 years ago

Last modified 14 years ago

[DS] WFS output format

Reported by: lawrence Owned by: awoolf
Priority: blocker Milestone: Reporting
Component: CSML Version:
Keywords: WFS DCIP C-SEKT Cc:


Our WFS needs to return both xml and data as a payload (I think). THe last thing we want to do is zip them up though, as unzipping a netcdf binary file is a thankless task.

Can we return a tuple (xml,netcdf)? If not, how can we do this?

Change History

comment:1 Changed 14 years ago by lawrence

I should say that it's not obvious we can use multipart MIME, although surely that's what we would want to do ... although I'm assuming using MIME types doesn't imply an ASCI encoding ... or does it?

comment:2 Changed 14 years ago by spascoe

Taking a look at the MIME wikipedia page it looks like you can encode raw binary in MIME multipart using "Content-transfer-encoding: binary". The restriction is that it can't be transferred over vanilla SMTP, which isn't appropriate here.

However, what is wrong with downloading the XML and NetCDF as separate WFS calls? I guess this would require a stateful WFS. I still think this is worth considering.

comment:3 Changed 14 years ago by lawrence

  • Keywords WFS, DCIP added; WFS removed

I guess it might come back to how we choose to handle the relationship between the feature (xml) and the storage descriptor, and the data at the end of the links. It might be better to do it with a WFS call followed by a WCS call (or a WFS enhanced as proposed so it can do WCS as well). In which case your proposal is fine. The question then becomes, what do the two calls look like! Can someone write down for me what the query would be to get the binary content from a WFS now? (Needs CSML schema knowledge I guess).

comment:4 Changed 14 years ago by awoolf

  • Status changed from new to assigned
  • Milestone changed from PROD to Reporting and Futures

Decision was to focus on WCS.

In any case, the root issue here is bound up with defining precisely how xlink is used, because CSML as an output format points to binary data using xlink (in the case of our on-disk data it goes via a StorageDecriptor? for aggregation etc).

The expected interaction pattern is to retrieve a CSML document with xlink to a single http binary resource (either WCS or flat file).

comment:5 Changed 14 years ago by selatham

  • Status changed from assigned to new
  • Keywords NERC-portals added
  • Owner changed from awoolf to spascoe
  • Milestone changed from Reporting to portal1

WFS not in NDG2 timescale. NERC portals?

comment:6 Changed 14 years ago by selatham

  • Keywords WFS C-SEKT added; WFS, NERC-portals removed
  • Owner changed from spascoe to awoolf
  • Milestone changed from portal1 to Reporting

This is going to C-SEKT.

comment:7 Changed 14 years ago by selatham

  • Status changed from new to closed
  • Resolution set to wontfix
Note: See TracTickets for help on using tickets.