[Geoserver-devel] Available Filters Community Module Proposal

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: ‘geoserver-devel@lists.sourceforge.net’ geoserver-devel@anonymised.coms.sourceforge.net
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: A.McKeown@anonymised.com

W: https://portal.aodn.org.au

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?

···


Jody Garnett

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:jody.garnett@…403…]
Sent: Friday, 16 March 2018 12:09
To: Alex McKeown <a.mckeown@…3907…>
Cc: geoserver-devel@lists.sourceforge.net
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 <a.mckeown@…3907…> 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:geoserver-devel@lists.sourceforge.net’ <geoserver-devel@lists.sourceforge.net>
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: A.McKeown@…3907…

W: 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_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Jody Garnett

Okay so kind of like a more complete schema description, the ability to get “distribution” information about the attribute values (min, max, unique values, equal breaks, etc…). It is a useful bit functionality that is not covered by the protocols to my knowledge.

Aside: For your specific example that could be represented in XML Schema (if you did indeed have a limited set of valid region), but the general case is not addressed.

···

On 15 March 2018 at 18:57, Alex McKeown <a.mckeown@anonymised.com> wrote:

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:jody.garnett@anonymised.com]
Sent: Friday, 16 March 2018 12:09
To: Alex McKeown <a.mckeown@anonymised.com>
Cc: geoserver-devel@anonymised.comsourceforge.net
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 <a.mckeown@anonymised.com> 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:geoserver-devel@anonymised.comsourceforge.net’ <geoserver-devel@anonymised.comsourceforge.net>
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: A.McKeown@anonymised.com

W: 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_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Jody Garnett


Jody Garnett

Hi,
something similar (the same thing ?) can be done with the gs:PagedUnique WPS process.

Regards,

Nuno Oliveira

···

On 03/16/2018 01:57 AM, Alex McKeown wrote:

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:jody.garnett@anonymised.com]
Sent: Friday, 16 March 2018 12:09
To: Alex McKeown a.mckeown@anonymised.com
Cc: geoserver-devel@lists.sourceforge.net
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 <a.mckeown@anonymised.com> 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:geoserver-devel@lists.sourceforge.net’ <geoserver-devel@lists.sourceforge.net>
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: A.McKeown@anonymised.com

W: 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_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
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](http://sdm.link/slashdot)
_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)

-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit [http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:      +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.
 
The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Hi Alex,
as other said, the functionality you’re proposing seems to be at least partially covered by two existing features in GeoServer:

  • WFS DescribeFeatureType (list of attributes and their type)

  • WPS process reporting unique values of an attribute
    Is the module going to offer something further? Like, for example:

  • Configuration reporting which attribute it’s best to filter (and not to filter) on, e.g., based on knowledge of which attributes are indexed in storage for example

  • Soft configuration of which attributes are actually enumerated (the paged unique process is nice, but computing unique over a very large dataset can take forever)
    Mind, don’t take this a a “no” on the module, a community module can overlap with core functionality, no problem there, it’s just for discussion sake

Cheers
Andrea

···

On Fri, Mar 16, 2018 at 2:01 AM, Alex McKeown <a.mckeown@anonymised.com> 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:geoserver-devel@anonymised.comsourceforge.net’ <geoserver-devel@anonymised.comsourceforge.net>
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: A.McKeown@anonymised.com

W: 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


Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Thanks for the responses everyone. We weren’t aware of the “gs:PagedUnique” WPS process. For now we’re going try to using PagedUnique in combination with DescribeFeatureType and see if it can match our requirements. I’ll get back to you if we decide to implement something extra.

Cheers,

Alex

···

From: andrea.aime@…403… [mailto:andrea.aime@…403…] On Behalf Of Andrea Aime
Sent: Saturday, 17 March 2018 20:27
To: Alex McKeown <a.mckeown@…3907…>
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Available Filters Community Module Proposal

Hi Alex,

as other said, the functionality you’re proposing seems to be at least partially covered by two existing features in GeoServer:

  • WFS DescribeFeatureType (list of attributes and their type)
  • WPS process reporting unique values of an attribute

Is the module going to offer something further? Like, for example:

  • Configuration reporting which attribute it’s best to filter (and not to filter) on, e.g., based on knowledge of which attributes are indexed in storage for example
  • Soft configuration of which attributes are actually enumerated (the paged unique process is nice, but computing unique over a very large dataset can take forever)

Mind, don’t take this a a “no” on the module, a community module can overlap with core functionality, no problem there, it’s just for discussion sake

Cheers

Andrea

On Fri, Mar 16, 2018 at 2:01 AM, Alex McKeown <a.mckeown@…3907…> 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:geoserver-devel@lists.sourceforge.net’ <geoserver-devel@lists.sourceforge.net>
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: A.McKeown@…3907…

W: 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


Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.