ESA > Join & Share > HMA > HMA Implementation status at 16 September 2011

HMA Implementation status at 16 September 2011

EO Product Metadata

Implemented by all projects implementing EO Product Catalogue

HMA-I version: implemented by ESA, EUMETSAT, DLR, Spot-IMAGE, e-Geos, DMC, VITO, MDA, InfoTerra, RapidEye, Euromap, GENESIS EC-FP7 Integrated Project

Implementation Planned by Digital Globe–EUSI, DEIMOS

Available in commercial product: ERDAS

HMA-FO version: third party implementation not yet available

OGC document type:

Standard

Status : approval pending (due soon)

Open source code available: N/A

EO Product Catalogue

HMA-I version:

implemented by ESA, EUMETSAT, DLR, Spot-IMAGE, DMC, VITO, MDA, InfoTerra, RapidEye, Euromap, GENESIS EC-FP7 Integrated Project

Implementation Planned by e-Geos, Digital Globe–EUSI, DEIMOS

Available in commercial product: ERDAS, Taitus

HMA-FO version: third party implementation not yet available

OGC document type:

Standard

Status : HMA-I approved HMA-FO in OGC internal review

Open source code available: HMA-I yes

Collection & Service Discovery

HMA-I version:

implemented by ESA, EUMETSAT

Commercial products: ERDAS

HMA-FO: N/A

OGC document type:

Discussion Paper

Status : approved

Open source code available: yes

ORDER

HMA-I version implemented by:

ESA, EUMETSAT, DLR, Spot-IMAGE, DMC, VITO, MDA-RSAT, InfoTerra, RapidEye, Euromap, GENESIS EC-FP7 Integrated Project

Implementation Planned by e-Geos, Digital Globe–EUSI, DEIMOS, RCM

Commercial products: Taitus

HMA-FO improved and more complete version available

OGC document type:

Standard

Status : approved (end of August 2011) to be published soon

Open source code available: yes

EO Map Server

HMA-I version implemented by: ESA, EUMETSAT, DMC, GEOLAND-2

Commercial Products

Spacemetric/Keystone

Planned:

DEIMOS

OGC document type:

Best Practice

Status : approved

Open source code available: N/A

COTS: Spacemetrics

Online Data Access – Coverages

HMA-FO implementation ongoing by

Project O3S (GSTP-ESA)

Project DREAM (GSTP-ESA) planned

OGC document type:

Standard

Status : approvedwith documents still in the approval process

Open source code available:

server: yes

Identity Management

HMA-T Implementation By:

ESA, EUMETSAT, DLR, Spot-Image, GEOLAND-2 GMES Service Project (to various levels)

OGC document type:

Best Practice Paper

Status : approved

Open source code available: N/A

Feasibility Analysis

HMA-FO implementation planned by:

ESA (DREAM GSTP Project) with requirements from EMSA and EUSC. The Earth Observation CFI will be updated to support the feasibility analysis standard.

RCM (Radarsat Constellation)

OGC document type:

Standard

Status : approved

Open source code available:

client: yes

server: yes

Additional information

A table of standards implemented for by GCMs is available on the HMA Community wiki

The table is under configuration control of the HMA AWG

Information of which standard is implemented by ground segment is as well available within the same wiki

Input on implementation by industry is available on the HMA forum

Contributors to this page:

Page last modified on Friday 16 of September 2011 15:14:27 CEST by .

Category: HMA

History

Search Help

Non Advanced Search or Natural Search

The documents are returned sorted on relevance depending on order, proximity, frequency of terms.

Advanced Search or Boolean Search

Default search behavior

By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:

objects that include both terms
objects that include the term wiki
objects that include the term forum

Requiring terms

Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.

Excluding terms

Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum

Grouping terms

Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.

Finding phrases

Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.

Using wildcards

Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:

objects that include the term run
objects that include the term runner
objects that include the term running

Reducing a term's value

Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.

Changing relevance value

Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.