Schema Central > NIEM 2.0 > wfs.xsd > wfs:Insert
Advanced search
Need NIEM Help?

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

wfs:Insert

            The Insert element is used to indicate that the Web Feature
            Service should create a new instance of a feature type.  The
            feature instance is specified using GML3 and one or more 
            feature instances to be created can be contained inside the
            Insert element.
         

Element information

Content

Attributes

NameOccTypeDescriptionNotes
idgen [0..1]wfs:IdentifierGenerationOptionType The idgen attribute control how a WFS generates identifiers from newly created feature instances using the Insert action. The default action is to have the WFS generate a new id for the features. This is also backward compatible with WFS 1.0 where the only action was for the WFS to generate an new id. Default value is "GenerateNew".
handle [0..1]xsd:string The handle attribute allows a client application to assign a client-generated request identifier to an Insert action. The handle is included to facilitate error reporting. If an Insert action in a Transaction request fails, then a WFS may include the handle in an exception report to localize the error. If no handle is included of the offending Insert element then a WFS may employee other means of localizing the error (e.g. line number).
inputFormat [0..1]xsd:string This inputFormat attribute is used to indicate the format used to encode a feature instance in an Insert element. The default value of 'text/xml; subtype=gml/3.1.1' is used to indicate that feature encoding is GML3. Another example might be 'text/xml; subtype=gml/2.1.2' indicating that the feature us encoded in GML2. A WFS must declare in the capabilities document, using a Parameter element, which version of GML it supports. Default value is "text/xml; subtype=gml/3.1.1".
srsName [0..1]xsd:anyURI ===== PAV 12NOV2004 ==== WHY IS THIS HERE? WOULDN'T WE KNOW THE INCOMING SRS FROM THE GML GEOMETRY ELEMENTS? I ASSUME THAT IF THE INCOMING SRS DOES NOT MATCH ONE OF THE STORAGE SRS(s) THEN THE WFS WOULD EITHER PROJECT INTO THE STORAGE SRS OR RAISE AN EXCEPTION.

Used in

Sample instance

<wfs:Insert>
   <mo:MovingObject>
      <gml:metaDataProperty>
         <!--any element-->
      </gml:metaDataProperty>
      <gml:description>string</gml:description>
      <gml:name>string</gml:name>
      <gml:boundedBy>
         <gml:Envelope>...
         </gml:Envelope>
      </gml:boundedBy>
      <mo:geometryProperty>
         <gml:Point>...
         </gml:Point>
      </mo:geometryProperty>
      <gml:validTime>
         <gml:TimeInstant>...
         </gml:TimeInstant>
      </gml:validTime>
      <mo:track>
         <mo:MovingObjectStatus>...
         </mo:MovingObjectStatus>
      </mo:track>
      <gml:dataSource>string</gml:dataSource>
   </mo:MovingObject>
</wfs:Insert>

Site developed and hosted by Datypic, Inc.

Please report errors or comments about this site to pwalmsley@datypic.com