Local Component Verification Guidelines

Size: px
Start display at page:

Download "Local Component Verification Guidelines"

Transcription

1 Local Component Verification Guidelines ETC/ULS Gergely Maucha, Róbert Pataki, Róbert Lehoczki (FÖMI) Stefan Kleeshulte (S4E) Christoph Schröder, Dania Abdul Malak (UMA) Christoph Perger (IIASA) Eionet Copenhagen 9-10 October 2017

2 Purpose of the verification exercise Raise the awareness of the country authorities regarding the availability of the data Support the best possible familiarization with the VHR land cover data by national actors Provide complementary information to the systematic quantitative validation results provided by the European scale validation exercise Assess the fitness-for-purpose of the local component products at national and sub-national level 2

3 Products to be verified I. Urban Atlas (UA) 2012 status layer II. III. Urban Atlas 2012 Street Tree Layer (STL) Riparian Zones LCLU 2012 status layer (RZ) IV. Riparian Zones Green Linear Elements 2012 status layer (GLE) V. Natura Grassland LCLU 2012 status layer (N2K) 3

4 Verification is not planned for Urban Atlas 2006 status Urban Atlas changes Delineation of Riparian Zones (DRZ) Natura 2000 Grassland 2006 status Natura Grassland changes 4

5 Main approaches A. Combined quantitative / look & feel verification B. Collection of information about fitness for purpose (usability) 5

6 Combined quantitative / look & feel verification Tool: Improved LACO-WIKI tool + optional extension by linking local desktop GIS High-level workflow: Data preparation (national team / ETC/ULS if required) Training of photo-interpreters (ETC/ULS, if required) Upload national dataset to LACO-WIKI (national team) Stratified random sampling (LACO-WIKI) Visual photo-interpretation supported by LACO-WIKI (national team) Evaluation (national team, supported by summary statistics genereted by LACO- WIKI) Reporting (national team) Summary evaluation of national reports (EEA / ETC/ULS) 6

7 Step 1: Data preparation Necessary data preparation may be done by the country or may be supported by ETC if required. A general size limitation is 2 Gbytes / shapefile components. Within LACO-Wiki system shapefiles larger than Gbyte may be uploaded to the system, but according to latest tests the sample creation may be not supported. Special preparation is needed for Riparian Zones Green Linear element data to create on single land cover code as. In case of Riparian Zones land cover data lower level codes (e.g. 3000) are still appearing in the dataset. It is recommended to include these classes to the verification, but this needs some special preparation. 7

8 Step 2: Login to LACO-Wiki LACO-Wiki is a new web-based solution for validating land cover and land use maps: LACO-Wiki currently supports three different login options: An existing Geo-Wiki account, Facebook login or Google account. Use of the offered options to create your account and get started using LACO-Wiki right away. LACO-Wiki may ask you to access your address and public profile in order to create your account. 8

9 Step 3: Upload data set Add name and description Choose Categorical Select & upload shapefile Valid CRS: ETRS1989 LAEA, WGS84. 9

10 Step 4: Define a legend Choose from available legends for UA, UA STL, N2K Create legend for RZ Green Linear Elements Create own legend for RZLC if decide to validate lower level codes as well. Note: You are still able to delete your new dataset, but beyond this step - once a sample is created based on this dataset - deleting is not anymore possible but not neccessarily shared with anyone else.. 10

11 Step 5: Create Samples Add name and description to sample set Choose stratified polygon Add samples Select Equally instead of By area Set number of samples as Min=1, Max=10 Type in a large number to Intended Samples The method creates polygon samples + additional points within each polygon. Download these if using linked external GIS.. 11

12 Step 6a: Create a Validation Session Add name and description to Validation Session Choose Enhanced Plausability method Check Comment field & Geometry Validation!! May use defaults for Zoom and Navigation options. 12

13 Step 6b: Create a Validation Session Add Base layers: Google Maps Copernicus Image2012 VHR Optional Open Street Map Bing Add Overlays: Validation Dataset. 13

14 Step 7a: Interpretation your samples Example UA LACO-Wiki screen - VHR Copernicus 2012 Correctness of LC/LU code - Correct - Proposed code: - Delineated area: - Missing and unnecessary parts Detail of delineation: - Too coarse Positional accuracy: - Correct (no shift) Comment: - Code OK around sample point, but not correct for the whole polygon 14

15 Step 7b: Costumize additional GIS environment Google Earth screen -Time series of VHR imagery available (in many cases) Local desctop (Q)GIS screen (VHR IR ortho-aerial ortho) - Locally available layers may be displayed via extent link LACO-Wiki screen - Urban Atlas 2012 Correctness of LC/LU code - Correct - Proposed code: - Delineated area: - Missing and unnecessary parts Detail of delineation: - Too coarse Positional accuracy: - Correct (no shift) Comment: - Code OK around sample point, but not correct for the whole polygon 15

