Hi,
This is relating a bug when viewing the elevation profile on the website. Let's take this previously done journey as an example: https://cycle.travel/map/journey/153632.
When looking at the elevation profile, on day 5, leaving quaint Frelighsburg, you notice there's a huge climb, perfect to showcase the bug in question. Point the mouse cursor to where the beginning of day (on the elevation profile) crosses the actual elevation at that point. You have the tooltip (popup) that shows an elevation of around 105 m, depending where exactly you point. Now, carefully move the cursor up and the tooltip will show a higher elevation, without even moving the cursor on the X-axis. It will show the elevation of where the cursor is at, regardless where the actual route passes.
That said, I realized you can't make the tooltip give you a lower reading if you bring the cursor down on the Y-axis below the actual route. So at least there's a way to confirm the elevation. Still, it would be nice if the reading didn't change as long as you stayed on the same Y-axis. I know this is probably a really complicated thing to code! Let me know if you need more information.
Thank you again for making such a great website!
Comments
Chinook,
In my experience, once the cursor is away from the (top) line representing elevation it gives no data. In other words, are you sure that there is no movement along the x-axis? I can't manage it on such a small scale.
Given the length of the route, I wonder if the issue may be clarified by either zooming the elevation profile or saving the route as individual days. Then the elevation profile is not so compact.
Here is the default view of the elevation of your route:
Now, here is the profile for the appropriate day having zoomed the elevation profile in:
Apologies if I'm misunderstanding something, but it seems to me that the profile & tool are working exactly as they should.
I took the time to test out the zoomed in elevation profile and it appears much less problematic. However, I also enabled the mouse accessibility settings in Windows where I can move the cursor with the number pad. And I can confirm the problem I mention does exist, when I move the cursor with the number pad in a vertical fashion.
I think it’s finding the nearest point on the graph to your mouse cursor, and giving the readout for that. So if you move the cursor upwards, then it might be a distance of (say) 2 pixels to the hill on the right, or 5 pixels to the point below, so it chooses the former.
Unfortunately this is part of the third-party chart library (Flot) that draws the elevation graph, and as such not something I’m able to change without digging into, trying to understand, and rewriting someone else’s code – sorry.
That makes sense. And no worries, I understand it's mostly out of your control. It's a small bug, and now that I know the probable issue, I'll be more careful using the elevation profile!