tbep-tech / hmpu-workflow Goto Github PK

4th category - proposed 'conservation' restorable

Include this dataset in counts for oyster bar acreages: https://geodata.myfwc.com/datasets/oyster-beds-in-florida/explore

Need to do union with SWFWMD subtidal layer to get total count, see email 7/6/23

Mostly have this done but need to do relative to categories in HMPU doc (e.g., subtidal, intertidal, supratidal and their subcategories). Product would be tables and alluvial plots as in existing land use HTML.

Need to figure this out, is it shiny apps? static maps? static tables? Might be really cool to do the latter two as embedded html on our website with routine builds on GH actions.

Create script for data that feeds current extent table (ES-3 in HMPU doc), will require LULC, conservations lands, and supp data.

Feature request: Realign group, class, habitat descriptor table rows to resemble the following format:
landuse_table_format_example.xlsx .

The FLUCCSCODES in the habitat descriptor categories of "Algae", "Patchy_Seagrass", "Continuous_Seagrass", "Tidal_Flats", "Estuary" should be removed from all the summary tables, and I think that will make the yearly totals more consistent to the total watershed area.

Salt_Barren acreages for 1990, 1995, and 1999 = 468, 479, 492 respectively. These were developed separately by ESA.

as the title implies...

Suggesting that the tab order be reversed, to start with simplest (group) and progress out to busiest (descriptor)

LTD,
Gmangrove

Create workflow for data feeding target progress table (ES-4 in HMPU doc), relies on all other workflows in #4, #5, #6, and #7

This could be a as a single script, pulling data from source, wrangling, and saving as RData file. Done exclusively for input datasets for the other workflows.

Static:

• Coastal stratum (from existing vector layer on T drive)
• Soils (from existing vector layer on T drive)
• TB watershed (from tbeptools)
• FLUCCS bins (already have it as csv)
• Salinity contours (0-18 in coastal stratum are Juncus, from existing vector layer on T drive)
• LULC data (all excluding most current)
• Seagrass data (most current)

Dynamic:

• Tidal tribs (not sure this is spatial data)
• Living shoreline (not sure this is spatial data)
• LULC data (most current)
• Seagrass data (most current)
• Hard bottom (not sure where this comes from)

Workflow for creating opportunities map (ES-1 in HMPU doc), an intermediate step to #6.

Use co/city boundaries here to reproduce tables/maps cropped to specific polygons

T:\05_GIS\BOUNDARIES\CitiesTBEP

Create workflow for maps of restoration potential by habitat type (Map 5-3 in HMPU but extended to all restoration types - protected/proposed/neither)

Reproduce table ES-3 from 2020 HMPU, related to issue 8. This rolls up from all intermediate data/maps.