Feature level metadata

From Wikicap - European Commission

Go up to the main update page

Feature level metadata gives generic information needed for traceable management of information in LPIS, as well as in IACS in general. As the name suggests, this metadata type is linked to feature types (for example reference parcel, EFA, anomaly, issue, etc.) to express additional properties. Feature level metadata records may carry a global identifier, but the most important are those properties (attributes) that clarify the validity and the status of the data. The status of data is connected with the life cycle of the data, which covers the creation, through various phases of updates, to its retirement (archival). Life-cycle information is related with data management within the information system. Therefore, it is a pure technical (IT) concept.

Validity is related to the business rules, in case of IACS to the validity for the processes. When an instance of a feature type, for example a reference parcel is valid, it can participate in all business processes: an application can be submitted on it, or can become subject of OTSC, etc. Obviously, this is not the case of an archived reference parcel, which is kept in the system for historical references. Archive data are needed, for example, for retroactive recoveries.

Although life-cycle and data status relate to data base characteristics, the purpose of all upkeep processes is to ensure that a given data base element is only valid when it correctly represents an object in the real world.

The information content of feature level metadata and the code list describing life-cycle status values are presented in Figure 1.


Figure 1: Feature level metadata and code list for tracing life-cycle information of reference parcel and LPIS information model


Mnemonic name


IACS identifier


Universally unique identifier of object / feature. An object identifier (UUID as GlobalID) is a unique object identifier maintained by the responsible body. The identifier is a unique identifier of the object / feature within the IACS system, therefore it is not an identifier of the real-world phenomenon; therefore it is not a thematic identifier either. NOTE. Reference parcel identifier is not necessarily a global identifier; it may be a thematic identifier (e.g. cadastral ID) too. However, it is highly recommended to use unique IDs within the IACS.

Status type


Information about the life cycle status of the data or feature type. Validity/update status of feature / object / schema, values depend on implementation choice. The LCM proposes the following values of status type:

  • open
  • under evaluation
  • in progress
  • under cross check
  • under approval
  • rejected
  • approved
  • valid
  • archived

NOTE. It is not mandatory to implement all the values. The list is exemplar to express different possible scenarios in updating, cross checking, verifying, etc. processes.

Status description


Narrative description of the status. Additional text commonly used to display the extended description of status of object / feature.

Begin life span version


Date and time at which this version of the feature was inserted or changed in the dataset.

Valid from


Official date and time when the object / feature has been (will be) in situ or legally established. NOTE. In case of reference parcel it is the date from which the reference parcel can enter into the application process with those properties that it has. It is a legal category.

Valid to


Official date and time at which the feature in situ (or legally) ceased (will cease) to be used. NOTE. It is a legal category

End life span version


Date and time at which this version of the feature was superseded or retired in the dataset. It is a database (IT) concept



Text commonly used to display the extended description of particular feature.

Go up to the main update page