Opened 16 months ago

Last modified 16 months ago

#22112 new enhancement

Elevation data

Reported by: rstp@… Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: elevation, gpx Cc:


What steps will reproduce the problem?

  1. import and convert a .gpx file with elevation data
  2. convert to data layer
  3. save as .geojson

What is the expected result?

geojson linestring dropped the elevation data

It would be very usefull to keep the elevation data even if it is not used by JOSM.

Attachments (0)

Change History (1)

comment:1 Changed 16 months ago by taylor.smock

The problem is that there is an intermediate step.

  1. Import the gpx file with elevation data
  2. Convert to an OSM data layer (which has no use for the elevation data, and the only way to "keep" the elevation data would be to add a ele tag as the OSM data model doesn't have node elevations)
  3. Export the data layer as a geojson

TBH, if you want to convert a gpx file to a geojson, I would recommend using something else that can do it without the intermediate step.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.