Changes between Version 8 and Version 9 of GeoServer_integration


Ignore:
Timestamp:
Nov 12, 2009, 7:54:14 AM (15 years ago)
Author:
fxp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GeoServer_integration

    v8 v9  
    1010== Overview ==
    1111
    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.
     12The purpose of this integration is to allow users to upload a GeoTIFF file or a zipped Shapefile to a metadata and deploy that dataset 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.
    1313
    1414
     15=== User Interface ===
     16[[Image(geopublisher.png)]]
     17
     18Actions :
     19 * Select a node to publish the dataset in (See configuration for details on adding a node)
     20 * Check button: Try to get current dataset in selected node.
     21 * Publish button: Publish current dataset to remote node. If dataset is already publish in that node, it will be updated.
     22 * Unpublish button: Remove current dataset from remote node.
     23 * Add online source button: Add an onlinesource section to the current metadata record pointing to the WMS and layername.
     24
     25=== Sequence diagram ===
    1526[[Image(publish-wxs.png)]]
    1627
    1728=== Proposal Type ===
    18  * '''Type''': GUI Change and Core Change
     29 * '''Type''': GUI Change and new geopublisher service
    1930 * '''App''': !GeoNetwork
    20  * '''Module''': Data Manager and Metadata editor
     31 * '''Module''': Metadata editor
    2132
    2233=== Links ===
    … …  
    2536 * '''Other wiki discussions''':
    2637 * '''Patch''': #159
     38  * Current status:
     39   * works with geotiff and a zip containing one shapefile (zip and shapefile name MUST be the same)
     40   * On big shapefile (more than 100M), OutOfMemoryError could be triggered on GeoNetwork side during file copy. Changing -Xmx and -XX:MaxPermSize parameters fixed the issue
     41   * Bug on !GeoServer 2.2 node - more test needed
    2742
    2843=== Voting History ===
    … …  
    3247
    3348== Motivations ==
    34 Integration of a map server allows users to quickly configure their data for interactive access without the need to go through the complexities of setting up and configuring a web map server. !GeoServer is already embedded with !GeoNetwork and uses the same Java technology making it easy to deploy both applications on any operating system.
     49Integration of a map server allows users to quickly configure their data for interactive access without the need to go through the complexities of setting up and configuring a web map server.
     50Web map server supported:
     51 * !GeoServer embedded with !GeoNetwork
     52 * Remote !GeoServer node (tested with 1.7.7)
     53
    3554
    3655== Proposal ==
    37 [wiki:GeoServer_integrationActivities List of Activities]
    3856
    39 We may provide an implementation for the following use case:
     57We provide an implementation for the following use case:
    4058
    41    1. A user edits a metadata, uploading the file as it is needed. Metadata also contains informations about layer type and SRS.
    42    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.
     59   1. A user edits a metadata, uploading the file as it is needed.
     60   2. In edit mode, online source section with a file for download attached, will provide the geopublisher panel.
    4361   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
    4462
    4563No layer name or other info will be asked to the user. We can make up this info in this way:
    46  *
    47     * 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.
    48     * 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.
     64 * 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.
    4965
    50 !GeoNetwork Configuration to register !GeoServer nodes :
    51  * !GeoServer node(s)
    52   * URL
    53   * namespace (default geonetwork)
    54   * workspace (default geonetwork)
    55   * login
     66
     67!GeoNetwork configuration to register !GeoServer nodes (geoserver-nodes.xml):
     68{{{
     69<nodes>
     70        <!--
     71                Add here all geoserver node which could
     72                be configure by GeoNetwork.
     73               
     74                @param name             Name of the GeoServer node, display to metadata editor
     75                @param namespace        Namespace to use. If not set, GeoServer will link store to another namespace.
     76                @param adminurl         GeoServer REST service config URL
     77                @param wmsurl           GeoServer WMS service URL use to display map preview
     78                @param wfsurl           GeoServer WFS service URL use to display map preview
     79                @param user             GeoServer user login
     80                @param password         GeoServer user password
     81        -->
     82        <node>
     83                <id>geoserver2</id>
     84                <name>My preferred GeoServer node</name>
     85                <namespacePrefix>geonet</namespacePrefix>
     86                <namespaceUrl>http://geonetwork-opensource.org</namespaceUrl>
     87                <adminurl>http://localhost:8081/geoserver/rest</adminurl>
     88                <wmsurl>http://localhost:8081/geoserver/wms</wmsurl>
     89                <wfsurl>http://localhost:8081/geoserver/wfs</wfsurl>
     90                <user>admin</user>
     91                <password>geoserver</password>
     92        </node>
     93}}}
    5694
    5795