Re: [R-sig-Geo] runGdal in MODIS package overrides the default in MODISoptions asIn pixel size and output a smaller resoultion pixels

Dear Amit, I just want to correct my previous mail, runGdal uses gdalwarp not gdal_translate! Matteo Amit Boshale amit.bosh...@yahoo.com 11/20/14 11:08 AM Dear Matteo, Thank you so much for the quick response :-) Staying in Sinusoidal projection is a brilliant idea! I will keep the

Re: [R-sig-Geo] runGdal in MODIS package overrides the default in MODISoptions asIn pixel size and output a smaller resoultion pixels

Dear Matteo, Thank you so much for the quick response :-) Staying in Sinusoidal projection is a brilliant idea! I will keep the Sinusoidal projection for the first raster, then convert its projection to WGS84 using QGIS and use it as the extend raster r you kindly mentioned. If the gdal did

[R-sig-Geo] runGdal in MODIS package overrides the default in MODISoptions asIn pixel size and output a smaller resoultion pixels

Dear MailLister, I have a problem with runGdal function in MODIS package. At Nadir the resolution should be 250 m. The output of the following code result are NDVI, EVI, composite day of the year and VI quality Tifs (resolution of 150 m) library(MODIS) runGdal( job=H12V12, product=MOD13Q1,

Re: [R-sig-Geo] runGdal in MODIS package overrides the default in MODISoptions asIn pixel size and output a smaller resoultion pixels

Dear Amit, if you set pixelSize asIn, the handling of the pixelsize is done by gdal_translate, runGdal in such case does not provide any information about resolution to used 'gdal_translate'. As your outProj is 4326 you have geographic coordinates, this means that in planar coordinates your