You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In GeoServer own Extended CQL we have the ability to express a list of filters, separated by semicolon, e.g:
...&CQL_FILTER=persons>1000;quality='good'
This is used in combination with requests accessing multiple layers, e..g, GetMap, so that we can filter each layer in a different way.
I suppose having a similar capability would be interesting for OGC API operations against multiple collections as well. Has any thought been given to this scenario?
The text was updated successfully, but these errors were encountered:
As a related note... in a list of filters, matching 1-1 a list of collections, there might be a need to just accept everything from one of the collections, and maybe drop everything from another.
In GeoServer ECQL we have two dedicated predicates, "INCLUDES" accepting everything, "EXCLUDES" excluding everything, for this purpose.
In ECQL2 maybe "true" and "false" could be also considered predicates (the "static" predicate if you want) to address the same need.
Of course, this would be needed only if there is also a need for a list of filters, to start with.
In GeoServer own Extended CQL we have the ability to express a list of filters, separated by semicolon, e.g:
...&CQL_FILTER=persons>1000;quality='good'
This is used in combination with requests accessing multiple layers, e..g, GetMap, so that we can filter each layer in a different way.
I suppose having a similar capability would be interesting for OGC API operations against multiple collections as well. Has any thought been given to this scenario?
The text was updated successfully, but these errors were encountered: