USACE / USACE/go-consequences

Reprojection on the fly

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

@HenryGeorgist is already working on this.

Since Jun 16, 2021.

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

Description

The NASS data raw data projection is EPSG 5070, the NSI raw data projection is 4326. It is inevitable that depth grids supplied may not match those EPSGs which would cause inappropriate interpretation of the intersection of hazards and consequences receptors.

Describe the solution you'd like
We need to determine a strategy to reproject data to match. Maybe the solution is to reproject the consequence receptors to the hazard providers on the fly. Unfortunately this would likely be a lot of gdal calls at the innermost loop of the compute.

Another option is to blow up if data is not provided in the right projection for a consequence receptor... that would be bad if someone wants to do an ag and structure damage compute...

Since we allow for user provided structure inputs, we also potentially open our selves up to projection issues with the consequence providers not being in 4326 for the structures.

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.