control and agricultural land in iacs…strand... · 2016. 6. 3. · 3 • close follow up by jrc...

1

Control and management of agricultural land in IACS

Session: Image provision

Status of the satellite data provision for the 2016 CwRS/LPIS QA Campaign

Pär Johan Åstrand, and the GTCAP/CAPISA image acquistion team

Baveno, IT, 23-25/05/2016

Presentation Outline

• Satellite data management 2016 - what happened since Thessaloniki ?

• Campaign 2016 in a nutshell - status

• VHR/HR Specs; today & what will happen?

• G4CAP / S2 / Copernicus

• Image return / Miscellaneous

2

What happened since Thessaloniki (1)

Steps taken to reduce the requests for satellite data provision for Campaign 2016:

1. Pre-Image Request (pre-IR) (1) - we call it the “pre-Thessaloniki status”, as

of 24/11/2015

2. Pre-IR (2) - we call it the “post-Thessaloniki status”, as of 31/12/2015

3. Final IR after final insertion in G4CAP IR module (27/01/2016) and frozen for

feasibility with Image Providers, and which are the volumes we are

programming now.


3

• Close follow up by JRC and DG AGRI and interface with MS

Administrations allowed reduction in accordance with efficiency criteria

set for 2016 (mainly reduction in accordance to cost/OTSC area)

• So budget demand was reduced from 9.65M€ to 8.44M€ to 8.18M€ for

the VHR and HR imagery (does not include LPIS and some OH)

• MS should strictly follow up “efficient image use” during 2016

campaign

• MS should elaborate similar/other indicators for 2017 Campaign

� i.e. changing efficiency a little on a big budget is worth a lot …

� JRC can help …



• So, repeating from Thessaloniki: MS + EC need to ensure a method that

demonstrates efficient and effective controls at a cost efficient budget

• No change in budget planned for next campaign (2017)

• Short term:

� Efficient sampling

� Right size of control zone

� No. of acquisition windows needed

� Type/mode, profile (PSH, MSP; ORTHO)

� Use new sensors S1, S2

� Combine with alternatives: Recover LPIS

imagery, more aerial ? traditional OTSC ?, etc.

4





• G4CAP / S2

• Copernicus DWH

• Image return

• Miscellaneous

Methods

Including Macedonia

Map of control zones

VHR only 277 zones

VHR+HR 360 zones

Aerial+HR 38 zones

5

VHR - Satellite Zones (2016)

Map of control zones

497 zones with 1 VHR window(284.904 km2)140 zones with 2 VHR windows(101.965 km2)

Total Zones 637Zones*windows 777Av. images/zone 1.2

Total area to be acquired488.834 km2

(cf. 2015 final acquired ≈ approx. 470.000 km2)

Including Macedonia, excluding LPIS

VHR details - area by profiles

(*) - Excluding LPIS QA imagery

HU – 16 bands

HR – stereo

14 MS - use of A2, A5 enhanced profile

6

Map of zones

Zones 1 HR windows 38

(20.551 km2)


(120.773 km2)


(187.326 km2)


(9.712 km2)

Total zones 398

Zones*window 977

Av. images/zone 2.5

Total area to be acquired 862,923 km2

(cf. 2015 final acquired approx. 898 Zones*window / area 741.000 km2)

HR Satellite Zones 2016

HR - area by profiles

7

VHR - status campaign (1)

VHR area acquired 19/05/2016 (*)


VHR - status campaign (2)

VHR area acquired by sensor 19/05/2016


8

HR - status campaign (1)

HR area acquired 19/05/2016

HR - status campaign (2)

HR area acquired by sensor 19/05/2016

9

LPIS QA status

LPIS

• Similar approach as 2015 campaign, with the use of 40cm pixel size

when possible

• there is no upfront sensor selection, all three sensors WV2/WV3/GE1

can be considered by the image provider

� If WV2 acquires (=> 50 cm pixel size), delivery of 225 km²

� If GE1 or WV3 acquire (=> 40 cm pixel size), delivery of 169 km², i.e.

the single shot area of WV3 with smallest swath (13km)







10

VHR/HR Specs; Campaign 2016

• New specs out since Thessaloniki, and updated to their final version

after input from MS and contractors – these are valid this campaign

• https://g4cap.jrc.ec.europa.eu/G4CAP/ (under documentations tab)

• What has improved:

� documents are more consistent

� G4CAP better explained / links

� pre-IR parameters better explained

� issues on windows definition

