Proposal talk:Elevation and height
I would like to see OSM node data include elevation. Most GPS devices provide elevations and they can be approximated by interpolating SRTM data. I agree that such data could be very useful to many possible applications drawing on the OSM dataset. Such apps may, though, need some clever code to average out a range of elevations for clustered nodes and SRTM data in a given small area. A big difficulty is judging the elevation for a manually-added or moved node which does not coincide with a GPX track node, but these problems are no reason not to start including elevations in the raw dataset.--Elvin 15:13, 15 August 2008 (UTC)
I guess most uploaded GPS traces at OSM already include elevation data. The average of multiple gps traces along a way could give better elevation information as the STM data, which are distored by trees and buildings. Generally: I would be very happy to get automatically created elevation data from OSM. --ThomasT 17:21, 15 August 2008 (UTC)
- Yes, this is a very good idea. If you average the values this could result in a very good elevation model. --Derstefan 23:14, 4 April 2011 (BST)
- Elevation data within OSM database would be very interesting to have (and possibly to edit)! --Kozuch 10:16, 22 August 2011 (BST)
ele=* is already widely in use on features such as natural=peak --Skippern 17:10, 17 December 2008 (UTC)
wrong namespace
"height" is already used in the meaning of height of a building or in maxheight as the space under a bridge.
Evevation information is already added to OSM as ele=*.
A little research before postin a proposal would be appreciated.
Really usefull feature
I'd like to point some streets as "downhills", and I have GPS elevation data for this streets. For bikers it's sometimes usefull to know, if you are riding up, or flying down. --Danbst 21:09, 21 October 2011 (BST)