At the moment you can create lines and routes in a plan. A line is meant to be something to help with your planning... eg for a route from A to B you can start by drawing a straight line from A to B, then plot an efficient route that stays as close to it as possible.
The resulting plan would then have both the line and the route within it.
If you went to export it to GPX then there's two LineString geometries and therefore you would be limited to <trk> export only. If you did export that then on your device you'd see both the straight line and the route, which you clearly don't want.
One workaround is to export just the route feature and ignore the line. However this would have the default name 'Route.gpx'. Again, you could fix this in the feature settings. But it starts to become a bit fiddly.
Whereas it seems a reasonable default that a line should never be in a GPX plan export. In the example above that would mean the plan has just one exportable LineString geometry so you would get the option for a <rte> as well as <trk>. And the resulting GPX would have just the relevant contents.
Exporting individual features remains relevant for eg exporting one day of a multi-day plan. And therefore you could still export a line via this route if you wanted to. I think this issue only applies as a sensible default when exporting the entire plan itself.
At the moment you can create lines and routes in a plan. A line is meant to be something to help with your planning... eg for a route from A to B you can start by drawing a straight line from A to B, then plot an efficient route that stays as close to it as possible.
The resulting plan would then have both the line and the route within it.
If you went to export it to GPX then there's two LineString geometries and therefore you would be limited to
<trk>export only. If you did export that then on your device you'd see both the straight line and the route, which you clearly don't want.One workaround is to export just the route feature and ignore the line. However this would have the default name 'Route.gpx'. Again, you could fix this in the feature settings. But it starts to become a bit fiddly.
Whereas it seems a reasonable default that a line should never be in a GPX plan export. In the example above that would mean the plan has just one exportable LineString geometry so you would get the option for a
<rte>as well as<trk>. And the resulting GPX would have just the relevant contents.Exporting individual features remains relevant for eg exporting one day of a multi-day plan. And therefore you could still export a line via this route if you wanted to. I think this issue only applies as a sensible default when exporting the entire plan itself.