Add a WARNING when a geo file is specified but the file does not exist #1790
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I was trying to use a geo.txt file option to override my input image geolocation metadata. I ran a case with and without the
--geo <path>option to compare and was surprised when the results were the same. When searching for the cause, I realised I had a typo in my geo.txt file path. However, when reviewing the logs, I noticed that anODM_INFOmessage is printed to the logs when the file is correctly found but no message is printed when a path is given but no file is found. Hence this pull request: I suggest adding anODM_WARNINGmessage to the logs to help users debug such a case.Thanks for all your work on this excellent open source project!