Land administration in the agricultural sector under INSPIRE

Transcription

1 PCC workshop, Rome, 11 December Land administration in the agricultural sector under INSPIRE Wim DEVOS Agriculture Unit, JRC Ispra

2 PCC workshop, Rome, 11 December Introduction: the legal and general context

3 PCC workshop, Rome, 11 December Context Common Agricultural Policy Aid to the farmer s is decoupled from production but area based To manage aid, MS have to set up an Integrated Administration and Control System (IACS) with: (a) a computerised data base, (b) an identification system for agricultural parcels (LPIS), (c) a system for the identification and registration of payment entitlements, (d) aid applications, (e) an integrated control system, (f) a single system to record the identity of each farmer who submits an aid application

4 PCC workshop, Rome, 11 December Context (cont d) 2004R0796 6: 1. The identification system for agricultural parcels shall operate at reference parcel level such as cadastral parcel, or production block 2003R Use of payment entitlements 1 Any payment entitlement accompanied by an eligible hectare shall give right to the payment of the amount fixed by the payment entitlement. 2. Eligible hectare shall mean any agricultural area of the holding taken up by arable land and permanent pasture except areas under permanent crops, forests or used for non agricultural activities 2003R Verification of eligibility conditions 1. shall carry out administrative checks on the aid applications including a verification of the eligible area and corresponding payment entitlements supplemented by a system of (sampled) on the spot checks

5 PCC workshop, Rome, 11 December Context (cont d) 2003R a farmer receiving direct payments shall respect the statutory management requirements, and the good agricultural and environmental condition Statutory Management Requirements (SMRs): 18 Community legislative acts in the areas of environment, public, animal and plant health and animal welfare 2. Good Agricultural and Environmental Conditions (GAECs): defined by MS in a common framework covering soil erosion soil organic matter soil structure minimum level of maintenance NEW: CAP Health Check- respect buffer strips along water courses Maintenance of land under permanent pasture

6 PCC workshop, Rome, 11 December Context (final) LPIS, part of IACS GIS, has 2 roles 1. protect the EU financial interests by quantifying area Denotation: for at least 75 % of the reference parcels being subject to an aid application, at least 90 % of the respective area is eligible Connotation: at least 98 % of the financial value is regular 2. Increasingly safeguard the broader CAP objectives for environmental sustainability and rural development by recording eligible features for these schemes No denotation, use imagery to detect landscape elements Connotation: accountability, what is paid must be recorded

7 PCC workshop, Rome, 11 December Earlier arguments not to use cadastre for LPIS Land management respects rarely ownership limits, so that an agricultural fields intersect usually several cadastral plots, The percentage of rented land is high in most Member States, so that the ownership information provided by the cadastre is of little use, Land use in the cadastre is rarely up to date, land eligibility has thus to be based on other sources, Due to fiscal reason, the motivation is low to declare the land restructuration. It results that the actual limits can differ significantly from the official ones, Delays of cadastral update are generally long due to lack of resources, Areas are not guaranteed and disagreements can exist between the numerical and graphical information, For budgetary reason, cadastres are often analogue and of difficult and onerous access for farmers and administrations.

8 PCC workshop, Rome, 11 December How did systems develop?

9 PCC workshop, Rome, 11 December National implementations LPIS type (2006) An example FI SE IE UK DK LV EE NL LT BEf BEw LU DE PL CZ FR SK AT SI HU PT ES IT GR MT CY 5 agriculture parcel 3 cadastral parcel farmer block 8 physical block varies by Laender 2 MS in accession 4 MS have recently switched

10 PCC workshop, Rome, 11 December How do systems quantify the ReferenceArea Questions: How many spatial feature layers are used? What spatial solutions for exclusions? Replies (25) Physical block Farmer's block Agri parcel Single Layer Single layer, flags or points 2 Layers >2 layers Cadastral parcel 3 2 Observations Cadastral parcel is a multilayer (land tenure land use/land cover) unexpectedly, production blocks are often too! Agricultural parcel? need to be clarified

11 PCC workshop, Rome, 11 December How is the Cadastral Parcel performing? A study of 3 x 4 LPIS by D. Grandgirard and R. Zielinski (2008 ) LPIS types AP CP FB PB LPIS zones Anomalous reference parcels percentage AP AP AP CP CP CP FB FB FB PB PB PB Average (STDV) 18.8 (7.7SD) 13.7 (12.7SD) 33.9 (23.7SD) 42.5 (28.6SD) significant difference (a) (a) (a) (a) - Proportions of anomalous parcels were high (from 5% up to 67%!) -No significant difference between LPIS types -But a trend to observe higher anomalous parcels proportion in blocks (FB, PB) than in single parcels (AP, CP) -Remark: it doesn t mean that the LPIS are of very bad quality do not forget that it was anomalies and not irregularities!!!!!!!!!!

12 PCC workshop, Rome, 11 December How does INSPIRE affect the agriculture LAS?

13 PCC workshop, Rome, 11 December IACS-GIS, in particular LPIS, is an operational, regulatory based, EU wide dataset large scale, parcel-based register 9 million clients annually 500,000 farm / 3,000,000 parcel controls in 2007 not an INSPIRE annex theme / DS2.3 dataset itself but has many dependencies on INSPIRE themes: cadastre, topography, land cover Reference Parcel land use, orthophotos Agricultural Parcel soil data, elevation, hydrology, restriction/regulation zones cross-compliance similar needs towards technology and data access

14 PCC workshop, Rome, 11 December The Inspire Theme versus LPIS INSPIRE annex data set LPIS at be bg cy es se uki EC 796/ common concepts at bevl bewa bg cy es se uken ukni spec spec spec spec spec spec spec spec spec spec spec spec spec spec spec INSPIRE specific. db db db db db db db view - transformation services db 2 common use db payment control file application db db db db CAP operations db db db eu db report eu clearance 3 common QC

15 PCC workshop, Rome, 11 December Align the common concepts example: relate eligibility of land -in LPIS context- to land cover, not to land use: Land doesn t change when Regulations are modified! FAO LCCS äs a language to describe the different land cover features in a standardised way. 1.Comprehensive (cover complete range, accommodate variability, enable comparisons) 2.Practical (adaptable, minimal number of classifiers) 3.Scientifically sound (systematic, multipurpose, scale independent, UML compliant) FAO/UN Land Cover Classification System (LCCS) Draft ISO Standards for Land Cover Classification ISO Geographic information Classification Systems Part 1: Classification System Structure, and; ISO Geographic information Classification Systems Part 2: Land Cover Classification System (LCCS: UN-FAO, 2005)

16 PCC workshop, Rome, 11 December Land use/ land cover definition (INSPIRE EU 2007/2) Land cover: Physical and biological cover of the earth s surface including artificial surfaces, agriculture areas, forests, (semi-) natural areas, wetlands, water bodies. Art 44(2) Council Reg (EC) No 1782/2003 Land Use: Territory characterised according to its current and future planned functional or socio-economic purpose (e.g. residential, industrial, commercial, agricultural, forestry, recreational) Art. 49 Comm. Reg. (EC) No 796/2004

17 PCC workshop, Rome, 11 December These lands may be grazed, but are ineligible!!

18 PCC workshop, Rome, 11 December Pasture on different grasslands one definition? It is not possible to develop a pan-european legend because legends are specific by region and scale. It is feasible to adopt standard classification systems

19 PCC workshop, Rome, 11 December Test Cases Bulgarian LPIS The Reference Parcel is Physical Block. Full coverage of the country. LC/LU code assigned to each RP LPIS Land cover/land use map 1: Independent Land Cover Mapping 1: Using LCCS concept Forest Arable land Mixed (arable/grass/trees) Grassland Woodland Urban

20 PCC workshop, Rome, 11 December support the common use / procedures Example: sharing of GI documentation and reuse of components LPIS Core model UML documentation of the LPIS/IACS-GIS based on the Regulation requirements and common practices then compared against the LADM ISO19152 draft to propose an LPIS add-on annex F See: SDIC/Presentations/S6-Van-Oosterom

21 PCC workshop, Rome, 11 December The LPIS core model

22 PCC workshop, Rome, 11 December The glue between LCM and LADM DeclaredAgriParcel and SpatialUnit Only relevant part of cadastral parcel (SpatialUnit) is used as reference parcel modeled via new SubParcel class Land Use/Cover Types «CodeList» SubPARCEL:: SubParcelType + arableland + permanentcrop + permanentpasture + seminaturalgrassland + olivetrees + othertrees + nonagricultural SubPARCEL::SubParcel + area: Measure + layer: Integer [0..1] + spid: Oid + structure: LA_StructureType + typesubparcel: SubParcelType + referencepoint: GM_Point [0..1] 0..* 1 LADM:: LA_RecordedObject Excluded

23 PCC workshop, Rome, 11 December Only area SpatialUnits (Parcel) relevant class LADM - IACS/LPIS Spatial Classes By Halil Inan et al. SubPARCEL::SubParcel + area: Measure + layer: Integer [0..1] + spid: Oid + structure: LA_StructureType + typesubparcel: SubParcelType + referencepoint: GM_Point [0..1] constraints {Sum (DeclaredAgriParcel.claimedArea) <= area} 1 0..* 1 Hierarchical Topology in a different Layer LADM::LA_SpatialUnit LADM::LA_RecordedObject + roid: Oid + name: CharacterString [0..1] + registertype: LA_RegisterType [0..1] Adjacent 0..* 0..* +element +set 1..* 0..* Outside the Scope of IACS/LPIS +set element 1..* LADM::LA_SpatialUnitSet + susid: Oid + level: Integer + label: CharacterString + name: CharacterString [0..1] + referencepoint: GM_Point [0..1] + oidtype: LA_SuOidType [0..1] 0..* IACS/LPIS:: DeclaredAgriParcel + suid: Oid + psuid: Oid [0..1] + label: CharacterString [0..1] + referencepoint: GM_Point [0..1] + type: LA_SpatialUnitType [0..1] + Area: Integer [0..1] + Volume: Integer [0..1] LADM:: LA_BuildingReserve +partof 1 +element 1..* «CodeList» SubPARCEL:: SubParcelType + arableland + permanentcrop + permanentpasture + seminaturalgrassland + olivetrees + othertrees + nonagricultural «CodeList» LADM:: LA_SpatialUnitType + 2D + 3D + liminal «CodeList» LADM:: LA_StructureType + fullpartition + polygons + polygonwithholes + unstructured LADM:: LA_BuildingUnit LADM:: LA_NetworkReserve Outside LPIS

24 PCC workshop, Rome, 11 December Administrative side (mainly IACS) class LADM - IACS/LPIS Administrative Classes LADM::LA_Party +party +rrr LADM::LA_RRR + partyid: ExtParty + type: LA_PartyType + role: LA_PartyRoleType [0..*] * + share: Rational + timespec: Time If claimedarea = 0, it means that there is no claim for this parcel IACS/LPIS::Farmer + farmerid: CharacterString + farmeraddress: CharacterString IACS/LPIS::YearlyAidApplication + applicationid + applicationseasonyear: CharacterString + paymentcalculation() : Currency 1 1..* IACS/LPIS::DeclaredAgriParcel + claimedarea: Floa + croptype: CropGroupCode + paymenttype: PaymentCode + nationalpaymenttype: NationalPaymentCode +/ determinedarea: Float * IACS/LPIS::PaymentEntitlement + amoutofhectare: Float + valueperhectare: Currency + calctype: EntitlementCalcType + unusedhectare: Float 1..* IACS/LPIS:: YearlyFarmerSketch 1 SubPARCEL::SubParcel

25 PCC workshop, Rome, 11 December Some administrative model details Farmer inherits from Party YearlyAidApplication inherits from SourceDocument and has 2 components: YearlyFarmerSketch (1..*) and DeclaredAgriParcel (1..*) Code lists used class Code Lists for Administrative Classes «CodeList» IACS/LPIS::PaymentCode + SPS + set-a-side + durumwheat + proteincrop + nuts + energycrops + starchpotato + arablecropsregionalaid + arablecropsareapayment + seeds «CodeList» IACS/LPIS:: CropGroupCode + nocrop + wheat + rye + barley + oats + vines + starchpatatoes + linseed +... «enumeration» IACS/LPIS:: EntitlementCalcType singlefarmpayment regionsinglefarmpayment combination

26 PCC workshop, Rome, 11 December Attention to the Farmer in the model Farmer in article 2 of Regulation EC No 1782/2003: natural or legal person or group of natural or legal persons Farmer gets to additional attributes: farmerid, farmeraddress lass Farmer as a kind of Person LADM::LA_GroupParty + groupid: Oid + type: LA_PartyGroupType + name: PT_FreeText [0..1] constraints {sum(la_member.share)=1 per group} «CodeList» LADM:: LA_PartyGroupType + tribe + association + family +group 0..* LADM::LA_PartyMember + share: Rational [0..1] +parties 2..* LADM::LA_Party + partyid: ExtParty + type: LA_PartyType + role: LA_PartyRoleType [0..*] «CodeList» LADM:: LA_PartyRoleType + farmer + loanprovider + conveyor + surveyor 0..1 «enumeration» LADM::LA_PartyType Attributes + naturalperson + nonnaturalperson + recordedobject + group IACS/LPIS::Farmer + farmerid: CharacterString + farmeraddress: CharacterString RecordedObjectAsParty 0..1 LADM::LA_RecordedObject

27 PCC workshop, Rome, 11 December LADM: Farming rights and restrictions right to be paid (entitlement) FarmingLimitations due to cross compliance class Aid Application and RRR relation «CodeList» LADM:: LA_RightType + agriactivity + grazing + lease + occupation + ownership + waterrights LADM::LA_Right + type: LA_RightType LADM::LA_RRR + share: Rational + timespec: Time +rrr 1..* LADM::LA_Restriction + type: LA_RestrictionType IACS/LPIS:: FarmingLimitation + typeofcrosscomplience: Character + typeoflimitation: CodeList IACS/LPIS::DeclaredAgriParcel 0..* 1 SubPARCEL::SubParcel + area: Measure + layer: Integer [0..1] + spid: Oid + structure: LA_StructureType + typesubparcel: SubParcelType + referencepoint: GM_Point [0..1] 0..* 1 +object 1 LADM::LA_RecordedObject + roid: Oid + name: CharacterString [0..1] + registertype: LA_RegisterType [0..1] 0..* 0..* LADM::LA_SpatialUnit + suid: Oid + psuid: Oid [0..1] + label: CharacterString [0..1] + referencepoint: GM_Point [0..1] + type: LA_SpatialUnitType [0..1] + Area: Integer [0..1] + Volume: Integer [0..1]

28 PCC workshop, Rome, 11 December Addressing quality reporting Objective: developing a quality assurance framework Currently, the EC assesses LPIS performance during Audit missions: Investigating OTSC control files and repeating control procedures PLUS: All aspects and the whole process can be investigated MINUS: Only a very sample is checked and resources are limited. ==> this is an example of an internal quality control by external body To be more representative and systematic, there is a need for a QA strategy is evident, where MS report on the observed performance of their LPIS. QA is a proactive strategy of continuous quality control and reporting This is a very high DGAgri priority

29 PCC workshop, Rome, 11 December LCM Testing methodology ISO 19105: Conformance and testing 1.Prepare/document the implementation 2.Verify the logical consistency with the model 3.Verify other data quality elements 4.Report FC ATS ETS Application Schema or Feature Catalogue of the implementation under test Model Conformance Test Conformance Statement (ICS) Abstract Test Suite (ATS) Additional Information for Testing Data Conformance Test Executable Test Suite (ETS) Analysis of results Conformance Test Report

30 PCC workshop, Rome, 11 December The Feature catalogue (ISO19110) Example: Slovenia

31 PCC workshop, Rome, 11 December Abstract Test Suite Purpose: Tests that the implemented data model conforms to the LCM specification Side-effects: Good way to decide which RP type is implemented help to find potential misinterpretations of certain values VS1 31

32 Diapositiva 31 VS1 but they cover 99% or RPs, not only 5 files of current audit procedure Valentina Sagris; 02/12/2008

33 PCC workshop, Rome, 11 December Executable Test Suite Purpose: check data conformance to LCM and feature catalogue to be implemented for each MS separately - simple with guidelines VS2 32

34 Diapositiva 32 VS2 but they cover 99% or RPs, not only 5 files of current audit procedure Valentina Sagris; 02/12/2008

35 PCC workshop, Rome, 11 December Conclusions

36 PCC workshop, Rome, 11 December LPIS and LAS 1. Cadastral parcel based LPIS systems hold their ground provided : the cadastral index maps reflect the real situation of the land, (as should probably any LAS) the system integrates ancillary data (aerial imagery, eligibility layer) 2. Cross-compliance with EU policies tends to broaden LPIS/IACS-GIS scope for land, spatial concepts and terrain features a true rural LAS 3. If cadastral systems will become LAS, for the rural area they will have to face the same dynamics. 4. To date, there are very few technical documents and little guidance

37 PCC workshop, Rome, 11 December LPIS and INSPIRE 1. Although not a theme, LPIS is well caught by the rapid developments 2. An obvious benefit as environmental data user is expected 3. The methodological framework is being tested and applied on the fields where the scope for standardisation is greatest Concepts and definitions Shared Documentation. a Common Quality Framework 4. A lot of work ahead.

38 PCC workshop, Rome, 11 December Thank you for your attention!