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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
