UDig & Mapserver WFS

[Bart van den Eijnden (OSGIS)]

Later on I realized this means Mapserver's parameter checking is more 
strict (therefore correct) on DescribeFeatureType than on GetFeature.

Since parameter values need to be interpreted case-sensitive, it should 
already report on your GetFeature request with capitals instead of 
Capitals that it does not know of such a typename. Instead of that it's 
using the value of the typename parameter in the DescribeFeatureType url 
and giving back there an error that it does not know of such a feature 
type later on.

I have opened up a bug for this:
http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1848

Best regards,
Bart

Bart van den Eijnden (OSGIS) wrote:

> I think your problem is with the schema (DescribeFeatureType 
> refererence in the GML response).
>
> If I use:
> http://ogc.midwestsurveys.com/geoserve/ms?SERVICE=WFS&VERSION=1.0.0&REQUEST=DescribeFeatureType&TYPENAME=capitals&OUTPUTFORMAT=XMLSCHEMA 
>
>
> I don't get back the schema.
>
> capitals should be Capitals then it works.
>
> uDIG is very sensitive to such things.
>
> Best regards,
> Bart
>
> Angus Dickey wrote:
>
>> Hey List,
>>
>> Has anybody tried using UDig as a client for a WFS service from 
>> Mapserver? I have mapserver running a WFS service that seems to 
>> produce fine GML, some other clients can connect correctly, but UDig 
>> always errors out.
>>
>> I will post the actual error to the UDig list, but was hoping 
>> somebody might have some insight into whether this is a UDig or 
>> Mapserver problem.
>>
>> For a sample mapserver response try this:
>>
>> http://ogc.midwestsurveys.com/geoserve/ms?SERVICE=WFS&version=1.0.0&request=getfeature&TYPENAME=capitals&OUTPUTFORMAT=gml2 
>>
>>
>> Thanks,
>>
>> ~Angus
>>
>>
>>
>>  
>>
>
>


-- 
Bart van den Eijnden
OSGIS, Open Source GIS
http://www.osgis.nl