Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not writing M*D15A2 geotiff files #60

Closed
ghost opened this issue Feb 7, 2017 · 3 comments
Closed

Not writing M*D15A2 geotiff files #60

ghost opened this issue Feb 7, 2017 · 3 comments

Comments

@ghost
Copy link

@ghost ghost commented Feb 7, 2017

using R version 3.2.2 on Platform: x86_64-w64-mingw32/x64 (64-bit)
The tiff files for 8-day LAI/FPAR (LAI_1km and FPAR_1km) are not created on the output folders (i.e., folders FAPR and LAI are empty). It does write Tiff files for QC bits.

@lbusett
Copy link
Collaborator

@lbusett lbusett commented Feb 7, 2017

Thanks for reporting this. Will have a look ASAP.

Can you tell us if you are using the master or the devel branch ?

@ghost
Copy link
Author

@ghost ghost commented Feb 7, 2017

I used the default one and DID NOT specify ref='devel' during installation.
MODIS level -6 products such as 8-day LST, 8-day surface reflectances are working just fine.

@ranghetti
Copy link
Collaborator

@ranghetti ranghetti commented Feb 8, 2017

The error was due to a problem in managing multiple nodata values. As you can notice from the product description, fpar and lai have a range of values associated with nodata (249-255): this caused the error.
Commit fb05d3b should have partially fixed it: now the layer is produced, but nodata values are not recognised (you have to know than values between 249 and 255 are nodata).
This problem will fully fixed in future (it requires more code editing, since GDAL does not manage multiple nodata for the same band).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.