Hi all! We have implemented a datastore, which is supposed to be used in Geoserver to aggregate the responses from several other WFS.
Our datastore uses the WFS-datastore to communicate with the cascaded WFS (therefore, it is restricted to WFS 1.0). From the WFS-datastores it retrieves responses and aggregates them into one response, which is then passed on. So far the aggregation part of the datastore is rather limited. Apart from making sure the features match the common schema (ie. removing attributes that are not part of the schema and mapping the FeatureTypeName if necessary), they are passed on without being changed. The FeatureTypes provided by the datastore are defined in a config-file as well as the configuration of the cascaded WFS. The configuration of the WFS contains at the moment the URL to the WFS, the supported FeatureTypes and the mapping of the FeatureTypeNames (This is for example necessary, if other Geoservers are cascaded). The project is still in an early stage. We think, we implemented most of the required functionality, but so far we haven't had the opportunity to do run too many tests. However, if you, the Geotools community, are interested, we are happy to contribute our datastore. It would be also great to get some feedback on the code from people who know more about Geotools/Geoserver than we do. So if anyone is interested in our datastore and wants to see it, please let me know. What would actually be the next steps we have to do, so our datastore can become an unsupported module or something like that? cheers, stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
