[WCS SWG] Subset in KVP requests allows to specify crs, but POST requests are not allowed to
All Fields marked with * are mandatory.
Change Request 257
#:
Assigned OGC 12-167
Document #:
Name: *Andrea Aime
Organization: *GeoSolutions
Email: *[email protected]
Document
Name/Version:
*Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension / 2.0
OGC Project
Document:
*09-147r1
If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:
Title:
Source:
* [WCS SWG] Subset in KVP requests allows to specify crs, but POST requests are n
*Page 3 of the standard document
Work item code:
Category:
* $ # '# #$!
Reason for *
change:
The KVP request style allows to specify trimming or slicing using the following syntax:
dimension [ , crs ] ( intervalOrPoint )
However the equivalent trimming and slicing constructs in POST do not support the notion of a CRS.
Adding to the confusing, there is going to be a separate extension for CRS handling.
Summary of *
change:
Have the CRS be handled the same way in both KVP and POST requests.
Consequences if
not approved:
Clauses affected: *
6.4
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Assigned
Assigned To:
WCS SWG
Disposition:
Referred and Posted
Change Request 257
#:
Assigned OGC 12-167
Document #:
Name: *Andrea Aime
Organization: *GeoSolutions
Email: *[email protected]
Document
Name/Version:
*Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension / 2.0
OGC Project
Document:
*09-147r1
If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:
Title:
Source:
* [WCS SWG] Subset in KVP requests allows to specify crs, but POST requests are n
*Page 3 of the standard document
Work item code:
Category:
* $ # '# #$!
Reason for *
change:
The KVP request style allows to specify trimming or slicing using the following syntax:
dimension [ , crs ] ( intervalOrPoint )
However the equivalent trimming and slicing constructs in POST do not support the notion of a CRS.
Adding to the confusing, there is going to be a separate extension for CRS handling.
Summary of *
change:
Have the CRS be handled the same way in both KVP and POST requests.
Consequences if
not approved:
Clauses affected: *
6.4
Additional
Documents
affected:
Supporting
Documentation:
Comments:
Status:
Assigned
Assigned To:
WCS SWG
Disposition:
Referred and Posted