Whilst GPX importing errors are relatively few and far between, there can be a number of complexities that can cause errors or mismatched routes from time to time. With some troubleshooting, we can have you Beelining on these rides in no time!
Troubleshooting GPX Import Issues
Changes to the planned route when imported
This can happen for a couple of reasons:
There could be differences between the underlying map data from the source of the GPX file and the Beeline app. When you import a route into the Beeline app, it goes through a process of “Map-matching”, which can occasionally result in small differences between the route you have imported and the route you receive in return from the Beeline app.
There could be incompatible components within your file. To list a couple:
Non-standard GPX format (extensions including GPXX)
Via waypoints - a waypoint type that is not supported by the Beeline app
Identifying a Map-Matching Issue
There are a few ways to identity map-matching issues within the Beeline app. Firstly, you might have a notification show up on your app, it could have a variety of messages, but the underlying note will be that the GPX import has not been successful.
Alternatively, you might notive a map-matching issue on a GPX file that has been imported, but not completely or accurately.
What to Do if You Encounter a Map-Matching Error
If you experience a map-matching error:
Note the Error Code: Make a note of the specific error code displayed on your screen. This will be helpful for our support team; a screenshot would be perfect!
Export Your GPX File: The most crucial step is to export the GPX file for the ride in question. To export a GPX file from the Beeline app, follow these steps:
1. Select the ride you would like to export as a GPX file
2. Tap on the 'Options' menu in the top right corner and select the 'Share/ download' option
3. Select the planned route
4. Choose your desired method of saving the file
Contact Support: Once you have your GPX file, please get in touch with our support team here.
When contacting us, please include:
A brief description of the issue.
The error code you observed.
Attach the GPX file to your email.
Our team will then review your GPX file and investigate the map-matching problem. Providing us with this file allows us to accurately diagnose the issue and work towards a solution, helping you get your ride data accurately reflected.
Using GPX Studio to standardise incompatible file types
In the off chance your file contains components that are incompatible with the Beeline app, you can convert your file to a compatible GPX format using a tool such as gpx.studio
To do this:
1 - Go to GPX Studio
2 - Open your file there:
3 - Export your file - this will be done in the standard format accepted by the Beeline app
4 - Import your file into the Beeline app. Hopefully, this will show the route mapped out to plan.
Waypoints are being lost in Route Mode imports
This is most likely caused by incompatible file types or the use of waypoints. Please read the section above to check if the file type can be standardised to resolve this. If it cannot, there is the chance that some of the waypoints in the file are configured as “via waypoints” ie points that guide the route. Waypoints and via waypoints are tagged differently within the GPX file. The Beeline app pulls true waypoints tagged with the <wpt> tag, not those tagged as <rtept> or <trkpt>.
There is no fix for importing via waypoints at the moment, aside from using external tools to change the tagging of the via waypoint.
Unsure or stuck? We’d be happy to have another look! Please get in touch with our support team here with the file, and we can double-check.
GPX Import: Timed Out Error
If you receive a "Timed out" error during GPX import, it typically means a section of the route is too complex or long for our system to process within the allotted time during Map-matching.
What to do:
Break down the route: A common solution that often works is to divide your route into smaller segments. We recommend keeping individual GPX files under approximately 150 miles (240 km). You can then import these smaller segments as separate routes.
Send us the file: If step 1 hasn’t done the trick, please send us the GPX file that caused the timeout error. Our team would be happy to examine it and see if we can find a solution from our end. Please get in touch with our support team here.
Samsung "Unable to read file" Error
If you're a Samsung user and see an "Unable to read file" error when trying to import a GPX, it's likely a permission issue.
Solution: You need to grant "All files access" permission to external storage.
Go to your phone's Settings.
Search for "Special app access" and select it.
Tap on "All files access."
Once in "All files access," tap the menu button (often three dots or lines).
Select "Show system" or "Show system apps."
Find "External Storage" in the list and ensure it is enabled (toggled on).
Viewing Multiple Tracks from a Single GPX File
Currently, our system is designed to import only the first track found within a GPX file. If your GPX file contains multiple separate tracks, you won't see all of them as individual routes.
Solution: You have two main options:
Separate Files: Break down your multi-track GPX file into individual GPX files, with each containing only one track. Then, import each file individually as separate routes into the Beeline app.
Merge Tracks: Use a GPX editor to merge all the individual tracks within your file into a single continuous track. Then, import this modified file.
We recommend using online tools like gpx.studio or the software you originally used to create your GPX route, as they often have features to merge tracks.
We hope these solutions will see you off to a great ride. As always, should further issues or questions remain, please do get in touch with us via our contact page here, and we’ll be happy to have another look!