This vocabulary consists of a hierarchical set of labels with their definitions expressing the duties an implementer might need to carry out to produce any INSPIRE resources.

The list of tasks relies on the legal requirements (both from the Directive and Regulations) and INSPIRE’S technical guidance documents.

When implementers describe their implementation guides as a series of steps in a workflow, they pick relevant tasks from this common reference vocabulary. Also solution providers are invited to link the INSPIRE tasks supported by their tools so they are easily retrievable.



identify and document transformation to INSPIRE spatial object types


For all spatial objects in the spatial data set, identify the information that is within scope of an spatial data theme in the annexes of the Directive. For each theme, identify the information that may be represented as part of a spatial object in one of the INSPIRE application schemas specified for the theme.


In simple cases, all data may be transformed to spatial objects from a single INSPIRE application schema (e.g. a cadastral parcel data set will often contain only information that is covered by the INSPIRE application schema "Cadastral Parcels"). However, in general a data set will be transformend into spatial objects from multiple INSPIRE application schemas (e.g. a topographic data set will cover themes like transport networks, hydrography, buildings, land use, etc.). This task is broken down into a sub-tasks for key interoperability aspects. In principle it could be broken down into much more detialled subtasks (per application schema, per spatial object type, per property, per code list value, etc). This has not been done as typically the mapping documentation templates (see asset dsi-map) are made available per application schema. Transformation tools will often work on a spatial object type level, so it may be that it makes sense to include another level of subtasks, but this should be evaluated based on feedback and experiences.

Assets out: 



INSPIRE component: