OpenGIS
©
Specification OGC 04-094
Copyright © Open Geospatial Consortium, Inc 2005
95 14.3.2 Request
parameter
The REQUEST parameter indicates which service operation is being invoked. The value operation_name must be one of those offered by the web feature service.
14.3.3 Bounding box
The bounding box parameter, BBOX, is included in this specification for convenience as a shorthand representation of the very common a bounding box filter which would be
expressed in much longer form using XML and the filter encoding described in [3]. A BBOX applies to all feature types listed in the request.
The KVP encoding for a bounding box is defined in subclause 10.2.3 of normative reference [15]. The general form of the parameter is:
BBOX=lcc1,lcc2,…,lccN,ucc1,ucc2,…uccN[,crsuri] where lcc means Lower Corner Coordinate, ucc means Upper Corner Coordinate and
crsuri means the URI reference to the coordinate system being used. This encoding allows N coordinates for each corner listed in the order of the optional crsuri. If the
crsuri is not specified then the 2-D coordinates shall be specified using decimal degrees and WGS84 as described in [15].
14.3.4 Vendor-specific parameters
Requests may allow for optional vendor-specific parameters VSPs that will enhance the results of a request. Typically, these are used for private testing of non-standard
functionality prior to possible standardization. A generic client is not required or expected to make use of these VSPs.
An OGC Web Service must produce a valid result even if VSPs are missing or malformed i.e., the Service shall supply a default value, or if VSPs are supplied that are
not known to the Service i.e., the Service shall ignore unknown request parameters.
An OGC Web Service may choose not to advertise some or all of its VSPs. If VSPs are included in the Capabilities XML, the VendorSpecificCapabilities element must be
redefined accordingly. Additional schema documents may be imported containing the redefinition of the element.
Clients may read the vendor specific definition from the capabilities schemas and formulate requests using any VSPs advertised therein.
Vendors should choose vendor-specific parameter names with care to avoid clashes with standard parameters.
