Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<extensions> tags in gpx file #77

Closed
ShelleyLake opened this issue Dec 21, 2019 · 2 comments
Closed

<extensions> tags in gpx file #77

ShelleyLake opened this issue Dec 21, 2019 · 2 comments

Comments

@ShelleyLake
Copy link

ShelleyLake commented Dec 21, 2019

Please do not trash any <extensions> tags that may be present in the original gpx file.
I'm not asking to show and/or modify them in any way, but only to read, preserve and save them in the export of the gpx file.

@rnorris
Copy link
Collaborator

rnorris commented Apr 5, 2020

Unfortunately Viking only explicitly supports GPX1.0 which doesn't have any extensions.

This is hopefully made slightly apparent since you can not 'save' a GPX file directly, you have to 'export' to it.

Internally Viking processes GPX files into it's own understanding and then creates newly generated GPX format when requested to export to GPX.

There have been requests for the common extension types (such as Power, Cadence & Heart Rate) which is likely to see some level of at least read support in the near future, however (saving) this might conflict with a reasonably simple approach to storing extension information as literal copy of the extension(s) as text for every point, track and gpx file.

Hopefully with enough thought there should be a viable solution that has a chance of being implemented.

@rnorris
Copy link
Collaborator

rnorris commented May 28, 2020

This commit addresses this issue.

d93a038

Further GPX1.1 items are in the pipeline.

@rnorris rnorris closed this as completed May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants