UPD Specification scope
Go up to the main update page
The LPIS upkeep aims at maintaining such an information system that fully responds to the requirements, which means that data hosted in it is current and correct.
An update should be triggered when discrepancies arise between spatial data and the land features they actually represent. Changes on the land leading to discrepancies are detected in course of farmer declarations, inspections (OTSC, LPIS QA), or with involvement of third party data (other authorities, data companies) and are reported as anomalies. Therefore it is very important that anomalies can be coherently generated by any stakeholder and that they can be transmitted for further processing to the LPIS custodian in due time. In order to facilitate the exchange of anomaly and the subsequent cross checks after data updates, the anomaly feature type is introduced.
The methodology proposed in the LPIS update is based on anomaly processing and describes the detection of changes, the surveys and measurements to be applied, and the decision criterion (2% stability threshold) whether data update is necessary. The resulting effectiveness of LPIS update is assessed by the Member States performing the yearly Executive Test Suite (ETS) on data.
The following pages contain the recommendations of DG JRC of the European Commission concerning the maintenance procedure of the LPIS data. This document is the result of the revision of previous, draft technical documentation due to the CAP reform. Even though this technical guideline follows the logic of the business processes presented as UML use cases and activity diagrams, for sake of understanding detailed text descriptions, in depth explanations, and practical examples are given too. The purpose of this guidance is to provide a comprehensive view of the technical activities and interactions related to keeping an LPIS up to the specifications, which aims at removing the observed non-conformities.
A reference parcel does not always represent correctly the land that is subject of different payment schemes. A deviation from the business and technical rules is detected as non-conformity. Non-conformity can appear when:
- the IACS rules have changed, but the changes have not been applied,
- the local implementing regulations have changed, but they have not been followed,
- the physical land has changed, but the changes have not been reflected in the corresponding data,
- processing has been incomplete,
- erroneous processing has been performed.
The change of rules and regulation must be handled at the level of the information model (application schema) first, land changes, omissions and error are pure data questions that are handled in the update process. If a discrepancy between data and reality cannot be directly linked to any of the six above causes, further and deeper investigation in the design and procedures should take place.
The information carried by anomalies provides transparency and traceability and gives the managerial information needed for the appropriate planning, reporting, and analysis of the upkeep activities.
In principle, every confirmed anomaly or issue has to be resolved, which means that the erroneous instances of data (reference parcel) or information model elements have to be corrected. In order to keep the correction process traceable and provide a time stamp for validity of the affected elements, appropriate metadata has to be attached. The generic principle of assigning life-cycle metadata values is described in the common introductory part of upkeep.
Go up to the main update page