I'm thinking here of the CQL/ECQL filters that can be used in WMS GetMap and 
WFS GetFeature requests 
(http://docs.geoserver.org/latest/en/user/filter/syntax.html).

For instance a layer might have a property called 'region' which can be 
filtered by three potential string values "pacific", "indian", and "southern". 
Adding "&CQL_FILTER=region%20LIKE%20'pacific'" to your request would get only 
the subset of data located in the pacific region.

Under the proposed module a user could make a "getFilters" request to find out 
that 'region' is a potential property to filter on with type string, and make a 
"getFilterValues" request to find out that the potential values of 'region' are 
"pacific", "indian", and "southern".


From: Jody Garnett [mailto:[email protected]]
Sent: Friday, 16 March 2018 12:09
To: Alex McKeown <[email protected]>
Cc: [email protected]
Subject: Re: [Geoserver-devel] Available Filters Community Module Proposal

I am fine with a community module, but I am not sure I understand about 
filters? Do you mean function reference? Schema attributes overview? WFS 
predefined queried?
On Thu, Mar 15, 2018 at 6:02 PM Alex McKeown 
<[email protected]<mailto:[email protected]>> wrote:
Hi,
I think this may have been one of the posts that was missed because of the 
sourceforge mailing problems. I should add that we already have something 
similar running off a fork, though we need to make it much more generic. Any 
thoughts? Happy to discuss further.

Cheers,
Alex

From: Alex McKeown
Sent: Monday, 22 January 2018 15:10
To: 
'[email protected]<mailto:[email protected]>'
 
<[email protected]<mailto:[email protected]>>
Subject: Available Filters Community Module Proposal

Hi all,
I would like to propose a community module to add a RESTful interface for 
describing the filters available for a particular layer. This would entail two 
new request types, "getFilters", and "getFilterValues". A "getFilters" request 
would return a list of the available filters, with their names and types. A 
"getFilterValues" request would describe the valid values of a particular 
filter. This would make it easier for users to discover the filter 
functionality available to them.

Regards,
Alex

---

Alex McKeown
Software Engineer
Australian Ocean Data Network (AODN)
University of Tasmania
Private Bag 110
Hobart TAS 7001 Australia
E: [email protected]<mailto:[email protected]>
W: https://portal.aodn.org.au<https://portal.aodn.org.au>



University of Tasmania Electronic Communications Policy (December, 2014).
This email is confidential, and is for the intended recipient only. Access, 
disclosure, copying, distribution, or reliance on any of it by anyone outside 
the intended recipient organisation is prohibited and may be a criminal 
offence. Please delete if obtained in error and email confirmation to the 
sender. The views expressed in this email are not necessarily the views of the 
University of Tasmania, unless clearly intended otherwise.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot<http://sdm.link/slashdot>_______________________________________________
Geoserver-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/geoserver-devel<https://lists.sourceforge.net/lists/listinfo/geoserver-devel>
--
--
Jody Garnett
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to