16 Step 8: Create Report Add name and description to report Check Raw data May leave default settings (all statistical measures) Download report as Excel file Interpreted samples may be downloaded as a shapefile in a previous step - Validation Session Details. 16

17 Step 9: Extract statistical measures from report Use weighted page to extract statistics (because of stratified sampling) 17

18 Step 10: Create one report per dataset 18

19 Local component verification report example 19

20 Local component verification report example 20

21 Collection of information about fitness for purpose Aim: To present a simple methodology for interviewing national users about the usability of VHR data Methodology: 1. NRCs contact end users, providing information about products and consultation activity 2. NRCs send out the questionnaire to the selected end users, with following options: a. The questionnaire is filled together with the end user during a personal call or a dedicated workshop b. The end users fills the questionnaire on their own and send it back to the NRC. 3. The responses are checked by the NRC for consistency and open issues. The end users are contacted again for a follow-up consultation about open questions, issues or clarifications. 4. All feedbacks are to be documented in a structured way and sent to EEA. 21

22 Collection of information about fitness for purpose Part1: General knowledge and opinion about the Copernicus Local Component products 1. Do you use the Local Component product: a. Yes, I have used it b. Yes, I am planning to use it. c. No (specify why) 2. Describe the (potential) uses of the local component products in your workflows [Free text] 3. What kind of support do you expect from the local component products (which you do not find yet) to fulfil your reporting/monitoring obligations? a. High update frequency allows gap filling of national products b. Classification system supports national MAES obligation c. Comparability between national N2K sites/urban areas/riparian Zones d. Others (specify) 22

23 Collection of information about fitness for purpose 5. What is its added value when compared to rather national, local data? a. Higher spatial resolution b. Higher temporal resolution c. Better thematic classification d. Others (specify) 6. What are the limitations experienced by the user? a. Spatial resolution (please, specify) b. Temporal resolution (please, specify) c. Nomenclature (please, specify) d. Thematic content (please, specify) e. Delineation (please, specify) f. Others (please, specify) 23

24 Collection of information about fitness for purpose Part2: Technical aspects 6. What are your comments (for improvement in further updates) regarding: nomenclatures? (e.g. class descriptions, missing classes) [Free text] technical documentations? (e.g. information about thematic content, geographical coverage, interpretation methods)? [Free text] thematic/semantic content of classes? [Free text] delineation? [Free text] Part 3: Final remarks /follow-up comments [Free text] 24

25 Post production verification of Local component data Thank you for your attention! Service Contract No 3436/R0-Copernicus/EEA (ETC/ULS) Gergely Maucha, Róbert Pataki, Róbert Lehoczki (FÖMI) Stefan Kleeshulte (S4E) Christoph Schröder, Dania Abdul Malak (UMA) Christoph Perger (IIASA) 25

26 HRL 2015 reference year post-production verification Post-production verification of HRL 2015 products Products will be available from around March 2018, some first 20m, European Projection status layer full EEA39 mosaics are already finished (IMD, TCD, DLT, WAW) Delays for SWF (small woody features) product due to problems with VHR 2015 imagery Detailed guidelines for post-production verification will be drafted by the ETC ULS, but do not exist yet Verification will likely follow the verification done in 2012 and contain: Detailed look & feel analysis to identify systematic issues Some quantitative evaluation Collect information and feedack on use/usability of the products on national level 26

27 HRL 2015 reference year post-production verification Product Status production as of early October 2017 Expected full delivery of all products Comment Lot 1 Imperviousness Key status product fully delivered, additional products pending and slightly delayed Next delivery major parts of the total of 40 products early December Final deliveries early March 2018 Key status layer delivered: 100% of 2015 status layer in 20m spatial resolution and European Projection Lot 2 Forest Key status products fully delivered, additional products pending and slightly delayed Next delivery major parts of the total of 40 products early December Final deliveries early March 2018 Key status layers for tree cover density and dominant leaf type in 20m spatial resolution and European Projection delivered Lot 3 Grassland Key status product partly (46%) delivered, full mosaic and additional products pending Full status layer expected early December, final additional products early March 2018 Part of key status layer for grassland in 20m spatial resolution and European Projection delivered Lot 4 Wetness and Water Key status products fully delivered, production fully on schedule Early December 2017 Key status layer fully delivered, aggregated product pending but fully on schedule Lot 5 Small Woody Features Delayed due to VHR input data issues. Streamlining and various mitigation measures concluded, but no deliveries yet TBD A draft modified production schedule will be agreed with lot 5 before end October