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 :

AI-generated illustration
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.
Reading workshop
DEMO territories do not exist. The exercise separates exact aggregation from allocation with unknown weights.
Fictional data and records for learning: none of these results comes from a live service query.
For the same period and count definition, A has 30 and B has 70. They are disjoint and C combines them exactly. A later classification splits B into B-North and B-South without detailed counts.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Fictional unit | Known value | Scope relation | Decision |
|---|---|---|---|
| Old unit A | 30 | Member of C, no overlap with B | May be included in A+B. |
| Old unit B | 70 | Other member of C | Same period and definition as A. |
| Aggregate C | 100 | Already includes A and B | Choose C alone or A+B; never A+B+C. |
| B-North and B-South | Allocation of 70 unknown | New boundaries split B | Request counts or a documented method; do not assume halves. |
Open each proposition to compare its diagnosis. More checks may still be needed.
No. 30+70+100 counts the same units twice. These levels are not disjoint.
Yes. A+B aggregation is documented, but transfer from B to the new units lacks appropriate weights.
No. Two new codes establish neither equal populations nor equal shares of the variable.
Classification: DEMO-old then DEMO-new Period and definition: identical for A, B and C A=30; B=70; C includes exactly A+B=100 Selected total: C alone, without its members added New boundaries: B-North and B-South Allocation: not calculated, weights unknown
The correspondence table establishes membership here, not transfer weights. Retain direction, validity and multiplicity of each link.
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.
Fictional example: A has 100 residents, then 130 after absorbing B, which had 30. The total rises 30%, but this example shows no growth within the original boundary. Reconstruct A+B for the starting year when data permits before interpreting the change.
Two illustrative areas have rates of 10% among 100 people and 20% among 900 people. Their combined rate is (10+180)/(100+900), or 19%, not the simple average of 15%. Denominators must describe the same population and period.
From observation to decision
In 2024, the published total covers A and B: 100 + 50 = 150 units. In 2025, B leaves the scope; only A remains, with 120 units. Comparing totals mixes changes in the phenomenon with changes in coverage.
Fictional learning case: counts and dates illustrate the method and do not describe a real assignment.
Common scale from 0 to 160 fictional units. The first two bars cover different areas.
| Observation | Useful check | Next action |
|---|---|---|
| Published totals: 150 then 120 | (120 − 150) / 150 = −20%. | Describe a fall in the published total without calling it a constant-scope change. |
| A alone: 100 then 120 | (120 − 100) / 100 = +20%. | Report the change for A, provided definitions and units remain the same. |
| B in 2025: value missing | The 2025 total for A + B cannot be reconstructed. | Do not assign zero to B; retain the missing status and seek compatible data. |
No. It identifies territories but does not automatically supply historical values. Mergers, splits or coverage changes may need detailed data. Check additivity before summing; rates cannot be reconstructed by adding rates.
Document reference: COG provides geographical vintages and histories. The territories and values in this case are fictional. Insee — Code officiel géographique
Worked exercise
Fictional example: the values and documents teach the method and do not describe a real organisation.
A and B are disjoint and share period and definition. C is exactly their union.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Area | Cases | People |
|---|---|---|
| A | 10 | 100 |
| B | 90 | 300 |
C has 100 cases among 400 people: 25%. The simple mean of 10% and 30% is 20%, giving equal weight to unequal populations. The boundary correspondence permits this aggregation; similar names would not.
If part of B remains outside C, obtain its counts. Area alone does not automatically provide population weights.
Keep the correspondence table, period, both counts and C calculation.
DOCUMENTED REFERENCE
M49 assigns three-digit numeric codes to countries or areas and geographic groupings. ISO letter codes appear alongside them but belong to another system. These are actual mappings from the consulted official table.
| Reference | Value or form | What it identifies |
|---|---|---|
| 001 | World | World: the global aggregate. |
| 150 | Europe | Europe: an M49 geographic region, different from the European Union. |
| 155 | Western Europe | Western Europe: the M49 subregion containing France. |
| 250 | FRA / FR | France: M49 250, ISO three- and two-letter codes FRA and FR. |
| 004 | AFG / AF | Afghanistan: the leading zero is part of the M49 code; preserve it in joins. |
Keep geographic level, the code as text and classification version. World → Europe → Western Europe → France describes nested sets, not four territories to add. For older periods, check territorial and code changes before applying today’s classification.
Check the system and level as well. M49 code 150 means the Europe region; an internal code with the same number may mean something else. Name columns explicitly, such as m49_code and geographic_level, and inspect unmatched values before aggregation.
Documentation consulted on .
DOCUMENTED REFERENCE
These codes and levels were checked in the GISCO NUTS 2024 file properties on 22 October 2026. They are statistical units; no population figure is attached here. GISCO’s LEVL_CODE includes the country at level 0.
| Reference | Value or form | What it identifies |
|---|---|---|
| NUTS 2024 | 2024-01-01 | The classification applies from January 2024. NUTS 2027 is announced for 1 January 2027; do not treat the future version as that of a 2024 series. |
| FR | 0 | France: country, level 0 in this file. NUTS then organises three regional levels, 1, 2 and 3. |
| FR1 | 1 | Île-de-France at NUTS 1. Keep the code as text, even though it combines letters and digits. |
| FR10 | 2 | Île-de-France at NUTS 2. Sharing a name with FR1 does not make these records interchangeable in a level-specific join. |
| FR101 | 3 | Paris at NUTS 3. Do not assign it a value published for the whole FR10 area; retain each observation’s territorial unit. |
Keep code, level and territorial version alongside the indicator period. The file uses generalized 1:60 million geometry, suitable for this classification check, not parcel boundaries or address analysis.
Not necessarily. Check code, level, territorial edition and actual boundaries. Boundary changes may require a correspondence table without permitting values to be copied between units.
Documentation consulted on .
DOCUMENTED REFERENCE
Official GeographicLib examples provide reproducible inputs and outputs on WGS 84. These documented calculations do not route or geocode your addresses.
| Reference | Value or form | What it identifies |
|---|---|---|
| WGS 84 · a | 6 378 137.0 m | Ellipsoid semi-major axis in metres, not point accuracy or a universal degree length. |
| WGS 84 · 1/f | 298.257223563 | Inverse flattening defines the model with a; a sphere differs. |
| Wellington → Salamanca | Inverse(-41.32, 174.81, 40.96, -5.50) | Inverse takes starting latitude, longitude then ending latitude, longitude, unlike GeoJSON. City coordinates have two decimals. |
| s12 | 19 959 679.267 m | Ellipsoidal geodesic distance displayed to a millimetre does not make rounded input positions millimetre-accurate. |
| Perth · Direct | (-32.06, 115.74, 225°, 20 000 000 m) | Direct starts near Perth at initial azimuth 225° for 20000 km. Azimuth need not remain constant. |
| Direct · latitude | 32.11195529° | Positive arrival latitude is north; do not copy the departure sign. |
| Direct · longitude | −63.95925278° | Negative arrival longitude is west. Retain order, units and model. |
This is not travel time, road access or terrain-following distance. Euclidean degrees and Web Mercator length are different calculations. Preserve inputs and method; assess positional uncertainty separately.
They express numeric output for rounded inputs, not a unique official point or real-world positioning uncertainty.
Documentation consulted on .
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.
Eurostat lists NUTS 2024 for data transmission in 2024–2026 and NUTS 2027 from 2027. Also inspect series metadata: a backcast series may use a common geography for earlier years. The observation year alone does not determine its geography.
This depends on the indicator and the available data. Total and ratio are not always gathered in the same way; the rule must preserve the meaning of the numerator and the denominator.
TOOLS / REGISTERS
Check duplicates, unmatched units and level. Never add an aggregate and its members together; maps also need coordinate system and layer date.
Proposed exercise: this protocol is not a performed service test.
Record filters, then read the final document’s geographical and temporal scope.
Separate search region from described population; a localised result does not make a rule applicable to that country.
DOCUMENTED REFERENCE
Four countries and one observation year: this table preserves the 2023 WDI values retrieved on 23 October 2026. It supports checking a division before comparing territories. Population figures are midyear estimates, not counts taken on the retrieval date.

