Ripple Task Details: Ripple Boundary Service

[RobHanna-NOAA]

This separate service, currently called ras2fim Boundary service, needs to be upgraded and renamed to Ripple Boundary Service.

It simply each HUC8 feature from the WBD (.gpkg) which has ras2fim or Ripple data in it. It is not a live dataset and can be built quickly by hand.

The layer was calculated just one per ras2fim dataset release and loaded just once as static layer.

Rob can help or take care of this easily if desired. I already have the WBD and can make/get the HUC8 list.

Questions / Design topics:

• Ask Carson / Derek. I assume we update and rename the boundary service. We can have continue to it so show HUC8 boundary for where we have ras2fim or Ripple data. So..
  • Do we have a single layer which shows the attribute if it is from ras2fim or Ripple? So people can see which it came from? TBD:
  • What should we call the layer? (seeing as it has both ras2fim and Ripple HUC8 boundaries).
    • TBD: But likely Ripple Boundary Service

Development Tasks

• Make a csv (yes. csv) of HUC8s that are in ras2fim or Ripple. Note: Don't include any ripple HUC8s that also exist in ras2fim. We are keeping the ras2fim data and it takes priority over the Ripple collection data for any given HUC. We have most of the data already, just have to turn it into a list of HUC8, ras2fim/Ripple flag. Note.. this list can likely be used in other ways including in live HV services.
• Use the current FIM WBD_national.gkpg -> HUC8 layer. Do this by hand as it is a one-off just in arc / qgis. Create a new gpkg / shape file that only the applicable HUC8 features. Reproject to 3857 and then the new dataset is ready to load into HV
• Look in code for places where we can rename the service. Note: See Question about rename of service and extra attribute for ras2fim or Ripple field.
• Update the git code for uploading the new dataset (which also needs likely renaming and adjusting).

[RobHanna-NOAA]

Talked to Monica:

• She was fine with it being called Ripple Boundary Service, super easy fix.
• The question becomes... do we want the users to know that some of that boundary service data (aka. FIM 10 which is from ras2fim) and FIM 30 comes from Ripple. Note.. Ripple / RTX did not include FIM 10 HUCs, only just FIM 30 - FIM 10 hucs.
  - If we do want the users to know that the boundary service does want to know if it came from ras2fim versus Ripple.... then we have two more options:
  - Separate layers for ras2fim versus Ripple..... OR
  - Just a meta data field
• Also.. right now ras2fim Boundary service has no meta data, so no popup.
• Do we want to add meta data and a popup? Maybe for this ras2fim/ripple and/or maybe HUC name?
• She will talk to WPOD to see if they have some thoughts.

Derek / Carson: Thoughts?