I wanted to add that so far it seems like old routes works and new routs doesn't. I don't have a time line. I came here after I found that new routes I just made didn't work.
Same for me
Route
http://www.gps-sport.net/routes/13km-from-home-and-south_190720
3 runs after creation of route that is not picked up
http://www.gps-sport.net/trainings/13km-from-home-and-south_1907212
http://www.gps-sport.net/trainings/13km-from-home-and-south_1912497
http://www.gps-sport.net/trainings/13km-from-home-and-south_1916442
20.08.2016 14:05:41 UTCgeändert am 23.08.2016 21:20:44 UTC
Hi admin,
I hope you will find a solution on your server.
Like you already said was for 25% of my trainings the corresponding route found.
But allmost all of my trainings are exactly the same as my routes, with deviations of 0 to max. 3 meters.
A fine feature on your site would be if we could link a training to a route afterwards, in case the route wasn't found.
Meaning that the route has been found as a possible matching candidate, but could not be loaded from the server. This seems to be an internal technical problem and we'll investigate and solve it.
It's also not working for me:
First example:
route:
http://www.gps-sport.net/routes/Bolko_191001
training:
http://www.gps-sport.net/trainings/running_1910951
Second example:
route:
http://www.gps-sport.net/routes/Obwodnica_190992
training:
http://www.gps-sport.net/trainings/running_1910953
This function does not depend on the app version - it's solely done on the gps-sport.net server.
I can see from your logs, that some trainings are assigned to a route, e.g. this one: http://www.gps-sport.net/trainings/St-Oedenrode_1891450
The routes and trainings are compared point by point and if the deviation is too high the route is not assigned. It's also important that the starting point of route and training match by at least 50 meters.
Since the end of april the connection between my new trainings and (new and existing) routes is gone. Every training I upload has this "no matching route found" message ever since.
* Is this due to an upgrade or a setting in my app (I now have version 3.1.9 build 4413)?
* Is it possible to fix this on trainings that are already uploaded to the Community?