3.4. Metadata Elements Layout

All the metadata elements specified in an ESPON dataset must be presented in conformity with the Implementation. An incorrect presentation can be the cause of data/metadata losses, invalid interpretations or even impossibility to integrate the dataset into the ESPON Database.

This sectionn describes the layout of all existing metadata elements in a tabular form. For each element, the optional and multiple properties that can affect the layout, are commented.

The order of the labels appearing in the document is strict and must be respected by all tabular files.

3.4.1. Dataset Information Element

The Dataset Information element must be presented like follows in a tabular sheet:

Table 3.6. Dataset Information element layout

1Dataset Information
2NamePopulation of Europe 
3ProjectEuropop Survey 
4Upload Date2011-07-10 
5Creation Date2011-06-01 
6Revision Date  
7Metadata Date2011-07-10 
8AbstractProvides the population data on all European countries from 1990 to 2050 (projections).
9Resource Locatorhttp://database.espon.eu/data?dataset=35 
10Unique Resource IdentifierEuropop_PopulationEurope_20110710_v1 
11Topic CategorySociety 
12KeywordsVocabularyKeyword Value
13 GEMETSocial aspects, population
14 GEMETDemography
15 INSPIREpopulation distribution - demography
16  population projections
17LineageLineage description specified here...
18Resource Typedataset 
19Dataset Languageeng 
20Metadata Languageeng 
21Temporal Extentstartend
22 19902050
24 SpecificationINSPIRE Metadata Implementing Rules
25 Specification Date2011-05-06
26ConstraintsUse ConstraintCopyright
27 Access ConditionSee the Terms&Conditions Agreement of the ESPON Database Web Application
28 Other Constraintsno limitations
29 Access Classificationunclassified

Optional properties: Resource Locator and Conformity.

Multiple properties: Topic Category and Vocabulary + Keyword Value.

The values at rows 18-20 (Resource type, Dataset Language and Metadata Language) are constants and must not be modified. Contact Information

The contact information is represented by the contact elements Responsible Party, Metadata Contact and Point Of Contact. The first two are mandatory, while the third one can have multiple optional occurrences in the document.

The contact properties may be presented as follows:

Table 3.7. Contact element layout

31Responsible Party
32Individual NameANDRE, Ronald 
33Organization NameESPON Research Centre 
35Email[email protected] 
37Metadata Contact
38Individual NameBURTON, Patrick 
39Organization NameESPON Research Centre 
42Email[email protected] 
44Point Of Contact
45Individual NameBRUCKERS, Stella 
46Organization NameESPON Research Centre 
49Email[email protected] 
52Individual NameVAN HERWIJNEN, Marjan 
53Organization NameESPON Coordination Unit 
55Email [email protected] 
57Delivery PointUCRP HT - P.O. Box 144 
59Postal CodeL-4221 
60Administrative AreaCedex 13 
61CountryGrand-Duché de Luxembourg 

Optional properties: Position and Phone.

Multiple properties: Phone and Email.

3.4.2. Spatial Binding Element

The Spatial Binding element should follow the Dataset Information element on the same sheet of the spreadsheet. It classifies the nomenclatures used in the dataset and lists their respective versions and levels. This element must respect the following layout:

Table 3.8. Spatial Binding element layout

63Spatial Binding
64Geographic LocationNorth70.09
65 South34.56
66 West-10.58
67 East34.59
68Nomenclature NameNomenclature VersionNomenclature Level
70  1
71Nomenclature NameNomenclature VersionNomenclature Level
73  1
74  2
75Nomenclature NameNomenclature VersionNomenclature Level

The order of appearance of nomenclature names entries is not relevant, neither the order of versions and levels inside a nomenclature entry.

Optional properties: none.

Multiple properties: Nomenclature Name, Nomenclature Version and Nomenclature Level.

The dataset of the example contains statistical units of the NUTS nomenclature, of its 2006 and 2010 versions. The NUTS statistical units of the dataset belong to the 0th, 1st and 2nd levels of the nomenclature. This dataset also contains units from the EFTACC nomenclature, of its version of 2008. These units are present only at the 2nd level of the EFTACC nomenclature. Please note that a combination of the values of the Nomenclature Name and the Nomenclature Level properties is used to identify units, as shown in Section 3.5.1.

3.4.3. Indicator Identification Element

All the Indicator Identification and Indicator Aggregation elements present in a dataset should be put in a single separate sheet of the spreadsheet. This should be done to facilitate the analyzis of the metadata.

The Indicator Aggregation element must respect the following layout:

Table 3.9. Indicator Aggregation element layout

1Indicators Aggregation
2Aggregation CodePOP_BY_AGE 
3Aggregation NamePopulation by age 
4Aggregation AbstractPopulation divided in age groups

A singular Indicator Identification element must use the following layout:

Table 3.10. Indicator Identification element layout

1Indicator Identification
3PCTPDPopulation Development, TotalThe annual evolution of the total population of the specified territorial unit, both natural and migratory change.
6Nat TypeRR 
7ThemePopulation and living conditions 
8KeywordsVocabularyKeyword Value
9 GEMETdemography
10  population growth
12 Formula 
13 URIhttp://espon.eu/reports/report111031.pdf
14Temporal Extentstartend
15 20092009
16 20102010
17 20112011
18Data TypeType Identifierinteger

