You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a planner/analyst, I would like to see the potential exposure and direct damage risk to proposed infrastructure assets/projects. I should be able to identify and view future projects on the map, with designed asset condition and vulnerability taken into account in the presentation of expected exposure and potential damages from the relevant hazard layer included in the tool.
Implementation idea: include these assets in the existing networks data (pack into the same features table and vector tile sets, or set up new "future" vector tile sets) with an additional attribute indicating "future/potential/planned" and possibly a portfolio/plan ID to group them. In the first instance, just visualise alongside current infrastructure. More usefully, add UI controls to filter current/potential or even (?) a separate sidebar section for potential.
The text was updated successfully, but these errors were encountered:
Early notes for this.
As a planner/analyst, I would like to see the potential exposure and direct damage risk to proposed infrastructure assets/projects. I should be able to identify and view future projects on the map, with designed asset condition and vulnerability taken into account in the presentation of expected exposure and potential damages from the relevant hazard layer included in the tool.
Implementation idea: include these assets in the existing networks data (pack into the same features table and vector tile sets, or set up new "future" vector tile sets) with an additional attribute indicating "future/potential/planned" and possibly a portfolio/plan ID to group them. In the first instance, just visualise alongside current infrastructure. More usefully, add UI controls to filter current/potential or even (?) a separate sidebar section for potential.
The text was updated successfully, but these errors were encountered: