Wrong autodetection of distance on importing/loading a GPX track

[hrws]

See: https://demo.wanderer.to/trail/view/744947fa4f8a146
Version: v0.15.2

When I create a new track (either here in the demo, or in a new local docker compose environment) and upload a GPX file, the basic info determines the track distance somehow completely wrong. Most often is it off by a factor of 4.
Unfortunately that also impacts the automatically generated summit book entry.
The complete distance will be correctly rendered in the map view.
I previously had an older installation (I believe it was v0.9.x) which worked correctly with the same GPX tracks.

The GPX files come from Samsung Health where I remove the heart rate data extension xml portion before importing the files.
e.g.:

<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" version="1.1" creator="Samsung Health_0.2" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd">
<metadate>2024-09-30T15:14:52Z</metadate>
<trk>
<name>20240930 Canyonlands</name>
<trkseg>
<trkpt lat="38.1434874" lon="-109.8034843">
<ele>1558.511</ele>
<time>2024-09-30T15:14:52Z</time>
</trkpt>
<!-- ... more entries ... -->
</trkseg>
</trk>
<exerciseinfo>
<exercisetype>13001</exercisetype>
<distance>14898.59</distance>
<elevationgain>203.222</elevationgain>
<avggradient>11.186347845839999</avggradient>
<duration>20940044</duration>
<avgspeed>0.71148795</avgspeed>
</exerciseinfo>
</gpx>

Here in the exercise info, the correct distance (in meters) is even given. But still, the import detects it as nearly 62 km

[letharo]

I noticed the same behaviour and was about to open an issue.