8000 Terrain data faults · Issue #413 · orbitersim/orbiter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Terrain data faults #413

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.

Sign up 8000 for GitHub

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

Jump to bottom
Open
GLS-SSV opened this issue Jan 15, 2024 · 1 comment
Open

Terrain data faults #413

GLS-SSV opened this issue Jan 15, 2024 · 1 comment

Comments

@GLS-SSV
Copy link
Contributor
GLS-SSV commented Jan 15, 2024

(issue originally posted in the old O-F tickets)

There some terrain issues in Madeira Island:
madeira_terrain_fault_1
madeira_terrain_fault_2

Looking at the terrain data, some isolated "elevation points" have obviously wrong values, leading to those peaks in the sim.
I don't know if these faults are present in the original raw data, or if they are the result of the conversion into tiles.

A possible way to find other such issues would be an offline script or program, that would flag elevation points when their value differs from adjacent points by more than some threshold.
@n7275
Copy link
Contributor
n7275 commented Jan 22, 2024 •
edited
Loading

This would be a good first thing to check in our elevation data:
image
PlanetTextures.pdf p.9 (2016)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@n7275 @GLS-SSV
0