[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] Re: WFS bugs in RC8 Fixed
|
Hi Neil,
On 1-Feb-07, at 11:04 AM, Neil Best wrote:
I have used uDig with mapserver's WFS a few times. But I have to say
that Mapserver's WFS is not very good. A large part of that is
because they do not support post which limits the filters that can be
sent. I don't think we have a check for that yet so it is possible
for a request to fail because of it. Although that is not common for
normal usage but could potentially be an issue for rendering
complicated styles.
Jesse
Jesse, I was unable to unpack a recent build and successfully
connect to
my Mapserver WFS, but *only* when I set the output SRS to EPSG:4326,
WGS84 lat/lon. Does this have to do with the way the bounding box is
given in lat/lon in the GetCapabililities output? Is this a
limitation/shortcoming of the client or the server in this case?
Also,
when I set MS to expose some or all attributes uDig throws an error an
won't render the features. What do you think is going on here? I
would show you some output but for some reason when my output SRS is
set to 4326 Mapserver refuses to include any data in response to a
wget
but complies nicely for 42303 (NAD83 / Albers NorthAm).
That is the fix that I recently made after RC8 was released (or it
sounds like it is at any rate.) I am making a new release right now
and it should be out soon so you can play with that.
BTW, the Mapserver docs indicate that GET and POST are supported
now and
I have had varying success with both when using MS as both client and
server. It appears that the client gets confused and applies layer
styles incorrectly when two POST layers are coming from the same
server.
Well I have gotten POST to work but it has taken some pretty serious
hacks because it doesn't parse certain GML constructs correctly.
Specifically it has problems when a <coordinate> has certain
attributes. There is a JIRA about it. Perhaps that has been fixed
but 4.10 when I did a cursory check didn't seem to. So rather than
make a bunch of strategy objects for each WFS I decided that GET
worked good enough for MapServer until they fix at least that bug.
At which point I can re-test. DOn't worry though. uDig will try
POST first and if it fails it will try GET. But I think it is a
little stupid in that it will try both each time.
Jesse
