NASA generates and provides heaps of data to the scientific community. Not allof it is looking out at the stars. Some of it is looking back at us here onEarth. NASA’s Earth science program observes, understands and models theEarth system ¹ . We can use these data to discover how our Earth is changing,to better predict change, and to understand the consequences for life on Earth.

We’ve just released a new version of rnoaa with A LOT of changes. Check outthe release notesfor a complete list of changes.

I’ve recently released the new package ccafs, which provides accessto data from Climate Change, Agriculture and Food Security(CCAFS; http://ccafs-climate.org/) General Circulation Models (GCM) data.GCM’s are a particular type of climate model, used for weather forecasting,and climate change forecasting - read more athttps://en.wikipedia.org/wiki/General_circulation_model.

A new package isdparser ison CRAN. isdparser was in part liberated from rnoaa,then improved. We’ll use isdparser in rnoaa soon. isdparser does not download files for you from NOAA’s ftp servers. Thepackage focuses on parsing the files, which are variable length ASCII stringsstored line by line, where each line has some mandatory data, and any amountof optional data.

One of the goals of the rOpenSci is to facilitate interoperability between different data sources around web with our tools. We can achieve this by providing functionality within our packages that converts data coming down via web APIs in one format (often a provider specific schema) into a standard format. The new version of rWBclimate that we just posted to CRAN does just that.

We recently pushed the first version of rnoaa to CRAN - version 0.1. NOAA has a lot of data, some of which is provided via the National Climatic Data Center, or NCDC. NOAA has provided access to NCDC climate data via a RESTful API - which is great because people like us can create clients for different programming languages to access their data programatically.

One of our primary goals at ROpenSci is to wrap as many science API’s as possible. While each package can be used as a standalone interface, there’s lots of ways our packages can overlap and complement each other. Sure He-Man usually rode Battle Cat, but there’s no reason he couldn’t ride a my little pony sometimes too. That’s the case with our packages for GBIF and the worldbank climate data api.

A recent video on the PBS Ideas Channel posited that the discovery of climate change is humanities greatest scientific achievement. It took synthesizing generations of data from thousands of scientists, hundreds of thousands (if not more) of hours of computer time to run models at institutions all over the world. But how can the individual researcher get their hands of some this data?

Half-baked idea time. Thinking about projects such as the Earth Microbiome Project and Genomic Observatories, the recent GBIC2012 meeting (I'm still digesting that meeting), and mulling over the book A Vast Machine I keep thinking about the possible parallels between climate science and biodiversity science.

I’ve avoided writing about the Climate Research Unit emails leak for a number of reasons. Firstly it is clearly a sensitive issue with personal ramifications for some and for many others just a very highly charged issue. Probably more importantly I simply haven’t had the time or energy to look into the documents myself. I haven’t, as it were, examined the raw data for myself, only other people’s interpretations.