On 31/05/2010 12:25 PM, Stefanie Weykam wrote:
Dear list members,
I am having trouble with parsing the GetCapabilities response from my
WFS services:
If I send a GetCapabilities-request indicating VERSION=1.0.0 –
metadata having non ascii characters (like characters with accent) are
parsed without any problem. But indicating VERSION=1.1.0 or omitting
this parameter causes a parsing error at the first ‘strange’ character
encountered. Is there anything I can do about that?
Both, GetFeature and DescribeFeatureType work just fine with any version.
This is possibly related to http://trac.osgeo.org/mapserver/ticket/3297.
The difference between wfs 1.0 and 1.1 in Mapserver GetCapabilities is
that the version 1.1 uses libxml2 as the libarary to build the xml that
is returned. It is parlty fixed is the current svn version.
Question nº 2 – data type is always string:
In response to a DescribeFeatureType request, the server returns data
type ‘string’ for all fields. I wonder if I can specify the real data
type somehow?? This would allow thick clients to apply filter
expressions on this layer.
You should be able to set metadata at the layer level to do that:
`"gml_PERIMETER_type" "double" #where PERIMETER is your attribute name
best regards,
--
----------------------------------------------------------------
Assefa Yewondwossen
Software Analyst
Email: yass...@dmsolutions.ca
http://www.dmsolutions.ca/
Phone: (613) 565-5056 (ext 14)
Fax: (613) 565-0925
----------------------------------------------------------------
_______________________________________________
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
