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
Tony is excited about "including point of use water rights data" in WaDE. Once we load at least one state POU data, let's look into how to support it in the RShiny app. I think we are encoding the POU geometry in the site's table using WKT format. Now, how do we create a layer out of that format across the states? Once we do, how could we relate the POU(s) shape and POD points(s) in the app? e.g., if a user selects a POD of interest, how would they know where it's POU shape(s)? that would be pretty interesting to show for the Colorado River as in this example. I think a POU can be a point too, not just a polygon.
Tony is excited about "including point of use water rights data" in WaDE. Once we load at least one state POU data, let's look into how to support it in the RShiny app. I think we are encoding the POU geometry in the site's table using WKT format. Now, how do we create a layer out of that format across the states? Once we do, how could we relate the POU(s) shape and POD points(s) in the app? e.g., if a user selects a POD of interest, how would they know where it's POU shape(s)? that would be pretty interesting to show for the Colorado River as in this example. I think a POU can be a point too, not just a polygon.
https://uagis.maps.arcgis.com/apps/opsdashboard/index.html#/8502820c41374e6eb35fd90a2ffb656a
The text was updated successfully, but these errors were encountered: