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
Sure, that sounds great! Maybe the flights data could be moved into a directory all its own, with various subsets there and the addition of the lineage you mentioned into the README there.
The original source data has a lot more details (http://stat-computing.org/dataexpo/2009/the-data.html) and is 12 GB uncompressed. I'd like to use the vegaExample data because the date is well formatted, unlike the crossfilter example data or the ASA source, making it easy to define a schema.
The flight JSON files in the vegaExamples directory are, I believe, subsets of the corssFilter data here: https://github.com/square/crossfilter/tree/gh-pages/ which is 230k rows. This itself a subset of the ASA Data Expo dataset.
The ASA dataset is very big, but you might consider adding your own large subset from the original source.
As for the vegaExamples JSON files they are formatted poorly. Would you consider a PR these PrettyPrints the JSON files?
The text was updated successfully, but these errors were encountered: