Routes are doubling or tripling themselves
Sometimes after I've saved a route and come back to it, the system will double it or triple it and add it onto itself. Example:
https://www.gaiagps.com/map/?loc=11.3/-71.6579/44.1290&pubLink=DVMlEzMsLlYSrZsYnilCbon9&trackId=91e6dd94-0e1e-4061-a5de-988c2a2bd7e2
This is the Pemi Loop in NH. It's 30 miles and about 9,300 feet of gain. Now when I open it, it displays as three laps of the loop. What is going on here?
-
The same thing happened yet again with another attempt at mapping this route:
https://www.gaiagps.com/map/?loc=14.9/-71.5887/44.0649&pubLink=MtI8O26rGiGWXUDSv44wQ1Ok&trackId=be954f64-34ad-4ce8-ad85-5af757cbdfe9Is this actually a bug or am I missing something?
-
This happens to me occasionally too. Not sure why it happens and it can destroy a lot of routing work as I end up having to redo the route. It seems to happen more frequently when the route doubles back on itself (like and out and back) or where the route crosses over itself. Again, no fix for you but I have experienced this a number of times as well.
-
Just happened to me again today, which is why I'm back in these forums! A route I was going to ride tomorrow that I painstakingly created was 62 miles. And it had stayed that way for a few days. Now, I return to the route and it has looped itself 5x times and is now 301.1 miles!
There is no easy fix. You can't trim a route like you can do a track that you've forgotten to stop recording. Boy would that be helpful! And it would be madness to try and edit individual points that have looped on themselves five times.
I notice this error happens when points on the route overlap (like in a figure 8 where they cross) or when parts of the route double on themselves, like in a lollipop route where the "stick" of the handle is an out and back to get to the loop part. My guess is the algorithm is stupid and gets confused by the overlapping and the out and back portions.
This has happened to me many times for a LONG time now.
What to do? Delete the route and redo the whole thing of course! And then export as fast as you can (I use Garmin hardware for turn by turn directions during the event) before the bug crops up and ruins the route. At least this way, I can get a "clean" .gpx file before the issue crops up again.
EDIT: I just got lucky. I hadn't sync'd the Gaia app since noon today, so the route in question was not yet damaged on the app! Hahahahah. So I exported the correct version (62 miles) of the route from the App to my desktop using mac's nifty AirDrop feature and then imported the route BACK into Gaiagps.com. Voila! The original route is back. For now. Annoying? Yes, beyond belief. But at least I now have something to import into Garmin for tomorrow.
-
@5stone -
That's very interesting, I really hadn't noticed this. On the other hand, I use Gaia mostly for hiking and trail running and it's most often the case that my routes loop back on themselves or cross in some way. But yes, the route that I opened this thread with is indeed a lollipop with a very short stick.
I'm also a road rider in additional to avid hiker, but I use ridewithgps to plan my rides and then put them into Garmin. And, Garmin itself has not been too kind to me these days. It red lines rides just fine, but go off course just one teeny bit - and you're screwed. But, ridewithgps has been nearly flawless for route planning. -
These has been happening to me for at least 6 months. It so frustrating. Just happened again yesterday. I created a route in the Adirondacks. Came back today to check something out, and sure enough it was doubled up. I have used this program for years and have over 250 routes, but with the frequency of this occurring, I am seriously considering moving to another program. GAIA GPS please fix this.
-
Just happened to me again for a route that's been solid for weeks; when I opened it this morning so I could ride it tomorrow, it "changed" the mileage by 10+ miles. Now I have to redo the whole frickin' thing. Kinda pissed. Typically I've tried to give Gaia a pass because they got bought (how's that metaverse initiative panning out? No?), lots of layoffs (see above), etc. etc. but this has been a problem for a LONG time and they don't fix it. Instead they move on to new features in order to market them probably because the only thing that matters is attracting new subscribers. And NEW subscribers won't know they don't fix years old bugs. Jesus. Can you imagine Strava having this kind of bug for years? And they're BOTH subscription services; they both take our money. Super annoyed right now. Really? we need to incorporate Open Snow pinpoint weather before you fix this essential part of your route planning? And work on more new layers and constantly redesigning your existing proprietary layers (Overland, anyone?) yet AGAIN before you fix stuff like this? THIS IS A FUNDAMENTAL FLAW IN A BASIC, BASIC FUNCTION. PLEASE FINALLY, AFTER YEARS, FIX IT.
CORRECT ROUTE (42.4): after redrawing the whole friggin' thing
THE F'D UP ROUTE (54.6)
Isn't ANYONE embarrassed by this? WHO originally programmed this? SOMEONE did it. Don't you get annoyed when you use your own system to work out and it does this? Why don't these basic bugs make that secretive "Road Map" of yours?
-
This is happening to me on a complicated route I've now created from scratch 4 or 5 times thinking it was operator error. It's really disappointing to see that this thread is 8 mos old and another is 10 months. We're doing a big mapping project at our park and I don't think we're going to be able to use this product unless there is a solution.
Please sign in to leave a comment.
Comments
9 comments