Loading...
 
ESA > Join & Share > HMA-T > ERGO PROGRESS 0808 4CT
Print

ERGO PROGRESS 0808 4CT

WP2200 Support to the requirement definition: OMAR


Activities performed

  • none.


Outcomes and results

  • none.


Problems and concerns

  • none.


Plans for next period

  • This WP has been completed

WP3200 Implementation of the CSW/EbRim and EO Application Profile for CSW 2.0 /EbRim based on the OMAR


Activities performed

  • Most important parts of OASIS ebXML Registry Information Model v3.0 are implemented. All the parts needed to support implementation of the EO Product Application Profile are supported.
  • Implementation of the OGC CSW 2.0 EO Application Profile for ebRIM (as specified in OGC 06-131r3).
  • First release of implementation of the OGC CSW SOAP interface. The following SOAP operations are implemented: Transaction, GetRecordsById and GetRecords
  • The Transaction operation also includes a translation of EO Products GML to ebRIM EO Product format. This function will be re-used later for implementation of the Harvest operation.
  • GetRecords supports search queries with the following spatial operators: Disjoint, Touches, Overlaps, Crosses, Equals, BBOX, Within, Intersects, DWithin, Contains. Note: This is more then the minimal required spatial operators as defined in ERG-SR-EBR-OPE-180.
  • GetRecords supports search queries with the following comparison operators: PropertyIsLessThanOrEqualTo, PropertyIsLike, PropertyIsNotEqualTo, PropertyIsGreaterThanOrEqualTo, PropertyIsNull, PropertyIsLessThan, PropertyIsBetween, PropertyIsEqualTo, PropertyIsGreaterThan. Note: This is more then the minimal required spatial operators as defined in ERG-SR-EBR-OPE-190.
  • Implementation of passing of number of records to be returned (ERG-SR-EBR-OPE-150).
  • Implementation of support for joins, variable substitutions and XPath expressions in search queries (ERG-SR-EBR-OPE-160).
  • Start implementation of Java Client API
  • Development of SOAP-UI based unit tests for all spatial and comparison operators
  • Deployment of a testable public version of the registry online (to enable external testing)
  • Startup of a Google Code project with name buddata-ebxml-registry. This will be the new name: "Buddata ebXML Registry/Repository".



Outcomes and results

  • Preliminary technical test results are performed on 4600 records (based on generated metadata).
  • GetRecords operations (via the SOAP-UI unit tests) return results on such recordset in 0,5 seconds (limited to a collection of max. 20 records) on a development laptop and with no special optimization performed.
  • A first release will soon be published beginning of September on Google Code with license type GPL v3.


Problems and concerns

  • We are awaiting the 20.000 test records (or more) in GML EO Product format to perform tests to prove the minimally required performance.


Plans for next period

  • Implementation of the temporal operators
  • Meet performance requirements based on the test dataset of 20.000 records or more.
  • More testing and fixing errors from tests
  • Writing more unit tests
  • Implementation of GetCapabilities and DescribeRecords


WP4200 Support to the testing activities: OMAR


Activities performed

  • Activity is not yet started.


Outcomes and results

  • none.


Problems and concerns

  • none.


Plans for next period

  • none



Contributors to this page: Jef Vanbockryck .

Page last modified on Friday 29 of August 2008 15:05:32 CEST by Jef Vanbockryck.

Category: HMA-T