Hi All,

After a LONG time away from Geoserver I am now back working with it and
hopefully for a long while yet :)

We have a layer that has around 200 different "network_id" values in there
and we are looking at the implications of the following when using vector
tiles:

CQL_FILTER=network_id in (1,2,3)
CQL_FILTER=network_id in (1)
CQL_FILTER=network_id in (22,57,23,178)
CQL_FILTER=network_id in (12,58,66,81.94.122.,146,178,201)

Or explained another way, users can choose which networks they want to show
as a combination of any off the 200 available networks - and the CQL_FILTER
is what updates.

Many of our networks are HUGE - they are road networks indicating where
vehicles can be driven in Australia. We are not talking about small data
here. The data is also living data, so we will want to refresh (either
reseed or truncate) fairly frequently.

I'll leave if there rather than "lead the witness" but would really
appreciate any advice on why this approach is horrible, good, are there
limitations it will hit or what is a better way of doing this (and yes, it
MUST be vector tile).

Many thanks & good to be back on the Geoserver bandwagon.
Andrew
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to