Skip to content

Conversation

@acpaquette
Copy link
Collaborator

@acpaquette acpaquette commented May 30, 2025

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation change (update to the documentation; no code change)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

  • I have read and agree to abide by the Code of Conduct
  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • I have added myself to the .zenodo.json document.
  • I have added my user impacting change to the CHANGELOG.md document.

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:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

  • I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

@github-actions
Copy link

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.

@github-actions
Copy link

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
@github-actions
Copy link

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.

@Kelvinrr Kelvinrr marked this pull request as ready for review September 12, 2025 16:06
@github-actions
Copy link

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
@github-actions
Copy link

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.

@github-actions
Copy link

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.

@github-actions
Copy link

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
@github-actions
Copy link

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.

@github-actions
Copy link

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.

@github-actions
Copy link

github-actions bot commented Dec 4, 2025

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
@github-actions
Copy link

github-actions bot commented Dec 4, 2025

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.

@github-actions
Copy link

github-actions bot commented Dec 4, 2025

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.

@Kelvinrr
Copy link
Collaborator

I imagine the CH-2 test failures are unrelated.

Spiceinit on a GTIFF was fine.

CSMINIT gave an error

(isisgdalbuilds) igswza281l2305:isisbuild krodriguez$ ./bin/csminit from=~/cnets/I52634011RDR.tiff isd=~/cnets/I52634011RDR.json
**USER ERROR** No loaded model could be created from the ISD [/Users/krodriguez/cnets/I52634011RDR.json].Loaded plugin & model names:
Plugin [UsgsAstroPluginCSM], Model [USGS_ASTRO_FRAME_SENSOR_MODEL]
.
.
.

@Kelvinrr
Copy link
Collaborator

Problem seems to be from an unrelated bug.

@Kelvinrr
Copy link
Collaborator

Looks good, needs a changlog entry.

@github-actions
Copy link

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
@github-actions
Copy link

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.

@acpaquette acpaquette requested a review from Kelvinrr December 31, 2025 21:00
if (hDriver != nullptr) {
GDALDriver* poDriver = (GDALDriver*)hDriver;
QString driverDescription = poDriver->GetDescription();
openWithGdal = driverDescription == QString("GTiff");
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

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
@github-actions
Copy link

github-actions bot commented Jan 6, 2026

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.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

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.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

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.

@Kelvinrr Kelvinrr merged commit 3546b33 into DOI-USGS:dev Jan 7, 2026
3 checks passed
@github-actions github-actions bot added bug Something isn't working inactive Issue that has been inactive for at least 6 months labels Jan 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working inactive Issue that has been inactive for at least 6 months

Projects

None yet

Development

Successfully merging this pull request may close these issues.

weird csminit behavior with GTIFFs Spiceinit web fails with geotiffs

2 participants