Optional property: Methodology.

Multiple properties: Code (Name and Abstract), Theme, Vocabulary + Keyword Value, start + end.

The Code, Name and Abstract properties use vertical layout because it allows to optimize the representation of similar indicators that share all the other fields. This is, for example, the case of the indicators concerning the population structure by ages, when the indicators "Population, males, 20-24 y.o.", "Population, females, 20-24 y.o.", etc share all the properties but the three cited ones. In this case the element can be layouted as follows:

Table 3.11. Indicator Identification element layout for several indicator with shared properties

1Indicator Identification
3POP_0-24Population, young (0 - 24 y.o.)Total number of persons of 0 - 24 years old.
4POP_25-64Population, adult (25 - 64 y.o.)Total number of persons of 25 - 64 years old.
5POP_65+Population, old (65 y.o. and more)Total number of persons of 65 and more years old.

All the indicator codes listed in this layout must be also enumerated in the respective Indicators Aggregation element.

The Temporal Extent properties may be specified in several ways. If the time period covers several years, both the start and the end years are mandatory. If it concerns only one year, it may be specified as follows:

Table 3.12. Layout of a Temporal Extent property covering one year

14Temporal Extentstartend
15 20092009
16 2010
17 2011 

If the temporal value is an instance (a day), the exact date of the instance must be specified:

Table 3.13. Layout of a Temporal Extent property for a time instance

14Temporal Extentstartend
15 2011-09-25 
16 2011-09-252011-09-25
17 2011-09-25

Data Types Layout

This section describes the layout to be used to specify the Data Type property of the Indicator Identification element.

The Type Identifier and Description properties use the same layout for all data types:

Table 3.14. Layout of the shared properties of the Data Type element

18Data TypeType Identifierinteger
19 DescriptionThe value denotes the year when the country ratified the Convention on...

The Description property is mandatory only for the Other data type.

Numeric data (Integer or Float) must use the following layout:

Table 3.15. Numeric Data Types layout

18Data TypeType Identifierinteger
19 Description 
20Unit of MeasureNumerator / Denominator Nameinhabitants
21 Numerator / Denominator Scale1000
22 Rankingfalse
23 Min 
24 Max 

If the numeric data is bound to a range, the minimun and/or the maximum values of the range must be specified.

For the Unit Of Measure property, name and scale properties are mixed for numerators and denominators of fractional units, which must be separated by the "/" sign or the "per" preposition in the cell. For example, the fractional unit "births per 100000 inhabitants" must be presented as "births per inhabitants" or "birth / inhabitants". The scale property must be specified as "1 per 10000" or "1 / 10000".

For Text data, the properties to specify are the Unique boolean (mandatory) and an optional Description:

Table 3.16. Text Data Type layout

18Data TypeType Identifiertext
19 DescriptionThis text describes the...
20 UniqueFALSE

If the Enumerated data are used, the layout must contain the description of all the elements of the enumeration:

Table 3.17. Enumerated Data Type layout

18Data TypeType Identifierenum
19 Description 
20 OrderedTRUE
21 Value LabelValue Description
22 VLVery low rate of activity
23 LLow rate of activity
24 MMedium rate of activity
25 HHigh rate of activity
26 VHVery high rate of activity

Please note that an ordered enumeration is described in ascending order of elements, but the order of elements is not meaningful for an unordered enumeration. See also the paragraph entitled Important: constraints regarding the enumeration type.

The Boolean data type represents a particular case of an ordered enumeration of two elements:

Table 3.18. Boolean Data Type layout

18Data TypeType Identifierboolean
19 Description 
20 Value LabelValue Description
21 OFFThe machine is switched off
22 ONThe machine is switched on

The Flagged data type is an extended enumeration of elements.

Table 3.19. Flagged Data Type layout

18Data TypeType Identifierflagged
19 Description 
20 OrderedFALSE
21 Value LabelValue Description
22 IThe migration is increasing
23 DThe migration is decreasing
24 NThe rate is impossible to calculate
25 Position 
26 1Characterizes the net migration
27 2Characterizes the internal migration
28 3Characterizes the international migration

Please note that the indices in the list of positions must begin from the smallest and increment to the largest one and each position must be described in the cell next to the index.

The Other data type is represented as follows:

Table 3.20. Other Data Type layout

18Data TypeType Identifierother
19 DescriptionThe value represents the name of an image file enclosed to the dataset.

The Description is mandatory for this data type.

3.4.4. Source Reference Element

All the Source Reference elements present in a dataset should be put in a single separate sheet of the spreadsheet. This should be done to facilitate the analyzis of the metadata.

The Source Reference element must use the following layout:

Table 3.21. Source Reference element layout

1Source Reference
4Copyright(c) ESPON 
5ProviderNameESPON 2013 Database Project
6 URIhttp://www.espon.eu
7PublicationTitleESPON Report on ...
8 URIhttp://www.espon.eu/reports/report111031.pdf
9 Referencepage 228
11 Formula 
12 URIhttp://espon.eu/reports/report111031_method.pdf
13Access Rulepublic 
15Quality Levelhigh 

Optional properties: URI, Reference and Methodology.

Multiple properties: Provider.