Warn when request has invalid query parameters (criteria)

[arlowhite]

Ideally, we should warn or error if making a request with invalid query parameters. Otherwise the client/developer may assume the parameter is defined correctly and being used.

IMO this should be an error. HTTP 400 Bad Request

[ConnectedSystems]

Notes:

• Query parameters need to be derived from the available data
• An API endpoint is needed to serve the above to the client.
• Ideally, this would be done in conjunction with Use ModelParameters to specify criteria type and bounds #22

[ConnectedSystems]

Actually, what is meant by invalid here?
Selected ranges/values being out of bounds?

In future, the bounds would be set based on what's in the available data (across the entire area of interest).

Unless you're referring to a situation where the combination of criteria values/ranges produce no results?