Skip to content
This repository has been archived by the owner on Jun 30, 2023. It is now read-only.

Add field species_most_affected field to the eventsummary endpoint response #489

Closed
BlakeDraper opened this issue Jun 8, 2021 · 5 comments
Assignees

Comments

@BlakeDraper
Copy link

This field will need to calculate which species within the event has the most individuals affected. In other words, it will need to add up the cumulative affected count for each locationspecies, compare across the whole event, and provide the species with the highest total affected count (ideally the whole species object, but can also work with just the species ID if necessary).

Background: the report currently calculates "Species Most Affected" by counting the total instances in which that species appears, which is misleading. Meaning: white-tailed deer may be present at 5 different event locations, with one dead each, where brown bat appears at only 2 event locations, but with 300 dead at each. Brown Bat is the most affected, obviously, but the current count method would say the deer. I cannot calculate the actual cumulative count on the client with this summary response, because the needed data detail is not there. Therefore kicking it to the server.

@aaronstephenson
Copy link
Contributor

Would this field be available to the public, or just to the owner + org + collab, or just admins?

@BlakeDraper
Copy link
Author

Available to public

@aaronstephenson
Copy link
Contributor

Field added in 30225b8 and deployed to the test environment.

@BlakeDraper
Copy link
Author

Hold off on promoting this to prod. See (USGS-WiM/whispers#1197) for details.

@aaronstephenson
Copy link
Contributor

Removed in e93568f.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants