Hi @jmmease, that sounds good. I didn’t realize that countymaps was only available to plotly.py, but that now makes sense given the extra dependencies. I’m working in dash though so an only python solution would still be fine.
In particular, what the API could look like
Ideally, this would have the same name as the
To allow something like this though,
fig = ff.create_choropleth(area_codes=area_codes, values=values, ... )
or in @thedatasleuth’s case,
fig = ff.create_choropleth(congressional_codes=congressional_codes, values=values, ... ) would require some restructuring to the current code.
To keep backwards compatibility, I’d probably create multiple
create_choropleth() functions with some logic that decides whether we create a county, congressional, metro, or whatever type of choropleth figure. How does that sound?
and what kind of unique identifiers should be used to specify values for each metro areas (Is there something like FIPS codes for these?)
Yes, areas do have unique identifiers. Here is a link to the area definition file that is provided by the US Bureau of Labor Statistics: https://www.bls.gov/oes/current/area_definitions_m2017.xlsx Codes are in column D ‘MSA code (including MSA divisions)’
I’ll continue this on the PR thread as well. Really looking forward to getting involved with this!