search

dams-mcda / Dams-MCDA

Emma Fox R/Shiny Project with a docker server configuration
1 stars 0 forks source link

Task 15 (Step 5: View Map Recommendation) #82

Closed elbfox closed 4 years ago

elbfox commented 5 years ago

New page called "Step 5: View Map Recommendation"; add a Maine map that matches the format of the map from Step 2 (Task 5), showing the location of each dam (post-MCDA decision) labeled with the name of dam and essential information about each dam, some coding (color or shape) will need to be added to show the decision alternative selected for each dam; try to show the size of fish habitat on the map as well; display the original map from Step 2 (Task 5) next to the results map so user can see the difference. This can be done in ggplot2 with maptools, RColorBrewer, rgdal, and spdep. Add download capability here.

elbfox commented 4 years ago

This page (tab needs to be created first) needs to dynamically pull the map from \maps using the fname reference. All the WSM script does is identify which map, it doesn't actually go into the file to get it. Maps are all ready to go, no edits necessary, just need to get the map to show up.

Maps to be shared over email.

sythel commented 4 years ago

added html container and logic to add map in branch RebuildWSM, there is a issue #118

elbfox commented 4 years ago

Is this a persistent issue? Looks to me like it works in CombinedPreferenceOutput branch. Let me know if we can close.

sythel commented 4 years ago

think this is all set. I haven't verified output is correct, but output is there.

elbfox commented 4 years ago

Right now, the output is actually incorrect, but we are aware of the issue. It's slightly off because the f_nrge dataset is outdated and doesn't match up to DamsData.csv. So, the "social criteria" (e.g. community identity, socio-environmental justice) are going to have different values between the two datasets. This is something that will get resolved once Sam re-runs the MOGA with the survey data (to be collected in a few weeks). I think we can close this issue and re-open after testing with more specific wording if the problem persists.