N. Fanjeau, Airbus Defence & Space June 11, 2014

Slides:



Advertisements
Similar presentations
OASIS OData Technical Committee. AGENDA Introduction OASIS OData Technical Committee OData Overview Work of the Technical Committee Q&A.
Advertisements

Service Description: WSDL COMP6017 Topics on Web Services Dr Nicholas Gibbins –
Proposed update of Technical Guidance for INSPIRE Download services based on SOS Matthes Rieke, Dr. Albert Remke (m.rieke, 52°North.
1 Understanding Web Services Presented By: Woodas Lai.
SOAP Quang Vinh Pham Simon De Baets Université Libre de Bruxelles1.
Introduction to push technology © 2009 Research In Motion Limited.
HTTP By: Becky Fultz, Joe Flager, Katie Huston, Tom Packard, Allison Wilsey.
JavaScript Forms Form Validation Cookies CGI Programs.
Hypertext Transfer Protocol Kyle Roth Mark Hoover.
Processing of structured documents Spring 2003, Part 6 Helena Ahonen-Myka.
TP2653 Adv Web Programming SOAP and WSDL. SOAP Simple Object Access Protocol – Lightweight XML-based messaging protocol – A protocol for accessing a Web.
1 Web Developer & Design Foundations with XHTML Chapter 6 Key Concepts.
Discussion and conclusion The OGC SOS describes a global standard for storing and recalling sensor data and the associated metadata. The standard covers.
CSCI 6962: Server-side Design and Programming Introduction to AJAX.
Grid Computing, B. Wilkinson, 20043b.1 Web Services Part II.
JavaScript, Fourth Edition Chapter 12 Updating Web Pages with AJAX.
Copyright © Orbeon, Inc. All rights reserved. Erik Bruchez Applications of XML Pipelines XML Prague, June 16 th, 2007.
James Holladay, Mario Sweeney, Vu Tran. Web Services Presentation Web Services Theory James Holladay Tools – Visual Studio Vu Tran Tools – Net Beans Mario.
© 2009 Research In Motion Limited Advanced Java Application Development for the BlackBerry Smartphone Trainer name Date.
CEOS WGISS, Hanoi May OSCAR Prototyping the sensor web Wyn Cudlip BNSC/QinetiQ Presentation to WGISS Hanoi May 2007 (Slides.
1 Web Service Description Language (WSDL) 大葉大學資工系.
© 2009 Research In Motion Limited Advanced Java Application Development for the BlackBerry Smartphone Trainer name Date.
Module: Software Engineering of Web Applications Chapter 2: Technologies 1.
Web Technologies Lecture 10 Web services. From W3C – A software system designed to support interoperable machine-to-machine interaction over a network.
1 G52IWS: Web Services Description Language (WSDL) Chris Greenhalgh
HMA Sep 2009 – Slide 1 Daniele Marchionni Elsag Datamat HMA Follow On – Task 4 - Workplan.
SOAP, Web Service, WSDL Week 14 Web site:
05 October 2010 HMA-FO Task 2: Feasibility Analysis Service HMA Follow On Activities Task 2: Feasibility Analysis Service (Sensor Planning Service) Monthly.
Teleconference, 22 October 2008 SPS Mandatory I/F Development Slide 1 HMA SPS Mandatory I/F Development HMA-T Phase 2 Progress Meeting 26 Nov 2008, by.
AR meeting Esrin, 26. January 2011 Slide 1 Ordering Services for EO Products Abstract (ATS) and Executable (ETS) Test Suite HMA FollowOn – Task 4 AR Meeting.
Spacebel - Hoeilaart, February 2009 SPS Mandatory I/F Development Slide 1 HMA SPS Mandatory I/F Development HMA-T Phase 2 Acceptance Review 1 18.
Page /06/2014HMA-S Final Presentation HMA-S Final Presentation OGC ROSEO Protocol D. Marchionni, Telespazio S.p.A. June 11, 2014.
ESRIN, 15 July 2009 Slide 1 Web Service Security support in the SSE Toolbox HMA-T Phase 2 FP 14 December 2009 S. Gianfranceschi, Intecs.
19 January 2010 HMA-FO Task 2: Feasibility Analysis Service HMA Follow On Activities Task 2: Feasibility Analysis Service (Sensor Planning Service) Monthly.
National College of Science & Information Technology.
Frascati, 2-3 July 2008 SPS Mandatory I/F Development Slide 1 HMA SPS Mandatory I/F Development HMA-T Phase 2 KO Meeting 2-3 July 2008, Frascati Ricardo.
Chapter 5 Validating Form Data with JavaScript
HMA Follow On Activities
HMA Follow On Task 4 - Order Final Presentation June 2011
HMA Follow On Activities
Task 2.6 Eric Delory PLOCAN
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
z/Ware 2.0 Technical Overview
Ordering Services for EO Products SWG ATS / ETS
Data Virtualization Tutorial… CORS and CIS
HMA-S Final Presentation OGC DSEO Protocol
N. Fanjeau, Airbus Defence & Space June 11, 2014
HMA Follow On Activities
HMA Follow On Task 4 - Order Final Presentation June 2011
HMA SPS Mandatory I/F Development
Introduction Web Environments
HMA Follow On Task 4 - Order Preliminary Review 2-3 February 2010
Ordering Services for EO Products SWG ATS / ETS
HMA Follow On Activities
Ashish Pandit IT Architect, Middleware & Integration Services
Testing REST IPA using POSTMAN
WEB API.
Chapter 9 Web Services: JAX-RPC, WSDL, XML Schema, and SOAP
HMA for Science SRR Download Protocol
EO Data Access Protocol
JavaScript & jQuery AJAX.
HMA Follow On Task 4 - Order Final Presentation 21 June 2011
Ordering Services for EO Products Abstract Test Suite (ATS)
HMA Follow-on Kickoff Meeting
Status OpenSearch Standardisation Activities - HMA-S Project
HMA Follow On Task 4 - Order Final Presentation 21 June 2011
Pier Giorgio Marchetti - European Space Agency
WEB SERVICES From Chapter 19, Distributed Systems
DAIL RIDS are posted to SSE wiki
OpenSearch and JSON-LD for enhanced Earth observation data and service discovery Dr. Ingo Simonis Workshop on making spatial data discoverable through.
Presentation transcript:

N. Fanjeau, Airbus Defence & Space June 11, 2014 HMA-S Specifications OGC 14-012 OGC RESTful encoding of Sensor Planning Service for Earth Observation satellite Tasking N. Fanjeau, Airbus Defence & Space June 11, 2014 OGC TC Geneva / HMA-S /FP

Summary Overview Items Operations Methodology Resources – Capabilities – URLs Resources – Capabilities – HTTP Methods Resources – Procedure – URLs & Parameters Error Handling Requirement Classes Best Practice Demonstrator ETS Resources OGC TC Geneva / HMA-S /FP

Overview The OGC Best Practice document OGC 14-012 OGC RESTful encoding of Sensor Planning Service for Earth Observation Satellite Tasking (RESET) is a “RESTful” version of the OGC 10-135 OGC Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking Extension allowing accessing to Feasibility and Mission Planning functions via appropriate HTTP requests and not via SOAP based Web Services calls. In this way Feasibility and Planning functions will be available to Web browsers without the need of more complex infrastructures based on SOAP. This protocol covers, in RESTful way, the 6 mandatory operations and 10 optional. OGC TC Geneva / HMA-S /FP

Items Sensor description, which permits to give descriptions of the sensors that can be tasked. These descriptions can be provided in multiple OGC standards, including SensorML, SOS, etc. Tasking requests, which are the requests to be sent, that contain all the information to configure the acquisition of a sensor, or set of sensors; Feasibility Study, which describes the result of a study of feasibility. This preliminary process permits to calculate the possibilities offered by a given sensor to perform a given tasking request. This structure contains a list of Segment, which represent a given acquisition. Programming Status, that describes the results of the submission of a task. It describes the current status of the Segment, which represent a single acquisition. OGC TC Geneva / HMA-S /FP

Operations GetCapabilities M GetStatus M DescribeSensor M GetTask M DescribeTasking M GetSensorAvailibility O GetStationAvailibility O GetFeasibility O Submit M SubmitSegmentByID O O, Optional M, Mandatory GetStatus M GetTask M DescribeResultAccess O Cancel O Validate O Reservation system: Reserve O Update O Confirm O OGC TC Geneva / HMA-S /FP

Methodology The structure has been defined after reviewing other OGC REST specifications: WMTS, WFS REST binding change request, WCS Extension for REST binding. Structured by Resources: Capabilities, Procedure, Feasibility, Planning & Reservation. Each resource has a dedicated section including description, URLs, supported HTTP methods. Addressability: each identified resource has specified URLs. Uniform interface: the operations performed on resources are only the Methods of HTTP protocol: GET for reading a resource; POST for creating a resource with ID defined by the server; PUT for creating / replacing a resource with ID defined by the client; DELETE for deleting a resource. Connectdness: each resource has links (URLs) to the other related resources. OGC TC Geneva / HMA-S /FP

Resources – Capabilities - URLs <Service Root URL> http://<hostName>:<hostPort>/<cont extPath> <ROSEO Root Path> <Service Root URL>/RESET/<version> URL Definition <CapabilitiesResourceURL> <ResetRootPath> <ServiceIdentification> <CapabilitiesResourceURL>/identification <ServiceProvider> <CapabilitiesResourceURL>/provider <OperationsMetadata> <CapabilitiesResourceURL>/operations <Notifications> <CapabilitiesResourceURL>/notifications <Contents> <CapabilitiesResourceURL>/contents OGC TC Geneva / HMA-S /FP

Resources – Capabilities – HTTP Methods URL Definition Request Entity Body Response Entity Body GET <RESET Root Path> It returns the complete capabilities document. Empty <sps:Capabilities > element instance <RESET Root Path>/ServiceIdentificat ion It returns the ServiceIdentificatio n element. <ows:ServiceIde ntification> element instance <RESET Root Path>/ServiceProvider It returns the ServiceProvider element. <ows:ServicePro vider> element instance <RESET Root Path>/Contents It returns the Contents element. <sps:Contents> element instance <RESET Root Path>/OperationsMetad ata It returns the OperationsMetadat a element. <ows: OperationsMetad ata > element instance <RESET Root Path>/Notifications It returns the Notifications element. <sps: Notifications > element instance OGC TC Geneva / HMA-S /FP

Resources – Procedure – URLs & Parameters Definition <ProcedureResourceURL> <ResetRootPath>/procedures/{procedure} / <Sensor Description> in canonical XML format <ProcedureResourceURL>/{sensorDescript ionFormat} <Sensor and Tasking Description> in OpenSearch Description Document (OSDD) <ProcedureResourceURL>/osdd <Tasking Description> <ProcedureResourceURL>/tasking <Availability> <ProcedureResourceURL>/availability Names Definition Data type and values {procedure} Identifier of the sensor, or sensor type, which description is required. xs:string (max 255 chars) URL encoded {sensorDescriptionFor mat} XML format in which the sensor description is required. OGC TC Geneva / HMA-S /FP

Resources – Procedure – HTTP Methods & Parameters URL Definition Request Entity Body Response Entity Body GET <ResetRootPath>/procedu res/{procedure}/{sensor DescriptionFormat} It returns the description of the sensor in the required format. Empty <eosps: eoTaskingParameters > element instance <ResetRootPath>/procedu res/{procedure}/osdd It returns the ServiceIdentificatio n element. <swes:ServiceIdentifica tion> element instance <ResetRootPath>/procedu res/{procedure}/tasking It returns the ServiceProvider element. <swes: procedureDescriptionFor mat > element instance <ResetRootPath>/procedu res/{procedure}/availabili ty It returns the Contents element. <eosps:GetSensorAvail abilityResponse> element instance Names Definition Data type and value {procedure} Identifier of the sensor, or sensor type, which description is required.   xs:string (max 255 chars) URL encoded Allowed values are described in the Capabilities. {sensorDescriptionFormat} XML format in which the sensor description is required. OGC TC Geneva / HMA-S /FP

Resources – Feasibility – URLs & Parameters Definition <FeasibilityResourceURL> / <AllTasks> <ResetRootPath>/feasibility/ <Task Status By ID> in canonical XML format <FeasibilityResourceURL>/{taskId} <TaskSegmentsByID> in canonical XML format <FeasibilityResourceURL>/{taskId}/seg ments Names Definition Data type and values {taskId} Identifier of the task required by the user. xs:string (max 255 chars) URL encoded OGC TC Geneva / HMA-S /FP

Resources – Feasibility – HTTP Methods & Parameters URL Definition Request Entity Body Response Entity Body GET <ResetRootPath> /feasibility/{taskId} Equivalent to GetStatus It returns the status of a task. Empty < eosps:StatusReport > element instance <ResetRootPath> /feasibility/{taskId}/segments Equivalent to GetTask. It returns the results of a task. < eosps:FeasibilityStudy> element instance POST <ResetRootPath> /feasibility?synchronous={isS ynchronous} Equivalent to GetFeasibility Permits to perform a Feasibility analysis. EO-SPS: Tasking Parameters < eosps:FeasibilityStudy> element instance if synchronous processing <ResetRootPath>/ feasibility/{taskId}/ segments/{segmentID*} Equivalent to SubmitSegmentByID. It permits to submit the segments resulting from a Feasibility Analysis. <eosps:FeasibilityStudy> element instance Names Definition Data type and value {taskId} Identifier of the sensor, or sensor type, which description is required. xs:string (max 255 chars) URL encoded Allowed values are described in the GetTask operation. {segmentId} Identifier of a segment, within the given task, to be submitted for planning. Allowed values are described in the GetTask operation { isSynchronous } A Boolean permitting the client between synchronous and asynchronous processing when starting a feasibility analysis. xs:boolean (true or false) OGC TC Geneva / HMA-S /FP

Resources – Planning – URLs & Parameters Definition <PlanningResourceURL> / <AllTasks> <ResetRootPath>/planning/ <Task Status By ID> in canonical XML format < PlanningResourceURL >/{taskId} <TaskSegmentsBy ID> in canonical XML format < PlanningResourceURL >/{taskId}/segments <TaskResultsBy ID> in canonical XML format < PlanningResourceURL >/{taskId}/results <SegmentBy ID> in canonical XML format < PlanningResourceURL >/{taskId}/segments/{segmentId} Names Definition Data type and values {taskId} Identifier of the task required by the user. xs:string (max 255 chars) URL encoded {segmentId} Identifier of the segment of the task required by the user. OGC TC Geneva / HMA-S /FP

Resources – Planning – HTTP Methods & Parameters URL Definition Request Entity Body Response Entity Body GET <ResetRootPa th>/ planning/{tas kId} Equivalent to GetStatus It returns the status of a task. Empty <eosps:StatusRe port> element instance <ResetRootPa th>/ planning/{tas kId}/segment s Equivalent to GetTask. It returns the results of a task. <eosps:Program mingStatus> element instance <ResetRootPa th>/ planning/{tas kId}/results Equivalent to DescribeResul tAccess It returns the links to the products generated by the task. <sps:DescribeRe sultAccess Document> - <sps:DataAvaila ble> - <sps:DataNotAv ailable> POST <ResetRootPa th>/ planning/ Equivalent to Submit Permits to perform a Planning request. EO-SPS: Tasking Parameters <ResetRootPa th/ planning/{tas kId}/ segments/{se gmentID*} Equivalent to Validate. It permits to validate a (set of) segment(s). < eosps:StatusRep ort > element instance PUT Not used by this document.   DELETE Equivalent to Cancel. It permits to cancel a task that has been submitted earlier. Names Definition Data type and value {taskId} Identifier of the sensor, or sensor type, which description is required. xs:string (max 255 chars) URL encoded Allowed values are described in the GetTask operation. {segmentId } Identifier of a segment, within the given task, to be submitted for planning. OGC TC Geneva / HMA-S /FP

Resources – Reservation – URLs & Parameters Definition <ReservationResourceURL> / <AllTasks> <ResetRootPath>/reservation/ <Task By ID> in canonical XML format <ReservationResourceURL>/{taskId} Names Definition Data type and values {taskId} Identifier of the task required by the user. xs:string (max 255 chars) URL encoded OGC TC Geneva / HMA-S /FP

Resources – Reservation – HTTP Methods & Parameters URL Definition Request Entity Body Response Entity Body GET <ResetRootPat h>/ reservation/{t askId} Equivalent to GetTask. It returns the results of a task. Empty <eosps:StatusRe port> element instance <eosps:Program mingStatus> element instance POST <ResetRootPat h>/ planning/ Equivalent to Reserve Permits to reserve a Planning request. EO-SPS: Tasking Parameters <ResetRootPat h/ planning/{task Id}/ Equivalent to Confirm. It permits to validate a task by sending it to the mission planning system. < eosps:StatusRepo rt > element instance PUT Equivalent to Update. It permits to update the tasking parameters of a task. DELETE <ResetRootPat h>/ planning/{task Id} Equivalent to Cancel. It permits to cancel a task that has been reserved earlier. Names Definition Data type and value {taskId} Identifier of the sensor, or sensor type, which description is required. xs:string (max 255 chars) URL encoded Allowed values are described in the GetTask operation. OGC TC Geneva / HMA-S /FP

Error Handling In the event that a RESET server encounters an error during the access to some resource, then it returns an HTTP response including: HTTP Status Code: 4XX for errors on the client side; 5XX for errors on server side. HTTP Entity Body: ows:ExceptionReport element. The specific values for Status Code and ows:ExceptionReport depend on the accessed resource and performed HTTP method. There are dedicated errors for each of them. OGC TC Geneva / HMA-S /FP

Requirement Classes Core, minimum behaviour that all RESET servers shall implement. Operations Tasking description, Sensor description or Task description. Feasibility, for performing a feasibility analysis process. Planning, for performing a planning process. Feasibility Planning, for performing a feasibility analysis process, and then submitting the results of this process. Reservation, for performing a feasibility analysis process, and then submitting the results of this process. Cancellation, for performing the cancel of planning or reservation process. OGC TC Geneva / HMA-S /FP

Best Practice OGC TC Geneva / HMA-S /FP

Demonstrator OGC TC Geneva / HMA-S /FP

ETS OGC TC Geneva / HMA-S /FP

Resources Google Code: restful-sps-earth-observation-server https://code.google.com/p/restful-sps-earth-observation-server/ opensearch-earth-observation-products-system https://code.google.com/p/opensearch-earth-observation-products-system/ OGC TC Geneva / HMA-S /FP