A note about the examples

OpenGIS © Specification OGC 04-094 Copyright © Open Geospatial Consortium, Inc 2005 94 14.2 Request parameter rules

14.2.1 Parameter ordering and case

Parameter names shall not be case sensitive, but parameter values shall be case sensitive. In this document, parameter names are typically shown in uppercase for typographical clarity, not as a requirement. Parameters in a request may be specified in any order. An web feature service must be prepared to encounter parameters that are not part of this specification. In terms of producing results per this specification, a web feature service shall ignore such parameters.

14.2.2 Parameter lists

Parameters consisting of lists shall use the comma , as the delimiter between items in the list. In addition, multiple lists can be specified as the value of a parameter by enclosing each list in parentheses; , . The characters “,”, ““ and “” may be escaped using the “\” character. Example 1 This example shows a list of items. parameter=item1,item2,item3,item4a\,item4b This list consists of 4 values: item1, item2, item3 and the value “item4a,item4b”. Notice that the last comma has been escaped using the “\” character which means that it is actually part of the value and not a delimiter. Example 2 This example shows multiple lists of items assigned to a single parameter. parameter=item11,item12,item13item21,item22,item23 Parentheses may also be used to delimit multiple local filters when more than one feature type is specified for the TYPENAME parameter. The following URL fragment shows how this may be done: typename=FEAT1,FEAT2filter=Filter… FEAT1 filter…FilterFilter… FEAT2 filter…Filter 14.3 Common request parameters 14.3.1 Version parameter The VERSION parameter specifies the protocol version number. The format of the version number and the version negotiation algorithm are described in subclause 6.2.4. 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.