Loading...
 
ESA > Join & Share > ERGO > ERGO PROGRESS 0902 GEOCAT
Print

ERGO PROGRESS 0902 GEOCAT

ERGO Progress February 2009: GeoCat B.V.

WP2300 Support to the requirement definition: GeoNetwork opensource


Activities performed

  • none.

Outcomes and results

  • none.

Problems and concerns

  • none.

Plans for next period

  • This WP has been completed

WP3300 Implementation of the CSW/EbRim profile based on the GeoNetwork opensource software


Activities performed

  • One-click Installer created for the application. The installer provides an embedded servlet container Jetty 1.6.14 and the ebRIM registry automatically deploys on web application startup.
  • CSW web service created based on Axis2. The implementation uses WSDL 1.1 (see also problems and concerns)
  • CSW 202 GetRecord, GetRecordById, GetRepositoryItem and GetRepositoryItemResponse service implementation
  • ISO19139 to ebRIM RegistryObjects conversion has been completed and is undergoing internal validation.
  • Added all Basic Extension Slot names (OGC 07-144r2 section 9)
  • Added all CIM Extrinsic Object types, etc.
  • Added all CIM Classification Schemes


Outcomes and results

  • One-click multi-platform installer.
  • Updated ADD v0.2
  • CIM packages
  • ISO19139 to ebRIM transformation service


Problems and concerns

  • What version of WSDL should we use? The specification describes version 2.0, but this is technically challenging since WSDL 2.0 is not widely used yet and the general consensus seems to be that we should use WSDL 1.1. We have both WSDL 1.1 and 2.0 documents for the CSW specification. With 4CT we have discussed what version to use and the general consensus is that we should use WSDL 1.1. Is this OK with ESA and Intecs?
  • Issues concerning the ISO to ebRIM conversion have been described here: http://trac.osgeo.org/geonetwork/wiki/ISO2ebRIMIssues

The most important ones:

  1. The object type of DataSet is defined in the Basic Extension package (OGC 07-144r2), as being "urn:ogc:def:ebRIM-ObjectType:OGC:Dataset". In the CIM spec (07-038), many references are made to DataSet, but with object type "urn:x-ogc:specification:csw-ebrim-cim:ObjectType:Dataset". This type is not defined in 07-038. Which one should be used?
  2. Table F.3 : abstract is mapped to Description. Now is a Description something that has a LocalizedString, where the actual string value goes in attribute 'value'. That one has a max length of 1024. What to do?
  • We will need feedback from among others ERDAS on the issues identified.
  • XPATH search implementation is considered at high risk at the moment. It will be proposed to remove this requirement from the project.


Plans for next period

  • finalize the searchers
  • Implement the team engine testing
  • Draft installation manual

WP4300 Support to the testing activities: GeoNetwork opensource


Activities performed

  • Custom Team Engine was not available at URL, activity is delayed a little


Outcomes and results

  • none.


Problems and concerns

  • none.


Plans for next period

  • none

Contributors to this page: Jeroen Ticheler
Massimiliano Fanciulli .

Page last modified on Tuesday 17 of March 2009 09:20:09 CET by Jeroen Ticheler.