Feature request: Preserve <rte><desc> and <rte><link> when importing GPX routes

Route transfer and 3rd party integration
, ,
1

Hi Kurviger team,

I would like to suggest a small but useful improvement to the GPX route importer.

I use Garmin BaseCamp to plan routes and then import the resulting GPX files into Kurviger.

In BaseCamp, a route has properties where I can enter additional information in a description/notes field and also add web links. BaseCamp exports these properties directly as part of the <rte> element.

For example, my exported GPX contains:

<rte>
    <name>Black Forest Motorcycle Tour</name>
    <desc>These notes in the route should be transferred to Kurviger!</desc>
    <link href="http://examplelink.com/"/>
    ...
</rte>

So in this case the information is definitely present in the GPX file and is associated with the route itself, not with an individual waypoint.

When importing this GPX into Kurviger, however, the route description and the route link are not preserved in the Kurviger route properties.

Suggested mapping

Would it be possible to support the following mapping during GPX route import?

<rte><name>    → Kurviger route name
<rte><desc>    → Kurviger route description
<rte><link>    → Kurviger route web link(s)

Kurviger already has a route description field, so this would allow information created in BaseCamp to be transferred directly into the corresponding Kurviger route property.

I am not suggesting that the information should be converted into additional waypoints or overlay POIs. It should remain metadata attached to the route itself.

A question about the GPX importer

Is <rte><desc> currently deliberately ignored by the Kurviger GPX importer?

And is there already support, or a plan to support, <rte><link> for links associated with the route itself?

If there are technical reasons why these elements cannot currently be mapped to the Kurviger route object, I would also be interested to know what GPX structure Kurviger recommends for transferring route-level descriptions and links.

This would be particularly useful for BaseCamp → Kurviger workflows, because route descriptions are often used for things such as:

  • accommodation information
  • ferry details
  • tour notes
  • useful websites
  • booking information
  • links to road or destination information

Thanks!