Re: [udig-users] WFS layer from FeatureServer

["Paolo Corti" <pcorti@xxxxxxxxx>]

Hi Jody and Jesse

looks like the WFS implementation of FeatureServer does not allow a
DescribeFeatureType schema request (some data sources haven't a fixed
schema, though for most of them could make sense).

Here for more infos:
http://featureserver.org/pipermail/featureserver/2008-February/000196.html

Paolo

On Feb 14, 2008 6:44 PM, Jody Garnett <jgarnett@xxxxxxxxxxxxxxx> wrote:
> Morning Paolo:
>
> Can you create an issue for this item; you will need to attach the
> capabilities document generated by the link you provided.  I would love
> to ask what WFS implementation is behind featureserver.cgi :-)
>
> You can create an issue by going to this page
> (http://jira.codehaus.org/browse/UDIG) and clicking on the Create a new
> issue in project uDIG.
>
> A couple of notes when setting up a WFS server to work with uDig:
> -  uDig uses the DescribeFeatureType XML Schema file to define the data
> structure used to read your Features; the slightest mistake and uDig
> won't be able to function. WFS providers are not very good about making
> sure it is valid 90% of the time this is where the problem is.
> - make sure the document generated by GetFeatures actually uses the
> DescribeFeatureType schema as its schema for validation
> - uDig can just read WFS 1.0 at this time; a developer from the Open
> Planning Project is adding WFS 1.1 support to trunk as we speak
>
> Hopefully this gives you some ideas to check.
> > SEVERE: must be one feature 0
> > org.geotools.xml.gml.GMLComplexTypes$FeatureAssociationType.getValue(GMLComplexTypes.java:5082)
> >
> Looking at what the code is doing here it sounds like a feature
> association is empty (an association is how the capabilities document
> describes what to expect inside the feature collection returned by the
> WFS GetFeature operation). It looks like it was hoping to read the name
> of your FeatureType here and none was provided.
>
> Jody
>



-- 
Paolo Corti
http://www.paolocorti.net