cities.type fieldEvery city record carries an optional type field describing what kind of
place it is. This page explains where the values come from, what each one
means, and how to filter the dataset down to genuine settlements.
Why this exists:
typeis inherited from the upstream GeoNames feature classification. It mixes two different ideas — what a place is (city,town,village) and what administrative role it fills (adm2,county,parish). The same place can be tagged either way depending on whether it is also the seat of an administrative division. For example, Dallas isadm2because it is the seat of Dallas County, and major Australian cities areadm1because they are seats of state-level governments. Cleanup of this inconsistency is tracked in #1303.
Countries are being moved, one at a time, to their official administrative categories
(ADMINISTRATIVE_STRUCTURE.md): city type becomes a standard English term
(municipality, city, town, village, locality, section), a new type_local field keeps the official local
term (commune, Gemeinde, municipio), and units between the state and the municipality (arrondissements, Kreise,
counties) move to the separate contributions/counties/ dataset. Until a country is moved, its records keep the
values below.
There are 35 distinct values across 156,025 city rows. Counts are a snapshot (2026-05-24) and drift as the data evolves — treat them as approximate.
type |
Count | Settlement? | Meaning |
|---|---|---|---|
city |
96,098 | ✅ | Actual settlements |
adm2 |
20,796 | ✅ | 2nd-order admin division — usually a real city that is also a county/district seat (e.g. Dallas) |
adm3 |
15,774 | ✅ | Mostly real municipalities/communes (small towns) tagged with their admin role |
section |
5,346 | ✅ | Suburbs and districts of larger cities |
county |
4,409 | ❌ | County-level admin unit — not a settlement |
adm4 |
3,909 | ✅ | Similar mix to adm3 |
adm1 |
3,505 | ✅ | 1st-order admin division — usually a state/region seat (e.g. major AU cities) |
district |
2,381 | ✅ | District-level populated place |
| (null) | 1,900 | ⚠️ | No type assigned — see Records with no type |
regency |
390 | ❌ | Indonesian kabupaten — admin division |
prefecture |
369 | ❌ | Prefecture-level admin division |
locality |
319 | ✅ | Named populated place |
capital |
281 | ✅ | National/regional capital |
municipality |
209 | ⚠️ | Municipality; US territorial units are excluded below, as are the other country exceptions |
parish |
80 | ❌ | Louisiana-style parish (= county) |
banner |
52 | ❌ | Inner Mongolia banner — admin division |
town |
48 | ✅ | Town |
province |
36 | ❌ | Province-level admin division |
adm5 |
16 | ✅ | 5th-order admin division (populated) |
abandoned |
15 | ❌ | Abandoned place — not a live settlement |
cities |
13 | ✅ | Data artifact of city |
area |
12 | ❌ | Generic administrative area |
village |
10 | ✅ | Village |
historical |
9 | ❌ | Historical place — not a live settlement |
settlement |
9 | ✅ | Settlement |
oblast |
8 | ❌ | Oblast — admin division |
gov_seat |
6 | ✅ | Government seat (populated) |
special municipality |
6 | ✅ | Special municipality |
administrative zone |
5 | ❌ | Administrative zone |
region |
4 | ❌ | Region-level admin division |
destroyed |
3 | ❌ | Destroyed place — not a live settlement |
township |
3 | ✅ | Township |
religious |
2 | ❌ | Religious site — not a settlement |
subdistrict |
1 | ✅ | Subdistrict (populated) |
historical_capital |
1 | ❌ | Former capital — not a live settlement |
Destatis GV-ISys Textkennzeichen describes the municipality’s official legal class:
60 → municipality / Markt, 61 → city / kreisfreie Stadt, 62 → city / Stadtkreis,
63 → city / Stadt, 64 → municipality / Gemeinde, 67 → city / große Kreisstadt.
The class follows the Land’s municipal law as recorded in the federal register, not a population threshold.
The 30 September 2026 edition and its GV100AD record description are the source of these codes.
Land is level 1; a current Regierungsbezirk adds a tier, as does a Kreis; an independent city skips the Kreis tier.
Gemeindeverbände are cooperative administrative bodies, not an extra territorial tier for these municipality rows.
A missing Kreis link is not filled by this classification patch. Sections and former municipalities cannot borrow a successor’s class.
Sources: Destatis GV-ISys,
Data licence Germany – attribution – version 2.0 (dl-de/by-2-0).
Statistics Canada’s census subdivision (CSD) type records the municipal designation adopted by provincial or territorial law;
it also includes statistical equivalents that must not be inferred to be legal municipalities.
For independently bound legal CSDs: CY/C → city / city, T/TV → town / town, VL → village / village,
V → city / ville, MÉ → municipality / municipalité, MU/M → municipality / municipality,
TP → municipality / township, CT → municipality / canton, P → municipality / paroisse,
DM → municipality / district municipality, RM → municipality / rural municipality,
MD → municipality / municipal district, HAM → locality / hamlet, SV → village / summer village,
SM → municipality / specialized municipality.
Unlisted classes, nonmunicipal statistical CSDs and ambiguous former municipalities remain held.
Province/territory is level 1; existing documented level 2 or 3 is retained, otherwise the province/CD/CSD hierarchy gives level 3.
A CSD and its same-named population centre are distinct entities; a CSD total or class is never assigned to the latter.
Sources: 2021 Census Dictionary, CSD,
2021 boundary attributes and 2025 CSD register, under the Statistics Canada Open Licence.
In AU.json, an LGA row is the local-government territory: municipality at level 2,
with its jurisdiction-published status in type_local (for example City, Shire, Council,
Regional Council, Aboriginal Shire or Municipality). City status on an LGA does not make
it the separate town of that name. Bind a namesake row using its own Wikidata item,
official ABS LGA code/name/state and the unchanged point inside its LGA boundary.
A gazetted populated place is locality at level 3, with its gazetteer class in
type_local, only when name, state, point and its own place item agree.
The reviewed AU type ledger and
shared source catalogue retain
exact edition, retrieval date, source hash and attribution. Conflicting identity,
former-unit statements or an out-of-boundary point remain held; no coordinate, name,
identifier, parent or table change is authorized by this type correction.
Localidades at level 3 link by parent_id to their own level-2 municipio or Mexico City alcaldía city row; an official cabecera point may represent a municipio only when it lies inside that municipio, and its population is the municipio total.
In MX.json, adm1 is a state-capital town, adm2 a municipal-seat town (GeoNames PPLA2) and
municipality the municipal territory itself (GeoNames ADM2), so a municipality and its seat town can both
appear (e.g. Medellín and Medellín de Bravo). To list only settlements in Mexico, leave out municipality.
For reviewed rows, INEGI catalogue AMBITO U/R maps to locality / localidad urbana or locality / localidad rural at level 3; cabecera is a seat role and does not itself establish urban class. A legacy place-typed row is corrected to municipality / municipio at level 2 only when its literal v4 own item is the municipio (own P3801 and municipality class), the official code/name/state and current municipal polygon agree, and the unchanged point lies inside that territory. An item naming the seat cannot take its municipality’s class.
In PL.json, municipality is a gmina (gmina wiejska or gmina miejsko-wiejska), the council area at level 3,
not a town. An urban-rural gmina and its town can share a name (Krobia, Nowogrodziec), and the gmina’s population
includes the town’s, so do not add the two. An urban gmina (gmina miejska) is the town itself and is typed city.
Villages (village / wieś) and towns (city / miasto) are level 4, linked by parent_id to their gmina where
the gmina has a reviewed row (474 are not yet linked). This describes reviewed rows. The 88 legacy adm3 and 4 adm2 rows are not yet
reviewed: some are towns, such as Bielsko-Biała (85861) and Jastrzębie-Zdrój (86528), and others carry a gmina’s
Wikidata item, so keep them in a settlement list. Many gminy have no separate row for their seat yet, so leaving out
municipality would drop that place too. The settlement filter below keeps Polish rows until v7 reviews them, so its
results include gminy.
In CU.json, a reviewed municipio is a city-table row municipality / municipio at level 2,
directly under its province (state, level 1), with parent_id: null. Its seat town is a separate entity.
Reviewed towns retain their types, use level 3, and link by parent_id only when their own item’s
P131 or an official source names the municipio and their unchanged point lies within it.
To list only settlements in Cuba, leave out municipality. Isla de la Juventud is the state CU-99;
there is no duplicate municipio row in cities. Existing names, IDs and points are preserved, including
the 33 names beginning “Municipio de” and San Germán (the Urbano Noris municipio row).
Unknown item scopes, unavailable or conflicting points and the Guantánamo Bay naval base area remain held.
The compact ledger and its sources sidecar record
each changed row, archived evidence, point checks and held cases. New names use the standard Spanish
form with diacritics (the municipio’s own Wikidata Spanish label where it is the same name), not ONEI’s table
typography; Wikidata CC0 supplies their own-item points. geoBoundaries/OSM ODbL geometry is
checking evidence only. No ONEI population is imported.
In GR.json, municipality is a municipal territory (e.g. Lake Plastiras, Pangaio), not a town, and Mount
Athos’s monasteries are religious. To list only settlements in Greece, leave out municipality.
In NL.json, municipality is a gemeente. A BAG woonplaats (a named place within a gemeente) is city when an official
source names that place itself as a city (the Rijksdienst voor het Cultureel Erfgoed’s historic-city inventory or the
municipality’s own publication, with no current municipal text calling it a village; see the
evidence ledger), and locality otherwise; both keep
type_local woonplaats. This is a documented identity, not a legal status, as the Netherlands has no statutory city
category today. Older city records outside the woonplaats set (Eindhoven, Delft) were not reviewed, so type = 'city'
alone is not a complete list of Dutch cities; use the settlement filter below. Most
gemeente records are also the place itself (Haarlem, Hilversum) and belong in a settlement list. Records named
“Gemeente …” (Gemeente Groningen, Gemeente Smallingerland …) are the municipal territory beside separate records for
its places: a town of the same name (Groningen) or places with other names (Drachten, in Smallingerland). To list
only settlements in the Netherlands, leave out the records whose name starts with “Gemeente “.
In NZ.json, settlements have no legal status. type_local keeps Stats NZ’s 2026 urban-rural class and type follows
it: a major or large urban area is city, a medium or small urban area is town, a rural settlement is locality and a
suburb is section. A place the New Zealand Geographic Board lists as an official town (LINZ NZ Place Names, feature
type Town) or that its council names as a town is at least town, whatever its size class (Fairlie, Waiouru). The
classes are statistical sizes, not city status. District and city councils are county records (#2006).
In ZA.json, places have no legal town or city status. A place matched to a Statistics South Africa Census 2011 main
place is locality with type_local main place: a statistical class, not a legal status or a population threshold.
Local municipalities stored as cities are municipality / local municipality at level 3. Metropolitan and district
municipalities are county records; rows for them in ZA.json are typed county and wait for removal in v5.0.0.
In KZ.json, the category is the one in the KATO classifier: city / қала, town / кент, village / ауыл. Cities
of republican significance are at level 1, of regional significance at 2 and of district significance at 3. A town or
village is at 3, or at 4 when it lies in a rural okrug; a “conditional” city or village administration in KATO is not
a unit and adds no level. Districts (аудан) are county records; rows for districts in KZ.json are typed county, and
their removal is queued for a major release. Where a district row and a county record share the district’s own
Wikidata item, they are the same entity. county_id is the containing district, so a village in a rural okrug (level 4) links to
its district (level 2); parent_id is the record directly above, and is empty when that tier has no record.
In TZ.json, a record that is itself a city, municipal or town council is municipality at level 2 with the
council’s Swahili category (Halmashauri ya Jiji, Halmashauri ya Manispaa, Halmashauri ya Mji). A record of the
town or city a council is named after is not the council: it keeps its own identity and is not typed until a register
of settlements binds it. Levels follow the census hierarchy: region 1, district or council
2, division 3, ward (section / kata) 4. Rows for districts are typed county / wilaya at level 2, and their removal is
queued for a major release; Tanzania has no county records yet.
For reviewed US places, type follows the Census Bureau’s official legal/statistical
area description (LSAD), rather than population size or county-seat status:
LSAD 25 is city / city, 43 town / town, 47 village / village, and
21 borough / borough. A census-designated place (LSAD 57, FUNCSTAT S) is
locality / census designated place, including large CDPs. Puerto Rico’s
statistical places have LSAD 55 (comunidad) or 62 (zona urbana); all Puerto Rico
rows remain held here because municipio versus town identity is not proved.
Under contract 6, reviewed US territorial units use municipality, with their legal
category in type_local: town, township, charter township or plantation.
A territorial town is not its seat or its contained village/CDP. The 776 New York
territorial towns added in #2170 (never published under contract 5) are therefore
municipality / town; all 6,298 territories added by that PR are municipality.
Their contained places keep separate rows and their own place categories. Reviewed
incorporated places (including a city, borough or village coextensive with an MCD)
keep their place category; a county-subdivision code alone does not authorize retyping
a settlement. These reviewed units are level 3 under the state/county framework.
GNIS populated-place names alone do not establish legal incorporation or authorize
a containing town’s population.
Upgrade the settlement filter: also exclude US municipality rows, including
municipality / town. A unit’s population includes its contained settlements; do
not add the unit and place totals together. This rule changes in v6.0.0. The
review ledger binds each retyped NY row to #2170’s
creation record, Census county subdivision and unchanged full row.
Released-row exception: 1,478 older rows with reviewed territorial-town
bindings still retain their published town / town classification in this bounded
release. They are inventoried by id in the adjacent sources registry
and await v7 review; this patch does not retype them. Consequently, the filter below
still returns those legacy territories. One released incorporated place, Bethel Park,
PA (112287, Census LSAD 37), is typed municipality for its Pennsylvania legal class, so
the US exclusion leaves it out; retyping a released row waits for v7. It is a documented
starting filter, not a verified complete list of US settlements. Never exclude every town / town row:
incorporated place towns use that pair too; use reviewed entity identities for any
stricter application-specific selection.
A village or CDP inside a same-named town is a separate entity. Each binding must agree with its row’s own Wikidata GNIS (P590), FIPS (P774), or explicit instance class (P31), without a conflicting identifier. Rows without an item cannot bind a county subdivision with a nearby same-named place or CDP. Ambiguous matches, duplicate keys on one Census entity, special consolidated governments and unproved legacy identities stay held; this convention does not assert that every existing US row is reviewed. Population 2020 is the count of the bound entity itself. A missing county link is filled only when the whole entity belongs to one county. See the 2024 Gazetteer LSAD and FUNCSTAT fields, Census LSAD definitions and the per-record evidence ledger.
Reviewed rows bind a 2020 Census place only through their own P774 equal to its GEOID, their own P590 equal to its ANSI code, or an own P31 incorporated-place or CDP class with one same-name, same-kind place in the same state; every route requires strict stored-point containment. Any conflicting own P774 or explicit township or other county-subdivision P31 blocks a place binding, including township-only items and mixed township/place classes. LSAD 25/43/47/21/57 supplies the existing place classification at level 3, and every accepted place binding with no population year of 2010 or later receives that place’s 2020 P1 total and population_year 2020. Class-bound rows additionally require every own P590 to equal the ANSI code or identify a GNIS feature strictly inside the polygon. Retained own-item neighborhoods and unincorporated communities keep their proved classifications. Additional nonhistorical own GNIS Populated Place bindings use locality / unincorporated community / 3 outside incorporated places or section / neighborhood inside one independently proved incorporated parent, with parent_id empty or already that parent and level equal to parent level + 1. Historical names, former CDPs without a 2020 CDP, Puerto Rico and ambiguous bindings remain held in the combined US type ledger.
The US item and former-CDP ledger applies the preceding binding veto to both current and proposed own items before correcting or supplying an item through a same-name, same-state 2020 Census place with strict stored-point containment and an exact own P774 GEOID or P590 ANSI code, or through an own P590 for the unique same-name GNIS Populated Place within 1 km with no other within 5 km, uses the preceding classification and population rules for accepted Census bindings, and permits the formerly held former-CDP rows as locality / unincorporated community / 3 only with a nonhistorical own GNIS Populated Place, no own item P774 or P590 matching any 2020 Census place or county subdivision, no same-name 2020 place in the state and a point outside every 2020 incorporated place and CDP; Items already owned by another CSC row and county or independent-city duplicate records remain unchanged for v7; Puerto Rico, abandoned missing-item rows, conflicting identifiers, township or county-subdivision classes and ambiguous bindings remain held.
In UY.json, a centro poblado’s legal category maps to city / ciudad, town / villa or
village / pueblo; the existing town / pueblo spelling of the English category is corrected only
on independently bound rows. A census locality without an established finer legal category is
locality / localidad. These are categories, never population thresholds. The open INE
Toponimia y categorización jurídica oficial de las localidades register is historical (2004,
georeferenced 2025), so it alone does not establish a place’s current legal status. Legislative
category acts, for example Law 12,297 (25 de Agosto),
provide the legal basis for these terms. The evidence ledger
keeps each applied category and any field held for further legal review.
A municipality / municipio denotes the territorial local-government unit established under
Law 19,272, at level 2 beneath the departamento
(level 1). Its seat locality is a different entity; locality census counts are never municipal counts.
A locality wholly within one municipio has level 3; a locality outside the municipal layer has
level 2. Partial overlaps and localities crossing municipios have their level held for review.
The documented Montevideo urban-containment model keeps the city at level 2 and its official
section / barrio records at level 3, with Montevideo as their city parent. Barrios are not
independent census localities and do not receive Montevideo’s total population.
parent_id should identify the verified immediate same-dataset parent, or be null when that
parent has no record. This patch makes no ancestry changes; containment alone is not a reviewed parent link. Legacy adm1 rows remain held where their unit/place identity
cannot be reconciled under the published model; no unit is relabelled as its seat.
Population uses INE’s POB_TOT_23: persons enumerated by the census operation or administrative
enumeration, excluding people experiencing street homelessness. It is not the departamento total.
INE permits free reuse with source attribution in the dataset’s embedded metadata; the ledger
retains that notice, the Uruguay Open Data Licence reference, edition, retrieval time and checksums.
For independently bound Ukrainian rows, the Ministry’s KATOTTH codifier
(7 July 2026, Order 1321; original Order 290 of 26 November 2020,
category appendix in the edition of Order 48 of 19 January 2024) maps
M (М) to city / місто, X (Х) to town / селище, and C (С) to
village / село. The codifier uses Latin category letters. X is the current
settlement category, including former urban-type settlements; an old urban-type
label alone does not establish today’s category.
Ordinary settlements are level 4: oblast 1, raion 2, hromada 3, settlement 4.
K is city / місто, що має спеціальний статус at level 1 (Kyiv or Sevastopol).
B, район у місті, maps to section / район у місті; a district directly
under a special-status city is level 2. P, район, belongs in counties at level 2;
H, територіальна громада, is the basic municipality at level 3; O denotes
an oblast or the Autonomous Republic of Crimea at level 1 in states.
These unit categories never authorize replacing a unit with its seat.
Legacy or reformed units whose v4 scope is unproved remain held in this regular release.
Only type, local type and level change; the territorial policy and stored membership stay in force.
The compact ledger records applied bindings and official-bound holds.
Sources: Ministry codifier and category appendix,
CC BY 4.0. Wikidata’s KATOTTH property is P9435, and KOATUU is P1077.
Reviewed concelhos use municipality / município at level 2; current freguesias
use section / freguesia at level 3, beneath the district or autonomous region
(level 1) and municipality (level 2). A freguesia is a territorial unit with its
own government, not automatically its same-named settlement.
Legal cidades use city / cidade and vilas town / vila, at level 3 under
PT.json’s existing place convention; lugares use locality / lugar at level 4.
Legal place status does not establish that the place is a civil parish.
A cidade or vila requires its dated elevation law; population and administrative-seat
status do not determine the category. Santa Catarina da Serra is a vila under
Lei n.º 65/2001, de 12 de julho.
A municipality and its seat can share a name: the row’s own Wikidata item,
own P6324 (DICOFRE) code, official CAOP name/district and containing boundary
decide its identity. A former parish cannot borrow a current successor’s class.
Conflicting codes, ambiguous identities, and unproved literal v4 continuity remain held.
Only type, local type and level change; existing ancestry and membership are retained.
The compact ledger records changed rows
and holds with an official binding; its adjacent sources registry records revisions,
editions, licence notices, retrieval dates and exact response hashes.
Source: DGT CAOP2025,
licence CC-BY 4.0. DGT’s exact licence statement is preserved in the sources registry:
reuse is free, with attribution to Direção-Geral do Território. Island containment uses
Esri Portugal’s CAOP2025 mirror under CC-BY-4.0; no geometry or points are copied into rows.
In MA.json, a reviewed commune is municipality / جماعة, bound by its own HCP RGPH 2024 legal register code
(Wikidata P11958). The commune is the territorial unit, not its seat village or town, which can share its name.
The urban or rural subtype is set only where the register proves it. Levels, points and ancestry are unchanged.
These rows were adm3 before, and the settlement filter below returns them as it did then; Morocco has no
documented exclusion.
In RS.json, a reviewed opština is municipality / opština, bound by its own RZS register code (Wikidata P3727).
The municipality is the territory, not its seat: the census lists Lapovo municipality, Lapovo varošica and Lapovo
selo separately. A row whose v4.0 identity is unresolved changes only with a reviewed classification event.
The settlement filter returns these rows as it did when they were adm3; Serbia has no documented exclusion.
In TW.json, an ordinary district (區) of a special municipality or provincial city is section / 區 at level 2,
under its level-1 municipality, bound by its own MOI township code. Mountain indigenous districts, which have their
own councils, are not covered by this rule. #1935 typed the first 163 city districts this way. The settlement filter
includes both district and section, so its result is unchanged.
A Scottish NRS locality (own S19 code) sits at level 3: Scotland (level 1), council area (level 2), locality (level 3). Historic parishes are not a current tier, so they do not add a level. Only the level changes; type and links are kept, and village status is not inferred from the locality code.
For use cases like “find the nearest city, town, or village to a location”, exclude the admin-only and non-place types. An exclusion list is more robust than an include list, because any new settlement-style value added in future is kept by default.
Exclude these types:
county, regency, prefecture, parish, banner, province, area, oblast,
administrative zone, region, abandoned, historical, destroyed, religious,
historical_capital
In Cuba, Mexico, Greece and the United States, also exclude municipality (the municipal territory; see Cuba, Mexico, Greece, United States).
Romanian comune and Polish gminy stay in until v7 reviews their seats, because many seats have no row of their own yet; see Romania and Poland.
US legacy territorial towns retained as town, and Bethel Park, PA (112287), are explicit limitations; see the US section.
In Vietnam, also exclude municipality: since the July 2025 reform it is a commune, ward or special zone (xã, phường,
đặc khu) directly under the province, a territory formed from several old units; former cities and towns stay as
city / đô thị loại II and town / đô thị loại III urban places (#1977).
In the Netherlands, exclude the records named “Gemeente …” (see Netherlands).
SELECT *
FROM cities
WHERE (
type IS NULL -- keep null-type rows (see "Records with no type")
OR type NOT IN (
'county', 'regency', 'prefecture', 'parish', 'banner', 'province',
'area', 'oblast', 'administrative zone', 'region',
'abandoned', 'historical', 'destroyed', 'religious', 'historical_capital'
)
)
AND (country_code NOT IN ('CU', 'MX', 'GR', 'VN', 'US') OR type IS NULL OR type <> 'municipality') -- CU/MX/GR/VN/US municipality = territory
AND NOT (country_code = 'NL' AND name LIKE 'Gemeente %') -- NL municipal territory beside its town
AND latitude IS NOT NULL
AND longitude IS NOT NULL;
Note on
NULL:type NOT IN (...)evaluates toUNKNOWN(notTRUE) for rows wheretypeisNULL, so it would silently drop them. The explicittype IS NULL OR ...keeps null-type rows, matching the JavaScript filter below. Drop thetype IS NULLclause if you’d rather exclude them.
const EXCLUDED_TYPES = new Set([
'county', 'regency', 'prefecture', 'parish', 'banner', 'province',
'area', 'oblast', 'administrative zone', 'region',
'abandoned', 'historical', 'destroyed', 'religious', 'historical_capital',
]);
const settlements = cities.filter(
(c) => !EXCLUDED_TYPES.has(c.type)
&& !(['CU', 'MX', 'GR', 'VN', 'US'].includes(c.country_code) && c.type === 'municipality') // CU/MX/GR/VN/US municipality = territory
&& !(c.country_code === 'NL' && c.name.startsWith('Gemeente ')) // NL municipal territory beside its town
&& c.latitude != null && c.longitude != null
);
This keeps all city/adm*/town/village/section/locality-style rows
(including admin seats like Dallas and Sydney) while dropping pure
administrative units and defunct places under the exclusions above. US legacy
territorial towns still typed town, Romanian comune and Polish gminy remain included; the filter cannot establish
settlement identity for unreviewed rows.
About 1,900 rows have a null type. They are a mix of legitimate places
and unclassified entries. For strict settlement queries, the safest signal is
the presence of valid coordinates (latitude/longitude not null), and —
where available — a non-null population.
type_local, level, parent_id, the counties dataset)CN city level follows depth in the official hierarchy: prefecture 2, county-level unit 3, township 4.
County-level units directly under a province-level municipality or a province are 2 (for example the districts and counties of Beijing, Tianjin, Shanghai and Chongqing, and Hainan’s directly administered county-level cities and counties); their townships are 3, as are townships directly under no-county prefectures such as Dongguan and Zhongshan.
Unproved tiers, own-item/type conflicts and excluded territories remain held in the per-record ledger.
Where any row of a linked prefecture group was not proved, the whole group keeps its older levels (prefecture 1, county-level 2) for now, so no parent link skips or repeats a level; 55 of the 335 prefecture rows are in such groups, including Jiayuguan, whose three districts were abolished in 2019, and Jiangmen, Dongguan and Zhongshan in Guangdong.
A UAT (unitate administrativ-teritorială) is a level 2 city-table row under its județ: a comună has type municipality and type_local comună, an oraș has type town and type_local oraș, and a municipiu has type city and type_local municipiu. Its parent_id is null. Villages (village, sat) and localities (locality) are level 3 and link to their UAT by parent_id. A seat village and its same-named commune are distinct entities, and the commune’s population includes its villages’, so do not add the two. Some seat villages have no row of their own yet, so leaving out municipality would drop that place too; the settlement filter keeps comune until v7 reviews their seats.
France uses Insee’s Code officiel géographique (COG 2026) for the current legal unit and its own code:
| Unit | type |
type_local |
level |
|---|---|---|---|
| Commune | municipality |
commune |
4 |
| Commune déléguée | section |
commune déléguée |
5 |
| Commune associée | section |
commune associée |
5 |
| Arrondissement municipal | section |
arrondissement municipal |
5 |
| Quartier | section |
quartier |
Parent’s level + 1 |
| Inhabited named place | locality |
lieu-dit habité |
Parent’s level + 1 |
Communes in overseas collectivities without departments and arrondissements, such as Nouméa in New Caledonia, stay unclassified until an overseas level model is documented.
A commune déléguée or associée links by parent_id to its COG COMPARENT commune where that commune has an independently proved CSC row. An unresolved parent remains null. A former commune keeps its own identity and population; a code reused by a successor does not transfer the successor’s class or population.
IGN BD TOPO v3 zone_d_habitation supplies populated-place designations for places without their own government: Lieu-dit habité maps to locality / lieu-dit habité, and Quartier to section / quartier. Other natures stay unresolved. A match requires the same name after case, accent, hyphen, apostrophe and leading-article normalization, the stored point within 1 km of the feature, and no other same-name feature within 5 km. Its insee_commune must bind a CSC municipality / commune / 4 by that row’s own Wikidata P374 or exact COG LIBELLE in the same department. The place links to that row and is one level below it (level 5 under a commune). Missing communes may be added only after independent current COG identity, own Wikidata code, open point containment, population scope and duplicate checks; ambiguous identities remain held.
Sources: Insee COG, IGN BD TOPO (Licence Ouverte / Open Licence 2.0), and literal own-item Wikidata claims and labels (CC0). The France ledger records changed and held rows. French communes remain included by the settlement filter above.
BR rows carry municipality / município / 2, section / distrito / 3,
section / bairro / 4, and locality / vila, povoado or outras localidades at level 4.
The estado is level 1. A município has a null city parent_id; its state is recorded separately.
These classes require evidence for the place itself, rather than a population threshold or a generic settlement class.
For the Brazil ledger, a city row is bound to the município only through
a unique current IBGE name or live-item alias in the same estado, no existing CSC owner, its unchanged point strictly
inside the original municipal polygon, and a live município item’s own P1585 (IBGE code).
A seat item’s identifier is corrected to that município item as the same-place scalar correction; row ID,
population, coordinates and state remain unchanged. This rule is specific to this reviewed Brazil cohort.
Brasília/DF and Fernando de Noronha are municipal equivalents rather than municípios and remain held;
ambiguous names, points outside the named município and unsupported locality classes also remain held.
Sources: IBGE DTB 2025,
IBGE Malha Municipal 2025,
under the CC BY 4.0 compatible boundary licence stated in the technical note, printed page 9,
and Wikidata structured facts (CC0). The source sidecar records licences and capture hashes.