GEOSS Banner

Section 2.2 : How Interoperability is improved through the use of the server service

Table of contents
No headers

2.2.1 Sharing features interoperability

2.2.1.1 Sharing data model problem
2.2.1.2 Sharing feature collection problem
2.2.1.3 Editing a feature collection problem

2.2.2 Data modeling needs and GML

2.2.2.1 Formal definition of a data model
2.2.2.2 Practical definition in GML application schemas
2.2.2.3 GML application schemas from UML models
2.2.2.3.1 ShapeChange setup
2.2.2.3.2 UML model edition
2.2.2.3.3 Automatically application schema generated by ShapeChange
2.2.2.3.4 Generating a feature collection from the automatically generated application schema
2.2.2.4 GML profiles
2.2.2.5 Using Simple feature profile
2.2.2.6 GML media type
2.2.2.7 The axis order issue

2.2.3 Simple WFS Service Interface. Serving features

2.2.3.1 Describing Your WFS Server: The GetCapabilities operation
2.2.3.1.1 GetCapabilities required
2.2.3.1.2 Capabilities document
2.2.3.2 Describing Your FeatureTypes: The DescribeFeatureType operation
2.2.3.2.1 DescribeFeatureType required
2.2.3.2.2 DescribeFeatureType response: GML application schema
2.2.3.3 Serving a Feature collection: The GetFeature operation
2.2.3.3.1 Implementing GetFeature: Required Parameters
2.2.3.3.2 GetFeature Response. GML data
2.2.3.4 Exceptions

2.2.4 Basic WFS Service Interface. Creating new queries

2.2.4.1 Forgetting about the geometries: The GetPropertyValue operation

2.2.5 Transactional WFS Service Interface. Updating features

2.2.5.1 Implementing a Insert Transaction: Required Parameters
2.2.5.2 Insert transaction response
2.2.5.3 Implementing a Update Transaction: Required Parameters
2.2.5.4 Update transaction response
2.2.5.5 Implementing a Delete Transaction: Required Parameters
2.2.5.6 Delete transaction response

2.2.6 Locking WFS Service Interface. Decentralized updating features


<<Prev T.O.C.  Next>>
Tag
none

Files (0)

 
You must login to post a comment.