Main bottleneck on Disaster Management for the EO data Lack of capability to discover the archive and/or to acquire data in a multi mission context. Lack of rapid data processing for High Resolution products 80 % of the product is delivered with a poor geometric level and the user has to geo-process first the data before to obtain EO data ready for GIS Lack of link with other sensor such as weather satellite or In Situ Despite the increasing number of EO satellites, such of assets should not be use for all the Disaster activity. The EO sensor has to be used in conjunction with other sensor such as In Situ or weather satellite. There is a strong need to better integrate all the sensors.
The catalogue component –made with the support of the ESA FedEO EO Community Clearinghouse project. –consist on an access to a product catalogue compliant with CSW 2.0 ebrim profile, –an access to the collection and associated services with possible access to a description of the sensors in SensorML. The other services and components consist to SPS, WCS, and WCTS. All the services will offer access to SPOT2, SPOT4, SPOT5, Formosat2 and Kompsat2 sensors.
EO components and services Sensor Planning Service (SPS) –generating detailed feasibility reports based on user parameters (via GetFeasibility), –submitting tasks to our internal system (via Submit) –following coverage acquisition status (via GetStatus). Scene Parameters Platform : SPOT-5 Instrument : HRG Mode : PAN Time : 2008-03-28T10:25:12 Resolution : 5m Incidence : 5.8° ROI
EO components and services Web Coordinate Transformation Service (WCTS) –The WCTS provide capability to transform raw EO sensor data to geocoded product. –The WCTS is dedicated to SPOT, Formosat2 and Kompsat2 sensors and –Its foreseen to update the service to translate WCTS within WPS and offer capability to other sensors..
Your consent to our cookies if you continue to use this website.