[Feature Request]: Hazard Shoreline Interface(HSI) Data Entry
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Background
Populate HSI polyline attribute data/ relation with planning reach linkage, characterize the physical setting category, formulation priority; qualitative assesment of erosion, wave attack, and inundation susceptibility (H,M,L), & fluvial risk possibility (Y/N)
User Story
Spatially define & document hazard, hazard sources, and physical setting risk components within the SCT
Purpose
Identify Risk: develop & substantiate problems & opportunities / Define study objectives & constraints
Workflow
Roles include:
- Engineer
Requirements
No response
Misc. Notes
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue describes an HSI data-entry interface and spatial hazard information, but names no files, tests, entry points, or implementation requirements. Start by locating the SCT and existing HSI or shoreline data-entry workflow in the repository. Done should include the requested hazard attributes and planning-reach linkage, with the expected risk values documented and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100