Changes between Version 3 and Version 4 of GeoServer_integrationActivities


Ignore:
Timestamp:
Jan 14, 2008, 7:24:52 AM (17 years ago)
Author:
ticheler
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GeoServer_integrationActivities

    v3 v4  
    55GS = !GeoServer team
    66
    7 || Who? || Description || Steps ||
     7|| Who? || Description || Details ||
    88|| GN || Changes to the !GeoNetwork's editor. || When editing an online recource, the 'upload' button present in the editor, will redirect to another page that will contain a form with the following contols: ||
    99||  ||  ||  - File : an upload file control ||
    … …  
    1414||  ||  ||  - A button to upload the map ||
    1515||  ||  ||  - A back button to return to the editor ||
    16 || GN || Service deploy: use of the GS API of the communication layer to create a service. || Input parameters will come from the web form and will be: ||
    17 ||  ||  ||  - SRS, layer name, mimetype, a link to allow GS to get the data file ||
     16|| GN || Service deploy || Use of the GS API of the communication layer to create a service. Input parameters will come from the web form and will be: SRS, layer name, mimetype, a link to allow GS to get the data file ||
    1817|| ||  ||  ||
    19 || GN || - When an uploaded map is removed, GN should check if that map has a service created on GS. In this case, GN should delete that service from GS using the developed communication layer. ||
     18|| GN || Remove map service || When an uploaded map is removed, GN should check if that map has a service created on GS. In this case, GN should delete that service from GS using the developed communication layer. ||
    2019||  ||  ||  ||
    2120|| GS || Provide a server side API to create and remove services. || Creation: depending on the input mime type, GS will discriminate between a geotiff image and a zipped shape file and will create the service accordingly. ||
    2221||  ||  ||  ||
    23 || GN || Make GN's group names unique and readonly in order to use them as GS's namespaces || ||
     22|| GN || Unique Group names || Make GN's group names unique and readonly in order to use them as GS's namespaces ||
    2423||  ||  ||  ||
    25 || GS || Provide a SRS text file with all SRS codes present in GS. Each line of this file will have this format (fields are comma separated, 1 srs per row): || '<srs-id>', 'n', '<short label>', '<description with no CR/LF>' ||
    26 ||  ||  ||  Here 'n' is an internal, fixed flag. It will indicate if the SRS must be displayed in the combobox. ||
     24|| GS || Spatial Reference System (SRS) || Provide a SRS text file with all SRS codes present in GS. Each line of this file will have this format (fields are comma separated, 1 srs per row): '<srs-id>', 'n', '<short label>', '<description with no CR/LF>' Here 'n' is an internal, fixed flag. It will indicate if the SRS must be displayed in the combobox. ||
    2725||  ||  ||  ||
    28 || GN || Creation and filling of a database table with content of the SRS file from the task above. Service to retrieve information from that table. || ||
     26|| GN || SRS service || Creation and filling of a database table with content of the SRS file from the task above. Service to retrieve information from that table. ||
    2927||  ||  ||  ||
    30 || GS || Class to authenticate on !GeoNetwork. This class will use the xml service xml.user.login to login inside GN. || ||
     28|| GS || Authentication || Class to authenticate on !GeoNetwork. This class will use the xml service xml.user.login to login inside GN. ||
    3129||  ||  ||  ||
    32 || GS || Create a tiny communication layer to communicate with !GeoServer. This will be provided as a separate jar that will include a high level API to access GS's services. The API must include at least the operations needed for the integration (create service, remove service, ...). || ||
     30|| GS || Communication layer to !GeoServer || Create a tiny communication layer to communicate with !GeoServer. This will be provided as a separate jar that will include a high level API to access GS's services. The API must include at least the operations needed for the integration (create service, remove service, ...). ||