� e.g. even if you agree to VHR backup you may extend window

� VHR feasibility (removal of +/- 3 days in most cases)

� HR feasibility improved

� new profiles inserted, and LPIS profile better explained

� ortho image return chapters revised

� better description of sensors in annex

VHR/HR Specs; Campaign 2017 … tbd (1)

New revisions open for discussion for 2017 Campaign

VHR/VHRplus

• Clear justification to use VHR2 window

HR/HHR

• Discontinue HR ? - extensive use of S2A and S2B (launch during 2016)

• Clear justification for request of autumn / winter / HR-1; revert to S2

use for especially these windows

• Continue use of HHR (1.5/6m SPOT 6/7) for the other windows; revert

to use of S2 also here where possible

• HHR window length 6-8 weeks like VHR

• MS need to use earliest start date / latest start date / dead period

better. Maybe introduce a

latest close date =>

will allow a ‘real’ feasibility

also for HHR

11

VHR/HR Specs; Campaign 2017 … tbd (2)

HR/HHR (cont.)

• Sentinel 2A repeat cycle at equator 10 days => ≈≈≈≈ 35 passes/year; this

means >70 passes at 60 deg. lat. due to overlapping swaths from

adjacent orbits …

• in “mid-EU” we have 40-50 passes / year => approx. every week (with

one satellite) => approx. 6 passes per window

• with S2B the double …

Suggestion to use all cloud free pixels from S2 together with 1VHR plus 1

or 2 HHR

• 2016 tests

• 2017 operational

• Needs assessment by MS

• Needs validation by EC

• Session in November

conference in PT …

Sentinel 2, as part of the OTSC

WV2 15 May SPOT7 2 August Sentinel 2 25 August

WV2 15 May with CAPI measurements

0,5m 1.5m 10m

12

Sentinel 2, as part of the OTSC

WorldView-2 15 May

SPOT7 2 AugSentinel 2 25 Aug

Soy-bean

SPOT6 9 April







13

G4CAP:

For general news on G4CAP, and S2 alert module see next presentation …

Copernicus:

1.) See ESA presentation in session on Data access on Wednesday

25/05/2016

2.) S1/S2 accessible from ESA scientific

hub: https://scihub.copernicus.eu/

3.) DWH (CORE datasets …) of the

Copernicus Space Component

Data Access (CSCDA):

https://spacedata.copernicus.eu/ where pan EU HR and VHR data

coverages exists are renewed every 3 years and can be used where

suitable for the CAP (licensing allows MS Administrations to DL)

G4CAP S2 alert module and Copernicus







14

Image return status

Both SOURCE and ORTHO image return of both CwRS and LPIS imagery

goes to JRC via the image providers.

The MS Administrations and their contractors need to collaborate with the

image providers in the return of their ORTHO corrected imagery

• See details in the VHR/HR Specs

Some problems for 2015 return:

VHR

FR-LPIS, LT-LPIS, NL-LPIS

HR

DE-GeoData, PT

(pls. contact JR / image providers (EUSI, Airbus) here these days since

some issues to solve)

© EUSI/DG

© AirBus

Miscellaneous

General - communication within G4CAP needs to be fast, efficient, and

according to specificatioons !!!

• Need fast reaction from you and your contractors on e.g. IDQA, on ’proposed’

imagery, etc. You are receiving autoimatic email reminders.

• Always communicate window changes due to adverse climate or hazards asap to

EUSI, and Airbus ASAP (2 weeks specs)

• Now you should also insert aerial acquisition dates in G4CAP. This will trigger

dead period, and then next window opening

• Always use G4CAP for all interactions; avoid sending bilateral emails. If in doubt

contact [email protected] of the GTCAP/CAPISA image acquisition

team

• Set your e-mail notifications correctly so you get right e-mails !

15

Conclusions

Budget in line with Thessaloniki reductions

• MS to follow up ‘efficient image use’ during 2016 and prepare for 2017

Campaign status on line

• HR-1 window over central EU difficult due to bad weather (FR)

• VHR ≈≈≈≈ 50% acquired

• HR ≈≈≈≈ 50% acquired

• LPIS ≈≈≈≈ 80% acquired

Short term:

S2 usage in place of the ‘low resolution’ HR and more where possible …

Follow Copernicus evolution, give input to the new DWH 2020+ data sets

for the agriculture cummunity

control and agricultural land in iacs…strand... · 2016. 6. 3. · 3 • close follow up by jrc...

Documents