View source for 23.07.2014 Geospatial Cluster

Google Hangout - 2pm-3pm

'''People'''

*FAO: E.Blondel
*CNR: P.Pagano, G.Coro, F.Sinibaldi, F.Mangiacrapa

'''Summary'''

Exchanges around Layer dimension widget in GeoExplorer/Gis Viewer
* it was clarified that the use case described in #2996 is more related to the GIS Viewer than GeoExplorer, and deals with filtering on layer DIMENSIONS, in order to visualize dimension-enabled observations.
* another use case related with dimensions was highlighted by CNR. It's out of scope of the current ticket, and relates to the capacity to search on a given dimension like time (this might be addressed later in a separate ticket)
* need of generalization, e.g. While available in WMS implementations like Geoserver or Mapserver, it might not be the case for other WMS implementations used in the iMarine infrastructure. This raises the problem if WMS Time/Elevation is OGC approved or not.
* on how to distinguish between dimension-enabled vs. disabled layers: having a metadata temporalExtent (or verticalExtent for elevation) does not mean that the associated WMS resource includes an explicit DIMENSION:
**CNR asked if there is a way to known in Geoserver if a layer is dimension-enabled
**According to FAO, only one way to get this information without authentication, the WMS GetCapabilities, which includes for a layer, the dimension information and range.
**GetCapabilities could be used but targets a instance of WMS service, hence a list of layers, which can makes the document huge. A cache system should be used if GetCapabilities documents are parsed.
* In term of graphical widget:
** The time slider as mentioned by CNR, as some work was done in the project such kind of widgetr
** A calendar widget was also suggested by CNR & FAO

'''Development plans'''
* CNR mentioned the scheduled activity on integrating OWS Context (Terradue OWS4J) within the GeoExplorer/GisViewer, and the fact that the Layer Dimension widget would be started after this activity, for October 2014.
* FAO will further discuss internally if this is fine, or if more priority should be given to this enhancement

'''Other GIS aspects'''
* Clarifications were given about scope of geonetwork-manager (client for interacting with Geonetwork Web-Services) vs. Geotoolkit (for generating the metadata)
* CNR reported issues with Geotoolkit (Geotk) to deal with the metadata production. They use Geotk 3.20. FAO currently uses 3.21 in GEMS. CNR will analyse upgrade of Geotoolkit, and investigate issues dealing marshalling metadata TemporalExtent.
* FAO has shown a example of GEMS metadata (successfully generated), handling the TemporalExtent, and generated with Geotk.
* The issue of conflict between official OGC approved GeoAPI vs. Geotools gt-opengis module was highligthted.

'''Actions'''
* Emmanuel: liaise with A.Ellenbroek to discuss priorities, and report to CNR