Skip to main content

World Bank Visualizations with googleVis

Building on the last post: I just put together a short slideshow explaining how to use R to create Google Motion Charts with World Bank data. It uses the packages googleVis and WDI. It mostly builds on the example from Mage's Blog post. I just simplified it with the WDI package (and used national finance related variables).

Comments

mages said…
Hi Christopher,

Thanks for pointing out the deck.js library. This seems to be a good solution to present results using the googleVis library. I will use your idea on my blog as well.

Regards

Markus
Vincent said…
Hey Christopher,

I got to this slideshow from the `slidify` website. I'm glad you're finding the WDI package useful!

A quick style thing: WDI will merge a bunch of indicators for you if you just feed it a vector of indicator strings. For example,

dat <- WDI(indicator=c("DT.DOD.DPNG.CD",""DT.DOD.DECT.GN.ZS"))
head(dat)

Best,

Vincent

PS: It appears we know some of the same people: Cassie G. and Bill C.
Vincent said…
Without the two consecutive double-quotes, of course
Unknown said…
Hi Vincent

Thanks for pointing to a solution for the unnecessary verbiage.

Also, thanks for the WDI package, as a heavy user of World Bank data it is definitely helpful.

P.S. Are you going to be at APSA presenting your and Bill's fed paper?
Vincent said…
I'd love to go to APSA, especially since I've never been to NO. But unfortunately, at the moment I'm leaning towards "probably not".

Popular posts from this blog

A Link Between topicmodels LDA and LDAvis

Carson Sievert and Kenny Shirley have put together the really nice LDAvis R package. It provides a Shiny-based interactive interface for exploring the output from Latent Dirichlet Allocation topic models. If you've never used it, I highly recommend checking out their XKCD example (this paper also has some nice background). LDAvis doesn't fit topic models, it just visualises the output. As such it is agnostic about what package you use to fit your LDA topic model. They have a useful example of how to use output from the lda package. I wanted to use LDAvis with output from the topicmodels package. It works really nicely with texts preprocessed using the tm package. The trick is extracting the information LDAvis requires from the model and placing it into a specifically structured JSON formatted object. To make the conversion from topicmodels output to LDAvis JSON input easier, I created a linking function called topicmodels_json_ldavis . The full function is below. To

Set up R/Stan on Amazon EC2

A few months ago I posted the script that I use to set up my R/JAGS working environment on an Amazon EC2 instance. Since then I've largely transitioned to using R/ Stan to estimate my models. So, I've updated my setup script (see below). There are a few other changes: I don't install/use RStudio on Amazon EC2. Instead, I just use R from the terminal. Don't get me wrong, I love RStudio. But since what I'm doing on EC2 is just running simulations (I handle the results on my local machine), RStudio is overkill. I don't install git anymore. Instead I use source_url (from devtools) and source_data (from repmis) to source scripts from GitHub. Again all of the manipulation I'm doing to these scripts is on my local machine.

Slide: one function for lag/lead variables in data frames, including time-series cross-sectional data

I often want to quickly create a lag or lead variable in an R data frame. Sometimes I also want to create the lag or lead variable for different groups in a data frame, for example, if I want to lag GDP for each country in a data frame. I've found the various R methods for doing this hard to remember and usually need to look at old blog posts . Any time we find ourselves using the same series of codes over and over, it's probably time to put them into a function. So, I added a new command– slide –to the DataCombine R package (v0.1.5). Building on the shift function TszKin Julian posted on his blog , slide allows you to slide a variable up by any time unit to create a lead or down to create a lag. It returns the lag/lead variable to a new column in your data frame. It works with both data that has one observed unit and with time-series cross-sectional data. Note: your data needs to be in ascending time order with equally spaced time increments. For example 1995, 1996