Hi,
thanks for looking into it! Is there any chance for me to change the
characters manually (for example in the dialogue: WFS
service/capabilities) or can only the WFS's producer itself encode the
URL resp. replace the characters?
Thanks and best regards,
Astrid
Andreas Schmitz schrieb:
Astrid Lipski wrote:
Hi,
I'm trying to use a WFS of the LBEG in Lower Saxony:
http://memas01.lbeg.de/LucidaMap/project/Applications/cc_erosion/wfs.erosion.asp?pkgid=e-strict-client/{CBFCBEFD-370D-4918-A048-CA0661EB6648}^68660654382befee75c618006fcd7bce&
Creating a connection to the service is working, feature type and
properties are shown.
But when clicking "ok", an error message comes up...Has anybody an idea,
why this WFS is not working?
ok, I looked into it. The problem is, that some characters (probably {, } and/or
^) are not valid in URLs. Since they are returned in the WFS's capabilities
document's URLs they are used by the client. Unfortunately that's not feasible,
since the HTTP client used by the WFS client cannot know which characters to
encode and which not.
The conclusion is, that the WFS is not set up correctly. While it may work with
other clients, the URLs returned are not valid. The solution would be to encode
the URLs of the WFS correctly in its setup. To do so, replace { with %7B, } with
%7D and ^ with %5E.
Best regards, Andreas
--
l a t / l o n GmbH
Aennchenstrasse 19 53177 Bonn, Germany
phone ++49 +228 18496-11 fax ++49 +228 1849629
http://www.lat-lon.de http://www.deegree.org
------------------------------------------------------------------------
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users
_______________________________________________
jump-users mailing list
[email protected]
http://lists.refractions.net/mailman/listinfo/jump-users