"HMA Outline and Status - PowerPoint"
ESA GMES preparatory Activities: Heterogeneous Missions Accessibility Pier Giorgio Marchetti ESA / ESRIN Earth Observation Programme Ground Segment Department Project Manager HMA HMA December 2005 – Slide 1 HMA Background … The ground segment includes the “necessary interfaces for requesting and accessing data from national and Eumetsat missions forming part of GMES”… GAC(2004)7_Fin (12.07.04), Reflection Paper: GMES Space Observation Component The Concept comes from “Oxygen” and is applicable to any mission ESA plans to apply the same principles, standards and technical solutions not only to the GMES missions but for any ESA mission and for TPM. HMA December 2005 – Slide 2 HMA December 2005 – Slide 3 HMA - High level objectives • Consolidate scenarios and interoperability requirements NOTE we will appreciate your input in this item !!!! • Specify the interface standards among data providers to allow seamless access to data from multiple missions • Address interoperability requirements arising from: data quality and formats data policy, SLA, etc. security interoperability for harmonised data access • Define the EO DAIL architecture • Define and prototype an interoperable protocol for catalogue, order, mission planning,… • Define approach for User Management • Define approach for online data access HMA December 2005 – Slide 4 Key partners and GMES contributing missions Partner Mission ASI / Alenia Spazio Cosmo-Skymed CNES Pleiades, Spot CSA / MDA Radarsat DLR Terrasar, RapidEye EUSC User ESA ERS, ENVISAT, Sentinels HMA December 2005 – Slide 5 High level requirement: make easy • the search for available products • the request for future acquisitions • the ordering of the products • the delivery of the products • Across multiple missions HMA December 2005 – Slide 6 Related projects and activities External Requirements and Interfaces • ESA studies (sentinels, service architecture, …) • GSE projects • EC GMES Integrated Projects (e.g. ORCHESTRA, WIN OASIS, GEOLAND, …) • INSPIRE • EUMETSAT HMA December 2005 – Slide 7 Related projects and activities • ESA GMES Preparatory studies (PGS, service architecture, …) • ESA established the GMES TCT to coordinate activities • GSE projects • Co-location in December 2005 • EC GMES Integrated Projects (e.g. ORCHESTRA, WIN OASIS, GEOLAND, …) • Architecture WG established with ORCHESTRA, WIN OASIS • INSPIRE • Coordinated approach being set-up, work-plan on catalogue issues established • EUMETSAT • Technical co-ordination under definition HMA December 2005 – Slide 8 a VERY simplified view Protocol/standards Standardisation Bodies taxonomy (arbitrary) taxonomy (arbitrary) • Information Technology: • Information Technology: Service Oriented World Wide Web Architecture, Web Consortium W3C, OASIS Services, WSDL, SOAP • Geospatial: • Geospatial: Web Map Server, Web Open Geospatial Coverage Server, Web Consortium, ISO, CEN Feature Server • Space & EO: • Space & EO: Catalogue Interoperability Protocol, ISO, CEOS, CCSDS HDF, GeoTiff, JPEG2000 HMA December 2005 – Slide 9 proposed approach • Select (Pull) protocols based on current industrial technology standards & COTS • Push EO approach through the OGC standardisation process • Seek alignment with INSPIRE • Where applicable propose adoption of HMA protocols within the Implementing Rules • ISO adoption / standardisation of specifications - long term goal • Presentations form Joint ESA-JRC ws available at earth.esa.int/rtd/Events HMA December 2005 – Slide 10 Mission GS Mission GS User/Operator Catalogue Access Mission GS Initially Register catalogue services Include in catalogue services registry Service discovery update Catalogue service description update Collections discovery For each mission Collections discovery Result of collections discovery For each user request Result of collections discovery For each mission Metadata query Metadata query Requested metadata For each mission Apply cross- missions criteria Requested metadata Scenario US2_3 – Interoperable catalogue interfaces HMA December 2005 – Slide 11 GSE feedback needed!-1 • Which kind of data, with which frequency, over which areas you’ll need from the missions contributing to GMES (e.g. Cosmo, Pleiades, Radarsat, TerraSAR, ESA missions, etc…)? • If the products you’ll need will be provided from different missions you expect they’ll be already Cross- calibrated Co-registered & geo corrected with the same DEM of “reasonable quality” …no, this is part your business process, you want to do it? Quality certification by an external entity ? You want a close control on what is done You want to be able to select more than one product level/approach depending on the specific service to be provided and-or the mission which is the data source HMA December 2005 – Slide 12 GSE feedback needed!-2 In the GMES context you’ll need to search (catalogue) or request (order) data from multiple missions. In order to determine which kind of interactions these missions will need to support it is important to know if you expect you’ll need to… search for/request already archived single EO products? search for/request already archived large product sets? search for/request large coverage(s) (collection of products eligible to acquisition in the future)? few reference products from archives, many from future acquisitions each future acquisition will need a reference product from the archive HMA December 2005 – Slide 13 GSE feedback needed!-3 For the request (order) of products/coverage(s) for multiple GMES missions which approach you expect will be more suitable to your service? – Subscription (i.e. you are notified when a product/coverage is ready for delivery) of a product/coverage identified by someone on your behalf (whoever may be tasked to do so in GMES) – Standing order (i.e. you make your own request for Region of Interest, time interval, etc. ; then you do not have to repeat the request as the product/coverage will be acquired for you) – Individual product/coverage request as either your service does not allow to make regular requests or you want/need to verify each time which product/coverage will be acquired by which mission/when HMA December 2005 – Slide 14 GSE feedback needed!-4 Across mission online data access, distribution and publishing mechanisms you would like to use NOTE the following are examples, we would like to capture a trend, we do not expect a commitment on the use of specific approaches! • FTP/HTTP or DDS if needed e.g.: single DDS receiver for COSMO, RADARSAT-2 and Envisat data?; single FTP retrieval application/pick-up point ? Don’t care • You would like to see Coverage Servers as alternative data distribution mechanism • You expect you’ll need Coordinate Transformation Services • You expect to publish your own service results as vector data, maps Email, sms, tabular format other Do you have specific needs already identified? HMA December 2005 – Slide 15 • The HMA ESA Team • Contact point for GSE input to HMA is Ludwig Moeller (requirements) • Other responsibilities: • Jolyon Martin (standardisation, prototype) • Pierre Potin (capacity planning, security, policy, sla) HMA December 2005 – Slide 16