Opened 18 years ago

Closed 16 years ago

#1698 closed defect (invalid)

BBOX extent and SRS on WFS query

Reported by: olivier.courtin@… Owned by: mapserverbugs
Priority: high Milestone:
Component: WFS Server Version: 4.8
Severity: normal Keywords:
Cc:

Description (last modified by dmorissette)

WFS query using a BBOX with a specific SRS not work if the SRS is not
the same as the Layer one.

On mapwfslayer.c :
/* __TODO__ WFS servers support only one SRS... need to decide how we'll */
/* handle this and document it well. */
/* It's likely that we'll simply reproject the BBOX to teh layer's
projection. */

Change History (5)

comment:1 by jlacroix, 18 years ago

I re-check the spec of WFS 1.0.0 and the SRS parameter does not even exist as a
Request parameter. It's specified in section 13.3.3 that the BBox parameter in
the request to a WFS server _must_ always be in the same projection as the
layers queried:

"The SRS of the bounding box must be the same as the SRS of the feature type(s)
in a request. The SRS of a feature type is advertised by a WFS in the
capabilities document. If more than one feature type is specified in a request,
the feature types must all be in the same SRS and the BBOX must be specified in
the common SRS as well."

However in WFS 1.1.0 it seems that different SRS in the URL are supported.
Also the code to do that is already there, but is inside a #ifdef __TODO__. It
seems that someone developped it, but remove it because of the spec.

Should we include stick to the specification? Or be nice and support the vendor
specific SRS parameter?

My vote would go to include it we if plan to support WFS 1.1.0 someday, if not
then we should at least remove the TODO in the code.

comment:2 by dmorissette, 18 years ago

We used to "be nice" with our implementations of WMS in the past, and in order
to pass the compliance tests we had to modify several places where MapServer was
more forgiving than stated in the spec, causing MapServer to fail some tests
that were testing those limitations, so I think since WFS is a well documented
spec and likely to be tested the same way, we should stick to it for now to
avoid having to undo those changes later. 

If/when we upgrade to WMS 1.1 then support for the SRS request parameter should
be added, but only for this version.

comment:3 by tomkralidis, 16 years ago

Resolution: fixed
Status: newclosed

Should we mark this as wontfix as WFS 1.0 is fixed on a single SRS?

comment:4 by tomkralidis, 16 years ago

Resolution: fixed
Status: closedreopened

Sorry, didn't mean to close this one without agreement.

comment:5 by dmorissette, 16 years ago

Description: modified (diff)
Resolution: invalid
Status: reopenedclosed

Since the current behavior is correct for WFS 1.0.0 (i.e. SRS doesn't exist in WFS 1.0.0) then I think we should close as invalid.

When WFS 1.1 is implemented then the SRS parameter will be added as part of that work and only then.

Note: See TracTickets for help on using tickets.