[Featureserver] Fwd: [udig-users] WFS layer from FeatureServer
Paolo Corti
pcorti at gmail.com
Fri Feb 15 11:56:07 EST 2008
Hi
maybe now something is not obvious to me, but:
is there any way to get a DescribeFeatureType request? Looking at
source code seems not.
This would be a way to load FeatureServer layers in uDig (or other
desktop clients):
http://udig.refractions.net/confluence/pages/viewpage.action?pageId=5192
or am I missing something?
thanks
Paolo
---------- Forwarded message ----------
From: Jody Garnett <jgarnett at refractions.net>
Date: Thu, Feb 14, 2008 at 6:44 PM
Subject: Re: [udig-users] WFS layer from FeatureServer
To: Paolo Corti <pcorti at gmail.com>
Cc: udig-users at lists.refractions.net
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
More information about the Featureserver
mailing list