Hearing on Satellite Data Requirements

European Union Satellite Centre © 2013 European Union Satellite Centre © 2013

UNCLASSIFIED / FOR OFFICIAL USE ONLY

European Union Satellite Centre

Satellite Data Requirements - Copernicus Security Requirements focused on

Support to EU External Actions

Gracia Joyanes [email protected]

Brussels, 17 May 2013


Outline


Overview of Satellite Data Requirements for security

applications in Support to EU External Actions

Practical examples of application of requirements within

Copernicus projects

Feedback from G-MOSAIC

Present: G-NEXT

Future: towards an operational service


Outline





Copernicus projects


Present: G-NEXT


European Union Satellite Centre © 2013

Overview of Satellite Data Requirements

1. Category of Data

2. Specific Requirements

3. Quota Requirements

Overview of Satellite Data Requirements for security applications in Support to EU External Actions




Category of Data

Optical imagery Spatial resolution:

VHR1 (< 1m) Complementary - VHR2

Processing level: minimum bundle Archive data and New acquisitions Delivery time: Rush, Normal Frequency: Punctual or Monitoring For some specific applications: hyperspectral, thermal infrared




Category of Data

Radar imagery

Both Spotlight and Stripmap

All polarizations depending on the specific case

In some cases need to select the sensor e.g. for interferometry with previously acquired images




Specific Requirements

24h/7days availability

To be informed when the EO data is going to be available

Quicklook desirable (e.g. % Cloud coverage not sufficient parameter to reject images)

Delivery data in crisis mode: timeliness

Access to data: Secure, fast and easy

EO acquisitions for sensitive activations not to be displayed in catalogue




Quota Requirements

Additional datasets

Considerable quota of VHR1 is mandatory

Quota for sensitive activations: 40%



Outline





Copernicus projects


Present: G-NEXT



VHR1 important for:

- Identifying features precisely

- Recognizing shapes

Practical examples of application of requirements within Copernicus projects

Requirement: Optical imagery, resolution < 1 m

ERO

S B

, 0.7

Met

er R

eso

luti

on

, 2

2/0

4/2

011

© Im

ageS

at In

tern

atio

nal

N.V

./Im

ageS

at Is

rael

Ltd

. UNCLASSIFIED / FOR OFFICIAL USE ONLY




Container Train

Paved area, apparently for loading, unloading

Structure above the road

Pipelines

This must be a container of hazardous gas materials

< 1 m resolution important for:

- Recognizing shapes

- Understanding context

©G

eoey

e 2

01

0 p

rovi

ded

by

e-G

eos

un

der

EC

/ESA

GSC

-DA





Identification of features

Geo

Eye-

1, D

ate:

27

/11

/201

0, ©

Geo

Eye

(20

10

) Pro

vid

ed b

y e-

GEO

S S.

p.A

un

der

GSC

-DA



SPO

T-5

(06

Ju

ne

20

11

) , ©

CN

ES 2

01

1 D

istr

ibu

tio

n S

po

t Im

age

S.A

., al

l rig

hts

res

erve

d


Requirement: access to all type of data available

Availability of a wide

variety of imagery:

- Allows flexibility in the

detection of changes

- Guarantees the provision

of information

Change detection used to assess the level of activity in an airport



Geo

Eye-

1 (

0.5

m r

eso

luti

on

, V

isib

le +

NIR

) o

f 0

8 A

ug

20

10

©D

igit

alG

lob

e 2

01

0

pro

vid

ed b

y e-

Geo

s u

nd

er E

C/E

SA G

SC-D

A

Iko

no

s (1

m r

eso

luti

on

, V

isib

le +

NIR

) o

f 1

9 N

ov

20

10

. ©D

igit

alG

lob

e 2

01

0

pro

vid

ed b

y e-

Geo

s u

nd

er E

C/E

SA G

SC-D

A


Requirement: timeliness

1st December 2nd December 3rd December

Activation

Imagery received

Briefing Note is produced and delivered



Geo

Eye-

1 (

0.5

m r

eso

luti

on

, V

isib

le +

NIR

) 0

3/0

3/2

011

©G

eoEy

e (2

01

1) p

rovi

ded

by

e-G

EOS

S.p

.A u

nd

er G

SC-D

A


Requirement: % cloud coverage



Outline





Copernicus projects


Present: G-NEXT




Data Procurement System

As pre-operational service, the overall performance was very good

Good practices: in terms of timing and reactivity

Operators assistance very satisfactory

Coordinated access to data (Multimission approach) is essential

Delivery time for non-rush could be improved

Notification email of data availability: more information

