I use CQL for creating subsets of Geoserver layers in Google Earth, but am also thinking about showing small numbers of points by programmatically creating an ‘IN’ list in a CQL filter - maybe 100 or 200 choices in the ‘IN’ list.
Is this an undesirable thing to do?
How long (in characters or number of criteria) could a CQL filter be?
http://docs.geoserver.org/latest/en/user/tutorials/cql/cql_tutorial.html
Regards,
David Collins
Geological Survey of New South Wales
Hi David,
I don’t know about any GeoServer specific limitations on this, but it’s worth bearing in mind that HTTP itself has got some limits you may hit.
If the request is sent via the GET method, you’ll be limited to about 2000 characters by the web browsers/client. You’ll almost certainly hit this with 100-200 things in your CQL.
If the request is sent via the POST method, the limit should be much much higher. As in megabytes; this is something that you could potentially configure in Jetty/Tomcat.
See also: http://stackoverflow.com/questions/266322/is-there-a-limit-to-the-length-of-a-get-request
Maybe someone else can answer the GeoServer/WFS specific part.
Cheers,
Jonathan
On 02/11/2015 05:45, David Collins wrote:
I use CQL for creating subsets of Geoserver layers in Google Earth, but am also thinking about showing small numbers of points by programmatically creating an ‘IN’ list in a CQL filter - maybe 100 or 200 choices in the ‘IN’ list.
Is this an undesirable thing to do?
How long (in characters or number of criteria) could a CQL filter be?
http://docs.geoserver.org/latest/en/user/tutorials/cql/cql_tutorial.html
Regards,
David Collins
Geological Survey of New South Wales
------------------------------------------------------------------------------_______________________________________________ Geoserver-users mailing list [Geoserver-users@lists.sourceforge.net](mailto:Geoserver-users@lists.sourceforge.net) [https://lists.sourceforge.net/lists/listinfo/geoserver-users](https://lists.sourceforge.net/lists/listinfo/geoserver-users)
On Fri, Nov 13, 2015 at 11:58 PM, Jonathan Moules <
jonathan-lists@anonymised.com> wrote:
Maybe someone else can answer the GeoServer/WFS specific part.
As far as I remember, there is no built-in limit
Cheers
Andrea
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
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.
-------------------------------------------------------