NYC taxi visualization
nyctaxi.herokuapp.com
NYC taxi visualization
1–10 of 80 posts
Re: NYC taxi visualization
#2I was making a heatmap for taxi data : published for first 5 days for july
http://akuchlous.github.io/NYC_CAB_ANALYTICS/
maybe can help Uber / Taxi drivers figure out where to get most taxifare pickups are!
hosting on github.io
pushing to github.io is awesome. make maps, save and push!
Re: NYC taxi visualization
#3That's super interesting.
I wonder why my guy wandered really slowly up Riverside Ave for like 30 minutes instead of going inland to find a fare. Looks like it's really slow between 11am and 3pm, and constant driving otherwise.
Re: NYC taxi visualization
#4I was surprised by the amount of fares that just went a few blocks. Looks like it should have been pretty walkable in a lot of those cases.
Re: NYC taxi visualization
#5I was surprised at how inefficient some of the drivers' behavior was. I thought after dropping off a fare they would all immediately head to an area they knew of that might have a high likelihood of generating fares. Instead many of them seem to just wander around aimlessly looking for the next fare.
edit: spelling / grammar
Re: NYC taxi visualization
#6I was surprised by the amount of fares that just went a few blocks. Looks like it should have been pretty walkable in a lot of those cases.
Perhaps they're disabled.
Re: NYC taxi visualization
#7The taxi data just has startpoint and endpoint correct?
So the route in between each trip is just a guess?
Edit: Whoops, from the about page:
> The raw data include only start and end locations for each trip. These points were run through Google's Directions API to create the routes shown in this visualization. Of course, these are Google's best choice, not necessarily the one the taxi took.
Re: NYC taxi visualization
#8That's super interesting. I wonder why my guy wandered really slowly up Riverside Ave for like 30 minutes instead of going inland to find a fare. Looks like it's really slow between 11am and 3pm, and constant driving otherwise.
The route information between trips is just a guess. So he could have really just stopped for dinner or something.
Re: NYC taxi visualization
#9That's super interesting. I wonder why my guy wandered really slowly up Riverside Ave for like 30 minutes instead of going inland to find a fare. Looks like it's really slow between 11am and 3pm, and constant driving otherwise.
Only has data for begin/end points of the trips. They're just using google directions to move between the sampled data points - they don't have minute by minute gps location of the cab.
Re: NYC taxi visualization
#10I was surprised by the amount of fares that just went a few blocks. Looks like it should have been pretty walkable in a lot of those cases.
https://github.com/akuchlous/NYC_CAB_ANALYTICS/blob/gh-pages...
data from chriswong : 22% rides are less 1 mile long