Task #7579

Publish all available CLS outputs as WMS/WFS for use in AAPS VRE

Added by Emmanuel Blondel over 2 years ago. Updated 9 months ago.

Status:ClosedStart date:Mar 17, 2017
Priority:HighDue date:
Assignee:Manuel Goacolou% Done:

0%

Category:-
Sprint:WP07
Infrastructure:
Milestones:
Duration:

Description

Spatialite files can now be published as WMS/WFS.

This ticket is to proceed with the (batch) publication of all available CLS outputs as WMS/WFS. CLS to provide choice how to structure the layers (e.g. 1 workspace per country, etc), symbology styles to apply, etc.

I let you assign this task to the right people.

(I would advice to consider the related ticket on visualization #7578, as the chosen scenario might condition your way to publish your Spatialite files)


Related issues

Blocks BlueBRIDGE - Project Activity #7578: Discovery, Access & geovisualization of CLS Spatialite WM... Rejected Mar 17, 2017
Blocked by BlueBRIDGE - Project Activity #5828: Evaluate feasibly to publish Spatialite layer in GeoServe... Closed Dec 02, 2016

History

#1 Updated by Emmanuel Blondel over 2 years ago

  • Blocks Project Activity #7578: Discovery, Access & geovisualization of CLS Spatialite WMS/WFS in AAPS VRE added

#2 Updated by Emmanuel Blondel over 2 years ago

  • Blocked by Project Activity #5828: Evaluate feasibly to publish Spatialite layer in GeoServer with existing tools added

#3 Updated by Emmanuel Blondel over 2 years ago

@anton.ellenbroek@fao.org to clarify if my technical support is required or not.

#4 Updated by Nicolas Longépé over 2 years ago

  • Assignee changed from Nicolas Longépé to Manuel Goacolou

#5 Updated by Emmanuel Blondel over 2 years ago

Following our last discussion with CNR about the plan to publish & exploit CLS outputs (see https://support.d4science.org/projects/bluebridge/wiki/170327Telco, and @anton.ellenbroek@fao.org to give you more info if needed):

  1. we would use a single Geoserver workspace where all CLS outputs are published. This workspace is now named "aaps", probably it will be renamed as "staging" standing for staging area. Depending on the nb of layers to be published, GetCapabilities will be usable or not (in principle it should if they are only few layers), but keep in mind that later discovery should probably be relying on metadata discovery, when supporting technologies (gcube metadata REST interface) will be available for invokation (e.g. in Python script).
  2. another Geoserver workspace will be used for "public". A public layer will be published from staging area after a review/validation process, and metadata will be created at this step only.
  3. Two different map viewers (portlets) will be used for staging area and public area. A reviewer will be able to access the first on (adhoc viewer to implement), A default user the second one (certainly the GeoExplorer application already available). Review capabilities will need to be further discussed, but consider that depending on the requirements, the data structure (schema) of the Spatialite outputs may need to evolve a bit.

The present ticket is to tackle point 1, for which we need CLS to follow-up as all the other tasks depend on it:

  • give details on the data to be published: layer granularity (dimensions), naming (concatenation of elements identifying the layer) + keywords associated, used for layer identification (& later facilitate eventual clustering e.g. per country)
  • proceed with the publication of the available outputs as layers in https://geoserver1-p-spatial.d4science.org/geoserver/

Hope this clarifies

#6 Updated by Pasquale Pagano 9 months ago

  • Status changed from New to In Progress

#7 Updated by Pasquale Pagano 9 months ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF