Skip to content
Download and process GIMMS3g NDVI binary data
Branch: master
Clone or download
Latest commit 78277bd Dec 10, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
R Replaced direct journal links by actual DOIs due to link deprecation … Dec 10, 2018
man Replaced direct journal links by actual DOIs due to link deprecation … Dec 10, 2018
.travis.yml Update: added 'ncdf4' to r_packages. Jan 31, 2018
NAMESPACE Update: **curl** check for internet connection; this should be includ… Aug 1, 2017
NEWS Bumped version; Roxygen2 update. Dec 10, 2018 Bumped version; Roxygen2 update. Dec 10, 2018 Typo. Dec 10, 2018
gimms.Rproj Minor edits: Roxygen2 update; added encoding UTF-8; bumped version. Aug 23, 2018

Package downloads and build status

Downloads from the RStudio CRAN Mirror
This month In total
month total
Build status
CRAN Travis-CI (master) Travis-CI (devel)

Introducing the 'gimms' package

... is an open-access tutorial about the gimms package which has been developed using GitBook. The book will regularly be updated as gimms develops further, so make sure to check it out every now and then!

What's new?

2018-12-07, gimms 1.1.1 is out now

Starting with this update, rasterized NDVI3g.v0 images are no longer kept in memory, but properly linked to their corresponding files on disk (only applicable if 'filename' is specified in rasterizeGimms()).

2018-01-13, gimms 1.1.0 is now on CRAN

As of 2018-01-13, the next minor release of gimms has finally arrived on CRAN. Check out NEWS for a full list of changes. In addition, note that the accompanying GitBook will be updated (and hopefully extended) soon.

2017-01-02, "traditional" NDVI3g.v0 names from new NDVI3g.v1 files via oldNaming

For all users who prefer to work with the now outdated NDVI3g.v0 file names, I've added a function called oldNaming to the 'develop' branch. It takes a vector of .nc4 file names as input and transforms them to traditional half-monthly file names, optionally appending a suffix e.g. in preparation for writeRaster. As this is not on CRAN yet, remember to install the 'develop' version via

                         ref = "develop")

to be able to use that function in the first place.

2016-12-17, gimms 1.0.0 is now on CRAN

I am happy to announce that the brand-new package update (v1.0.0) has successfully been built for all platforms and is now available from CRAN. Among the major improvements are:

  • comprehensive support for the recently released GIMMS NDVI3g.v1 which comes as half-yearly NetCDF container files and spans the period until December 2015. For reasons of convenience, continuing support for NDVI3g.v0 ENVI binary files is maintained.
  • quality control is now directly available through rasterizeGimms. In order to make sure older scripts are still operable, separate calls to qualityControl are possible, but explicitly require the specification of a 2-layered RasterStackBrick object (NDVI and flags).
  • rasterizeGimms further takes an optional argument 'ext' which is passed to raster::crop which, if used, drastically reduces computation times. At the same time, the application of a scale factor and the rejection of 'mask-water' and 'mask-nodata' values is no longer optional.
  • parallel processing is no longer realized through foreach (alongside with doParallel), but instead relies on the built-in parallel package only. Therefore, the former two are no longer part of the package Imports section.
  • et cetera

2016-01-15, gimms 0.5.0 is now on CRAN

As of today, gimms 0.5.0 is available from CRAN and has some new functionality:

  • enabled flag support in rasterizeGimms. In addition to the raw and scaled values of NDVI3g, the function now optionally returns flag layers which can subsequently be used for quality control. Please refer to the official README for further reading.
  • improved performance of parallel processing.
  • revised package documentation.

2015-12-16, added parallel support

I decided to add optional multi-core support to downloadGimms, rasterizeGimms and monthlyComposite. The referring arument is called 'cores' and, if not specified otherwise, defaults to 1 (i.e., parallel computing is disabled). In the course of this, the gimms package version on branch 'develop' has been incremented to 0.4.0 and can be installed via devtools::install_github (see further below).

2015-11-13, gimms 0.3.0 is now on CRAN

It's Friday 13th and an updated version of the gimms package has been published on CRAN. The new version includes

  • significantTau to calculate pixel-based (and optionally pre-whitened) Mann-Kendall trend tests from a previously processed GIMMS NDVI3g (or any kind of) 'RasterStack/Brick' object. Note that it also works with simple 'numeric' vectors (i.e., univariate time series observations);
  • the below compatibility update of downloadGimms that enabled 'Date' input;
  • and some minor bug-fixes.

2015-11-11, downloadGimms now works with 'Date' input

In response to recent user suggestions, I decided to enable 'Date' input for downloadGimms which grants the user a finer control over the temporal coverage of the data to be downloaded. The changes are currently available from the 'develop' branch via

                         ref = "develop")

and will be submitted to CRAN soon.

##### 2015-11-06, pre-whitened Mann-Kendall trend test via `significantTau` In order to account for lag-1 autocorrelation when trying to deduce reliable long-term monotonous trends, **gimms** now features a function called `significantTau`. The code imports the standard (i.e., without pre-whitening) procedure included in package **Kendall** (McLeod, 2011) or, if the user decides to apply pre-whitening prior to the actual trend test, one of the algorithms included in **zyp** (Bronaugh and Consortium, 2013). Check out `?significantTau` for further details.
##### 2015-10-26, `downloadGimms` now works properly on Windows I recently received a bug report about some strange behavior of `downloadGimms` (when working on Windows platforms) which resulted in a rather awkward look of the rasterized images.


The problem was obviously related to download.file which worked just fine on Linux when using the default settings, but introduced distortions on Windows. In the newest package version 0.2.0 which is now brand-new on CRAN, I therefore specified download.file(..., mode = "wb") to explicitly enable binary writing mode.

Thanks again for the input!

You can’t perform that action at this time.