My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 3: motion chart time range doubled, data repeated in reverse
1 person starred this issue and may be notified of changes. Back to list
Status:  Done
Owner:  ----
Closed:  May 2011
Cc:  decastillo@gmail.com


 
Reported by skyeb...@gmail.com, Apr 20, 2011
What steps will reproduce the problem?

in R:

groups <- c(rep('a',1000),rep('b',1000),rep('c',1000))
times <- 1:1000
values <- 1000:1
myFrame <- data.frame(groups=groups,times=times,values=values)
Motion <- gvisMotionChart(myFrame,idvar="groups",timevar="times")
plot(Motion)

What is the expected output? What do you see instead?

I would expect the range to vary from 1 to 1000, instead it goes from 1 to 1999.  I would expect the points to move from the upper right to lower left, which they do, but they they move back up, as if the entire data set was repeated, backwards


What version of the product are you using? On what operating system?
R version 2.13.0 (2011-04-13) • googleVis-0.2.4  On Mac OSX

Please provide any additional information below.

When I look at the code for the chart, the data in the JSON part does not repeat, and there are no time values larger than 1000



Apr 21, 2011
#1 skyeb...@gmail.com
Issue doesn't seem to happen if I shift the range of the time values +1000 so they are more like years,  perhaps it is mistakenly converting numeric values to dates?
Apr 25, 2011
Project Member #2 markus.g...@googlemail.com
The Google Visualisation API interprets a numeric value of 1 in timevar as 1901 and not as year 1; equally it will only accept date from 0/1/01/1900 onwards
Here is a simple examples:

library(googleVis)
plot(gvisMotionChart(Fruits, "Fruit", "Year"))
Fruits[1,2]=1
plot(gvisMotionChart(Fruits, "Fruit", "Year"))

Fruits$Date[1]="0-01-01"
plot(gvisMotionChart(Fruits, "Fruit", "Date"))

Status: Accepted
Cc: decastillo@gmail.com
Apr 26, 2011
Project Member #3 markus.g...@googlemail.com
It appears that years greater 100 are accepted without problems.
So could it be that years before 100 (two digits) are interpreted as 19XX?

May 26, 2011
Project Member #5 markus.g...@googlemail.com
I have added a note to the help file of gvisMotionChart:
 Please notice that a \code{timevar} with values less than 100 will be shown as years 19xx.
Status: Done

Powered by Google Project Hosting