Changes between Version 14 and Version 15 of GeoManual


Ignore:
Timestamp:
02/12/08 15:29:46 (11 years ago)
Author:
domlowe
Comment:

Fixing reset of the false wikiwords

Legend:

Unmodified
Added
Removed
Modified
  • GeoManual

    v14 v15  
    99All this information is held by a !FeatureTypeMapping object, and a !ComplexDataStore, in turn, may hold an arbitrary number of that objects, each defining a !FeatureType that the !DataStore exposes. 
    1010 
    11 Geoserver uses an XML file which contains these definitions, and whose location in the form of an URL must be used to create a DataStore instance through the GeoTools DataStoreFinder lookup system.  This document presents detailed instructions for creating these definitions, specifying database connection parameters along with other necessary configuration related aspects of exposing a FeatureType through Geoserver. 
     11Geoserver uses an XML file which contains these definitions, and whose location in the form of an URL must be used to create a !DataStore instance through the !GeoTools !DataStoreFinder lookup system.  This document presents detailed instructions for creating these definitions, specifying database connection parameters along with other necessary configuration related aspects of exposing a !FeatureType through Geoserver. 
    1212 
    1313 
     
    4343 
    4444 
    45 The "describeFeatureType" request for a particular FeatureType against Geoserver is essentially a request for a schema file which could be used to validate a feature in the WFS getFeature response for that FeatureType.  In theory, Geoserver should be able to dynamically generate this schema file based on the mappings specified in the mapping file (Section 5) for a !FeatureType.  Unfortunately, at present, Geoserver does not handle this request very well. To get around this problem, the module of Geoserver that is responsible for dealing with "describeFeatureType" request has been modified so that it uses the relevant schema file from the Geoserver’s data directory instead of trying to generate it dynamically.  This requires further configuration of the Geoserver’s data directory as follows:   
     45The "describeFeatureType" request for a particular !FeatureType against Geoserver is essentially a request for a schema file which could be used to validate a feature in the WFS getFeature response for that !FeatureType.  In theory, Geoserver should be able to dynamically generate this schema file based on the mappings specified in the mapping file (Section 5) for a !FeatureType.  Unfortunately, at present, Geoserver does not handle this request very well. To get around this problem, the module of Geoserver that is responsible for dealing with "describeFeatureType" request has been modified so that it uses the relevant schema file from the Geoserver’s data directory instead of trying to generate it dynamically.  This requires further configuration of the Geoserver’s data directory as follows:   
    4646 
    4747In geoserver's data directory (Figure 1), create two folders called "schemas" and "xsl_conf".  In the folder called "xsl_conf", create a file called "xsl_conf_describe.config", which should contain key-value pairs where keys will be the names of different !FeatureTypes exposed by Geoserver and values will be relative paths to their corresponding schema files. An example of this is !PointSeriesFeature=schemas/csml.xsd, where !PointSeriesFeature is the name of a !FeatureType and schema/csml.xsd is the relative path to its corresponding schema file. The "schemas" folder will contain all schema files that are to be used as the results of “describeFeatureType” requests for the !FeatureTypes defined in Geoserver. 
     
    226226'''5.4 Attribute and id(s) mappings''' 
    227227 
    228 The last step is to define how to map attributes from one source !FeatureType to a target one. The typeMappings property contains a series of !FeatureTypeMapping elements, where each one defines exactly the information that a org.geotools.data.complex.FeatureTypeMapping object holds. 
     228The last step is to define how to map attributes from one source !FeatureType to a target one. The typeMappings property contains a series of !FeatureTypeMapping elements, where each one defines exactly the information that a org.geotools.data.complex.!FeatureTypeMapping object holds. 
    229229 
    230230For instance, this information is 
     
    255255        </groupBy> 
    256256}}} 
    257       * the mappings between FeatureSource and FeatureType. The mappings consist of three sets of mappings, one for the identifyable attributes (the  
    258         ones with gml:id), such as instances of the FeatureType itself and any direct or nested property that is also identifyable. The second is for   
     257      * the mappings between !FeatureSource and !FeatureType. The mappings consist of three sets of mappings, one for the identifiable attributes (the  
     258        ones with gml:id), such as instances of the !FeatureType itself and any direct or nested property that is also identifiable. The second is for   
    259259        mapping to any other attribute of an element in the target schema.  The final type of mapping is for the target attribute values. It should be 
    260260        noted that both for id and attribute mappings, the expression used to assign a value is expressed as an OGC's Common Query Language (OCQL)