A suggestion and a possible bug

[John Ellerton]

Hi Steve. Love your app. Have been using it for a couple of months now and it has performed admirably.

Can I make a suggestion - when the app gives it's summary of the route so far, I have set it to tell me moving time and distance. I find I am constantly trying to calculate average speed. Would it be easy to add another item - Average speed (distance divided by moving time) to save me from this mental arithmetic ?

A possible bug - on a ride yesterday, the app said I had missed an instruction point. Looking at the route on RideWithGPS, yes I had. I hadn't noticed a left hand corner had a slip road to the left, so I agree that I did miss the instruction point by about 15m but I was back on route within a further 20m. The app then give me the message "You missed an instruction point ...". But this was constantly repeated again and again even though I was back on the route and it was still being repeated when I got to the next instruction point. The only way I could stop it repeating the message was to press "Stop" to stop recording the route. Any ideas ?

Regards, John

[Steve Punter]

That's not a bad idea. I should actually add a few more summary features as well, including (for RWG routes) total distance left, estimated time left, and ETA. If I get some time in the coming weeks, I'll look into that.

As for the bug you have uncovered, the best way to deal with that is to send me copies of the RWG route you were following and the GPX of that ride, along with a description of where on the route the failure occurred. With these two files, I'm able to have a copy of my app SIMULATE your exact ride in hopes that it elicits the same response from the app as it did when you actually rode it. If it works, I have a REPEATABLE failure that I can examine as closely as necessary to find the cause, and formulate a fix.

All RideWithGPS routes are cached in the folder \data\RWG. The GPX files of your ride are in \data\GPX. You can email them to me at pbex...@gmail.com. No guarantees that the simulation will reproduce the problem, or that I'll have enough time to look at it right away. However, I do want to fix this issue, so these files will certainly be the place to start. Thanks in advance.