Skip to content

px.sankey #2094

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nicolaskruchten opened this issue Jan 17, 2020 · 4 comments
Closed

px.sankey #2094

nicolaskruchten opened this issue Jan 17, 2020 · 4 comments
Milestone

Comments

@nicolaskruchten
Copy link
Contributor

nicolaskruchten commented Jan 17, 2020

We need a px.sankey and I think modelling it after the path flavour of px.sunburst introduced in #2006 is a great starting point! By default it would be always-branching, but we could add a merge_nodes=True option which could collapse nodes or something

@emmanuelle
Copy link
Contributor

for 4.6 I guess?

@nicolaskruchten
Copy link
Contributor Author

Hehe yes :)

@nicolaskruchten nicolaskruchten added this to the v4.6.0 milestone Jan 17, 2020
@nicolaskruchten nicolaskruchten modified the milestones: v4.6.0, v4.x Mar 31, 2020
@MCBoarder289
Copy link
Contributor

Would love to pair on this one if this is already being worked. If it's helpful, I made a PyPI package to automate wrangling of dataframes for sankey charts with what I thought might be helpful assumptions/defaults. Maybe it sparks some good discussion on defaults, and I'm sure it could be modeled similarly to path in px.sunburst.

Here's a link to the main logic I was using: https://github.com/MCBoarder289/sankeyfy/blob/master/sankeyfy/__init__.py

@gvwilson
Copy link
Contributor

Hi - we are trying to tidy up the stale issues and PRs in Plotly's public repositories so that we can focus on things that are still important to our community. Since this one has been sitting for several years, I'm going to close it; if it is still a concern, please add a comment letting us know what recent version of our software you've checked it with so that I can reopen it and add it to our backlog. Thanks for your help - @gvwilson

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants