Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dem::Elevation(double _x, double _y) does not handle NoData values #607

Open
Ryanf55 opened this issue May 10, 2024 · 0 comments
Open

Dem::Elevation(double _x, double _y) does not handle NoData values #607

Ryanf55 opened this issue May 10, 2024 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@Ryanf55
Copy link
Contributor

Ryanf55 commented May 10, 2024

Environment

  • OS Version: Ubuntu 22
  • Source or binary build?
    Binary

Description

  • Expected behavior: The following call exposes information on whether the data is "NoData" values, which happens over the ocean in some terrain:
    • Dem::Elevationpublic: double Elevation(double _x, double _y);
  • Actual behavior:
    • It returns a double value, which may be the NoData value. This can silently return the NoData value, and if run against physics, could be a situation where the physics mesh is in the wrong location. For a path planner, this could mean you think terrain is safe and it's ok to fly inside a body of water and not collide with it.

Steps to reproduce

I"ll find a representative dataset shortly and create a minimum reproducible example.

  1. Load terrain with NoDat

Output

TBD

@Ryanf55 Ryanf55 added the bug Something isn't working label May 10, 2024
@azeey azeey added the help wanted Extra attention is needed label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
Status: To do
Development

No branches or pull requests

2 participants