A Visualization with Citibike Data
Bike-shares have become popular in major cities all across the US. Citibike in NYC is among one of the most popular. It's a convenient and fun alternative to taking the bus or subway.
For this Shiny project I was interested in utilizing Citibike's public database to bring this information to life through visualization. I was curious in bike station user activity with respect to a chosen hour via a heat map. Additionally I wondered what was the journey of a given bike throughout any chosen day.
Application and Results:
For this app there are 3 tabs to choose from; density map, trip map and data. The Density map tab contains two displays. On the left is a map of NYC and the right is a histogram. Additionally there are two selection boxes where you can choose the day and hour of interest. The map on the left displays the the number of users that checked out bikes from stations within the selected hour. This is displayed as purple clouds, the darker and larger the cloud relates to more users active at that station. On the right is a histogram displaying the number of users for any given hour of that selected day.
Figure 1: Density map
From the histogram we can see there are two peaks. One in the morning and one in the evening. This is not such a surprise given that the date chosen is a typical weekday in the mild month of September. Also notice the hour chosen is 5 pm and the density map is saturated in Manhattan, but sparse in Brooklyn or Queens. This suggests most users are leaving work from Manhattan.
The next tab is the trip map. It contains a single map display and two selectors. The selectors allow you to choose a bike ID and date. With these inputs selected the map will display that bike's entire journey for that day from all users. The red marker is the starting point and blue is the final end point. The travel path gets darker for multiple trips over the same path and lighter for single trips. Also it's worth mentioning here that the path displayed is the suggested bicycling route via google directions. It is the most likely path taken, but not the true paths taken by all users.
This app is convenient and easy to use, but there is far more room for expansion. For future editions the user will be able to graphically see the range traveled of a specific bike given a selected duration of time, not just a day. This can be displayed via a histogram or the trip map. This will give insight if bikes generally stay in one location or cycle through different boroughs.
Another feature to add is a play button to observe the user density map throughout the way.
Additionally this app can be scaled up to multiple bike-shares in other cities. This is very possible given most other bike-shares have public data sets with similar information and formatting.
Thanks for reading!