-
Notifications
You must be signed in to change notification settings - Fork 176
App Fixes For GeoTiffs #5824
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
App Fixes For GeoTiffs #5824
Conversation
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
1 similar comment
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
6ed4fc5 to
05474e7
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
2 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
9a0ab75 to
120ee2b
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
2 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
ec18882 to
96a92d1
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
2 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
I imagine the CH-2 test failures are unrelated. Spiceinit on a GTIFF was fine. CSMINIT gave an error |
|
Problem seems to be from an unrelated bug. |
|
Looks good, needs a changlog entry. |
8bc6971 to
adfb255
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
1 similar comment
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
isis/src/base/objs/Cube/Cube.cpp
Outdated
| if (hDriver != nullptr) { | ||
| GDALDriver* poDriver = (GDALDriver*)hDriver; | ||
| QString driverDescription = poDriver->GetDescription(); | ||
| openWithGdal = driverDescription == QString("GTiff"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Theoritically, with GDAL 3.12, could we GDAL translate to a PNG (or any other non-cube raster format) and still read in ISIS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reversed this, so instead of checking for a gtiff it now checks if the driver is not the "ISIS3" driver. So we will try to open it using the gdal control flow if it isn't an ISIS3 cube.
bd1ec61 to
a3a536a
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
2 similar comments
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
… the ISIS3 driver
b522714 to
7cde20c
Compare
|
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5824". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
Description
Fixes apps that fail when passing a GeoTiff with ISIS metadata
Related Issue
Fixes #5842
Fixes #5869
How Has This Been Validated?
Types of changes
Checklist:
Licensing
This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words: