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

[SCT-EAD]: Geospatial visualization of the EAD points #114

Open
trietmnj opened this issue Oct 7, 2024 · 1 comment
Open

[SCT-EAD]: Geospatial visualization of the EAD points #114

trietmnj opened this issue Oct 7, 2024 · 1 comment
Assignees

Comments

@trietmnj
Copy link
Contributor

trietmnj commented Oct 7, 2024

b) Visualize the EAD points. Four styling views should be available-

i. Aggregated damages view with styling for each point scaled according to the magnitude of the total EAD damage (sum of structure and contents damage). The current prototype should have a rudimentary implementation of this view.
ii. Inundation hazard view. The styling for each point should scale according to the modeled value of inundation depth available from the furnished dataset.
iii. Wave attack hazard view. If the point is subjected to wave action, its significant should be clearly visualized. The wave action and its significance for each EAD point can be identified from the furnished dataset. Wave height value less than 0 ft means no wave action, 0-3 ft means medium wave action and any higher indicates high wave action.
iv. Erosion hazard view. Erosion can be identified if the point lies within the user-uploaded erosion polygon.

@trietmnj trietmnj changed the title [SCT-EAD]: Visualize the EAD points [SCT-EAD]: Geospatial visualization of the EAD points Oct 7, 2024
@tyler-siskar tyler-siskar self-assigned this Nov 12, 2024
@tyler-siskar
Copy link

You have two options for filtering - (1) the H_ variables, as mentioned previously, which could work with the hazards-based view like ii and iii, and (2) modeled output attributes, which for EAD would be the C_ and S_ variables (and O_ and U_ for LL) which should be the best option for the modeled based view like i. The H_ filter is too unreliable for i because there might be data at all points.

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

No branches or pull requests

2 participants