Alaska Region Satellite Products and Data Needs −or− “Where We Are Going”
Copernicus Commercial Satellite Data Needs
Transcript of Copernicus Commercial Satellite Data Needs
Copernicus Commercial Satellite Data Needs
Jean-Christophe Gros, Catharina Bamps DG DEFIS – European Commission
Outline
• Background
• Copernicus services’ needs and requirements
• Copernicus services’ potential needs
• Request for Information – overview tables
Contributing missions:
commercial/nationalmissions
License conditions
…added-value information
Full, free and open data and information policy
Dedicated satellite
missions: Sentinel constellations
Full, free and open data and information policy
6 thematic Copernicus services use Earth Observation data to deliver…
Copernicus : EO data needs
In situ observation data and reference
information
• Copernicus Contributing Missions (CCMs) activity : (previously: Data WareHouse)
• operated by the European Space Agency - on behalf of the European Commission.
• Main/primary users: the 6 Copernicus services;
• Currently : Very High Resolution Optical and Radar Data
User categories and access rights for Contributing Missions’ data (2014-2022)
Who can access Copernicus Contributing Missions data ?
Viewing data (no download)
Downloading data
Tasking satellites
Copernicus services ✓ ✓ ✓
EU institutions & bodies ✓ ✓
Research projects funded by EU ✓ ✓ *
Public Authorities (national, regional, local)
✓ ✓ *
International organisations & NGOs ✓ *
General public ✓
*Simplified table. Full details in the tables at:
https://spacedata.copernicus.eu/web/cscda/copernicus-users/access-rights
User category Public Authorities – Definition
• Employees of a government or public administration of States participating in the Copernicus Programme
• A person having public responsibilities or functions, or providing public services relating to a EU policy
• Employees of research and academic organizations (i.e. National Research Council, University etc.)
• Contractors of such entities
The complete list of CCM User Categories under:
https://spacedata.copernicus.eu/web/cscda/copernicus-users/user-categories
Data needs of the Copernicus services for Copernicus contributing missions (previously known as Data Warehouse)
On-Demand(previously known as additional data)
Systematic (previously known as Core data)
systematic coverages and
acquisitions primarily for the needs
of the Copernicus Land, Marine and
Atmosphere Monitoring Services;
on-demand data acquired mostly in rush mode primarily for the needs of the Copernicus
Emergency Management and Security
Services;
Copernicus DEMOne cloud-free VHR optical coverage
Data requirements of the Copernicus services for Copernicus contributing missions (previously known as Data Warehouse)
On-DemandSystematic
Regular, planned coverages and acquisitions;
Pre-defined areas of interest;
Main characteristics: (data) quality (assurance), completeness (avoidance redeliveries) and uniformity;
Unplanned, acquired mostly in rush mode;
Not pre-defined areas of interest affected by natural and man-made disasters or crisis situations;
Main characteristics: quality, spatial resolution and timeliness, i.e. get the data as soon as possible
Systematic requirements
- Regular and planned optical VHR coverages of large pre-defined areas:
- Land data for the European continent every 3 years and potentially yearly/seasonal coverages in the future, for the Copernicus Land Monitoring Service with accessible satellite data for Public authorities in Europe - (CLMS)
- Coastal areas (e.g. HR optical data for Ocean Colour, VHR optical for land cover) – (CLMS, CMEMS)
- Optical and SAR for regular verification of a selection of sites of the ground motion service - (CLMS)
- HR SAR data for sea ice in the Polar regions, Copernicus Marine Environment Monitoring Service (CMEMS)
- Satellite data equivalent to the data from the future Sentinel Expansion missions (Polar Expert Group III report)https://www.copernicus.eu/sites/default/files/DEFIS_Copernicus_Polar_report_210414_HV-NC-29-144-EN-N.pdf
CurrentA. Lead time:B. Latency:
NewA. Lead time:B. Latency:
➢ On-demand for Optical and SAR data with more stringent timeliness requirements:A. Lead-time: from request to sensing B. Latency (delivery timeliness): from sensing to image availability
- The faster the data is delivered, the better
- No need of secure downlink reported, only 1 need out of 300 request license restrictions (“single-use”);
Req 1: <2h &15min
Req 3: <24h &
15min/30min/1h/3h
Req 2:<12h &
>3 h - < 12 h
«Rush» Requirement<16h
30 min
«Rush» data offer First image available <48h
(including latency <3h)
Req 4:<48h &
>3 h - < 12 h
On-demand requirements
➢ On-demand services requirements from Copernicus (future):- VHR Digital Surface/Terrain Models for CEMS and CSS - Tip & Cue* from HR to VHR for SAR and Optical (CSS)- Satellite data equivalent to the Sentinel Expansion missions (Hyperspectral, SAR L-band) (CSS, Polar Expert Group III)
* the process of using lower-resolution (free) systems to detect events that you want to investigate with a higher-resolution system;
On-demand requirements
Potential developments in VHR data consumption
✓ Increased need for optical VHR data 2-4 meters
✓ Continous high need for optical VHR < 1 meter for Copernicus Emergency Management and Security Services, but with more stringent timeliness requirements
✓ Continuous need for SAR VHR < 1 meter and eventual increased needs for data < 4 meter
Copernicus services: Potential needs for data from new instruments and platforms
• Hyperspectral data to prepare for the uptake of Copernicus Hyperspectral Imaging Mission.
• Manned/unmanned aircraft and high altitude pseudo-satellites
• LiDAR
• Automatic Dependent Surveillance Broadcast or Radio frequency signals detection
• Independently geolocated AIS (Automatic vessel Identification System)
Copernicus services: Potential needs for products and services
• 3D models
• To further improve the overall Copernicus information timeliness, data value-adding such as automated feature extraction and change detection e.g. Activity/change reporting
• SAR coherence change detection
• need to increase the possibility of agile observations, improving the probability of getting agile acquisitions in uncertain weather conditions as discontinuous cloud cover
• Possibility of direct Tasking e.g. a direct tasking API with the data providers?
(control quota or streaming?)
• Multiple acquisitions per day (subscription fee system?)
• Analysis Ready Data
Request for information:
CCM Activity evolution
New acquisition Tasking Lead
Time
New acquisition Latency/Delivery timeliness
Archive View Archive Download Area of Interest
QRT < 2 hours <15 min Possible to view
directly online
1 hour Anywhere
RUSH < 16 hours < 30 min 1 hour
FAST < 48 hours < 24 hours < 48 hours
STANDARD N/A N/A < 48 hours