Hi,
is it possible to specify the geometry attribute when configuring a
Postgis datastore in Geoserver ?
Thanks,
Christophe
Hi Christophe,
Not really... What is your use case? Do you have a postgis table with
multiple geometry columns in it?
Christophe ROUSSON wrote:
Hi,
is it possible to specify the geometry attribute when configuring a
Postgis datastore in Geoserver ?Thanks,
Christophe
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users!DSPAM:4007,478796b8235166491211187!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira a écrit :
Hi Christophe,
Not really... What is your use case? Do you have a postgis table with
multiple geometry columns in it?
Exactly, I have a feature table with multiple representations.
Geoserver seems to pick the first geometry column it sees.
As a workaround, I could define a view for each representation with only one geometry.
Christophe
Christophe ROUSSON ha scritto:
Justin Deoliveira a écrit :
Hi Christophe,
Not really... What is your use case? Do you have a postgis table with
multiple geometry columns in it?
Exactly, I have a feature table with multiple representations.
Geoserver seems to pick the first geometry column it sees.
As a workaround, I could define a view for each representation with only one geometry.
Hum, GeoServer picks the first geometry as the default geometry, yes,
but the others should be available as well. If you do a WFS GetFeature
request you should see them all. If you need to use a geometry other
than the default one in WMS you can do so by specifying the geometry
column in the symbolizer, for example:
<LineSymbolizer>
<Geometry>
<ogc:PropertyName>mySecondaryGeomColumn</ogc:PropertyName>
</Geometry>
<Stroke>
<CssParameter name="stroke">#B9AE9B</CssParameter>
<CssParameter name="stroke-width">3</CssParameter>
</Stroke>
</LineSymbolizer>
Hope this helps
Cheers
Andrea
Andrea Aime a écrit :
Christophe ROUSSON ha scritto:
Justin Deoliveira a écrit :
Hi Christophe,
Not really... What is your use case? Do you have a postgis table with
multiple geometry columns in it?
Exactly, I have a feature table with multiple representations.
Geoserver seems to pick the first geometry column it sees.
As a workaround, I could define a view for each representation with only one geometry.Hum, GeoServer picks the first geometry as the default geometry, yes,
but the others should be available as well. If you do a WFS GetFeature
request you should see them all. If you need to use a geometry other
than the default one in WMS you can do so by specifying the geometry
column in the symbolizer, for example:<LineSymbolizer>
<Geometry>
<ogc:PropertyName>mySecondaryGeomColumn</ogc:PropertyName>
</Geometry>
<Stroke>
<CssParameter name="stroke">#B9AE9B</CssParameter>
<CssParameter name="stroke-width">3</CssParameter>
</Stroke>
</LineSymbolizer>Hope this helps
Cool, it does work really well.
But is there some doc about the geoserver xml config files structure ?
I found http://docs.codehaus.org/display/GEOSDOC/2+Files
but it looks like examples, rather than doc.
Thanks.
Christophe
Christophe ROUSSON ha scritto:
Andrea Aime a écrit :
Hope this helps
Cool, it does work really well.
But is there some doc about the geoserver xml config files structure ?
I found http://docs.codehaus.org/display/GEOSDOC/2+Files
but it looks like examples, rather than doc.
There are no docs because you're not supposed to manually alter them.
All sort of crashes may happen if you do so.
Cheers
Andrea