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

GTC-2651 (part 2) - handle "antarctica case" for dashboard as well #229

Merged
merged 1 commit into from
May 1, 2024

Conversation

danscales
Copy link
Collaborator

GTC-2651 (part 2) - handle "antarctica case" for gfwpro_dashboard as well

This is handling GTC-2651 for gfwpro_dashboard as well. If all locations in the input list are outside of the TCL extent (e.g. all in Antartica), then the fire analysis will fail because there is no boundary that the spatial join wants to access. So, exit out of the fireStats if the RDD is completely empty.

This is handling GTC-2651 for gfwpro_dashboard as well. If all locations
in the input list are outside of the TCL extent (e.g. all in Antartica),
then the first analysis will fail because there is no boundary that
spatial join want to access. So, exit out of the fireStats if the RDD is
completely empty, because all locations are outside the TCL extent.
@danscales danscales requested a review from jterry64 May 1, 2024 17:27
@danscales
Copy link
Collaborator Author

Thanks for the review!

@danscales danscales merged commit 416b4aa into master May 1, 2024
4 of 5 checks passed
@danscales danscales deleted the gtc-2651b branch May 1, 2024 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants