Classification and location
Glottolog 5.3 supplies names, stable codes, classification, macroarea, country membership, AES endangerment, and one representative coordinate per record. Neither a country code nor a point defines a language territory.
Research tool
Find a language, inspect its classification, and see what each source can actually support. Search by name, stable code, WALS feature, or IPA sound. The map reports evidence coverage; it does not draw language territories.
Current selection
| Language | Family and branch | Countries | Endangerment | Source coverage |
|---|
This table is the text equivalent of the choropleth. The country-membership filter uses Glottolog’s declared country codes, which cover more small islands and territories than this generalized map.
| Country | Language records |
|---|
Evidence boundary
Glottolog 5.3 supplies names, stable codes, classification, macroarea, country membership, AES endangerment, and one representative coordinate per record. Neither a country code nor a point defines a language territory.
Wikidata P1098 statements keyed by Glottocode cover a minority of records. Figures retain their publication year when available and are shown as absent when unavailable.
WALS CLDF v2020.5 contributes 76,475 observations across 192 features. The compact index joins 2,423 current Glottocodes and supports searches such as 81A.
PHOIBLE as CLDF supplies inventory summaries and searchable IPA phonemes for 2,027 current Glottocodes. Original inventory sources remain part of PHOIBLE’s citation chain.
Natural Earth 1:110m boundaries group representative points. Small islands and disputed or generalized boundaries can leave records unassigned.
Diachronica remains the query surface for the Etymology Atlas, IE-CoR cognate judgments, WOLD loans, CLICS³ colexifications, and the currently capped ASJP extract. Those sources are not silently collapsed into language-level facts here.
Joshua Project is intentionally not merged. Its people-group and mission estimates answer different questions, use different entity boundaries, and carry restrictive reuse terms. Use its own explorer with that methodological context.