[tossaway842]

I'm more interested in the data than the tool. What was the start and end point for the trip and other details.

For example, this makes no sense:

"I had this one delivery that was an hour-and-a-half long and I got paid $16 and I thought, 'There is no way that's right,'" Armin Samii, an unemployed computer scientist who has been working Uber Eats on the side, told Salon. "I looked into it and found out that Uber paid me for a one mile delivery instead of a four mile delivery. Of course it's all made worse because I'm on a bike and they don't account for that, but that's a separate issue."

A 11 mile hill climb of Mount Hamilton with 2700 of elevation gain takes me about 1.5 to 2 hours to do. A straight hill climb which you would only find in cities like Hong Kong or Rio de Janeiro is like the worst case scenario. A 4 mile trip in pretty much any major city should be maybe 20-25 minutes with stop signs and traffic lights. Not saying there wasn't an issue with that trip, but this makes no sense.

I have worked a lot with this stuff in my career, so I'm inclined to want to see the data myself so I can try and reverse engineer what may have happened.

Furthermore Armin Samii appears to have worked for a direct competitor of the company he's criticizing while developing this.