Changes between Version 5 and Version 6 of GeoServer_integration
- Timestamp:
- Aug 17, 2009, 8:14:36 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeoServer_integration
v5 v6 11 11 12 12 The purpose of this integration is to allow users to upload a GeoTIFF file or a zipped Shapefile to a metadata and deploy that data as a map service on !GeoServer. After upload, the user will see a button that allows her/him to trigger this deployment. The metadata will be adjusted accordingly and the Capabilities document of !GeoServer will provide a link back to the !GeoNetwork metadata record. 13 14 15 [[Image(publish-wxs.png)]] 13 16 14 17 === Proposal Type === … … 37 40 1. A user edits a metadata, uploading the file as it is needed. Metadata also contains informations about layer type and SRS. 38 41 2. An item in the metadata list provided by the metadata search will have the button publish (or unpublish) related to it, if the resource has a valid layer stored in GN, and the logged user has edit privileges on the metadata itself. 39 3. When the publish button is pressed, GN will create the REST URLs needed by GS to publish the given layer. The REST URL will be different in case of raster layers or vect layers. We need at least a couple of URL in both cases: 40 1. Raster layers: 41 1. Creation of CoverageStore 42 2. Creation of Coverage 43 2. Shape layers: 44 1. Creation of DataStore 45 2. Creation of FeatureType 42 3. When the publish button is pressed, GN will create the REST URLs needed by GS to publish the given layer. The REST URL follow http://docs.geoserver.org/1.7.x/en/user/extensions/rest/rest-config-api.html 46 43 47 44 No layer name or other info will be asked to the user. We can make up this info in this way: 48 45 * 49 46 * Layer name: the layer name is usually derived by GS from the file name. There may be problems of name uniqueness. They could be resolved by using GS' alias facility, but there seems to be problem in using aliases in REST configuration. At the moment this is an open problem. 50 47 * SRS can be derived directly from ISO metadata. If such an info is not supplied (that field is optional in ISO), we will provide a predefined (hardcoded?) SRS. 48 49 !GeoNetwork Configuration to register !GeoServer nodes : 50 * !GeoServer node(s) 51 * URL 52 * namespace (default geonetwork) 53 * workspace (default geonetwork) 54 * login 51 55 52 56 … … 56 60 == Risks == 57 61 Due to the limited resources, complex scenario's will not be dealt with and not all data may be suitable for use. Both GeoTiff and Shapefiles require to be properly formatted before they are uploaded. 58 The integration will only work with !GeoServer instances that are embedded in the !GeoNetwork release. External !GeoServer instances are not immediately foreseen to be supported.59 62 60 63 == Participants == 64 * Francois 61 65 * Emanuele Tajariol (!GeoNetwork) 62 66 * Jeroen Ticheler (!GeoNetwork)
