Bug in the web App
In Progress
If the user is planning a hiking track everything above 2000 m above sea level is not displayed in the track profile. The window of the profile also can not be dragged up to see the highest point. See screenshot attached
Hi Antal, thanks for your report. The most likely reason why this is happening is noise in data recorded from the Earh orbit. We do not promise a quick fix, but we do consider another datasets. Radim
Hi Antal, thanks for your report. The most likely reason why this is happening is noise in data recorded from the Earh orbit. We do not promise a quick fix, but we do consider another datasets. Radim
Replies have been locked on this page!