Same aggregate name
Two files name a region alike, but one excludes a unit. Compare membership before explaining change.
In-depth practical guides
Check codes, aggregate membership and territorial versions before joining files or comparing years.
Updated :
A label defines neither a boundary nor a population. M49 classifies statistical units; a map layer supplies geometry. Link classification, layer and indicator coverage explicitly.
Keep code as text, level and version. Retain leading zeros; do not equate M49, ISO and NUTS codes by appearance.
List members and exclusions for each aggregate. Changed membership can change a total while national series remain unchanged.
Check mergers, splits and boundaries during the period. A correspondence needs direction, validity and multiplicity; one old code can map to several new ones.
Check duplicates, unmatched units and level. Never add an aggregate and its members together; maps also need coordinate system and layer date.
Typical situations for preparing a check. They do not describe completed assignments or actual observations.
Two files name a region alike, but one excludes a unit. Compare membership before explaining change.
One old area becomes two. A code correspondence alone supplies no weights for allocating an amount.
It can join an appropriate layer, but supplies no coordinates or geometry. Check layer licence, vintage and level.
Area weights do not automatically suit population or amounts. Justify weights against the variable and available data.
TOOLS / REGISTERS
Check duplicates, unmatched units and level. Never add an aggregate and its members together; maps also need coordinate system and layer date.