Flomp
Exported GPX created on app are not usable
I've just created new trails directly on Wanderer but exported GPX cannot be used neither on mobile nor on desktop (Basecamp import).
No error logs in backend, unknown issue from Basecamp, cannot be more precise I'm sorry.
Joining an exported file, just renamed with .txt extension instead og .gpx for Github authorization.
Version 0.16.1
Hi there,
Just tested your file in Basecamp. The problem seems to be the <author> tag in the metadata header:
<!-- does not import -->
<metadata>
<name>Lac Noir</name>
<desc /><time>2025-04-10T00:00:00Z</time>
<keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords>
<author>
<name>mf4qorb7jikggr2</name>
<email>[email protected]</email>
</author>
</metadata>
<!-- imports -->
<metadata>
<name>Lac Noir</name>
<desc /><time>2025-04-10T00:00:00Z</time>
<keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords>
</metadata>
I have no idea why that is. The author tag strictly follows specifications: [1][2]. So I don't see a problem with wanderer here.
Hi thanks for your reply ! Maybe we can talk in French ?
Basecamp was throwing an unknown exception and the mobile was downloading the file with TXT extension since I've put it in public and was unable to import it in Garmin connect too. But I've uploaded it to VisuGPX and it was able to read and print it correctly, then downloading the trail from VisuGPX was OK to import it in the two applications above. Maybe a format issue, I'll compare both of them (before and after VisuGPX import) and see the differences.
I'll let you know.
Regards
Le ven. 11 avr. 2025, 12:11, Flomp @.***> a écrit :
Hi there,
Just tested your file in Basecamp. The problem seems to be the
tag in the metadata header: <metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> <author> <name>mf4qorb7jikggr2</name> ***@***.***</email> </author> </metadata><metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> </metadata>I have no idea why that is. The author tag strictly follows specifications: [1 https://www.topografix.com/gpx/1/1/#type_metadataType ][2 https://www.topografix.com/gpx/1/1/#type_personType]. So I don't see a problem with wanderer here.
— Reply to this email directly, view it on GitHub https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASREXN6VOJAMQNESVUCCDET2Y6IM3AVCNFSM6AAAAAB24SUZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGQ3TAMJRGE . You are receiving this because you authored the thread.Message ID: @.***> Flomp left a comment (Flomp/wanderer#250) https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111
Hi there,
Just tested your file in Basecamp. The problem seems to be the
tag in the metadata header: <metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> <author> <name>mf4qorb7jikggr2</name> ***@***.***</email> </author> </metadata><metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> </metadata>I have no idea why that is. The author tag strictly follows specifications: [1 https://www.topografix.com/gpx/1/1/#type_metadataType ][2 https://www.topografix.com/gpx/1/1/#type_personType]. So I don't see a problem with wanderer here.
— Reply to this email directly, view it on GitHub https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASREXN6VOJAMQNESVUCCDET2Y6IM3AVCNFSM6AAAAAB24SUZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGQ3TAMJRGE . You are receiving this because you authored the thread.Message ID: @.***>
Hi,
Don't know if you're gonna see my replies but here what I found.
When exporting GPX from Wanderer, the file comes with 2 XML blocks that seem to be why it cannot be imported in Basecamp :
- The "features" block at the end of the file
- The sub block "author" in the metadata block in like you mentionned it
From my experience, when exporting a GPX file from Wanderer and remove these both blocks, the file can be freely imported in Basecamp.
For the mobile, I don't know why the phone seeing the file as TXT instead of GPX. Any idea would be welcomed !
Regards,
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Sans virus.www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
Le ven. 11 avr. 2025 à 13:29, Alexis Ring @.***> a écrit :
Hi thanks for your reply ! Maybe we can talk in French ?
Basecamp was throwing an unknown exception and the mobile was downloading the file with TXT extension since I've put it in public and was unable to import it in Garmin connect too. But I've uploaded it to VisuGPX and it was able to read and print it correctly, then downloading the trail from VisuGPX was OK to import it in the two applications above. Maybe a format issue, I'll compare both of them (before and after VisuGPX import) and see the differences.
I'll let you know.
Regards
Le ven. 11 avr. 2025, 12:11, Flomp @.***> a écrit :
Hi there,
Just tested your file in Basecamp. The problem seems to be the
tag in the metadata header: <metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> <author> <name>mf4qorb7jikggr2</name> ***@***.***</email> </author> </metadata><metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> </metadata>I have no idea why that is. The author tag strictly follows specifications: [1 https://www.topografix.com/gpx/1/1/#type_metadataType][2 https://www.topografix.com/gpx/1/1/#type_personType]. So I don't see a problem with wanderer here.
— Reply to this email directly, view it on GitHub https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASREXN6VOJAMQNESVUCCDET2Y6IM3AVCNFSM6AAAAAB24SUZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGQ3TAMJRGE . You are receiving this because you authored the thread.Message ID: @.***> Flomp left a comment (Flomp/wanderer#250) https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111
Hi there,
Just tested your file in Basecamp. The problem seems to be the
tag in the metadata header: <metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> <author> <name>mf4qorb7jikggr2</name> ***@***.***</email> </author> </metadata><metadata> <name>Lac Noir</name> <desc /><time>2025-04-10T00:00:00Z</time> <keywords>flbupoq4l2rqobx, La Palud, Auvergne-Rhône-Alpes, France</keywords> </metadata>I have no idea why that is. The author tag strictly follows specifications: [1 https://www.topografix.com/gpx/1/1/#type_metadataType][2 https://www.topografix.com/gpx/1/1/#type_personType]. So I don't see a problem with wanderer here.
— Reply to this email directly, view it on GitHub https://github.com/Flomp/wanderer/issues/250#issuecomment-2796470111, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASREXN6VOJAMQNESVUCCDET2Y6IM3AVCNFSM6AAAAAB24SUZXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJWGQ3TAMJRGE . You are receiving this because you authored the thread.Message ID: @.***>
Export not working on mobile is described here: https://github.com/Flomp/wanderer/issues/220
This is now fixed in v0.16.3.
The <feature> block did not cause issues in my test, only the <author> one. However, I will not change that as it is part of the GPX specification, and I see the issue here with Basecamp.