Conversation
Not required for these requests, but may be helpful to avoid limits
As an example, for comparing against the most recent I've added the 5 most recent
- Basic mechanism for discovering new versions - Tries to minimise number of and total size of requests
Experimenting with querying the url cache w/ expressions
- `metadata_full.parquet` stores **all known** file metadata - `GitHub.refresh()` to maintain integrity in a safe manner - Roughly 3000 rows - Single release: **9kb** vs 46 releases: **21kb**
- Still undecided exactly how this functionality should work - Need to resolve `npm` tags != `gh` tags issue as well
Suffix was only added due to *now-removed* test files
Made possible via vega/vega-datasets#681 - Removes temp files - Removes some outdated apis - Remove test based on removed `"points"` dataset
Makes more sense following (755ab4f)
Still need to update tests
-Seems to work pretty similarly to `geopandas`
- The repr isn't as clean
- Pretty cool that you can get *something* from `load("us-10m").st.plot()`
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR builds upon the amazing work in #3631 by @dangotbanned.
It introduces a modernised dataset interface for Altair, now based on
vega-datasetsversion 3.2.0 from the Vega organisation (link).This will provide Altair with more than 70 datasets that can be lazily loaded without any hard dependency on a specific dataframe library (single hard dependency on narwhals 🫶)
Primary interface:
Expert interface
Spatial data support
Spatial datasets are automatically loaded using:
geopandaswhen using thepandasenginepolars-stwhen using thepolarsengineExample:
Migration path
Migrating from the Python
vega_datasetspackage (link) to the newaltair.datasetsis just a one-line change:No other changes are needed, everything will continue to work and much more becomes possible (at least, that is the aim).