Bugfix/hack: Always use EPSG:4326 with GeocodedFile to fix crash #770
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.
Description
Adds a line that transforms all bounding boxes the GeocodedFile AOI receives to EPSG:4326.
Motivation and Context
Rest of the code is not properly set up to handle GeocodedFile AOIs that are not in EPSG:4326, which causes problems with EPSG:32617 interferograms like from ASF On Demand. I lack the time to fix this properly, but I did end up doing this much so that RAiDER would work with my code for the gemlab ASF On Demand notebook jlmaurer/gemlab#11. I offer what I have in case you might want to accept it and/or use it as a jumping-off point for a more in-depth solution.
In the case when the user inputs a geocoded file with projection other than EPSG:4326, this change fixes a crash, at the cost of more transformations in this code path, and any precision errors or other drawbacks that may come with it. A more thoughtful solution may be able to avoid doing a conversion here.
In all other cases (other projections, other input AOI types), nothing is changed/affected.
How Has This Been Tested?
Screenshots (if appropriate):
Type of change
Checklist: