-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracks will not register Garmin Basecamp gpx #1027
Comments
The track that 'works', as opposed to the Garmin track, uses wpt rather than trkpt. Is there a tracks protocol that Maps uses (perhaps?) and the Garmin tracks (gpx) diverges from that protocol in some way? If I knew what the protocol was I could possible write a script to convert to something Maps can read. Of course this may not be the problem at all. |
This comment was marked as outdated.
This comment was marked as outdated.
I'm confused for me the kepler track shows up, without changes. |
Thanks for considering this.
It still doesn’t show up for me:
***@***.***
I also get “Geo link could not be copied to clipboard” when I select “share this location”. Perhaps relevant?
Operating System: Linux 5.15.0-73-generic x86_64
PHP Version: 8.0.29
Mysql Version: 10.6.12
Nextcloud Nextcloud Hub 3<https://nextcloud.com> (25.0.5)
Contacts 5.3.2
Maps 1.0.2
From: Arne Hamann ***@***.***>
Sent: Sunday, 2 July 2023 12:23 pm
To: nextcloud/maps ***@***.***>
Cc: Chris Nicoll ***@***.***>; Author ***@***.***>
Subject: Re: [nextcloud/maps] Tracks will not register Garmin Basecamp gpx (Issue #1027)
I'm confused for me the kepler track shows up, without changes.
—
Reply to this email directly, view it on GitHub<#1027 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARFJ7WCJ65Y63NC5PVMC4YTXOC5PTANCNFSM6AAAAAAWR4O7OQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
My fitness tracker app exports gpx files that use a Garmin extension of the gpx format for the heart rate: <?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" creator="Notify for Xiaomi" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://www.topografix.com/GPX/1/1
http://www.topografix.com/GPX/1/1/gpx.xsd
http://www.garmin.com/xmlschemas/GpxExtensions/v3
http://www.garmin.com/xmlschemas/GpxExtensionsv3.xsd
http://www.garmin.com/xmlschemas/TrackPointExtension/v1
http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd"
xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3">
<name>Walk</name>
<trk><name>Walk</name><number>1</number><trkseg>
<trkpt lat="..." lon="...">
<ele>...</ele>
<time>2024-02-14T13:52:06Z</time>
<extensions>
<gpxtpx:TrackPointExtension>
<gpxtpx:hr>...</gpxtpx:hr>
</gpxtpx:TrackPointExtension>
</extensions>
</trkpt>
...
</trkseg></trk>
</gpx> "..." are omitted sensitive numbers They are working without any issue(the heart rate is just ignored). Having support for the heart rate to be on the map would be nice. I am thinking about implementing it. |
Bug description
Maps shows a simple gpx track (one created by me) but will not show a track exported from Basecamp in gpx form. However 'scan-tracks' does 'add' these Garmin tracks (they just don't show up under 'tracks' on the map).
Attached is a sample Basecamp track (gpx) converted to .txt because gpx not supported
The Kepler Track.txt
Steps to reproduce
Expected behavior
All tracks should appear on map
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install of the server?
None
Is this bug present after an update or on a fresh install of the app?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Browser Console
No response
Additional info
Nextcloud version 25.0.5
The text was updated successfully, but these errors were encountered: