USACE / USACE/go-consequences

Add CHS Save Point hazard provider

Open
#109 2 comments 0 reactions 1 assignee View on GitHub

@HenryGeorgist is already working on this.

Since May 18, 2023.

enhancement
Dominant language
Go
Stars
21
Forks
12
Avg merge
2d 10h
Merged PRs (30d)
4

Description

Is your feature request related to a problem? Please describe.
Save points are less dense than nodal data - adding a provider that handles this difference in density is necessary.

Describe the solution you'd like

  1. add areas that relate to the save points to know which save point is valid for a structure
  2. add ability to leverage nearest neighbor to set the save node for a structure.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.