Lake Saimaa around Varpasalo island, Finland: a shipping lane crosses the ice between islands. Landsat 8 OLI image acquired on 8 April 2024.
Real satellite image · Michala Garrison / NASA Earth Observatory · USGS Landsat · Source · Reuse
Image by Michala Garrison, NASA Earth Observatory, using USGS Landsat data. Resized and converted to WebP without cropping. Illustrates inland waters; no area measurement or NASA endorsement of this site.
| Reference | Value or form | What it identifies |
|---|---|---|
| SP.POP.TOTL | P | Population is the numerator. Its definition and coverage must match the area used. |
| AG.LND.TOTL.K2 | L | Land area excludes inland waters and is expressed in km². |
| AG.SRF.TOTL.K2 | S | Surface area includes inland waters and some coastal waterways. It cannot automatically replace land area. |
| EN.POP.DNST | P / L | Published density uses land area. The reader below repeats the division using values from the same snapshot. |
| Country / ISO3 | Population · people | Land · km² | Surface area · km² | Published density · people/km² of land |
|---|---|---|---|---|
| France · FRA | 68372286 | 538950 | 606410 | 126.862020595603 |
| Germany · DEU | 83287273 | 349430 | 357680 | 238.351810090719 |
| Spain · ESP | 48352528 | 499697.4 | 505975.98 | 96.7636173412149 |
| Finland · FIN | 5583911 | 303960 | 338480 | 18.3705454665088 |
Finland · 2023 · Check the definition before interpreting the result.
Local calculation from the 2023 snapshot. Results rounded to six decimals; chart rounded to two decimals.
Source update : · Retrieved :
Data: World Bank, WDI; upstream sources: FAO, UN, national statistical offices and Eurostat depending on the indicator. CC BY 4.0. Values preserved; table, chart and calculations added here.
A national average describes neither where people live nor neighbourhood density. Do not derive water area by subtracting two series until their territorial coverage, conventions and revisions have been checked. The alternative ratio using surface area is a sensitivity demonstration, not a new official indicator.
Documentation consulted on .
DOCUMENTED REFERENCE
Changing an area unit does not change the territory measured. A kilometre is one thousand metres, so a square kilometre contains one thousand times one thousand square metres. The table and converter make that square explicit.
| Reference | Value or form | What it identifies |
|---|---|---|
| 1 km² | 1 000 000 m² | The factor 1,000 applies to each length: multiply km² by 1,000,000 to obtain m². |
| 1 ha | 10 000 m² | A hectare, symbol ha, is exactly the area of a square with 100 m sides. |
| 1 km² | 100 ha | One square kilometre contains exactly 100 hectares. |
| 2.5 ha | 25 000 m² = 0.025 km² | Arithmetic example: 2.5 ha equals 25,000 m² and 0.025 km². No real parcel is represented. |
Enter a non-negative number, up to 40 characters. Decimal point or comma; no thousands separator or exponent. Results preserve the entered decimals without binary rounding.
Exact unit conversion.
Conversion factors are exact but do not improve the precision of the original measurement. Unit conversion does not calculate polygon area, correct a projection or validate a cadastral boundary.
Documentation consulted on .
DEEPER READING / PRACTICE
Two series describe territories whose contours or categories have changed. The comparison must specify the geography used and the validity period of the codes.
Updated on .
Name, code, geographical level and millesime. Examine contour changes and correspondence tables before grouping or approaching values.
An identical name can indicate a different scope depending on the date. An aggregation of territories does not automatically retain the meaning of a ratio.
The correspondence table documents initial territories, rule of approximation and loss of information. Non-comparable cases are kept separately.