2.8. Derivations Sheet

The derivations sheet contains information about the units of other nomenclatures that have been used to create a new nomenclature. This file can exist only for derived nomenclatures (produced using statistical units of other nomenclatures) and is optional. Establishing links with original units will allow the application to convert data between related nomenclatures.

Tree types of links can be established between the original and the derived units in the current version of the specification. These types must be indicated in the derivations sheet. They are the following:

The derivations sheet must respect layout shown in Table 2.11 example. In this example, the original units (BE, NL and LU) are used by a derived nomenclature to form an aggregated unit having the code BENELUX in this custom nomenclature. The aggregated unit can be characterized as a super-structure, a parent for the original ones, existing inside the described nomenclature.

Table 2.11. Derivations sheet layout example

 ABCDEFG
1unit_original_codeunit_original_levelunit_original_nomenclatureunit_original_versionunit_derived_codeunit_derived_levelrelationship
2BE0NUTS2003BENELUXincludes
3NL0NUTS2003BENELUXincludes
4LU0NUTS2003BENELUXincludes

[Note]

The lines of the tables must be read and understood as follows: the unit encoded BENELUX in this nomenclature description includes (or "derives in an inclusive relationship from") the units encoded BE (line 2), NL (line 3) and LU (line 4), which are available in the nomenclature encoded NUTS in its version 2003. This example assumes that the NUTS version 2003 is already stored in the database.

Details of columns are given below:

unit_original_code

MANDATORY

Contains the code of the original unit used to produce the unit of the described nomenclature. The original unit must be already registered in the Database and its code must be valid.

unit_original_level

MANDATORY

Contains the level label of the original unit used to produce the unit of the described nomenclature. The original level must be already registered in the Database and its code must be valid. An empty value references the default level of a non-hierarchical nomenclature.

unit_original_nomenclature

MANDATORY

Contains the literal of the nomenclature where the original unit exists. This column is added to the file layout because a custom nomenclature can derive from more that one others.

unit_original_version

MANDATORY

Contains the title of the version of the nomenclature where the original unit exists. This column is added to the file layout because a custom nomenclature can derive from more that one others.

unit_derived_code

MANDATORY

Must contain the code of the unit from the described nomenclature version (it must be present in the units sheet, see Section 2.3).

unit_derived_level

MANDATORY

Contains the level label of the present unit. An empty value references the default level of a non-hierarchical nomenclature.

relationship

MANDATORY

Characterizes the link between the units referenced in the currently described nomenclature (unit_derived_code column) and the units described by the three columns A (existing unit code) B (existing nomenclature code) C (existing nomenclature version). The possible values in this relationship column are:

  • INCLUDES - if the current derived unit fully includes (is a parent of) the original unit.

  • EQUALS - if the current derived unit and the original unit are equal.

  • INCLUDED - if the current derived unit is included (is a child of) in the original unit.

  • INTERSECTS - if the derived unit and the original one intersect without full inclusion or equality.

The line is rejected if the value in this column is not one of this enumeration.