A choropleth trace supports specifying locations as high-level string names/IDs, via the locations and locationmode keys. This is very convenient and makes it easy to get a nice plot 👍
A choroplethmapbox trace seems to not support this, and thus requires specifying any geometries as a manual GeoJSON file. It would be nice if choroplethmapbox supported the same automatic "inference" of appropriate geometries too.
Related issues:
A
choroplethtrace supports specifying locations as high-level string names/IDs, via thelocationsandlocationmodekeys. This is very convenient and makes it easy to get a nice plot 👍A
choroplethmapboxtrace seems to not support this, and thus requires specifying any geometries as a manual GeoJSON file. It would be nice ifchoroplethmapboxsupported the same automatic "inference" of appropriate geometries too.Related issues:
Introducing choroplethmapbox traces #3988 mentions the possibility of this, but it seems there's no progress:
Add new choroplethmapbox locationmode for geojson
properties.id#4154 was, I think, about generalising the GeoJSON support inchoroplethmapbox, but not adding the no-GeoJSON mode as hereAdd support for custom geojson polygons in choropleth traces #4267 was the opposite, I think: adding support for GeoJSON to
choropleth