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.

Best regards,

Andy



On 14/02/2011 17:39, David Winslow wrote:
Are you asking about styling? In other contexts it is usually pretty straightforward.  In SLD you can add an element like:

<sld:Geometry><ogc:PropertyName>the_geom</ogc:PropertyName></sld:Geometry>

in any Symbolizer (LineSymbolizer, PointSymbolizer, etc) to tell GS which geometry property to use.  This can even be used with functions to buffer, offset, or otherwise manipulate the geometry before rendering. See samples at http://docs.geoserver.org/stable/en/user/styling/sld-extensions/geometry-transformations.html of this more advanced technique.

-d

On Mon, Feb 14, 2011 at 12:32 PM, Andrew Chamberlain <[email protected]> wrote:
Hi All,

This should hopefully be straight forward, one way or the other...

Does anyone know how to tell Geoserver which geometry field to use when
there's more than one?  It would be nice to choose, but there doesn't
seem to be a way of doing this.

Many thanks,

Andy

------------------------------------------------------------------------------
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

------------------------------------------------------------------------------
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

Reply via email to