Changes between Version 10 and Version 11 of GeoManual
- Timestamp:
- 21/04/08 14:29:14 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeoManual
v10 v11 1 = GeoServer "Complex DataStore/Community Schema": User Manual =1 = GeoServer "Complex !DataStore/Community Schema": User Manual = 2 2 3 3 The objective of this document is to provide guidelines for creating and defining a FeatureType that is to be exposed by the “Community Schema” version of Geoserver. In summary, this special version of Geoserver facilitates serving up data from a relational database, in an externally defined schema, which exists independently of the underlying data structure of the database. In order to achieve this feat, Geoserver requires the followings: … … 25 25 4. The schema file along with other schemas that it depends on (unless they are referenced via URLs in the schema) that the XML output of a FeatureType conforms to may also be placed in this folder. However, it is recommended to keep the schemas used for all FeatureTypes exposed by Geoserver under the commonSchemas folder (Figure 1) in Georserver’s Data Directory. 26 26 27 [ img http://proj.badc.rl.ac.uk/ndg/attachment/wiki/GeoManual/geo_dir.JPG]27 [[Image(geo_dir.JPG)]] 28 28 [[BR]] 29 29 '''Figure 1: Structure of a Geoserver’s Data Directory''' … … 35 35 In order to serve up a FeatureType through Geoserver, it is necessary to properly define the associated DataStore in the Geoserver catalog. The Geoserver catalog is defined and configured in an XML document called “catalog.xml” in Geoserver’s data directory. This XML document essentially contains three categories of information: datastores to load, namespaces to be used by the datastores and styles to be used for the Web Map Service (see section 4). Figure 2 below provides an example of the catalog.xml document with explanations for each of its significant aspects: 36 36 37 [ img http://proj.badc.rl.ac.uk/ndg/attachment/wiki/GeoManual/catalog.JPG]37 [[Image(catalog.JPG)]] 38 38 [[BR]] 39 39 '''Figure 2: Catalog.xml file''' … … 127 127 The next step is to specify information necessary to acquire the data source (e.g. database) used. This information is recorded under the DataStore element, which is a child element of sourceDataStores element. The DataStore element requires a unique identifier which is recorded under its child element id. Information, such as database drivers and SQL used to retrieve the desired dataset is recorded as a series of name-value pairs under ''parameters/Parameter'' elements. It is permissible to add as many ''Parameter/name'' and ''Parameter/value'' elements as needed to configure the source datastore used, and as many DataStore elements as needed. The table below outlines a list of different parameters required to define a DataStore element. 128 128 129 [ img http://proj.badc.rl.ac.uk/ndg/attachment/wiki/GeoManual/table2.JPG]129 [[Image(table2.JPG)]] 130 130 [[BR]] 131 131 … … 266 266 267 267 268 [ img http://proj.badc.rl.ac.uk/ndg/attachment/wiki/GeoManual/table.JPG]268 [[Image(table.JPG)]] 269 269 [[BR]] 270 270 '''Table 2: Different Mapping Types'''
