You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Menu "File" -> "Save as..." does not store the elevation (ele tag) of waypoints and trackpoints from imported GPX files into the .mdc file. This is not crucial (the GPX file can be imported again), and the removal of the elevations saves a tiny amount of disk space, but I don't believe it happens on purpose. It rather looks like a bug.
The text was updated successfully, but these errors were encountered:
The cause is the TrackNode inherits from the generic Node class and adds the elevation property. But since it's not a tag in the sense of OSM, it is handled separately (in a similar fashing as coordinates are). Saving should not be a problem, implementing the proper toXML() method will take care of it. Reading it back will be a bit challenging, since it is currently squished with a regular node. The file format will likely have to be extended. Other option is to include the elevation as a special tag, but that would require some magic to convert all nodes with this tag to a TrackNode instances.
None of that is too difficult, but will possibly break compatibility. I may give it a try, but also if someone wants to pickup the task, I'd be happy to merge a PR. I suggest to:
Create a test for reading/writing OSM objects (just fragments like <node />, not whole files, that would require Document class instance, but that is a bit too difficult to create standalone).
Menu "File" -> "Save as..." does not store the elevation (ele tag) of waypoints and trackpoints from imported GPX files into the .mdc file. This is not crucial (the GPX file can be imported again), and the removal of the elevations saves a tiny amount of disk space, but I don't believe it happens on purpose. It rather looks like a bug.
The text was updated successfully, but these errors were encountered: