From 5d7004f08a6fc8a52213447823fc91539c4417da Mon Sep 17 00:00:00 2001 From: Igor Lukanin Date: Thu, 30 Jul 2026 00:35:38 +0200 Subject: [PATCH 1/2] docs: document country name matching in region maps --- .../docs/explore-analyze/charts/chart-types/map.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx b/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx index df9754e14fb7e..6cc50f3a75427 100644 --- a/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx +++ b/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx @@ -67,6 +67,14 @@ Built-in sources expose a fixed list of allowed properties. **Custom** lets you When the chart enters Region mode, the join dimension and measure are auto-picked when an unambiguous match exists in your query. +### Country name matching + +With **World countries**, country names do not have to be spelled the way the boundary data spells them. Long forms, endonyms, and common abbreviations all resolve to the same country, so `United States`, `United States of America`, `USA`, and `US` are interchangeable, as are `Brasil` and `Brazil`, or `Deutschland` and `Germany`. The same applies to the 2- and 3-letter ISO code properties, and it works in either direction — a name in your data still matches when **Property** is set to a code. + +Matching is exact, never approximate: `United States` resolves to the United States and never to `United States Minor Outlying Islands`. Bare 2-letter codes are only treated as country codes when **Property** is set to one of the ISO code properties, so a column of US state codes joined against country names stays unmatched rather than colouring `DE` as Germany. + +This applies to **World countries** only. With **US states** or **Custom**, values must match the chosen **Property** exactly (ignoring case and surrounding whitespace). + The choropleth gradient comes from the active palette — pick from the built-in palettes or supply a custom one, see [Color and stacking](/docs/explore-analyze/charts/configuration/color-and-stacking). ### Custom GeoJSON From c16cc12cd197a83b22a5f75d32e0bd6654fb07eb Mon Sep 17 00:00:00 2001 From: Igor Lukanin Date: Thu, 30 Jul 2026 20:22:41 +0200 Subject: [PATCH 2/2] docs: fix Region map section placement, US-code wording and spelling --- .../docs/explore-analyze/charts/chart-types/map.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx b/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx index 6cc50f3a75427..165ce16af1217 100644 --- a/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx +++ b/docs-mintlify/docs/explore-analyze/charts/chart-types/map.mdx @@ -59,7 +59,7 @@ Clustering groups nearby points into a single circle that expands on zoom. It is A region map requires: - **Source** — the GeoJSON to render: `World countries`, `US states`, or `Custom`. -- **Property** — which property in each GeoJSON feature acts as the join key (e.g. `name`, `ISO3166-1-Alpha-2`, `state_code`). +- **Property** — which property in each GeoJSON feature acts as the join key (e.g. `name`, `ISO3166-1-Alpha-2`, `ISO3166-1-Alpha-3`, `state_code`). - **Dimension** — which column from your query joins to **Property**. - **Measure** — the numeric measure that drives the choropleth fill. @@ -67,16 +67,16 @@ Built-in sources expose a fixed list of allowed properties. **Custom** lets you When the chart enters Region mode, the join dimension and measure are auto-picked when an unambiguous match exists in your query. +The choropleth gradient comes from the active palette — pick from the built-in palettes or supply a custom one, see [Color and stacking](/docs/explore-analyze/charts/configuration/color-and-stacking). + ### Country name matching -With **World countries**, country names do not have to be spelled the way the boundary data spells them. Long forms, endonyms, and common abbreviations all resolve to the same country, so `United States`, `United States of America`, `USA`, and `US` are interchangeable, as are `Brasil` and `Brazil`, or `Deutschland` and `Germany`. The same applies to the 2- and 3-letter ISO code properties, and it works in either direction — a name in your data still matches when **Property** is set to a code. +With **World countries**, country names do not have to be spelled the way the boundary data spells them. Long forms, endonyms, and common abbreviations all resolve to the same country, so `United States`, `United States of America`, and `USA` are interchangeable, as are `Brasil` and `Brazil`, or `Deutschland` and `Germany`. The same applies to the 2- and 3-letter ISO code properties, and it works in either direction — a name in your data still matches when **Property** is set to a code. -Matching is exact, never approximate: `United States` resolves to the United States and never to `United States Minor Outlying Islands`. Bare 2-letter codes are only treated as country codes when **Property** is set to one of the ISO code properties, so a column of US state codes joined against country names stays unmatched rather than colouring `DE` as Germany. +Matching is exact, never approximate: `United States` resolves to the United States and never to `United States Minor Outlying Islands`. Bare 2-letter codes such as `US` are only treated as country codes when **Property** is set to one of the ISO code properties, so a column of US state codes joined against country names stays unmatched rather than coloring `DE` as Germany. This applies to **World countries** only. With **US states** or **Custom**, values must match the chosen **Property** exactly (ignoring case and surrounding whitespace). -The choropleth gradient comes from the active palette — pick from the built-in palettes or supply a custom one, see [Color and stacking](/docs/explore-analyze/charts/configuration/color-and-stacking). - ### Custom GeoJSON When **Source** is set to **Custom**, paste a URL serving a GeoJSON `FeatureCollection`. Requirements: