Skip to content
Prev 24425 / 29559 Next

MODIS package's runGdal() returns error: dataFormat='GTiff', format not supported

Progress has certainly been made regards MODIS.

 > sessionInfo()
R version 3.2.2 (2015-08-14)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 14.04.4 LTS

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
LC_TIME=en_US.UTF-8
 [4] LC_COLLATE=en_US.UTF-8     LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C
LC_ADDRESS=C
[10] LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=C

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base

other attached packages:
[1] MODIS_0.10-34  raster_2.5-2   sp_1.2-3       devtools_1.9.1

loaded via a namespace (and not attached):
[1] rsconnect_0.4.1.11 tools_3.2.2        Rcpp_0.12.5
memoise_0.2.1      grid_3.2.2
[6] digest_0.6.8       lattice_0.20-33

Thomas Nauss, University of Marburg, examined the problem and proposed
a fix (https://github.com/MatMatt/MODIS/issues/5). It has not actually
been applied to the 'develop' branch currently the MODIS_0.10-34. But
cloning the develop branch and editing minorFuns.R with his suggested
fix and doing a local install from source gives me:
Loading required package: MODIS
Loading required package: raster
Loading required package: sp
MODIS_manual: https://ivfl-rio.boku.ac.at/owncloud/public.php?service=files&t=660dc830afb091237cc40b3dea2fdf6b


Attaching package: ?MODIS?

The following object is masked from ?package:base?:

    file.size
All suggested packages are installed
Detecting available write drivers!
Found: 64 candidate drivers, detecting file extensions...
44 usable drivers detected!

This is a darn sight better than zero drivers.

STORAGE:
_______________
localArcPath : /home/chris/MODIS_ARC
outDirPath   : /home/chris/MODIS_ARC/PROCESSED


DOWNLOAD:
_______________
MODISserverOrder : LPDAAC, LAADS
dlmethod         : auto
stubbornness     : high


PROCESSING:
_______________
GDAL           : GDAL 2.1.0dev, released 2015/99/99
MRT            : Version 4.1 (March 2011)
pixelSize      : asIn
outProj        : asIn
resamplingType : NN
dataFormat     : GTiff

Returning to Hakim's initial post:
+ h,tileV = v, SDSstring = bands, outProj="4326")
Loading required package: rgdal
rgdal: version: 1.1-3, (SVN revision 594)
 Geospatial Data Abstraction Library extensions to R successfully loaded
 Loaded GDAL runtime: GDAL 2.1.0dev, released 2015/99/99
 Path to GDAL shared files: /usr/local/share/gdal
 Loaded PROJ.4 runtime: Rel. 4.9.1, 04 March 2015, [PJ_VERSION: 491]
 Path to PROJ.4 shared files: (autodetected)
WARNING: no proj_defs.dat in PROJ.4 shared files
 Linking to sp version: 1.2-1
Loading required package: rgeos
rgeos version: 0.3-15, (SVN revision 515)
 GEOS runtime version: 3.4.2-CAPI-1.8.2 r3921
 Linking to sp version: 1.2-1
 Polygon checking: TRUE

########################
NOTE: rgdal::checkCRSArgs: no proj_defs.dat in PROJ.4 shared files
outProj          =  +init=epsg:4326 +proj=longlat +datum=WGS84
+no_defs +ellps=WGS84 +towgs84=0,0,0
pixelSize        =  asIn
resamplingType   =  near
Output directory =
/home/chris/MODIS_ARC/PROCESSED/MOD13Q1.005_20160525005632  (no 'job'
name specified, generated (date/time based))
########################
Loading required package: RCurl
Loading required package: bitops
Downloading structure on 'LPDAAC' for: MOD13Q1.005
Try: 1
Error in if (FtpDayDirs[1] == FALSE) { :
  missing value where TRUE/FALSE needed

Hummph.  Well, I'm very happy to have drivers. Uncertain if my 64
candidates vs 44 represents additional name changes as Thomas
suggested and the 44 apply to his fix and an additional 20 are
differences between Frank's and Evan's naming conventions as to those
other 20. And uncertain as to how to ask MODIS which 44 are viable vs
20 that were not viable, though this would probably be useful.

It appears, given Hakim's request code, that he won't be getting MODIS
data as Error after Try: 1 suggests a certain lack of stubbornness or
further problem. Nor will I of course.  I tried a debugonce(runGdal),
but the implications of the runGdal() are substantially above and
beyond my pay grade and current level in R.

So back to eyetracking data and Bagidis semi distances. I'm sure MODIS
will be sorted out by those more familiar with expected results.

Chris

On Thu, May 19, 2016 at 1:31 PM, chris english
<englishchristophera at gmail.com> wrote: