You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across this when trying to plot the running tracks I ran this year. For each run, I have latitude and longitude data and I want to plot the track. Each column should be a new route. And since tracks happen at various places across many countries, I need the scale to be resolved independently.
I believe this is related to the issue #3729 which prevents faceting on geoshape plots.
As a workaround you can manually concatenate each plot. When doing this you will also encounter #9321 which causes concatenated geoshape plots to have shared projections, so it is also necessary to slightly change the projection on each loop.
If there is an easier solution that doesn't involve trying to fully fix facte for geoshape, I am happy to review a pull request. Happy to reopen this if this is something you can help with.
I came across this when trying to plot the running tracks I ran this year. For each run, I have latitude and longitude data and I want to plot the track. Each column should be a new route. And since tracks happen at various places across many countries, I need the scale to be resolved independently.
Here's an MWE in
altair
that works:However, this obviously distorts the tracks. I should have used
latitude
andlongitude
instead ofx
andy
. So I tried this:This errors because
resolve_scale
does not acceptlatitude
orlongitude
as inputs.Is there a fundamental issue as for why
resolve_scale
can't work withlatitude
/longitude
? Could this be added?I first wanted to open this under
altair
but I guess this would have moved here eventually? Sorry for only providing thepython
code.Thanks a lot for the great work you're doing!
The text was updated successfully, but these errors were encountered: