Skip to content

Commit

Permalink
Range Subsetting: Improvements and addressing opengeospatial#162
Browse files Browse the repository at this point in the history
- Issue opengeospatial#162: Additional requirement component regarding field order
- Using 'fields' rather than 'bands' as it is a more general term
- Clearer separate requirement regarding RangeType
- Simplified redundant text
  • Loading branch information
jerstlouis committed Apr 13, 2022
1 parent 1a9e608 commit d4c8cff
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 8 deletions.
9 changes: 5 additions & 4 deletions standard/clause_8_3_range-subset.adoc
Original file line number Diff line number Diff line change
@@ -1,10 +1,11 @@
[[rc-range-subset-section]]
== Requirements Class Range Subset

The Range Subset Requirements Class defines the `properties` parameter for selecting a subset of the DataRecord fields (defined in the Range Type, e.g. individual imagery bands) to retrieve from Range Sets.

The `Range Subset` Requirements Class defines the application of the `properties` parameter against the RangeSet component of a Coverage resource using the HTTP GET operation.
The effect is to generate a subset of the range set of the coverage. That subset is then returned to the client in the HTTP response.
The Range Subset Requirements Class defines the `properties` parameter for selecting a subset of the DataRecord fields (defined in the Range Type, e.g. individual imagery bands)
to retrieve from Range Sets, either of a Coverage resource, or a separate RangeSet resource of the coverage, using the HTTP GET operation.
The effect is to generate a subset of the range set of the coverage. The order of the fields as listed in the value of the parameter also determines the order
in which those fields will be ordered in the response, if the negotiated format has such a concept of field order.
That subset is then returned to the client in the HTTP response.

This query parameter affects both the `/collections/{collection_id}/coverage` and `/collections/{collection_id}/coverage/rangeset` resource paths.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@
[width="90%",cols="2,6a"]
|===
^|*Requirement {counter:req-id}* |*/req/coverage-rangesubset/success*
^|A |The `range-subset` parameter SHALL be applied to the coverage (and rangeset, if available as a separate resource).
^|B |Only the bands of the coverage addressed SHALL be returned that correspond to one of the bands selected by the range subset expression
whereby a `*` (asterisk) at the begining or at the end of the comma-separated list denotes all other bands before or after the listed bands, respectively.
The RangeType shall be adjusted accordingly to the new selected bands.
^|A |The `properties` parameter SHALL be applied to the coverage (and rangeset, if available as a separate resource).
^|B |Only the fields of the coverage addressed SHALL be returned that correspond to one of the fields selected by the range subset expression
whereby a `*` (asterisk) at the begining or at the end of the comma-separated list denotes all other fields before or after the listed fields, respectively.
^|C |The RangeType describing the fields of the coverage being returned SHALL be adjusted accordingly to the new selected fields.
^|D |If the negotiated format of the response has a concept of field order, then the fields SHALL be in the same order as the list of selected fields.
|===

0 comments on commit d4c8cff

Please sign in to comment.