The web feature service specification defines the following operations:

1. GetCapabilities. A web feature service must be able to describe its capabilities. Specifically, it must indicate which feature types it can service and what operations are supported on each feature type.
   
   
2. DescribeFeatureType. A web feature service must be able, upon request, to describe the structure of any feature type it can service.
   
   
3. GetFeature. A web feature service must be able to service a request to retrieve feature instances. In addition, the client should be able to specify which feature properties to fetch and should be able to constrain the query spatially and non-spatially.
   
   
4. Transaction. A web feature service may be able to service transaction requests. A transaction request is composed of operations that modify features, i.e. to create, update and delete operations on geographic features.
   
   
5. LockFeature. A web feature service may be able to process a lock request on one or more instances of a feature type for the duration of a translation.

There are two classes of web feature services:

• A basic web feature service implements the GetCapabilities, DesribeFeatureType and GetFeature operations. This is considered a READ-ONLY web feature service.
  
  
• A transaction web feature service supports all the operations of a basic web feature service, as well as the Transaction operation, and possibly the LockFeature operation.

Click on the list below for examples of WFS responses.

WMS Example 1
WMS Example 2
WMS Example 3