Multi-Community, Multi-Sensor Maritime Earth Observation DC

Transcription

1 Multi-Community, Multi-Sensor Maritime Earth Observation DC How do you eat the elephant? Gianluca Luraschi EO Project Manager and Application Architect

2 SafeSeaNet Ecosystem 2

3 Interoperability: EIF State of the Art 3

4 QoS: Near real time CleanSeaNet : Near Real Time service 30 min* Analysis Results (EO derived information) Phone and alert (Alert Report) Planning Ordering Acquisition Processing Features Analysis Earth Observation Service Providers Acquisition Processing Delivering EMSA EO Data Centre Data dissemination ancillary data F e e d b a c k T0 = End of scene acquisition T = T min 4

5 EO Lessons Learnt QoS CSNDC 2015 CSNDC 2009 EODC 2016 Building Blocks (one bit at the time) CSNDC 2011 Interoperability 5

6 Multi-Community & Multi-Sensor Over the last years the Agency s services relying on EO information have expanded beyond the original CleanSeaNet Service use case. Multi-Community: CleanSeaNet (oil spill monitoring), FRONTEX (surveillance), MARSURV-3 (fishery control), and the upcoming Copernicus Services. Multi-Sensors: several EO Missions, different EO Sensors, and User Provided Data. 6

7 EODC user community The EODC will cater to the needs of a wide range of user communities in the maritime domain. These include: - Border Control - Fisheries Control - Maritime Security and Safety - Customs - Marine Environment - Law enforcement - Defence - Extended maritime surveillance. 7

8 Volume Variety - Velocity - Number of acquisitions for SAR imagery (including additional vessel detection, oil spill and SAR derived products): 20 acquisitions/day (4 concurrent) (4TeraBytes) - Number of acquisitions for optical imagery (including additional vessel detection, activity detection and change detection products): 15 acquisitions/day (6 concurrent) (10 TeraBytes) - SAR and optical imagery products: 120 seconds (T1-T0) - Value added products: 50 seconds (T1-T0) for vessel detection. 10 seconds for the remaining products (with exception for SAR wind and SAR Wave timeliness will be defined afterwards) (600 GB) - User provided products: 5 seconds (T1-T0) (excluding downloading / uploading of rich content information (i.e. images or video)). 8

9 Earth Observation Data Centre Earth Observation Data Centre building blocks : - Data Provisioning. Planning (programming the sensors to acquire EO products); Ordering (purchase EO product) - Data Acquisition. Once ordered, EO products need to be ingested into an EO Data Centre - Data Delivery. Once ingested, EO products shall be catalogued and delivered to different services that will make use of EO products through geospatial standard services. 9

10 Earth Observation Data Centre. 10

11 Reference workflow 11

12 Service viewpoint From SOA (HTTP/GET) to REST Identity Management Discovery Data Acquisition Request and Feasability Product Ordering Invoke View & Download Authentication and Authorization OGC CSW ebrim profile EODC adaptors to acquire desired datasets EODC Ordering and Financial component Oil Spill Modeling (forecast hindcast) OGC-WPS; Alerting OGC-WMS, OGC-WFS, OGC-WCS, sftp, dataset service (REST), Notification (Pub/Sub) Standard Ad-hoc

13 Information Viewpoint The EODC encoding information from XML (ISO 19115/ > JSON/RDF Earth Observation Product Quality NOtification EO DERived Data SAR and OPT (EOP) JPEG2000, GeoTIFF and SAR Level-1 B Image Displacement Wind, Waves, Detected Vessels, Oil Spill, Activity Detection Quality Report Quality indicators Standard Ad-hoc

14 Interoperability issues/questions Enterprise viewpoints: - Ordering (purchases products). Programming-based ordering OGC RESTful interfaces for ordering and r6 Ordering Services Framework for Earth Observation Products Interface Standard - Quality of services (performance, availability and capacity guidelines?) - Identify Management to harmonize with Maritime requirements. - Quality assessment of the EO products Information viewpoints: - Data models for the EO derived products. - Data: XML vs JSON Metadata: XML vs RDF - VGI and User Provided information - Sematic annotation (EO ontology alternatives best practices?) Service viewpoints: - SOA (HTTP/GET) vs ROA (REST EO URI structure best practice?) - Publish/Subscribe (Notification services) - PubSub 1.0 Release Candidate for internal review. - Long Term Archiving (best practice?) 14

15 How do you eat the elephant? One bite at a time, but before it goes off Multi Community and Sensors Earth Observation Data Centre Gianluca Luraschi EO Project Manager and Application Architect Gianluca.luraschi@emsa.europa.eu twitter.com/emsa_lisbon facebook.com/emsa.lisbon