Clarify KVP BBOX parameter interpretation

All Fields marked with * are mandatory.
Change Request 114
#:
Assigned OGC 10-174
Document #:
Name: *Andreas Schmitz
Organization: *lat/lon
Email: *schmitz@lat-lon.de
Document
Name/Version:

*Web Feature Service (WFS) Implementation Specification / 1.1.0

OGC Project
Document:

*04-094

If this is a revision of a previous submission and you have a Change Request Number, then check here:
Enter the CR number here:
Enter the Revsion Number that you are revising here:

Title:
Source:

*Clarify KVP BBOX parameter interpretation
*wfs-dev@lists.opengeospatial.org

Work item code:

Category:

* D (Editorial modification)

Reason for *
change:

It is not entirely clear from the text that the BBOX KVP parameter for
GetFeature requests is to be interpreted exactly as specified in
filter encoding.

Summary of *
change:

There has been a discussion on the mailing list
(wfs-dev@lists.opengeospatial.org, June 22nd 2010) that it should be

1 of 2

treated as the equivalent of the filter encoding variant (the BBOX
filter).

Consequences if
not approved:

Clauses affected: *
The BBOX parameter appears in sections 14.3.3, 14.7.3.1, 14.7.5.1,
14.7.6.1 (I hope I didn't miss any).

Additional
Documents

affected:
Supporting
Documentation:
Comments:
Status:

Assigned To:

Disposition:

Assigned

WFS WG

Referred and Posted

2 of 2