vega_datasets
source
#3150
Replies: 4 comments 3 replies
-
I like the idea. I remember it took me a while before realizing they are not the same repository. The goal of Since it is also used as teaching material, I can imagine we also like to provide a wider accessibility to choose which dataframe library a user prefers. An interesting change with the past is that the Vega datasets are currently versioned by GitHub releases. Maybe that provides a new entrypoint for Altair. Since this will change all examples in the documentation, we probably might think this through a bit how we can support users that are bound to older versions. |
Beta Was this translation helpful? Give feedback.
-
I'm quite interested in this, so I opened #3631 I'd noticed a lot of examples using |
Beta Was this translation helpful? Give feedback.
-
@ChristopherDavisUCI I hope it is okay with you, I've renamed this discussion to help with visibility. I can revert if not, but I stumbled upon this only after searching for previous |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Would there be a reliable way to transition from using https://github.com/altair-viz/vega_datasets as the default source of example datasets to instead https://github.com/vega/vega-datasets ? Or, if that's not realistic, would there be a way to synchronize the data in the altair-viz version with the data in the vega version? (As far as I can tell, they're not synchronized.)
I could imagine having no local datasets and having functionality like
alt.vega_datasets.cars()
which downloads the cars dataset from https://github.com/vega/vega-datasets/blob/main/data/cars.jsonI don't know at all about the tradeoffs involved, it just feels like this approach might remove one step of maintenance.
Any thoughts on that?
Beta Was this translation helpful? Give feedback.
All reactions