EO Profile of GML and HMA Product Catalogfor VITO CVB

FRASCATI ESRIN 15th of December 2009 Slide 1

EO Profile of GML and HMA Product EO Profile of GML and HMA Product CatalogCatalog for VITO CVBfor VITO CVB

HMA-T Phase 2 FP Meeting15th of December 2009, ESRIN

Steven Smolders, GIM nvTim Jacobs, VITO

Frédéric Houbie, ERDAS


OverviewOverview

Achievements• GML Application schema for EO Products• EO EP of ebRIM CSW RI• EO EP of ebRIM CSW with GetRepositoryItem

demonstration• Integration with EO WMS

Open Issues

HMA-T demos

Future work

FRASCATI ESRIN 15th of December 2009

EO GML achievementsEO GML achievements

• Tested the GML 3.1.1 Application schema for EO Products on a wide range of “derived” SPOT VGT Products:

• “Base” Physical Values Product: VGT- P• Synthesis Products: VGT S1, S10, D10• Derived Bio/GeoPhysical Products (produced in

VGT4africa, GMFS, GeoSuccess projects):• Normalised Difference Water Index (NDWI)• Vegetation Productivity Indicator (VPI)• Fractional Cover (fCover)• Leaf Area Index • Albedo• Phenology

• Aerosol Optical Depth (MERIS derived)

Slide 3



• A set of Change Requests (internal to SWG) for the EO GML that are addressed in OGC06-080r5

• cardinality of <eop:ProcessingInformation> or subelementsinconsistency between text and schemas => ProcessingInformation Cardinality changed to 1..n

• cardinality of ProductType - schema implies it is mandatory =>Made optional

• In order to describe synthesis products, more flexibility is to be allowed in the compositeType element: its type will be changed to xs:duration

• Editorial corrections (e.g. EarthObservationEquipement)

Slide 4


EO GML achievementsEO GML achievements• For description of VITO “derived” vegetation products a set

of additional metadata elements were described in a separate schema “vdp” for “vegetation derived products”targeted at

Product Discovery => Catalogues

Product exploitation => descriptive file that is shipped

together with the products: important to have

– Lineage information (different processing steps)

– Information for the correct interpretation of the images (flag

values, band ranges, …)

• Convenient to have same metadata model/format for bothSlide 5



• Schema contains mainly exploitation metadata: • Information for the correct interpretation of the

images • Significant digital value (display) ranges

(min/max)• Physical values ranges (min/max)• Scale factor and Offset • Flag values (Label, code and value): e.g. snow,

cloud, missing meteo values, ...• lineage information (different

processing steps)

Slide 6


EO EP AchievementsEO EP Achievements

EO EP of ebRIM CSW compliant Catalogue available as Reference Implementation

Containing EO GML EOP Metadata for

– 14 VGT4africa product collections with data covering 01/01/08 to30/06/09

– Metadata examples for VGT-P, S1, S10 and D10 products

Powered by ERDAS Catalog Solution

Compliance tested (against non-consolidated tests of IGN, CNR and INTECS)

Integrated in the HMA Portal

– Existing workflows

– Specific stylesheets


EO EP AchievementsEO EP Achievements

• Alternative Catalogue instance with metadata harvestedfrom VDP Compliant GML files Demonstrates on how extended “evaluation” metadata canbe offered from an EO EP CSW Compliant Cataloguewithout development of a new ebRIM-CSW EPUsing GetRecords for “Search” operationUsing GetRepositoryItem for “Present” operation to return “VDP compliant GML”

GetRepositoryItem in principle only HTTP GET bindingOne GetRepositoryItem call required for eachproductCompliancy tests fail due to “strict” comparisonbetween ebRIM and GML


EO EP CSW EO EP CSW ebRIMebRIM –– EO WMSEO WMS

• Browse images for catalogued products are served via the Web Map Service protocol using the InfoTerra UK WMS Application Schema for EO Products ReferenceImplementation

• Linkage from Catalogue metadata to EO Profile of WMS using the EO GML BrowseInformation/fileName element containing a WMS GetMap URL

• Interactive browse


Open IssuesOpen Issues

“Light” EO extension package approach• Problem:

Full mapping of EO Profile of GML to EO EP was initially done tominimise number of requests/responsesConsequence is that each (minor) change to or new product type within EO GML implies changes to EO EP of CSW ebRIM which makes EO GML redundant and EO EP of CSW hard to maintain

• Potential Solutions:Use of GetRepositoryItem to retrieve GML as demonstrated but changes to this operation are required to support SOAP and possibly allow multiple GML instances to be returned in responseto a single requestReturn of ebRIM and EO GML in a “composite message” structure using Multipart/MIME, SOAP attachments or similarUnder investigation in HMA FO project


Demonstration 1Demonstration 1

VGT4Africa EO EP ebRIM CSW Catalogue with EO WMS


VGT4Africa EO EP ebRIM CSW Catalogue with GetRepositoryItem

and EO WMS

Demonstration 2Demonstration 2


Future WorkFuture Work

Development of “official” EO GML derived application schemas for EO Synthesis and Systematic products. Generalising work performed in HMA-T by applying it to other product collections => addressed in HMA Follow On Task 1

Consolidation of the EO Product Discovery/ Evaluation / Ordering/ Data Access Chain scenarios and standards interlinkage involving CIM EP (collections and services), EO EP, EO GML, EO WMS, HMA Ordering and EO WCS


Open ActionsOpen Actions86: Propose a way to change EO GML to achieve what is in

RID SS-2: CR text is ready: proposed to take this up in the HMA-FO schema evolutions

186: Check with VITO whether URL to download products canbe provided => Implemented interactive browse instead

188: Move services to the operational environment and addlinks to SSE clients to HMA-T WIKI. => services are availableon services-test. Issue with deployment onservices.eoportal.org


Compliancy tests (1)Compliancy tests (1)Initial analysis of IGN Runs of compliancy tests (14/12/09)

• ATC1.2: ' ad hoc query. GIM VITO Catalogue does not support 'urn:ogc:def:ebRIM-Query:OGC:listExtensionPackages: Confirmed issue

• TC1.5 : Problem in mappings between repository item and extrinsic object (id: urn:ogc:def:EOP:VITO:VGT4AFRICA.ALBQ:VGT4AFRICA_ALBQ_20080211_Africa_POSTEL) : Confirmed Issue

• ATC1.6 : there is no rim:Classification inside the wrs:ExtrinsicObject (EOProductTypes classification): To bechecked


Compliancy tests (2)Compliancy tests (2)ATC1.12 : slot fileName must have type "anyURI", not "string" : Confirmed issue

ATC1.15 : slot fileName must have type "anyURI", not "string" : Confirmed issue

ATC1.18 : Two mandatory slots are missing on EOMaskInformation : fileName and format: Confirmed issue

Catalogue update to be provided by 15/01/2010

Documents

EO Profile of GML and HMA Product Catalogfor VITO CVB