[OACov] rename rangeSubset to range-subset for coverage queries (#816)

docs/source/data-publishing/ogcapi-coverages.rst

@@ -15,7 +15,7 @@ pygeoapi core feature providers are listed below, along with a matrix of support
 parameters.
 
 .. csv-table::
-   :header: Provider, rangeSubset, subset, bbox, datetime
+   :header: Provider, range-subset, subset, bbox, datetime
    :align: left
 
    rasterio,✅,✅,✅,
@@ -96,8 +96,8 @@ Data access examples
   - http://localhost:5000/collections/foo/coverage?f=json
 - coverage access via native format (as defined in ``provider.format.name``)
   - http://localhost:5000/collections/foo/coverage?f=GRIB
-- coverage access with comma-separated rangeSubset
-  - http://localhost:5000/collections/foo/coverage?rangeSubset=1,3
+- coverage access with comma-separated range-subset
+  - http://localhost:5000/collections/foo/coverage?range-subset=1,3
 - coverage access with subsetting
   - http://localhost:5000/collections/foo/coverage?subset=lat(10,20)&subset=long(10,20)
 

pygeoapi/api.py

@@ -2006,9 +2006,9 @@ class API:
             # Format explicitly set using a query parameter
             query_args['format_'] = format_ = request.format
 
-        range_subset = request.params.get('rangeSubset')
+        range_subset = request.params.get('range-subset')
         if range_subset:
-            LOGGER.debug('Processing rangeSubset parameter')
+            LOGGER.debug('Processing range-subset parameter')
             query_args['range_subset'] = [rs for
                                           rs in range_subset.split(',') if rs]
             LOGGER.debug('Fields: {}'.format(query_args['range_subset']))

tests/test_api.py

@@ -990,7 +990,7 @@ def test_get_collection_coverage(config, api_):
 
     assert code == 400
 
-    req = mock_request({'rangeSubset': '12'})
+    req = mock_request({'range-subset': '12'})
     rsp_headers, code, response = api_.get_collection_coverage(
         req, 'gdps-temperature')