-
Notifications
You must be signed in to change notification settings - Fork 7
Design Meeting Internal February 4, 2021
- Jamie H.
- Murray J
- Joost v.
- Tiegan H.
- Karolina P.
- Drew R.
- Will C.
- Malaika U.
- Nicky H.
- Sahar S.
- Philip L.
- Vanessa G.
Jamie: By Hazard Section Focus for today
- Tiegan: where does the scenario catalogue sit? Is it in the by Hazard section? Should we put it in another tab?
- What is the scenario catalogue:
- Good for tabletop exercise
- Finance using them for their regulatory framework
- We only have them for earthquake
- Murray - the other hazards can be thought of as scenarios
- Phil: fundamentally, we are trying to communicate who and what is exposed
- Jamie: we have to be realistic about what we can accomplish with time and budget
- Tiegan: maybe the scenarios can just be a map layer…
- Jamie:
- Risk Scenarios
- Hazard Scenarios
- Earthquake scenarios
- Murray: concerns about creating a design that the data can support
- What is the scenario catalogue:
- Decision: By Hazard is the deep-dive, a dashboard-type experience
- Tiegan: worried that we are going to have some duplication between Muni and By Hazard view
- Murray: we have some data in maps, some in charts so we need to plan for that, so the by hazard is probably best as a dashboard-type experience
Chat notes:
09:01:10 From Malaika U. to Everyone:
Do we want to have the scale on the bottom for the probability of a damaging earthquake? I think the number is great, but when you put it on a 1 to 100 scale, it changes perception. For example, 38% in 50 years is really high, but when you put it on the scale you assume that close to 100 is really high and it makes 38% seem low... Does the team agree, and can we remove the scale?
09:12:41 From Malaika U. to Everyone:
I love it! This supports targeted action.
09:13:51 From Nicky H. to Everyone:
I agree with you Malaika - I like how this approach supports sensible decisions by understanding the drivers of risk
09:15:51 From Tiegan H. to Everyone:
I like this a lot, especially in the By Municipality section, actually. It really brings that section to life... Maybe we would also want to be a little cautious in the ‘driving factors’ to make sure that we’re not purporting to have all of the answers for all of the hazards, but this is a really amazing solution for earthquakes.
09:16:21 From Tiegan H. to Everyone:
Or maybe that’s what you meant, Murray, about the part that we can figure out on our own.
09:24:54 From Malaika U. to Everyone:
And there needs to be clear and easy navigation between the 2 sections.
09:30:59 From Nicky H. to Everyone:
I am assuming that there will also be a narrative as well to explain the intended use, including limitations for the information portrayed in the maps and charts.
09:36:02 From Philip L. to Everyone:
that's a pretty cool solution Murray.
09:41:26 From Karolina P. to Everyone:
Including the number of people makes the information so much richer. I don't think it's too complicated at all.
09:46:29 From Nicky H. to Everyone:
I really like the way this is progressing - using the maps to inform strategies and action
Wikis: data | model-factory | opendrr-api | opendrr | python-env | riskprofiler-cms