Difference between revisions of "GIS Publisher Service"
(Created page with 'The GIS Publisher service manages geospatial data and metadata in a gCube based infrastructure. It relies on the gCube information system to gather information on which platforms…') |
|||
| Line 1: | Line 1: | ||
The GIS Publisher service manages geospatial data and metadata in a gCube based infrastructure. It relies on the gCube information system to gather information on which platforms are available in the current scope, balancing the load between the different platform instances. Its goal is to deal with the heterogeneous GIS platforms offering a common interface to other gCube services / application which need to publish geospatial data. Since each platform has a different approach on how to manage data, the GIS Publisher service is designed as a pluggable service, delegating to each plugin the platform specific interaction to third party software. Other than abstracting from specific GIS platform implementations, the GIS Publisher balances the load between the platform instances, and manages the replicas of the same services. | The GIS Publisher service manages geospatial data and metadata in a gCube based infrastructure. It relies on the gCube information system to gather information on which platforms are available in the current scope, balancing the load between the different platform instances. Its goal is to deal with the heterogeneous GIS platforms offering a common interface to other gCube services / application which need to publish geospatial data. Since each platform has a different approach on how to manage data, the GIS Publisher service is designed as a pluggable service, delegating to each plugin the platform specific interaction to third party software. Other than abstracting from specific GIS platform implementations, the GIS Publisher balances the load between the platform instances, and manages the replicas of the same services. | ||
| + | |||
| + | =Overall Design= | ||
| + | [[File:GIS Publisher Overall Diagram.gif]] | ||
| + | |||
| + | Applications which need to publish geospatial data can interact with the service via the [GIS Publisher CL]. | ||
| + | A GISRequestConfiguration object is sent to the service, specifying : | ||
| + | |||
| + | * The GISData to publish | ||
| + | * The destination platform type | ||
| + | * Information to generate layers | ||
| + | |||
| + | The service enqueues every received request, assigning it a unique identifier. When a request is handled, the appropriate plugin is selected and invoked. At the end of the process a publish operation object is returned to the client, reporting information on : | ||
| + | |||
| + | * Published data references | ||
| + | * Published metadata | ||
| + | * Error messages (in case some of the operations fail) | ||
| + | |||
| + | |||
| + | =Modules= | ||
| + | |||
| + | ==GIS Publisher CL== | ||
| + | === Publising data === | ||
| + | ==GIS Publisher Framework Library== | ||
| + | === Implementing a plugin === | ||
| + | === CSquareCode handling === | ||
| + | === Available plugins === | ||
Revision as of 10:21, 7 May 2013
The GIS Publisher service manages geospatial data and metadata in a gCube based infrastructure. It relies on the gCube information system to gather information on which platforms are available in the current scope, balancing the load between the different platform instances. Its goal is to deal with the heterogeneous GIS platforms offering a common interface to other gCube services / application which need to publish geospatial data. Since each platform has a different approach on how to manage data, the GIS Publisher service is designed as a pluggable service, delegating to each plugin the platform specific interaction to third party software. Other than abstracting from specific GIS platform implementations, the GIS Publisher balances the load between the platform instances, and manages the replicas of the same services.
Contents
Overall Design
Applications which need to publish geospatial data can interact with the service via the [GIS Publisher CL]. A GISRequestConfiguration object is sent to the service, specifying :
- The GISData to publish
- The destination platform type
- Information to generate layers
The service enqueues every received request, assigning it a unique identifier. When a request is handled, the appropriate plugin is selected and invoked. At the end of the process a publish operation object is returned to the client, reporting information on :
- Published data references
- Published metadata
- Error messages (in case some of the operations fail)
