Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

make use of altitude information (ele) #1582

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

make use of altitude information (ele) #1582

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment

Comments

@openstreetmap-trac
Copy link

Reporter: kavol
[Submitted to the original trac issue database at 11.02pm, Monday, 9th February 2009]

The .gpx files may contain element which corresponds to OSM key ele (http://wiki.openstreetmap.org/wiki/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.

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 11.15am, Tuesday, 10th February 2009]

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.

Regards

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant