USACE / USACE/go-consequences

Consequences Receptor only allows for Point Locations, not polygons

Open
#54 0 comments 0 reactions 1 assignee View on GitHub

@HenryGeorgist is already working on this.

Since Jun 13, 2021.

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

Description

When computing losses for some consequences receptors they may need a more complex geospatial relationship than a point. This means we need to allow for flexibility in the geometry utilized to connect a hazard to a receptor. @slawler found this issue when trying to use building footprints to define the hazard at a structure.

This advancement will be required for erosion at structures, so this will become critical path soon.

Describe the solution you'd like
Adding an interface or two in the geography package for points polygons and lines might be useful. It is hard to say what is appropriate, we shouldnt reinvent the entire feature, features, etc interface structure in gdal.

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.