La Flamme Rouge GPX not working anymore? Here is the solution!!!

[flockmastoR]

I am usually very rarely designing real races, but if I do, I always took the gpx exports from La Flamme Rouge (if available) as a good starting point doing so (uploading it in plotaroute and then use the route for detailed design, redesign of circuits etc.). What I experienced last week when supporting taka designing TA was that these gpx files do not work any longer, not in our editor and also not in plotaroute. So I asked ChatGPT to fix it for my usage and it worked out of the box. When taking a look at the files, the only changes made are in the first lines:

Original LFR version:
<?xml version="1.1" encoding="UTF-8" standalone="yes" ?>
<gpx creator="La Flamme Rouge - https://www.la-flamme-rouge.eu"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.topografix.com/GPX/1/1"
xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
<metadata>
<name>Strade Bianche ME 2026</name>

Fixed version that works with c4f/plotaroute:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<gpx version="1.1" creator="La Flamme Rouge - https://www.la-flamme-rouge.eu"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.topografix.com/GPX/1/1"
xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
<metadata>
<name>Strade Bianche ME 2026</name>


So maybe that helps you as well with designing!

[Nomorelulz]

What I experienced last week when supporting taka designing TA was that these gpx files do not work any longer, not in our editor and also not in plotaroute.

What exactly does not work for you when importing the gpx files? I designed one stage PN and checked some other stages in our editor with their gpx files and it worked for me.

[Gipfelstuermer]

So far it was also working fine for me.

Maybe you were unlucky and came across a corrupted file, but normally the LFR gpx files work for me.

Anyway, thanks for the solution in case the same happens to anyone else.

[flockmastoR]

So far it was also working fine for me.

Maybe you were unlucky and came across a corrupted file, but normally the LFR gpx files work for me.

Anyway, thanks for the solution in case the same happens to anyone else.

No, it was for all TA stages and now also for Strade Bianche.

What happens: When I want to upload it to plotaroute there is an error. It says "Unable to read file."
When I try to upload it in the c4f editor it simply does nothing.

But maybe after all it is a firefox issue (just came to my mind), can you confirm that e.g. the 2026 Strade Bianche is working for you? And if so, how the header looks like for you?

[Gipfelstuermer]

But maybe after all it is a firefox issue (just came to my mind), can you confirm that e.g. the 2026 Strade Bianche is working for you? And if so, how the header looks like for you?

Tested it and it works (Edge).

File is the same as you posted, but didn't have to adjust xml version and gpx creator.

[flockmastoR]

But maybe after all it is a firefox issue (just came to my mind), can you confirm that e.g. the 2026 Strade Bianche is working for you? And if so, how the header looks like for you?

Tested it and it works (Edge).

File is the same as you posted, but didn't have to adjust xml version and gpx creator.

So you automatically receive the 1.0 xml version file, or you have the same header as me but it works for you?

[Robyklebt]

Hasn't worked with Firefox for ages. Chrome+Edge never had issues.

[Gipfelstuermer]

But maybe after all it is a firefox issue (just came to my mind), can you confirm that e.g. the 2026 Strade Bianche is working for you? And if so, how the header looks like for you?

Tested it and it works (Edge).

File is the same as you posted, but didn't have to adjust xml version and gpx creator.

So you automatically receive the 1.0 xml version file, or you have the same header as me but it works for you?

No, I have the same header, but I can download from LFR and directly upload to C4F editor without issues.

[flockmastoR]

Hasn't worked with Firefox for ages. Chrome+Edge never had issues.

But why

[Robyklebt]

That first line according to you.

[Radunion]

Has to upload it to another website and save it again to get it working as well. I an on Firefox as well.

[Alkworld]

Is there any error shown?
And it really can be different depending on the browser you use. The file is parsed in the front end directly, maybe there's an error shown in the console? That could help making the code more robust.

[flockmastoR]

Is there any error shown?
And it really can be different depending on the browser you use. The file is parsed in the front end directly, maybe there's an error shown in the console? That could help making the code more robust.

When I open the F12 logging window I can see this:

XML-Verarbeitungsfehler: XML-Deklaration nicht wohlgeformt
Adresse: https://cycling4freaks.de/raceEditor
Zeile Nr. 1, Spalte 16: raceEditor:1:16
Uncaught TypeError: can't access property "points", e.tracks[0] is undefined
Sn RaceEditor.js:122
Sn RaceEditor.js:99
onChange RaceEditor.js:1092
RaceEditor.js:122:18

[Alkworld]

XML-Verarbeitungsfehler: XML-Deklaration nicht wohlgeformt
Adresse: https://cycling4freaks.de/raceEditor
Zeile Nr. 1, Spalte 16: raceEditor:1:16
Uncaught TypeError: can't access property "points", e.tracks[0] is undefined
Sn RaceEditor.js:122
Sn RaceEditor.js:99
onChange RaceEditor.js:1092
RaceEditor.js:122:18

Tried it now myself as well. My guess, Firefox (the browser you told me you used) is using a different XML parser. The file however looks perfectly fine. Maybe Firefox will fix the parser at some point.

[flockmastoR]

XML-Verarbeitungsfehler: XML-Deklaration nicht wohlgeformt
Adresse: https://cycling4freaks.de/raceEditor
Zeile Nr. 1, Spalte 16: raceEditor:1:16
Uncaught TypeError: can't access property "points", e.tracks[0] is undefined
Sn RaceEditor.js:122
Sn RaceEditor.js:99
onChange RaceEditor.js:1092
RaceEditor.js:122:18

Tried it now myself as well. My guess, Firefox (the browser you told me you used) is using a different XML parser. The file however looks perfectly fine. Maybe Firefox will fix the parser at some point.

Yeah, but as the community noted, it is a known issue with firefox, so I wouldn't plan that this is changed. Anyways the workaround I documented here works fine, just change those 2 lines and it works with firefox as well.

PS: I dont know how the upload of the gpx files work, but is it possible to adjust these in the code when it fails as well? Or is there a standard protocol used to upload and process the file?