search

UGS-GIO / wetlands

UGS Wetlands web application that compiles a large data set of Utah wetlands data and displays is on an interactive web map
https://geology.utah.gov/apps/wetlands/index.html
0 stars 0 forks source link

We would like to redo how the Wetland and Riparian mapping data show up on the map #61

Closed wetlandsDiane closed 1 year ago

wetlandsDiane commented 1 year ago

Why do you feel this application needs what you're requesting?

We want the data to more closely mirror the data that comes directly from USFWS instead of processing the data and having our own version on the webpage. Ideally, we will use data from the USFWS web map services so we no longer have to update the data at all so we never have to worry about having an out-of-date version on the website and there will be less work for us moving forward.

we would also like to know whether there is anything that can be done to speed up the time it takes to load the data.

Describe the solution you'd like and why it builds value

We want to do the following:

  1. Remove the "Wetlands Outline" feature from the mapper; we have found that this isn't being used
  2. Evaluate whether there are optoins to get the data to load faster
  3. Investigate what it would take to get data straight from USFWS for the data. You can find more info here: https://www.fws.gov/program/national-wetlands-inventory/web-mapping-services

If you get the data straight from the web mapping services, I am not sure what kind of processing you can do with the data or if you have to just display the data as-is. If possible, one thing we would like to see is some kind of spatial join to link the "IMAGE_YR" field from the wetlands metadata to the wetlands polygons. We would also like to see the riverine features still separated out from the other features and the metadata dissolved by image year and put into groups based on the decade of mapping.

We can provide more detail on the fields we would like in each layer and in the pop-ups, etc. if you let us know first what is possible and easy to do

What impact will this new functionality have on this application's audience?

These changes will ensure that the data on the app are always up-to-date. The data will also be less confusing for the audience b/c it will be more similar to the USFWS data that these data are based on.

The new functionality will also save time for UGS in the long-run b/c we wont have to process the data twice per year and push up the updates.

How Urgent is this?

Medium

Please provide additional evidence from other users to support medium and high ranking

I wrote app updates into one of our grants and you should bill UW21 for time spent making these updates.

I get maybe 3 or 4 calls per month from people who use the app to find out information about where wetlands are on in Utah and countless others likely use the map to get the data and don't follow up with a call. Some of these people are likely inadvertently looking at out-of-date data b/c the data aren't updated immediately after the USFWS makes an update.

I have attached an email chain from a consultant who couldn't find the riparian data for Cache County b/c our app wasn't updated yet, though the data were available through USFWS.

State of Utah Mail - Cache County Riparian Data.pdf

jjhi11 commented 1 year ago

This is implemented except for the spatial join. This will need to be worked on and probably not something that will be done in time for maps on the hill.

wetlandsDiane commented 1 year ago

Here is the information for the changes to be implemented for the next round of new wetlands data.

The new spatial layers can be found here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\nwi_update.gdb. You can ignore the layer just called "wetlands" and just work with the wetlands_riverine and wetlands_nonriverine files.

Info on which fields to show and how to format the pop-ups U:\GWP\Wetland\websiteAndApps\mapApplication\newFields.xlsx; note that there are two tabs here. These tabs show the fields that should show up in the pop-ups, how the fields should be labeled in the pop-up and the text that should show up when you hover over the field names. We could also get rid of the hover notes if they are too long.

I would also like to add this text to the pop-up box if possible: Visit the Wetlands Code Interpreter (with hyperlink https://fwsprimary.wim.usgs.gov/decoders/wetlands.aspx) for help interpreting the Cowardin Attribute Code.

Last, right now we have some custom text for the legend for the wetlands layer. The text says "Lake (including playa lakes)" Can we change this back to just saying "Lake" to match the field that the legend is pulling from here?

The goal with these changes is to hopefully have a verison of the app with these changes ready when the next round of NWI data is updated, approximately May of this year.

Thanks!

wetlandsDiane commented 1 year ago

Here is the second parts of the updates that we talked about the other day.

The goal is to take the spatial data from NWI, clip each of the four layers by the boundary file, and then process through code similar to the script I will share to produce the data for the update. Ideally we will be able to turn this around in a week or less. If we find that it will take longer than this, than it might make more sense for us to stick to a workflow similar to what we had in place before, where I download the data for the state, process through my scripts and then provide the results to the database manager who just has to replace the old data.

The boundary file is here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\nwi_update.gdb\data_boundary

The script I used to process the data is here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\UpdatingNwiData.py

The input data I used in the script is here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\UT_geodatabase_wetlands.gdb

I also used a file that shows the boundary of where LLWW is available. I took that boundary file from here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\nwi_update.gdb\llww_boundary_file, but the same file should also be somewhere on the SDE b/c that LLWW boundary layer also shows up in the map application.

This component is a lower priority than updating the fields and pop-ups that show up in the mapper but it would certainly be great to have a smooth workflow to take the data from NWI, process it, and then display it on the mapper.

It would be great to get a time estimate for how long it will take to implement this component, so we can think about that in terms of our grant budget.

Thanks

nmpayne commented 1 year ago

Awesome I will start looking at the code.

wetlandsDiane commented 1 year ago

@jjhi11 @nmpayne

Hello,

Looks like there is now new data available from NWI. The goal had been to have a new version of the app ready so that when new data were available, we could process the data with the new script Nate and I developed and then get the data into the app right away. Jay, have you had a chance to implement the changes? I will list them below again for your information.

The data will have new fields added to them. You can see an example of what the data will look like here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\nwi_update.gdb. You can ignore the layer just called "wetlands" and just work with the wetlands_riverine and wetlands_nonriverine files.

Info on which fields to show and how to format the pop-ups U:\GWP\Wetland\websiteAndApps\mapApplication\newFields.xlsx; note that there are two tabs here. These tabs show the fields that should show up in the pop-ups, how the fields should be labeled in the pop-up and the text that should show up when you hover over the field names. We could also get rid of the hover notes if they are too long.

I would also like to add this text to the pop-up box if possible: Visit the Wetlands Code Interpreter (with hyperlink https://fwsprimary.wim.usgs.gov/decoders/wetlands.aspx) for help interpreting the Cowardin Attribute Code.

Last, right now we have some custom text for the legend for the wetlands layer. The text says "Lake (including playa lakes)" Can we change this back to just saying "Lake" to match the field that the legend is pulling from here?

I am hoping to process the new data and get it to Nate by early next week. I am hoping we can update our mapper with the latest data ASAP. Looks like the NWI update was actually made a month ago, but I never received the usual email letting me know about the updates.

Let me know if you foresee any issues with making these updates in the next few weeks and getting the latest data out on the mapper.

Thanks

jjhi11 commented 1 year ago

@wetlandsDiane

I should be able to get on this soon after Nate has the data published. Nate is out of town next weds-friday

wetlandsDiane commented 1 year ago

Thanks! I just realized that NWI seems to have removed the "DATA_SOURCE" field in the latest version of the metadata. I am checking with NWI to see if this is a permanent change and will get back to you.

Nate, the data linked here are from the older version that I created a few months ago. I should have the latest version ready to go Monday. It is fine if you push the oldest version up first so that Jay can work on making the code changes, but just keep in mind you will need to replace that data with the new data. The two data layers should be identical except maybe not with the DATA_SOURCE field!!

wetlandsDiane commented 1 year ago

@nmpayne

The latest version of the NWI data can be found here: U:\GWP\Wetland\websiteAndApps\mapApplication\spatialData\nwi_update_2023\finaloutputs_202306.gdb.

These data are not exactly the same as what is currently in NWI and have all the field changes that we anticipate moving forward except the DATA_SOURCE field (see below).

I reached out to NWI to see what happened with the DATA_SOURCE field and to explain why we at UGS find that field useful. That field was in older version of the data but was not in the latest version. They said they aren't sure why they removed the field and will have some internal discussion to decide whether to add that field back in.

For now, I think we should proceed without the DATA_SOURCE field with the understanding that we may add that field back into the data in the future if NWI makes it available again.

Nate, I know you are headed out of town and might not be able to get the data published right away. Can you give me an ETA on getting these data published?

Thanks

wetlandsDiane commented 1 year ago

Also, just a reminder that you can bill UW21 for any work you do on this task. Thanks!

nmpayne commented 1 year ago

I'm planning on publishing tomorrow (June 27th) before I leave.

wetlandsDiane commented 1 year ago

Sounds great, Nate!

On Mon, Jun 26, 2023 at 4:18 PM Nate Payne @.***> wrote:

I'm planning on publishing tomorrow (June 27th) before I leave.

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1608396489, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTQY6TMAZKOE762LUZLXNIDFBANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

wetlandsDiane commented 1 year ago

Hello,

I wanted to check in on the status of this work. Nate, did you get the new data published? Jay, do you have an estimate of when you will be able to implement the changes and get the new data displayed on the mapper?

As a reminder, you can bill UW21 for this work.

Thanks

jjhi11 commented 1 year ago

Hey @wetlandsDiane I should be able to get to it next week. Nate has the data published already

wetlandsDiane commented 1 year ago

Awesome, thanks! Keep me posted if any questions come up

On Thu, Jul 13, 2023 at 12:49 PM Jay Hill @.***> wrote:

Hey @wetlandsDiane https://github.com/wetlandsDiane I should be able to get to it next week. Nate has the data published already

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1634730577, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTS6OZONN3IS4VLGAZDXQA7KDANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

jjhi11 commented 1 year ago

@wetlandsDiane @marshallrobinson The app is ready for review here https://geology.utah.gov/apps/wetlands/review/

wetlandsDiane commented 1 year ago

Thanks Jay! I will take a closer look at this but I noticed a few things right away.

The version of the app does not have some of the other changes you recently implemented, including

  1. removing the boundary and wetland dependent species layers
  2. change the name of some of the wetlands layers, such as changing Wetland Metadata to Wetland Project Informatoin
  3. Adding in the Additional Attributes layer under the wetlands and riparian mapping section.

Did you build the changes on an older version of the app?

Thanks

On Tue, Jul 18, 2023 at 2:22 PM Jay Hill @.***> wrote:

@wetlandsDiane https://github.com/wetlandsDiane @marshallrobinson https://github.com/marshallrobinson The app is ready for review here https://geology.utah.gov/apps/wetlands/review/

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1640942508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTQO674B72FZWNXN27TXQ3V7PANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

jjhi11 commented 1 year ago

Uh oh that is what I did. I see that branch was never merged. No problem. I'll get these changes moved into that branch and set up for review again.

wetlandsDiane commented 1 year ago

Awesome, thanks!

On Tue, Jul 18, 2023 at 3:12 PM Jay Hill @.***> wrote:

Uh oh that is what I did. I see that branch was never merged. No problem. I'll get these changes moved into that branch and set up for review again.

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1640998934, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTT6JFZKOR433IZYEELXQ334HANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

jjhi11 commented 1 year ago

ok @wetlandsDiane @marshallrobinson should be good now.

wetlandsDiane commented 1 year ago

Hi Jay,

I found a few issues, hopefully all pretty minor to fix.

There is one issue still in comparing the review version to the current version of the webpage.

-

Under wetland mapping: Wetland Metadata should be changed to Wetland Project Information

Under riparian mapping: Riparian metadata should be changed to Riparian Project Information

For wetland metadata, it used to be that features with "Null" values showed up as grey. Those areas now have "Unknown" in the decade field instead of null. Can you update that in the legend and hopefully that will make the grey areas reappear on the map.

Some changes for the pop-ups for both wetlands (non-riverine) and riverine

-

Additional Attributes available field appears incorrect- should be yes or no, not a year; is the data incorrect or are you just referencing the year field twice?

When you hover over Image Year, text says “Image of imagery...” should say “Year of imagery....”

For the hover text, change Wetland Type to Wetland type

Visit the Wetlands Code Interpreter https://fwsprimary.wim.usgs.gov/decoders/wetlands.aspx for help interpreting the Cowardin Attribute Code.

  Every time this shows up, turn the last word to lower case- code
  instead of Code
  -

For the Wetlands (non-riverine), can you change the legend so that it says “Wetland type” instead of WETLAND_TYPE?

For the riparian mapping pop-ups

-

For the Riparian Type field, add hover text that says “Riparian type”

Add image year field with the correct hover text after acres

For both the riparian and wetland project info files

-

Add hover text that says “Link to supplemental mapping report”

Update text at the top of the box to say Wetland Project Information and Riparian Project Information

Thanks!

On Wed, Jul 19, 2023 at 6:48 AM Jay Hill @.***> wrote:

ok @wetlandsDiane https://github.com/wetlandsDiane @marshallrobinson https://github.com/marshallrobinson should be good now.

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1642022548, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTSVW6OB3ZKSYT7E3NDXQ7JSJANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

wetlandsDiane commented 1 year ago

Hi Jay,

I just found at that the wetlands code interpreter no longer works and likely won't for some time.

Can you remove the text that says: Visit the Wetlands Code Interpreter (with hyperlink https://fwsprimary.wim.usgs.gov/decoders/wetlands.aspx) for help interpreting the Cowardin Attribute Code.

Thanks

jjhi11 commented 1 year ago

Ok. Working on the others now.

jjhi11 commented 1 year ago

@wetlandsDiane These changes should all be done now except for the WETLAND_TYPE title in the legend. If this must be done I can start code for a custom renderer. It will just take a few more hours.

wetlandsDiane commented 1 year ago

Jay, Is there a new version of the map I should be looking at? I don't see the expected corrections here: https://geology.utah.gov/apps/wetlands/review/. I tried refreshing using ctrl+F5, but still didn't see the fixes.

Thanks

On Tue, Jul 25, 2023 at 2:33 PM Jay Hill @.***> wrote:

@wetlandsDiane https://github.com/wetlandsDiane These changes should all be done now except for the WETLAND_TYPE title in the legend. If this must be done I can start code for a custom renderer. It will just take a few more hours.

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1650516929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTUTYSJGNU5WM5DODF3XSAUQLANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

wetlandsDiane commented 1 year ago

Thanks Jay!

I reviewed the app again and the changes look good. Can you explain to me what would need to happen to change how WETLAND_TYPE is displayed in the legend so I can decide whether it is worth pursuing that update?

Also, two things regarding the Wetland Project Information features that have Unknown in the decade field. First, can you update the legend to show the phrase "Unknown" instead of ? And, second, for the popups, can you just show two fields for those sites- Image Decade and Supplemental Map Info?

Thanks

On Mon, Jul 31, 2023 at 8:14 AM Diane Menuz @.***> wrote:

Jay, Is there a new version of the map I should be looking at? I don't see the expected corrections here: https://geology.utah.gov/apps/wetlands/review/. I tried refreshing using ctrl+F5, but still didn't see the fixes.

Thanks

On Tue, Jul 25, 2023 at 2:33 PM Jay Hill @.***> wrote:

@wetlandsDiane https://github.com/wetlandsDiane These changes should all be done now except for the WETLAND_TYPE title in the legend. If this must be done I can start code for a custom renderer. It will just take a few more hours.

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1650516929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTUTYSJGNU5WM5DODF3XSAUQLANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

jjhi11 commented 1 year ago

I would need to create a custom renderer in the code. I'm guessing 3-5 hours.

Should the riparian project information popup follow these changes as well?

wetlandsDiane commented 1 year ago

Lets go ahead and do the custom renderer to change how WETLAND_TYPE is displayed.

Regarding changes to the pop-up for the riparian data, all of that data is more up-to-date, so there shouldn't be any blank or unknown values. You could make the same changes if you want if that is simple, but it shouldnt' make a difference in the display.

Thanks

On Mon, Jul 31, 2023 at 9:43 AM Jay Hill @.***> wrote:

I would need to create a custom renderer in the code. I'm guessing 3-5 hours.

Should the riparian project information popup follow these changes as well?

— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/wetlands/issues/61#issuecomment-1658628388, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3KRTWTDQ2TFVASJSSJBOTXS7HBXANCNFSM6AAAAAASAI25X4 . You are receiving this because you were mentioned.Message ID: @.***>

--

[image: Photo] [image: Facebook icon] https://facebook.com/UTGeologicalSurvey[image: Twitter icon] https://twitter.com/utahgeological[image: Instagram icon] https://www.instagram.com/utahgeologicalsurvey/[image: LinkedIn Icon] https://www.linkedin.com/company/utah-geological-survey

Diane Menuz State Wetlands Coordinator O: (801) 538-7436 E: @.***

Utah Department of Natural Resources Utah Geological Survey

geology.utah.gov

jjhi11 commented 1 year ago

Sounds good. I'll get on it this week.