On Fri, Feb 4, 2011 at 9:02 PM, Richard (Abe) Coughlin <[email protected]> wrote: > Taking this a step further, the ogc:Property Name reflects a column in the table with the geometry that we are serving - is there a way to reference a > separate table (ie a lookup table), maybe through some incorporated CQL. > Other than creating a view. Or would you advise me that the database > processing time would be considerably greater than the speed to look up the > sld or css?
Definitely going to be slower, even if we had such function (and we'll actually very soon have it) it would result in one lookup query per record. Better publish a view that already does the join with the lookup tables directly. There is also a new classification function that would allow one to store the LUT in SLD in quite a compact way, but I have no idea whether it's actually working fine or not, just never tried it out so far Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
