Tracks will not register Garmin Basecamp gpx
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 598
- Forks
- 113
- PR merge metrics
- No merged PRs in 30d
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- Maps app is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
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
- Run scan-tracks - shows all tracks 'added'
- One Track shows up but others don't
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?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
No response
List of activated Apps
Maps 1.0.2
All other apps (Contacts etc up to date)
Nextcloud Signing status
No response
Nextcloud Logs
No response
Browser Console
No response
Additional info
Nextcloud version 25.0.5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the scan-tracks entry point and reproduce the issue using the attached The Kepler Track.txt Basecamp export, comparing it with a track that appears on the map. Trace why the Basecamp tracks are reported as added but are not displayed; done means all valid tracks from the sample file appear on the map.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100