-
Notifications
You must be signed in to change notification settings - Fork 82
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
readSLI: take byte order of hdr into consideration #47
Comments
I'm trying to modify readSLI() locally on my own, but as soon as I do it with using a windows box (today) and the github version o RStoolbox |
I have circumvented the problem by including .getNumeric() and .bracketRange() in a modified local version
to
and |
Well done, thanks! Fixed now. |
When I use readSLI() to read a library with byte order = 1 in its hdr, I get weird values in R, while libraries
that have byte order = 0 result in R obkects with meaningful values.
byte order = 1 : https://lost-contact.mit.edu/afs/enea.it/software/rsi/envi_3.5/spec_lib/jpl_lib/
byte order = 0: https://lost-contact.mit.edu/afs/enea.it/software/rsi/envi_3.5/spec_lib/usgs_min/
I understand that readSLI() assumes byte order = 0 (least significant byte first (LSF) data ),
am I wrong?
If I'm not wrong, could byte order be taken into account by readSLI() ?
The text was updated successfully, but these errors were encountered: