-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Part 3 - Cross-collection queries #576
Comments
I tend to agree. While the constraint simplifies implementation, it prohibits some meaningful cross-collection queries. At a minimum we shouldn't add such a hard constraint already in Part 3 where no cross-collection queries are specified. Cross-collection queries will be supported by https://github.com/opengeospatial/ogcapi-features/tree/master/proposals/search and we should specify the cross-collections requirements there. |
Another possibility is to allow a |
This would be really useful. I can imagine this call could take a while to build a response the first time (depending on how many collections you have) but caching would take care of that. |
Meeting 2021-06-07: This will be moved to the future Search/Query part as a result of #544. |
My proposal is #801 is a |
The Part 3 draft spec section Cross-collection queries states
This is followed by an example cross-collection query
The definition of the global list of queryables states the list "SHALL be valid for all collections", which I interpret to mean the common property set that exists across all collections in the implementation. Cross-collection filtering is potentially a very useful feature but I believe the spec is overly restrictive.
In an implementation with two or more collections there could be zero common properties, and one might assume that as an implementation supports more collections the number of common properties could tend towards zero, meaning that this feature's value might be inversely proportional to the number of collections.
I would like to propose that instead of only supporting global queryables in a cross-collection filter the spec instead permits any queryables that exist in all collections identified in the request. An API client can query each collection's queryables individually and use this information to build a list of properties common to those collections. The API implementation can return a 400 response if provided queryables are not common across the identified collections, rather than returning 400 if the provided queryables are not global.
The text was updated successfully, but these errors were encountered: