3 ms·
Like many other comments, I like this and find it useful. Recently I took a Lyft ride late from SFO to home and it was late and I was tired and I didnt concentr
by periferral 7y ago
Like many other comments, I like this and find it useful. Recently I took a Lyft ride late from SFO to home and it was late and I was tired and I didnt concentrate on the route taken by the driver but I was certain we took the 101. Later when I saw the charge, I was surprised to see the ride map showing me taking a roundabout way, heading on 280 and essentially doing a 70mile ride. I complained to Lyft and they refunded the money but I still wanted to know how I got home. Checked back on this and found that it was in fact a regular 101 ride home and I had proof just in case Lyft wanted it.
As others have mentioned, it is nice to look back at the trips I took and also share with others who might be visiting places where I have been in the past.
- futureastronaut 7y ago> it was in fact a regular 101 ride home Confused... you make it sound like faulty location history led you to erroneously report your Lyft driver. But that doesn't jive with the tone and thrust of your comment.
- buckminster 7y agoIt sounds like the Google map confirmed his intuition but the Lyft map had a lengthy bogus route. So he was overcharged.
- periferral 7y agoSorry my post was confusing. Lyft had the wrong route (280 and longer) Google confirmed my suspicion that we took the shorter route (101) Lyft credited back regardless but it was good to know what really happened
- 0xffff2 7y agoI too am confused. If I'm interpreting (guessing) correctly, Lyft showed (and charged based on) an erroneous route in their app. GP reported it and got a refund, but after reviewing Google's location history found that the driver had actually driven the route that they expect, not the route that Lyft claimed they did.