Quota Estimation and Quota Handling

Quota availability ensured throughout the project

Quota estimation for crisis is not easy in advance



Outline





Copernicus projects


Present: G-NEXT



Present: G-NEXT

Estimated satellite requirements

Core dataset code

Single AOI size

(sqkm)*

Number of

repetitions** Total sqkm Comment

Single AOI size

(sqkm)*

Number of


Single AOI size

(sqkm)*

Number of


Archive_rush_Optical_HR1 ADD_001a

Archive_rush_Optical_HR2 ADD_001b

Archive_rush_Optical_VHR1 ADD_003a 379 12 4.600 379 14 5.400 379 7 2.700

Archive_rush_Optical_VHR2 ADD_003b 277 12 3.400 277 14 3.900 277 7 2.000

Archive_rush_SAR_HR1 ADD_005a

Archive_rush_SAR_HR2 ADD_005b

Archive_rush_SAR_VHR1 ADD_007a 7 12 100 7 14 100 7 7 100

Archive_rush_SAR_VHR2 ADD_007b 53 12 700 53 14 800 53 7 400

New acquisition_rush_Optical_HR1 ADD_002a

New acquisition_rush_Optical_HR2 ADD_002b

New acquisition_rush_Optical_VHR1 ADD_004a 204 12 2.500 204 14 2.900 204 7 1.500

New acquisition_rush_Optical_VHR2 ADD_004b 149 12 1.800 149 14 2.100 149 7 1.100

New acquisition_rush_SAR_HR1 ADD_006a

New acquisition_rush_SAR_HR2 ADD_006b

New acquisition_rush_SAR_VHR1 ADD_008a 28 12 400 28 14 400 28 7 200

New acquisition_rush_SAR_VHR2 ADD_008b 212 12 2.600 212 14 3.000 212 7 1.500

Archive_standard_Optical_HR1 ADD_009a

Archive_standard_Optical_HR2 ADD_009b

Archive_standard_Optical_VHR1 ADD_011a 162 12 2.000 162 14 2.300 162 7 1.200

Archive_standard_Optical_VHR2 ADD_011b 119 12 1.500 119 14 1.700 119 7 900

Archive_standard_SAR_HR1 ADD_013a

Archive_standard_SAR_HR2 ADD_013b

Archive_standard_SAR_VHR1 ADD_015a 3 12 100 3 14 100 3 7 100

Archive_standard_SAR_VHR2 ADD_015b 23 12 300 23 14 400 23 7 200

New acquisition_standard_Optical_HR1 ADD_010a

New acquisition_standard_Optical_HR2 ADD_010b

New acquisition_standard_Optical_VHR1 ADD_012a 87 12 1.100 87 14 1.300 87 7 700

New acquisition_standard_Optical_VHR2 ADD_012b 64 12 800 64 14 900 64 7 500

New acquisition_standard_SAR_HR1 ADD_014a

New acquisition_standard_SAR_HR2 ADD_014b

New acquisition_standard_SAR_VHR1 ADD_016a 12 12 200 12 14 200 12 7 100

New acquisition_standard_SAR_VHR2 ADD_016b 91 12 1.100 91 14 1.300 91 7 700

New acquisition_standard_SAR_MR1 ADD_017a

New acquisition_standard_SAR_MR2 ADD_017b

New acquisition_standard_Optical_MR1 ADD_018a

New acquisition_standard_Optical_MR2 ADD_018b

Archive_standard_SAR_MR1 ADD_019a

Archive_standard_SAR_MR2 ADD_019b

Archive_standard_Optical_MR1 ADD_020a

Archive_standard_Optical_MR2 ADD_020b

* AOI size represents the amount of imagery consumed per activation

** Number of repetitions represents the amount of activations expected

20152014 (after June)2014 (before June)

VHR1 – Rush: approx. 20.000 Km2 VHR1 – Standard: approx. 9.000 Km2



Outline





Copernicus projects


Present: G-NEXT




To take into account the specificities of the services for security applications

To estimate and guarantee the data volume necessary for

deploying Copernicus operational services for Security

applications




Current Copernicus projects for pre-operational security applications will end in 2015.

Operational services for security applications shall follow.

Current security applications data requirements have been provided up to 2015.

How to evaluate requirements for security applications after 2015? On the basis of an extrapolation of projects requirements?

What is the deadline to get these 2015-2020 data requirements integrated in the DAP?



Thank you for your attention!

Gracia Joyanes European Union Satellite Centre Tel: +34 91 678 60 63 E-mail: [email protected]



Documents

Hearing on Satellite Data Requirements