Merge pull request #45 from philvarner/fix-collection-description

Fix collection description

Author: matthewhanson

CHANGELOG.md

@@ -15,6 +15,7 @@ For changes in 0.9.0 and prior, see the [STAC Spec Changelog](https://github.com
 ### Changed
 - Context Extension OpenAPI spec was updated to remove the no longer used `next` attribute
 - Added root endpoint Link `search` must have `type` of `application/geo+json`
+- Corrected the description of endpoint `/collections` to say it returns an object per OAFeat, instead of an array of Collection
 
 ### Fixed
 

api-spec.md

@@ -83,11 +83,13 @@ The core OGC API - Features endpoints are shown below, with details provided in
 | ------------ | ------------- | ----------- |
 | /            | JSON          | Landing page, links to API capabilities |
 | /conformance | JSON          | Info about standards to which the API conforms |
-| /collections | [Collection]  | List of Collections contained in the catalog |
+| /collections | JSON          | List of Collections contained in the catalog |
 | /collections/{collectionId}  | Collection | Returns single Collection JSON |
 | /collections/{collectionId}/items | ItemCollection | GeoJSON FeatureCollection-conformant entity of Items in collection |
 | /collections/{collectionId}/items/{featureId} | Item | Returns single Item (GeoJSON Feature) |
 
+The `/collections` endpoint returns an object with a field `collections` that is an array of Collection objects.
+
 The `/collections/{collection_id}/items` endpoint accepts parameters for filtering the results (also called filters). 
 Items in the collection should match all filters to be returned when querying. This implies a logical AND operation. If 
 an OR operation is needed, it should be specified through an extension filter.