On Mon, Feb 14, 2011 at 7:02 PM, Andrew Chamberlain <[email protected]> wrote: > Hi David, > > Thanks for the quick reply. That's certainly a useful tip about styling > features, as I wasn't aware that was possible > > Apologies are due, however, as I was unclear. I meant in the context of > defining a datastore. At the moment, Geoserver seems to choose the geometry > automatically. Not sure if it depends on the database type, but we're using > Oracle at the moment.
GeoServer (actually, the Feature subsystem of GeoTools) picks the first geometry it finds in the list of attributes and treats that as the default geometry, that is, the one that will be used in all places where you don't explicitly specify one (symbolizers, bbox filters in wfs). There is no simple configuration to override that. Using views as Jukka suggested is probably the best way Mind however that all geometries are preserved and are usable, you just have to name them explicitly in the requests 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 ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
