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

Just a note on bigtiffs #63

Closed
DandroidDeveloper opened this issue Sep 6, 2018 · 2 comments · Fixed by #134
Closed

Just a note on bigtiffs #63

DandroidDeveloper opened this issue Sep 6, 2018 · 2 comments · Fixed by #134

Comments

@DandroidDeveloper
Copy link

DandroidDeveloper commented Sep 6, 2018

The majority of bigtiff testing I have done is returning incorrect values for the stripOffsets.....

If anyone in the future needs the correct values for rendering data, you can just reference the first stripOffset (where your raster data starts), and then add (row * ImageWidth * 4), to get the correct value.
*assuming they are float32

@constantinius
Copy link
Member

Hi @DandroidDeveloper

Thanks for reporting this issue! The files I worked with could be displayed without error, do you have test files available that did not work so I can reproduce and fix the error?

@DandroidDeveloper
Copy link
Author

Unfortunately no :/

The behavior I saw was with bigTiffs that I am 100% sure are created correctly and have correct metadata. Most of the stripOffsets are correct, but maybe 30% are negative values when accessed using the library.

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

Successfully merging a pull request may close this issue.

2 participants