|
Not 100% sure this is the right place to post this but here we go: I am using Strava and according to their help page they are using openstreetmap (and mapbox). The route I am running on a daily basis maps out like this (It's a route in San Diego, CA):
You notice the dip between 0.5 and 1.0 kilometers. The elevation drops from 122m to 99m at this point and then immediately going up again. Let me assure you: the route is very flat. But On the point there is a bridge going over a highway that is far below (Adams Avenue going over the Jacob Dekema Freeway: https://www.openstreetmap.org/#map=19/32.76283/-117.12725). My assumption is, somewhere in the data the elevation from the highway below is assumed to be on the bridge. I haven't found any elevation data in the OSM data, so not quite sure what the next step (I opened an issue with Mapbox as well). |
|
You're correct in saying OSM doesn't contain the elevation data that Strava use. They have a support page here about elevation. |
|
Something that may help from an OSM perspective is if you add the bridge outline as Per EdLoach's answer, you are correct about OSM's lack of continuous elevation data, but Strava could conceivably interpolate between elevations at the points your track enters and exits the bridge area rather than using the elevation of the land below. (Whether they actually do this is another question.) |
