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

Show cone of uncertainty, path, and affected areas for GDACS, WFP ADAM and PDC #1265

Open
14 of 16 tasks
udaynwa opened this issue Jul 17, 2024 · 6 comments
Open
14 of 16 tasks
Assignees
Labels
DFS DFS team works on it type: epic Groups multiple user stories. Can be grouped under a theme.

Comments

@udaynwa
Copy link

udaynwa commented Jul 17, 2024

Task background

We have the data related to the cone of uncertainty, path, and affected areas for GDACs, PDC, and WFP ADAM, but currently, we are not showing them in the Risk Module in the GO platform.

Behavioral and implementation details

Development tickets

Review fixes (based on Justin and Mariam's review on 30.10.2024):

  • Map legend: Delete the word "Map" from "Map Sources" so that it just reads: "Sources"
  • In the pop-up box for GDACS storms, where it currently says "Source: [JTWC, or NOAA or other]" let's replace "Source:" with "Forecast provider:"
  • In the pop-up box for both PDC and for GDACS, replace "Exposed area" with "Exposed area to tropical storm or cyclone strength wind"
  • In the pop-up box for both PDC and GDACS where it says "Severity" : 1) first change the text to "PDC Severity" or "GDACS Severity"; and 2) add a tool tip with a link to the source
  • In the colouring of the exposed area, does this apply to future exposure, past exposure or both? At the moment, it's unclear and we need to make it clear whether its one, the other or both.
  • For storm position (at a specific date and time) as denoted by dots: this is currently not working for either the PDC or GDACS events -- nothing happens when you click on the dots
@udaynwa udaynwa assigned frozenhelium and tnagorra and unassigned frozenhelium Jul 17, 2024
@udaynwa udaynwa changed the title Show cone of uncertainty, path, and affected areas for GDACS and WFP ADAM Show cone of uncertainty, path, and affected areas for GDACS, WFP ADAM and PDC Aug 5, 2024
@udaynwa udaynwa assigned samshara and puranban and unassigned tnagorra Aug 5, 2024
@udaynwa
Copy link
Author

udaynwa commented Aug 5, 2024

Related to: #1013

@justinginnetti
Copy link

justinginnetti commented Sep 4, 2024

Feedback on GDACS tropical cyclones/storms:

  • Replace "Source:" with "Forecast Source:"
  • Replace "Alert Type:" with "GDACS Alert Level"
  • Replace "Track" with "Forecast track"
  • Replace "Buffer" with "Windspeed buffer"
  • Replace "Nodes" with "Position of storm"
  • Add the "time stamp" to each of the locations of the points (i.e., "nodes") related to the position of the storm
  • For the "nodes" replace the triangles with the icon for the cyclone or just a dot if we can't do the icon
  • To do: Find out from GDACS what the "track" represents (for example, the "most likely" track or something else?), and then we will have to update the label accordingly.
  • Under the "buffers" toggle: Specify "GDACS Red Alert Level" "GDACS Orange Alert Level" and "GDACS Green Alert Level"

@puranban
Copy link
Contributor

puranban commented Sep 5, 2024

Add the "time stamp" to each of the locations of the points (i.e., "nodes") related to the position of the storm

For this @justinginnetti , trackdate is missing in the current source. But there is seems to be another resources available in the GDACS system, so we will be trying to scrape the trackdate from there and soon update the cyclone timestamp in the visualization if it works.

Under the "buffers" toggle: Specify "GDACS Red Alert Level" "GDACS Orange Alert Level" and "GDACS Green Alert Level"

I think this one conflicts with the earlier feedback where you mention Replace "Alert Type:" with "GDACS Alert Level". Do we specify each alert level also as GDACS Red Alert Level, GDACS Orange Alert Level and such?

Besides these, we have incorporate other mentioned feedback along with some more improvements for GDACS, and pushed it to the Alpha 3 instance.

@udaynwa
Copy link
Author

udaynwa commented Nov 7, 2024

@justinginnetti @mariam-yu , replying to the requested review fixes:

  • In the pop-up box for both PDC and GDACS where it says "Severity" : 1) first change the text to "PDC Severity" or "GDACS Severity"; and 2) add a tool tip with a link to the source
    • We need to revisit the labels for GDACS and PDC
      We don't have "Severity" displayed on PDC
      "Severity" in GDACS is showing wind speed / category instead.
      "Alert Type" is actually showing "Alert Level" which is closer to "Severity"
  • In the colouring of the exposed area, does this apply to future exposure, past exposure or both? At the moment, it's unclear and we need to make it clear whether its one, the other or both.
    • We do not have different exposures for future or past. We just have single exposure data that we fetch from GDACS, PDC
  • For storm position (at a specific date and time) as denoted by dots: this is currently not working for either the PDC or GDACS events -- nothing happens when you click on the dots
    • Currently, we do not have much information from the sources to display on the popup

cc @frozenhelium @tnagorra

@tnagorra tnagorra added type: epic Groups multiple user stories. Can be grouped under a theme. DFS DFS team works on it labels Nov 21, 2024
@justinginnetti
Copy link

Let's have a quick, sync call on the pending items, @udaynwa just to triage which we can fix now, and which we will save for later.

@udaynwa
Copy link
Author

udaynwa commented Nov 25, 2024

Sure, @justinginnetti . Would you like to meet 30 minutes before GO check-in tomorrow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DFS DFS team works on it type: epic Groups multiple user stories. Can be grouped under a theme.
Projects
None yet
Development

No branches or pull requests

6 participants