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

Update and improve handling of projections and area definitions #436

Merged
merged 16 commits into from
Feb 27, 2025

Conversation

AnaVukasinovic
Copy link
Contributor

@AnaVukasinovic AnaVukasinovic commented Feb 3, 2025

To resolve this issue, a configuration change was required in the area_definitions.yaml file. The GUI was modified, along with the logic for applying resolution in the Open File Wizard window. Additionally, users are now able to select a custom resolution.

…rea definitions; unit testing still pending
Copy link
Contributor

@RudiLauster RudiLauster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provided Unit Tests and with that tested the changes functionally and successfully 🙂
Code looks good!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I guess it's a good idea to set back to "INFO".
Andrea @ameraner , what do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tbh I'd rather leave it do DEBUG, since it's then easier, in case of errors, to request the full log from a user without having him/her to modify the user settings first.

@AnaVukasinovic AnaVukasinovic marked this pull request as ready for review February 5, 2025 16:14
@ameraner ameraner linked an issue Feb 25, 2025 that may be closed by this pull request
Copy link
Collaborator

@ameraner ameraner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks a lot for this first PR and the nice work! Just some very minor modifications I can commit myself.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tbh I'd rather leave it do DEBUG, since it's then easier, in case of errors, to request the full log from a user without having him/her to modify the user settings first.

@ameraner ameraner changed the title Initial commit for bug fix #393 - Sift mixes up projections and area definitions Update and improve handling of projections and area definitions Feb 25, 2025
Copy link
Collaborator

@ameraner ameraner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems that one file was committed by mistake, please remove it. Otherwise LGTM!

@ameraner ameraner merged commit 9a24f47 into ssec:master Feb 27, 2025
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sift mixes up projections and areadefinitions
3 participants