Ground Segment Interoperability in the GSCB Missions · GSCB Workshop, ESA/ESRIN (Frascati) 18th...
Transcript of Ground Segment Interoperability in the GSCB Missions · GSCB Workshop, ESA/ESRIN (Frascati) 18th...
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Ground Segment Interoperability in the GSCB Missions
Pleiades & Spot
C. Dabin (CNES) / D. Giacobbo (SpotImage) / A. Meygret (CNES)
GSCB Workshop, 18th – 19th June 2009ESA/ESRIN Frascati
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission status
•–SPOT system main characteristics:
• orbit : 822 km at the equator 10:30 local time, 26 days cycle
• Placed to optimize repeat imagery acquisition• 450 km across-the-track pointing ability• revisit capability : 2 to 3 days
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission StatusSPOT 2 SPOT 4 SPOT 5
age 18 years 10 years 6 years
power 1,300 W 2,257 W 2,763 W
hydrazine 69.1 kg (43%) 106.7 kg (68%) 132.6 kg (84%)
thermal control ☺
recorders (since 10/93) ☺ (2x40'; 48'/day + 3' solid state)
☺ (110 Gbits)
gyros ☺ (nominal set still in use; redundant set as a spare)
earth sensor☺ ☺ (nominal still used) ☺ (nominal still
used)(redundant used since
09/97; nominal as a spare)
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Spot Family overview• A SPOT scene is 60 km x 60 km
– SPOT 2: 2 modes– PAN (black and white), resolution 10 m
– Multispectral XS (3 spectral bands), resolution 20 m
– SPOT 4: 3 modes– M (black and white), resolution 10 m
– Multispectral XS (3 bands) or XI (4 bands), resolution 20 m
– SPOT 5 • HRG: 4 modes
– HMA or HMB (black and white), resolution 5 m– Multispectral I (3 bands) or J (4 bands) , resolution 10 m – THR (HMA + HMB), black and white, resolution 2,5 m
• HRS: 1 mode– HRS1&2 (black and white), resolution 10 m– Swath 120 km
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission status• Pleiades
–450 images / day / satellite (PA+XS mode)–Mosaïc, bi stereo and tri-stereo capabilities–4 spectral bands (blue, green, red and infrared)–50 cm products–imaging swath of 20 km at nadir –single-pass collection of mosaics with a footprint of 100 km x 100 km –near-real-time stereo and tri-stereo acquisition with a 20 km x 280 km footprint–daily coverage of 1,600,000 sq.km. –image location accuracy, better than 7 m without ground control points (CE90) for optimal integration in a GIS
Viewing angle
1 satellite
2 satellit
es
5° 26 days 13 days
20° 7 days 5 days
30° 5 days 4 days
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission status• Pleiades
• Satellite ready for launch on March 2010• Launched from Kuru with Soyuz (planning from
Arianespace to be consolidated)
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission status• Pleiades : System products
GISCartographic projectionIdem 1+ fusion PA/XS
Orthoimage
GISCartographic projectionIdem 1+ fusion PA/XS
Orthomosaïc
Value Added Soc.Perfect SensorIdem 1+ fusion PA/XS
Perfect Sensor
System / DefenceRawRadio defaults correction and PA restoration
1
SystemRawRaw0
User(s)Geometric QualityRadiometric QualityLevel
Sensor geometry
GIS geometry
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Mission status• Two ways to access Pleiades System
– Defence Channel• For cooperating Defences : direct access to the satellites for
Defence high priority request
– Civil Channel• For the other users, responsibility of tasking, data reception,
processing, archiving and distribution is given to a Civilian Operator (Spot Image)
• Data Policy– CNES is the holder of the copyright– Licence to use granted to Defence, Institutional Users
of cooperating countries for non commercial use– Full and exclusive licence for data under the
responsibility of Spot Image• Specific requirements to serve Institutional Users at a
preferential price“Operational cost + a limited margin”
• Various levels of Civilian priorities
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementation• Current Implementation (HMA-Imp)
– Catalogue: Spot & Pléiades– Ordering: Pléiades– Programming: Pléiades protoype based
• Planned Implemention (GCM DA Part A)– Ordering: Spot– Programming: Spot
• Future works (to be initiated within HMA-FO)– Online Data Access: Spot & Pléiades
• Streaming delivery WMS/WCS • Automatic processing (ortho, mosaic)WPS
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementation• HMA I Project funded by ESA/ESRIN (CNES co founder)• Catalog services, Ordering services, Programming services• On site tests (SPOT catalog services) performed and
accepted, integration with DAIL can start
SPOT Data
SPOT Ground Segment
PLEIADES Data
PLEIADES Ground SegmentPLEIADES ordering fromcatalogue component
SPOT catalogue component
HMAI core components
DAIL
SPOT native
catalogueservices
PLEIADES native
catalogueand
orderingservices
EO Products extension package for ebRIM Profile of CSW 2.0
Ordering Services for Earth Observation Products
Sensor PlanningService Application Pofile for EOSensors
PLEIADES catalogue component
PLEIADES programmingcomponent (proto)
GML EO Product v 0.73
PLEIADES native
programingservices
PLEIADES Test Data
PLEIADES Test Platform
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [1]
• Restrictions to be defined and mutually agreed – Complexity of OGC specs.– Technology supported by COTS (Axis2, Saxon…)– Basic customer requirement subset (native services and
queries supported)– Logs/reports/behaviour in case of non supported requests,
slots or protocol
Exchange protocolsOperations
HTTP GET with KVP payload SOAP 1.1 over HTTP
GetCapabilities Supported Supported
GetRecords - Supported
GetRecordById - Supported
GetRepositoryItem Supported -
• Examples of restrictions
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [2]
• Examples of restrictions : GetRecords response / Filter encoding support
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [3]
• HMA on legacy catalog : Pleiades HR case– secured connection using the Kerberos protocol required – PostgreSQL/PostGIS database with a specific schema
optimized for Pleiades requirements (i.e. no generic schema)
– Pleiades HR catalog interfaces based on WFS with pagination support (GML EO Product v 0.73)
HMA implementation choice :– simple XSL transform within tomcat server (use of
saxon) – Non intrusive, evolutive– Performance (Intel Core 2 Duo [email protected] GHz – 2Go RAM)
• request (typical request ) : HMA -> WFS PHR transform : 31ms
• response : WFS -> HMA transform : 250 ms (for 10 results)
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [4]
• HMA “from scratch” : the Charter catalog– PostgreSQL/PostGIS database with a generic
ebRIM schema– Charter catalog interfaces based on HMA.
HMA implementation choice :– ERDAS RedSpider catalog– Intrusive (internal and external interfaces are
linked). Evolution of specification = upgrade of software…
– Performance : no measurement. However, ebRIM structure (i.e. all slots in one table) should be less efficient than dedicated schema for huge database
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [5]
• HMA Sensor Planning Service prototype implementation
– More complex than catalog façade (stateless internal data management, requests processed independently, no polling mechanism)
– Example : matching SPS GetFeasibility vs Pleiades services
– Key issues addressed during the development :
• Persistency• Serialization/Deserialization (xstream
library)• Pooling in / out • SPS library (Spot Image dev.) re use• Sync/async requests
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
HMA implementationFirst experience comments and recommendations [6]
• Recommendations :–Mapping between dedicated internal
interface and HMA interface is preferable on maintenance and evolution point of view
–Benchmark of ebRIM generic model to perform on huge databases
- Complex HMA I interfaces (e. g : SPS) to be prototyped
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Quality Assurance for Earth Observation (QA4EO)
• The implementation of the guidelines at CNES:– Pre-flights activities:
• characterization/calibration using traceable references (ex: CNES integrating sphere calibration managed by ASF/LABSPHERE,…) ⇒ budget documents + sensors data are internally managed and archived
• Level 1 processing methods description (ATBD) published for users
– Post launch activities:• IOT: complete characterization/calibration
– Comparison to pre-flight measurements and specifications– Documents :
» Detailed performance and calibration budgets (CNES internal documents)
» Image Quality performances (synthetic performance budget, method description, calibration parameters) published
» Publications (journal, conferences, workshops,…)– Products:
» Complete traceability of the processing through GIPP (Ground Image Processing Parameters)
» Calibration parameters updated» Quality Indicators:
⇒ at pixel level for radiometry mainly (singularity, saturation,…)
⇒ At product level for geometry (quality of the geometric model refinement when using GCP,…)
• Routine: periodic calibration and performances assessment→ Image Quality performances document updated once a year→ Product information updated
www.spotimage.fr
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Quality Assurance for Earth Observation (QA4EO)
• Futures plans and activities for the implementation ofthe guidelines:– CNES participation to CEOS activities– CNES calibration data base (SADE): export and
access for GSICS and CEOS cal/val users ofmeasurements performed over deserts (20 satellites, 34 sensors, 2.5 106 measurements)
– Participation to the « Pilot Comparison oftechniques/instruments used for vicarious calibration of land surface imaging through a ground referencestandard test site » (august 2009, Tuz Gölü, Turkey)
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Ground EO data flow: Online Data Access• Does ODA is a Web Service or part of delivery?
– Should be a delivery option • FTP, HTTP or WCS/WMS
– Should be a Web Service• WCS/WMS
• Two different types of ODA:– ODA-Transfer: dedicated to data transfer
• FTP or HTTP• No direct integration in a workflow or compound service
– ODA-Consumption: dedicated to data consumption• Based on WCS/WMS OGC services type• Should be part of a SDI• Direct integration on a workflow or compound service
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Online Data Access in GMES• GMES and ODA
– ESA provides horizontal access to all the European Spatial Data
– EC through Services Providers provides vertical application e.g. for Risk or Land Cover applications
– There is a hole between horizontal and vertical application– ODA-T doesn’t bring a solution for integration
• ODA-C: provides a full integration – WMS is used for background
– WCS is used for processing• WCS provides agility
– Ground Segment should give access to raw data through a WCS– GS should propose a geometric processing (e.g. WPS)– GS should propose a value added data through WCS (ortho)
• WCS permits to visualise quickly the data and extracts a part– Very valuable in case of mosaic
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
ODA-C/ODA-T: Open Issues• All the data shall be provided with
metadata– E.g. Web Service such as Google Earth
or Virtual Earth give no information about the data used
• No applicable for GMES
• A minimum set of harmonized metadata shall be defined to– Provide a minimum set for lineage
information• Raw data used• Processes applied
– Provide info for processing• Cal/val• …
– Provide license information• Single license• Multiple license Virtual Earth
Google Earth
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
ODA-C/ODA-T: Open Issues
• ODA for Standing Orders – Service Provider working on large area will not
request single image but a coverage• there is a need to develop a mechanism for monitoring
dynamic building of a coverage• For ODA-T Service Provider will maintain a kind of "mirror" of
the archive – Need to define an automatic synchronisation – No existing way to inform the SP
• For ODA-C we need to define an option for updating the coverage
– consider the T (Transactional) of OGC services– WFS-T already existing for vector– WCS-T and WMS-T should be defined
• Publish availability of already products data– Collect metadata from data or maintain a link with
catalogue
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Implication analysis
• Weak points– EbRIM doesn’t demonstrate his technical advantage and brings
complexity on the implementation phase – Need to insure a link between GML EO Product and ISO19115
(part II) within the Inspire context
• Benefits– GML EO Product gives a shared description of the product. De
facto standard for the EO domain– Involvement on the SPS OGC WG gives the opportunity for EO
domain to define a standard endorsed by missions and in good shape to be adopted by OGC / GEOSS / GMES
– Ordering as an example for internal specification of ordering service at Sisa
GSCB Workshop, ESA/ESRIN (Frascati)18th – 19th June 2009
Recommendations• Needs
– Online Data Access to be addressed with a focus on the streaming offer
– User management• not necessary whether ESA considered as focal point• Mandatory for ODA with streaming (ODA-C)
– Define the minimal processing to be done by GS for the Service Providers
• Eg ortho processing with Web Processing Service
• HMA FO involvement of Spot Image– Task 2 - Feasibility Analysis Service (Sensor Planning Service)
• Completion of the SPS Application profile for EO– Alignment with other SWE specifications and definition of
GetSensorWorkload operation
– Task 3 - Online Data Access• Define and prototype a WCS Application Profile for EO Sensors