Announcing Dash Bio 1.0.0 🎉 : a one-stop-shop for bioinformatics and drug development visualizations.

Choropleth geojson fitbounds with wrapping geojson

I’m having an issue with wrapping and geojson.

Here’s an example based on Choropleth map using GeoJSON (

from urllib.request import urlopen
import json
with urlopen('') as response:
        counties = json.load(response)

import pandas as pd
df = pd.read_csv("",
                 dtype={"fips": str})

import as px

df = df[df.fips.str.startswith("01")]

fig = px.choropleth(df, geojson=counties, locations='fips', color='unemp',
                    range_color=(0, 12),
                    labels={'unemp':'unemployment rate'}
fig.update_geos(fitbounds="locations", visible=False)

import dash
import dash_core_components as dcc
import dash_html_components as html

app = dash.Dash()
app.layout = html.Div([

app.run_server(debug=True, use_reloader=False)

From the code you can see I filter down to the Alabama data (FIPS state code 01) and use fitbounds=“locations” to center and zoom on the provided data. And you can see in the picture below that it works great.

Now, let’s try with Alaska (FIPS 02), as in

df = df[df.fips.str.startswith("02")]

Gross! I’ve tried all manner of update_geos with center, projection_rotation, *axis_range, etc. but the fitbounds overrides them all, and without it I have to manually calculate and set everything (assuming I can replicate all the zooming too).

Is there any way to have fitbounds locations understand that a rotation before bounding is better than wrapping? Or, let me provide a center or rotation prior to calculating bounds?

Using the following special case code for Alaska gets me close to what I want. However, I think any geojson shapes that wrap will have this issue.

if alaska:
              lonaxis_range=[20, 380],
        fig.update_geos(fitbounds="locations", visible=False)   

Any advice on a better way to do this so that a special case isn’t required? Or could the fitbounds location code be updated to handle this?

I had the same problem. Thanks for posting this. It would be great to get an update on how to fix this. Additionally, I’m struggling with keeping the aspect ratios 1:1. My Alaska looks stretched like yours. I have tried everything to try and get it to maintain the aspect ratio. Any guidance on that would be great.

Unfortunately, I have no update. Mapping a 3D object (the globe) to a 2d surface is just hard. Maintaining shape, distance, and relative size all at once is impossible and you have to be will to bend a little on one of them. This is true of all map projections and there are some great books about cartographic projections.

More importantly you’re really asking about better fixes to the problem I outlined above. For my use case the workaround I posted was “good enough.” So I stopped there and haven’t revisited. If you come up with something better I’d love to see it. Or if someone else from the community wants to chime in, that’d be great too.