# Include route name in export file

**URL:** https://community.citystrides.com/t/include-route-name-in-export-file/25164
**Category:** Completed
**Created:** [July 29, 2022, 9:18pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164 "2022-07-29T21:18:33Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![8f7162110d9eeaf907ab](https://community.citystrides.com/letter_avatar_proxy/v4/letter/8/ad7895/32.png) [@8f7162110d9eeaf907ab](https://community.citystrides.com/u/8f7162110d9eeaf907ab)
#### Post date: [July 29, 2022, 9:18pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/1 "2022-07-29T21:18:33Z")

</div>

I noticed today that Garmin Connect now also imports the route name from the .gpx file when importing a route (it used to leave the name blank). Currently, CS sets the parameter in the .gpx to “strider’s Route”, would it be possible to assign the name of the route as given in CS instead? That way it would import the name at the same time as the route, eliminating the need to (re)name the route in Garmin Connect.

---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [July 30, 2022, 1:13pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/2 "2022-07-30T13:13:32Z")

</div>

Nice find! This is being released now.

---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [July 30, 2022, 1:13pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/3 "2022-07-30T13:13:37Z")

</div>



---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [July 31, 2022, 2:21pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/4 "2022-07-31T14:21:40Z")

</div>



---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [July 31, 2022, 2:24pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/5 "2022-07-31T14:24:46Z")

</div>

🎶 whoops 🎵  
I didn’t actually fix it - got this message sent to me privately because I closed this topic too soon:

> responding here as the thread is closed.  
> As you mentioned that you were implementing this straight away (thanks!) I wanted to test it. It still shows the name as “JOMS’s Route”.

> Right now the "\<metadata \<name " tag gets set to the name of the route in CS, which to me makes intuitive sense. I think that Garmin Connect, however, bases its import on the “\<rte \< name” tag. Would it be possible to update that one with the CS route name instead?

> I had included the tag name in my original post but didn’t notice that closing the tag with \> makes the tag disappear from the text 😠, sorry about that.

---

<div class="post-metadata">

### Author: ![kevincharlespels](https://community.citystrides.com/user_avatar/community.citystrides.com/kevincharlespels/32/2536_2.png) [@kevincharlespels](https://community.citystrides.com/u/kevincharlespels)
#### Post date: [August 3, 2022, 1:10pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/6 "2022-08-03T13:10:53Z")

</div>

it works now, or at least it just did for me! route name from route builder was same as route name in Courses on Garmin Connect 👍

---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [August 3, 2022, 1:31pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/7 "2022-08-03T13:31:57Z")

</div>

Great! Sounds like I can _actually_ close this out now 😬  
I’m happy to see these route files are useful!

---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [August 3, 2022, 1:32pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/8 "2022-08-03T13:32:01Z")

</div>



---

<div class="post-metadata">

### Author: ![JamesChevalier](https://community.citystrides.com/user_avatar/community.citystrides.com/jameschevalier/32/2_2.png) [@JamesChevalier](https://community.citystrides.com/u/JamesChevalier)
#### Post date: [July 24, 2025, 6:08pm UTC](https://community.citystrides.com/t/include-route-name-in-export-file/25164/9 "2025-07-24T18:08:52Z")

</div>


