If using the "inX" functions is still too verbose, or if it's awkward to
split up the blocks of IDs, and depending on how much effort you want to
spend...
You could look at writing a custom filter function "inList(int, String)",
where the second argument is a string literal which represents the list of
IDs in some way (e.g. such as "1,2,3,4").
On Tue, Jun 11, 2013 at 8:41 AM, Chris Snider <[email protected]>wrote:
> Pedro,****
>
> ** **
>
> We used the function “in3” as referenced at
> http://docs.geoserver.org/latest/en/user/filter/function_reference.html
> This supports in2 through in10. You may be able to match multiple features
> based on the ogc:or.****
>
> ** **
>
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
