-
Notifications
You must be signed in to change notification settings - Fork 621
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
Support multiple source datasets like vega #1271
Comments
We do not plan to support multiple data sources in a single view. With multiple data sources the compiler wouldn't be able to resolve some ambiguities and so far we couldn't think of any use cases. We might add support for an initial union or join to combine multiple data sources into one, though. Is that what you were thinking about? Having said that, we do plan to support different data sources in different layers and when views are concatenated. We already have a few prototypes working (see #1241 for example) but it's not production ready yet.
Yes. We should add more developer documentation. Probably in the form of readmes in the source code directories. It would be great if you could document what you found unclear so we know what to focus on.
Actually we create a |
@domoritz here's a summary of where i found "sharp edges": https://github.com/okfn/datapackage-render-js#research - a result of my working getting a rudimentary data package + vega-lite integration working 😄 ) BTW if you have time for a call at some point with me and e.g. @pwalsh think that could be super productive ... |
@rgrp Sure. Let's organize a call. I sent you a message. |
We now support lookup transform which allow a form of joining multiple data sources |
I'm closing this since I'm not sure what are the actionable items left. |
Does vega support multiple datasets now? Hope someone can show me an example or point me in the right direction. |
Vega or Vega-Lite? |
Vega-Lite |
In Vega-Lite, data can be defined per view. For example, two hconcated charts may have different data. |
what happens if there are multiple records matching an entityId ? |
I would like to aggregate two datasets from two different API calls with identical structure (see below). I'm using Data from |
At the moment vega-lite's data property is a little different from vega's in that it only allows one data source (and does not name it).
Will it be possible in future to have vega-lite support multiple datasets similar to vega?
Aside: whatever you do it might be worth documenting the difference here and what happens in the transformation to vega data as technical users (like me) would be interested. It took me a while to grok what was happening e.g. that the data from vega-lite always ends up in a dataset called source -- and I'm still unsure whether i can do late data binding (does the
layout
dataset get transformed ...)?The text was updated successfully, but these errors were encountered: