Skip to content
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

Correctly infer date #91

Closed
1 task
kanitw opened this issue Jun 28, 2016 · 7 comments
Closed
1 task

Correctly infer date #91

kanitw opened this issue Jun 28, 2016 · 7 comments

Comments

@kanitw
Copy link
Member

kanitw commented Jun 28, 2016

  • Somehow in Voyager we infer date field in cars.json as date field but not in CompassQL.
    However, using datalib we only get it as integer/number. We need to investigate why such difference happens. (See "Univariate Summary" example in the editor.)
@kanitw kanitw modified the milestone: Feature Jun 28, 2016
@kanitw
Copy link
Member Author

kanitw commented Jun 29, 2016

  • We have similar problem in Vega-Lite-UI, which does not recognize Release_Date in movies.json as time.
  • try browsing other example dataset in Voyager

@kanitw kanitw modified the milestones: Feature, Constraint, Refactor, Data Import Jun 29, 2016
@kanitw kanitw modified the milestones: 2016-07-01 Sprint #1, Data Import Jun 29, 2016
@kanitw
Copy link
Member Author

kanitw commented Jun 29, 2016

@kanitw kanitw modified the milestones: 2016-07-01 Sprint #1, 2016-07-15 Sprint #2, 2016-07-12 Sprint #2, Sprint#1 16/07/01-08 , Sprint#2 16/07/11-22 Jul 8, 2016
@kanitw
Copy link
Member Author

kanitw commented Jul 11, 2016

Release Date is just a year.

@RileyChang
Copy link
Contributor

From discussion:

  • no good way to infer date, must provide a way for user to provide that through a new API
  • can pass the date format to vega-lite (once it is supported) e.g. parse: "data:%y" for dates that are just a year

@kanitw
Copy link
Member Author

kanitw commented Jul 12, 2016

Correction:

From discussion:

  • no good way to infer year, must provide a way for user to provide that through a new API
  • can pass the date format to vega-lite (once it is supported) e.g. parse: "data:%y" for dates that are just a year

@kanitw
Copy link
Member Author

kanitw commented Jul 29, 2016

Bumping this up.

From "Univariate Summary" Demo: year is inferred as string -- I'm not sure how should we address this, but definitely should address it ASAP.

vega_editor

@kanitw
Copy link
Member Author

kanitw commented Jul 29, 2016

It seems like the year field in vega-datasets's cars.json is different from the one in polestar/voyager.

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

No branches or pull requests

2 participants