Export and import of gpx is inconsistent

[Spielmops]

I create an item in a map-layer:

Then I export this item as gpx and look at it via editor:

And after that I import this file. Result:

Why is this so? Why is the description not in description-field any more?

Spielmops

[yohanboniface]

Thanks for the report!

Not sure exactly about the status of the external lib we current use for exporting to gpx: https://github.com/tyrasd/togpx
See also pnlabs/togpx#1 on this topic

Needs more investigation!

[yohanboniface]

Maybe switch to https://github.com/We-Gold/gpxjs ?

Edit: this lib is the other way (parsing)… For creating: https://github.com/dwayneparton/geojson-to-gpx

[davidbgk]

Why is this so? Why is the description not in description-field any more?

I would say the = within the description is unfortunate.

[yohanboniface]

From the togpx doc:

By default, the desc tag of GPX elements will be constructed by concatenating all respective GeoJSON properties.

So this is the expected behaviour. It's configurable, but from the specs it seems there is no way to have custom properties, only desc is expected (if I read it correctly). So we can either keep the current behaviour, so all properties are exported in the GPX, either have a custom configuration to export only the description field into desc.

First thing to decide: I wonder how other GPX tools behave, and specifically how other tools would load a GPX concatenating many properties in the desc field.

[Spielmops]

I would say the = within the description is unfortunate.

Even if I reduce in that gpx-file to
<desc>Und hier steht die Beschreibung des betreffenden Objektes.</desc>
the content of <desc></desc> is not imported to "description", where I expect it.

Spielmops

[yohanboniface]

A new release has been deployed just now that changes the lib used for GPX. Could have a try ?