Opened 11 years ago

Closed 11 years ago

#1582 closed enhancement (wontfix)

make use of altitude information (ele)

Reported by: kavol Owned by: cbro@…
Priority: major Milestone:
Component: merkaartor Version:
Keywords: Cc:


The .gpx files may contain element <ele></ele> which corresponds to OSM key ele ( But when importing tracks into Merkaartor, this information is lost, the imported nodes do not keep the altitude information. Please make use of it, autoconvert the element value to the key value on import.

Also, it'd be very nice if Merkaartor would allow some easy method of merging the elevation values from imported tracks into already existing routes. For example, if I record driving on a road, and I get a track which nearly perfectly matches the road in the map that is missing the altitude information, let me select that road and run a command to add the altitude information automatically from the track nodes which are nearest to the nodes of the road.

Change History (1)

comment:1 Changed 11 years ago by Chris Browet

Resolution: wontfix
Status: newclosed

I already had discussion on the OSM mailing lists regarding the pertinence of elevation in GPX tracks and the ele tag.

The response was: 1) The osm ele tag is meant for POI (e.g. peaks), not to generate pseudo SRTM data 2) Anyway, the precision of common GPS device is so poor that it would pollute the database. For proper elevation, use freely available SRTM data.

So, although at point Merkaartor did exactly this, it has be removed and won't come back.


Note: See TracTickets for help on using tickets.