# Importation GPX T

**URL:** <https://forum.kurviger.com/t/importation-gpx-t/7566>\
**Category:** Route transfer and 3rd party integration\
**Tags:** question\
**Created:** [February 19, 2022, 5:24pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566 "2022-02-19T17:24:56Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![loufy57](https://forum.kurviger.com/user_avatar/forum.kurviger.com/loufy57/32/3384_2.png) [@loufy57](https://forum.kurviger.com/u/loufy57)\
**Post date:** [February 19, 2022, 5:24pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/1 "2022-02-19T17:24:57Z")

</div>

Hello

Qu 'elles sont pour vous les meilleurs réglages pour importé des fichiers GPX qui ne contiennent pas forcement de traces jointes .  
Régulièrement confronté à ce probleme lors de partage de fichier GPX qui ne sont pas fait par Kurviger mais par d 'autres applications

---

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [February 21, 2022, 9:20am UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/2 "2022-02-21T09:20:11Z")

</div>

Hi,

sorry I cannot follow you. What exactly is the problem? Do you have a file that is not working? Or is this more general?

---

<div class="post-metadata">

**Author:** ![loufy57](https://forum.kurviger.com/user_avatar/forum.kurviger.com/loufy57/32/3384_2.png) [@loufy57](https://forum.kurviger.com/u/loufy57)\
**Post date:** [February 21, 2022, 10:32am UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/3 "2022-02-21T10:32:41Z")

</div>

en fait pour être au plus sur de l 'exactitude d’un fichier

Exemple un groupe de motards situé au coin de la France se partage des fichiers GPX réalisés avec different outils , comment être sur que le fichier GPX que j ’ ouvre avec Kurviger soit la bonne route ( tres souvent il n ’ y pas de trace joint dans le fichier )  
donc ma question est de savoir si il y a un reglace optimum pour l 'importation de route GPX pour qui il n ’ y a pas trop d 'interpretations différentes de la route

---

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [February 21, 2022, 10:37am UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/4 "2022-02-21T10:37:37Z")

</div>

Please see the documentation about how to import GPX tracks:

- [Importing a GPX Track into Kurviger [Kurviger Knowledgebase]](https://docs.kurviger.de/route_transfer/transfer_track_to_kurviger)
- [Route Transfer (Import, Export) [Kurviger Knowledgebase]](https://docs.kurviger.de/route_transfer)

---

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [February 21, 2022, 1:14pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/5 "2022-02-21T13:14:45Z")

</div>

If there is no GPX Track, you can’t make sure that the calculated route is actually equal to the route in the GPX file. You could compare the distance if that is available, but this is also no guarantee.

If you planned your route with Kurviger before, I would recommend to go with the .kurviger File.

---

<div class="post-metadata">

**Author:** ![dgp](https://forum.kurviger.com/user_avatar/forum.kurviger.com/dgp/32/6070_2.png) [@dgp](https://forum.kurviger.com/u/dgp)\
**Post date:** [February 26, 2022, 7:27am UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/6 "2022-02-26T07:27:22Z")

</div>

Do these other people have a link they can share with you where you can view the route?

---

<div class="post-metadata">

**Author:** ![rumbrummer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/rumbrummer/32/113_2.png) [@rumbrummer](https://forum.kurviger.com/u/rumbrummer)\
**Post date:** [February 27, 2022, 5:08pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/7 "2022-02-27T17:08:51Z")

</div>

A lot of distritbuted GPX (from friends, in a forum or elsewhere in the web) are Garmin GPX.

Inside this GPX in Garmin format frequently the calculated route is inserted in the GPX route with Garmin special extensions.

An example I found in the web:  
[Franken-Thueringer Wald 2010.gpx](https://forum.kurviger.com/uploads/short-url/oJibphobkvbuzjPBcC4lRzYoCw3.gpx) (271,3 KB)

If you import it in Kurviger, only the route points (tag \<rtept\>) of the GPX are used (as kurviger waypoints) - to show that, I imported the GPX only as overlay in Kurviger (1st picture). But there is much more info in the GPX, you can see that if you open that GPX in [gpxshaping.de](http://gpxshaping.de) (2nd picture): The magenta line shows only the connection between the route points, the blue line shows the additional info contained in Garmin specific extensions:

 ![image](https://forum.kurviger.com/uploads/default/original/2X/f/fc5e2e49d9bb39573261eebfd6944f59db882bf1.jpeg) ![image](https://forum.kurviger.com/uploads/default/original/2X/8/82fe2f0a66da00fd5dc26f9c05af44f295423fcf.jpeg)

You can export a new GPX from [gpxshaping.de](http://gpxshaping.de) (it contains the blue line as track) and import that in kurviger, so you can see also the “track” hidden in Garmin GPX extension before:

[Franken-\_Thüringer Wald\_2010Shp.gpx](https://forum.kurviger.com/uploads/short-url/dLi3h9kYAjjxgT1431aTvOXifY7.gpx) (149,6 KB)

 ![image](https://forum.kurviger.com/uploads/default/original/2X/4/44eb0cac26bf023911b1afe62af104a5f2d2f28a.jpeg)

As you can see, there are several differences between the Garmin route and the Kurviger route - you can fix that by adding further waypoints, for example between #11 and #12:

 ![image](https://forum.kurviger.com/uploads/default/original/2X/b/b2b22fb2dac51efa5c352065e3ea749044fc83c1.jpeg)

([gpxshaping.de](http://gpxshaping.de) can do that automatically - but that is OT here)

From my point of view it would be helpful, if Kurviger also reads that Garmin extensions, because (as mentioned before) a lot of GPX you get via web are in that format.

The format is quite simple, as an example I attached the route point “Straß4” from GPX below.  
Each route point (tag \<rtept\>) contains further points (tag \<gpx:rpt\>) showing the track to next route point, so it is not difficult to extract that points and build a track from the route points and the “track” points between:

\<rtept&nbsp;lat=“50.2757549”&nbsp;lon=“11.6003180”\>  
&nbsp;&nbsp;\<time\>2010-05-24T18:41:22Z\</time\>  
&nbsp;&nbsp;\<name\>Straß4\</name\>  
&nbsp;&nbsp;\<cmt\>Straße\</cmt\>  
&nbsp;&nbsp;\<desc\>Straße\</desc\>  
&nbsp;&nbsp;\<sym\>Waypoint\</sym\>  
&nbsp;&nbsp;\<extensions\>  
&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:RoutePointExtension&nbsp;xmlns:gpxx=“[http://www.garmin.com/xmlschemas/GpxExtensions/v3](http://www.garmin.com/xmlschemas/GpxExtensions/v3)”\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:Subclass\>00d000000000ffffffffffffffffffffffff\</gpxx:Subclass\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2757549”&nbsp;lon=“11.6003180”\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:Subclass\>06006bb87a00248d0500211600006c000000\</gpxx:Subclass\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\</gpxx:rpt\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2757549”&nbsp;lon=“11.6003180”\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:Subclass\>06006bb87a00658d05001f02070068d26100\</gpxx:Subclass\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\</gpxx:rpt\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2757978”&nbsp;lon=“11.6005754”/\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2757120”&nbsp;lon=“11.6006613”/\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2753258”&nbsp;lon=“11.6007042”/\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2749825”&nbsp;lon=“11.6008329”/\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2745104”&nbsp;lon=“11.6011333”/\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:rpt&nbsp;lat=“50.2740175”&nbsp;lon=“11.6015559”\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\<gpxx:Subclass\>06006bb87a00658d05002117000014000000\</gpxx:Subclass\>  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\</gpxx:rpt\>  
&nbsp;&nbsp;&nbsp;&nbsp;\</gpxx:RoutePointExtension\>  
&nbsp;&nbsp;\</extensions\>  
\</rtept\>

---

<div class="post-metadata">

**Author:** ![loufy57](https://forum.kurviger.com/user_avatar/forum.kurviger.com/loufy57/32/3384_2.png) [@loufy57](https://forum.kurviger.com/u/loufy57)\
**Post date:** [February 27, 2022, 6:39pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/8 "2022-02-27T18:39:40Z")

</div>

Non pas forcement

---

<div class="post-metadata">

**Author:** ![boldtrn](https://forum.kurviger.com/user_avatar/forum.kurviger.com/boldtrn/32/360_2.png) [@boldtrn](https://forum.kurviger.com/u/boldtrn)\
**Post date:** [February 28, 2022, 4:05pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/9 "2022-02-28T16:05:14Z")

</div>

> [@rumbrummer](#):
>
> From my point of view it would be helpful, if Kurviger also reads that Garmin extensions, because (as mentioned before) a lot of GPX you get via web are in that format.

Interesting, thanks for sharing. I can have a look if that is possible. The way the GPX import works right now, this is probably not possible.

There are a lot of Garmin GPX files, so this might help the compatibility with Kurviger 🙂.

---

<div class="post-metadata">

**Author:** ![rumbrummer](https://forum.kurviger.com/user_avatar/forum.kurviger.com/rumbrummer/32/113_2.png) [@rumbrummer](https://forum.kurviger.com/u/rumbrummer)\
**Post date:** [February 28, 2022, 7:27pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/10 "2022-02-28T19:27:16Z")

</div>

> [@boldtrn](#):
>
> I can have a look if that is possible. The way the GPX import works right now, this is probably not possible…

Just to prevent double work: There is an other topic about Garmin specific extensions:

> [@Process Garmin shaping point information in .gpx file on import](https://forum.kurviger.com/t/process-garmin-shaping-point-information-in-gpx-file-on-import/3353):
>
> My comment only referred to the import of a Garmin based .gpx file and the recognition of shaping points with the following structure: [sp] I don’t think we should make any changes on export. I’m not sure if older Garmin devices and TomTom navis can handle this.

But it seems that Wolfgang and me are the only users interesred in that … 🤔 - but nevertheless perhaps it might be useful to consider that topic if reworking GPX import.

---

<div class="post-metadata">

**Author:** ![devemux86](https://forum.kurviger.com/user_avatar/forum.kurviger.com/devemux86/32/6239_2.png) [@devemux86](https://forum.kurviger.com/u/devemux86)\
**Post date:** [February 28, 2022, 7:34pm UTC](https://forum.kurviger.com/t/importation-gpx-t/7566/11 "2022-02-28T19:34:49Z")

</div>

_Please let’s continue the discussion about Garmin GPX in its topic:_

> [@Process Garmin shaping point information in .gpx file on import](https://forum.kurviger.com/t/process-garmin-shaping-point-information-in-gpx-file-on-import/3353):
>
> My comment only referred to the import of a Garmin based .gpx file and the recognition of shaping points with the following structure: [sp] I don’t think we should make any changes on export. I’m not sure if older Garmin devices and TomTom navis can handle this.
