Discussion #2625

TG for DLS using WCS: Should we align with ISO and mandate HTTP POST (not HTTP GET)

Added by James Passmore almost 5 years ago. Updated almost 5 years ago.

Status:New
Priority:Normal
Assignee:-

Description

ref: OGC Coverages DWG wiki

September 2014: OGC Technical Meeting in Calgary:

  • OGC approaches ISO TC211 to adopt OGC GMLCOV, WCS Core, and WCS POST/XML as ISO standards.

 

Should we be aligned with this ISO standardization process and mandate WCS to use HTTP POST to be conformant and not HTTP GET?

 

History

#1 Updated by Jukka Rahkonen almost 5 years ago

If WCS POST/XML is accepted, does it really mean that older WCS GET-KVP corrigendum version 1.0.1 is now deprecated? It would be a pity because http GET-KVP is rather human readable and it could offer one possible route to pre-defined datasets

http://demo.opengeo.org/geoserver/wcs?service=WCS&version=2.0.1&request=getcoverage&coverageid=nurc__Img_Sample&subset=Lat("20","30")&subset=Long("-100","-80")

 

#2 Updated by James Passmore almost 5 years ago

Jukka Rahkonen wrote:

If WCS POST/XML is accepted, does it really mean that older WCS GET-KVP corrigendum version 1.0.1 is now deprecated? It would be a pity because http GET-KVP is rather human readable and it could offer one possible route to pre-defined datasets http://demo.opengeo.org/geoserver/wcs?service=WCS&version=2.0.1&request=getcoverage&coverageid=nurc__Img_Sample&subset=Lat("20","30")&subset=Long("-100","-80")  

No, this doesn't deprecate http GET-KVP support or indeed any other protocols,  this is just about what we would require as a minimum to ensure compliance.  In reality I think that most software will support both HTTP GET and HTTP POST/XML protocols.  

For example using the demo.opengeo.org service example we can see that both are supported:

<ows:Profile>

http://www.opengis.net/spec/WCS_protocol-binding_get-kvp/1.0.1

</ows:Profile>

<ows:Profile>

http://www.opengis.net/spec/WCS_protocol-binding_post-xml/1.0

</ows:Profile>

But thinking ahead, if WCS 2.0 becomes an ISO standard based on at least HTTP POST/XML support, then you could see an ISO compliant service which isn't INSPIRE compliant becuase in INSPIRE we have said HTTP GET-KVP is the minimum requirement, and in ISO it is HTTP POST/XML.

 

 

Also available in: Atom PDF