Hello,
I want to provide a proxy WFS for a third party GeoServer WFS. The
3rd party WFS is read-only, but I want to also support Insert
transactions in my proxy WFS, and support requests over both the
inserted data and the 3rd party's data.
So I was looking at the external/cascading and layer groups features
of GeoServer to acchieve this. Is this a good idea?
In looking into these features, I have the 3rd party WFS v1.1.0
configured as a external datastore.
I find that when I try to create a layer in the proxy WFS based on a
layer from the 3rd party WFS, properties shown in the gml: namespace
in the 3rd party's GetFeature responses aren't listed at all in the
Feature Type List when configuring the proxy WFS layer, and are
omitted in responses to GetFeature requests to the proxy WFS layer.
These are fields name 'name' and 'description'; I'm not sure by what
mechanism they end up in the gml: namespace.
If I connect the 3rd party WFS with v1.0.0, no fields are in the gml:
namespace and all are available to republish. But then GetFeature
requests produce error reports.
Also, it seems that the matchCase flag in comparison filters (tested
PropertyIsEqualTo and PropertyIsLike) aren't honoured by the proxy
WFS, but are supported when querying the 3rd party WFS directly.
I have been testing GeoServer v2.4.4 and v2.5-RC2 for the proxy WFS,
and accessing GeoServer v2.3.0 and v2.2.4 as the 3rd party
external/cascaded WFS.
Thanks
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
