Cascading WFS

Description

GeoServer should support Cascading WFS, that is using another WFS as a datasource, able to return its features to a client. The way to do this is probably in GeoTools, with a WFS DataStore. There are a few ways to approach this - we could have GeoServer read the gml passed by another datasource, which would obviously slow things down, but it would allow us to do a lot more with the data. For example if the cascaded WFS only supported BBOX filters, turning its gml into geoserver data would allow us to leverage all of GeoTools's native filtering capabilities. Of course this might actually be required by the spec, because we can not advertise for only specific capabilities in our FeatureTypes, the filters must apply to all. Another option is to just forward the responses to clients, without checking them. This is obviously a lot faster, but still would require a lot of tweaking to get it working right. Could be cool if we got a Caching WfsDataStore, that could hold the cascaded WFS's features in memory, or even in a pickle (memory persistant on disk) dataSource. A super cascading server with a bunch of disk space could slowly gather its cascaded server's feature information in fast datasources. Data could spread between geoservers in a peer to peer fashion. Of course then you get into all sorts of issues like updates and versioning and whatnot. There's lots of ideas on this front, and I need to get back to work, but it'd be nice to get some good comments on this issue. It's probably a ways off, but is definitely something a lot of people desire.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 3:54 PM

CodeHaus Comment From: dblasby - Time: Wed, 16 Mar 2005 18:08:31 -0600
---------------------
<p>Re-updating to move to next release (jira bug?)</p>

codehaus
April 10, 2015, 3:54 PM

CodeHaus Comment From: dblasby - Time: Tue, 17 May 2005 16:09:38 -0500
---------------------
<p>Also add support for &lt;UserLayer&gt; ... remote WFS in SLD</p>

codehaus
April 10, 2015, 3:54 PM

CodeHaus Comment From: cholmes - Time: Fri, 23 Dec 2005 11:20:18 -0600
---------------------
<p>All this really needs now is 20 minutes of QA to see if it works. We're already including it, which is why I put this for 1.3.0 path. If it doesn't work, don't have time to QA enough, then we should not be including it - everything in 1.3.0 should work.</p>

codehaus
April 10, 2015, 3:54 PM

CodeHaus Comment From: cholmes - Time: Wed, 27 Sep 2006 15:36:34 -0500
---------------------
<p>there are some issues with this, most reported on <a href="http://docs.codehaus.org/display/GEOSDOC/WFS+DataStore" class="external-link" rel="nofollow">http://docs.codehaus.org/display/GEOSDOC/WFS+DataStore</a></p>

<p>Am re-opening this so I can link to them all.</p>

codehaus
April 10, 2015, 3:54 PM

CodeHaus Comment From: cholmes - Time: Tue, 15 Jan 2008 17:21:59 -0600
---------------------
<p>This is fixed for 1.6.x, right? We're shipping with it, afaik. Woo hoo, closing one of the oldest geoserver wishes!</p>

Fixed

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

Affects versions

None

Components

Priority

Low