clarify /req/edr/rc-md-query-links against non EDR based collections

[tomkralidis]

Latest testing of EDR CITE beta against a local pygeoapi instance yields the following failure:

In my case, my OGC API instance has a few collections, a few of which are EDR related, and others are not. The above failure is based on a collection that is feature based, not EDR based.

When testing the same setup against Features CITE, all related tests pass.

Should this CITE test evaluate this requirement only if the collection if found to have EDR capabilities?

cc @bpross-52n

[tomkralidis]

Related issue below (i.e. The data_queries element is missing from the collection lakes . The data_queries element is missing from the collection canada-hydat-daily-mean-02hc003).

In other words, CITE tests should only evaluate collections which are EDR capable. This will also make things easier for products to provide CITE demos supporting multiple standards using a single deployment.

[dstenger]

Thanks for the proposal. We will discuss it in the CITE team.

[dstenger]

Question regarding #150 (comment):
This seems to be a error message which contains misleading content. The error is occurring in collection icoads-sst which should be an EDR collection. Can you confirm that?
All other mentioned collections are printed but not related to the error.
We will check if the error message can be improved.

[tomkralidis]

@dstenger confirm. Tests can be (now) run per below:

• Landing page: https://demo.pygeoapi.io/cite
• OpenAPI document: https://demo.pygeoapi.io/cite/openapi