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

Elevation data seems badly wrong #670

Open
sjakobi opened this issue Feb 11, 2024 · 3 comments
Open

Elevation data seems badly wrong #670

sjakobi opened this issue Feb 11, 2024 · 3 comments

Comments

@sjakobi
Copy link

sjakobi commented Feb 11, 2024

https://brouter.de/brouter-web/#map=14/51.1394/12.3867/osm-mapnik-german_style,Waymarked_Trails-Cycling&lonlats=12.376828,51.13994;12.400748,51.146846&profile=vm-forum-liegerad-schnell

image

I think the data is correct in so far, as the route has a lowest point around the border between Groitzsch and Neukieritzsch.

But from my experience cycling this route I seriously doubt that there is a gradient exceeding 3%. And there certainly isn't anything close to the 10–15% gradient shown in the elevation chart.

@quinncnl
Copy link

quinncnl commented Feb 12, 2024

Hi! Tracestrack Topo contour lines are generated from recent public LiDAR data in Europe. The hillshades are generated previously with SRTM and NASADEM data. See our data source at https://www.tracestrack.com/information/#data We'll regenerate the hillshade some time later this year.

@sjakobi
Copy link
Author

sjakobi commented Feb 12, 2024

@sjakobi I'm now quite positive #539 will solve your issue (albeit more in the medium term), so maybe close it as a duplicate?

I'm happy to hear that! If you don't mind, I'd prefer to keep this issue open, so we can check it's fixed once #539 has been implemented.

@quaelnix
Copy link
Collaborator

SRTM (3asec) LIDAR (1asec)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants