|
From: Brent O. <bre...@gm...> - 2005-12-21 22:48:30
|
The complex feature model should solve this for you. It is currently under development on another branch and is waiting to be merged back into trunk on both geoserver and geotools. Here is some documentation on it: http://geotools.org/display/GEOTOOLS/ComplexDataStore+project http://geotools.org/display/GEOTOOLS/Feature+Model+Design For a temporary solution, I would just query the edge layer for WMS. What do you mean by "the problem is the number of these Edges is variable depending on the database"? Brent Owens (The Open Planning Project) Davis Ford wrote: >How does GeoServer/GeoTools deal with complex features? > >For example, we have a Feature called road element, and it looks >something like this: > >int attributeA >int attributeB >ArrayList<Edge> edges > >where Edge is a class defined like: > >int attributeA >int attributeB >com.vividsolutions.jts.geom.LineString > >So..the geometry is really buried in an Edge, and the feature has an >array full of edges. > >Using WFS, we can get GML back, and it represent the int attributes, >but only the pointer to the array list. > >WMS fails completely, and my guess is the way we structured this is >causing it. I would love any pointers that could help. I'm guessing >we might have to pull the LineStrings out of this Edge class, but the >problem is the number of these Edges is variable depending on the >database. > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >_______________________________________________ >Geoserver-users mailing list >Geo...@li... >https://lists.sourceforge.net/lists/listinfo/geoserver-users > > > |