4.1. Structure input

In the the input structure.xls Excel file, ten sheets must mandatory be provided in a unique .xls file.

Optionnally, complex contiguities must be defined as a set of seven sheets in an unique other xls file. Thus the input data may be composed of:

Table 4.1 provides the list of these sheets names and a short description for each of them, as they are expected in the structure input definition. The expected columns and an example for each of them is described below this table.
[Note]

The names of sheets is case-unsensitive. For example, the mandatory UnitArea.txt file can be named unitarea.txt or UNITAREA.txt. Suffixes and prefixes around the file basename are also possible while choosing the plain text option: thus, my_UnitArea.txt will be considered as a UnitArea.txt file, e.g. the input file that contains the information about the relationships between areas and territorial units.

Table 4.1. Overview of expected sheets for data structure input

Excel Sheet NameDescription
unitIdentifiers for the set of territorial units. See Content of unit.
AreaIdentifiers for the set of study areas. See Content of area.
ZoningIdentifiers for the set of meshes. See Content of zoning.
UnitSupHierarchy between units: an UTSup_ID parent unit owns at least one child UT_ID unit. See Content of unitsup.
UnitAreaAn UT belongs to one or several study areas. See Content of unitarea.
UnitZoningAn UT belongs to one or several meshes. See Content of unitzoning.
languageProvides a human readable name for used languages codes. See Content of language.
UnitLanguageNames of UT in different languages. A translation may be missing. See Content of unitlanguage.
AreaLanguageNames of the study areas in different languages. A translation may be missing. See Content of arealanguage.
ZoningLanguageNames of the meshes in different languages. A translation may be missing. See Content of zoninglanguage.

Expected content for each of these sheets is following:

Unit

This file/sheet must contain one column whose header cell must be UT_ID. Example:
Table 4.2. Sample input Unit sheet
UT_ID
AT11
AT12
AT13
AT21
etc...

Area

This file/sheet must contain one column whose header cell must be Area_ID. Example:
Table 4.3. Sample input Area sheet
Area_ID
UE15
UE25
PECO
Arc_Atlantique
Nouveaux_UE
UE27
UE29

Zoning

This file/sheet must contain one column whose header cell must be Zoning_ID. An additional column named Rank may order given zonings. Example:
Table 4.4. Sample input Zoning sheet
Zoning_IDRank
Nuts_01
Nuts_12
Nuts_23
Nuts_35
Nuts_2_34

UnitSup

This file/sheet must contain two columns whose header cells must be named UTSup_ID and UT_ID. Example:
Table 4.5. Sample input UnitSup sheet
UT_IDUTSup_ID
AT1AT
AT2AT
AT3AT
BE1BE
BE2BE

UnitArea

This file/sheet must contain two columns whose header cells must be named UT_ID and Area_ID. Example:
Table 4.6. Sample input UnitArea sheet
UT_IDArea_ID
ATUE15
BEUE15
DEUE15
DKUE15
ESUE15

UnitZoning

This file/sheet must contain two columns whose header cells must be UT_ID and Zoning_ID. Example:
Table 4.7. Sample input UnitZoning sheet
UT_IDZoning_ID
ATNuts_0
BENuts_0
BGNuts_0
CHNuts_0

Language

This file/sheet must contain two columns whose header cell are Language_ID and Language_NAME. Example:
Table 4.8. Sample input Language sheet
Language_IDLanguage_NAME
DEallemand
CStchèque
DAdanois
ETestonien
ENanglais
ESespagnol

UnitLanguage

This file/sheet must contain three columns whose header cells must be UT_ID, UT_NAME and Language_ID. Example:
Table 4.9. Sample input UnitLanguage sheet
UT_IDLanguage_IDUT_NAME
AT11DEBURGENLAND
AT34DEVORARLBERG
BE24NLVLAAMS BRABANT
BE25NLWEST-VLAANDEREN
BE31FRBRABANT WALLON
BE32FRHAINAUT

AreaLanguage

This file/sheet must contain three columns whose header cells must be Area_ID, Language_ID and Area_NAME. Example:
Table 4.10. Sample input AreaLanguage sheet
Area_IDLanguage_IDArea_NAME
UE15FRUnion européenne des 15
UE25FRUnion européenne des 25
PECO FRPays d'Europe Centrale et Orientale

ZoningLanguage

This file/sheet must contain three columns whose header cells must be zoning_ID, Language_ID and zoning_NAME. Example:
Table 4.11. Sample input ZoningLanguage sheet
Zoning_IDLanguage_IDZoning_NAME
Nuts_0FRNomenclature des unités territoriales de niveau 0
Nuts_1FRNomenclature des unités territoriales de niveau 1
Nuts_2FRNomenclature des unités territoriales de niveau 2
Nuts_3FRNomenclature des unités territoriales de niveau 3
Nuts_2_3FRNomenclature des unités territoriales de niveau 2-3