Introduction

For our visualization project, we’ve chosen the “Analyzing Citybike Data” topic, because all of us are using the citybike service. In addition we really like the concept of sharing services like cars, bikes and other shareable resources. We ♥ citybikes.

Target application

In this visualization we’d like to create a webapplication, which provides the user the possibility to understand and analyse the more complex dataset of the citybikeservice. For this purpose we’d like to use a dataset which offers data information about the most frequently used stations, the occupancy of the stations, damage reports, driven routes etc. After checking at citybikewien.at we managed to find a csv-dataset which holds all stations with its properties. Furthermore we got some datasets from the professors of the course. Our visualization should provide a general overview of the citybike-service and is directed to all of the people, which are interested in citybikes. We created some different solution attemps to visualize a big dataset like this and tried to develop a broad spectrum of possibilities. So there are prototypes, which provide a station-comparisor or approximately draw likely driven routes to visualize connectivity between stations. After the presentation of M2 we'd really would appreciate feedback to our prototypes to define a specific direction of the project.

Dataset

User

We expect our users to be mainly cyclists, who are interested in citybikes and want to see which and how many stations there are. And which stations to pick or to avoid considering the station’s frequent usage. But there are even more possible users, like someone who's considering opening a restaurant or a bar. Maybe that person would like to check which station is really busy to find the perfect spot for his pub.

Implementation Details



We want to build a modern Application which runs on every platform. To accomplish this goal, we decided to build a Web Application which supports all modern web-browsers. The Web Application will be written in JavaScript. JQuery will be used to keep the application browser independent and to save us from writing code for each separate web browser. The d3 toolkit will be used for creating charts and views. The Google Maps API allows us to create an interactive map where we can draw bicycle routes and provide the user with a familiar interface to work with. To increase the performance we need to split the datasets in parts and load them when needed. Therefore we're going to use C#.NET and Java.

Timetable

Because of the project size and the small time frame each member of the team is equally involved in every task.

# Milestone Tasks Begin Date End Date
1 Proposal - April 14, 2015 May 05, 2015
2 Setup Environment Config Workstations, Set Up IDEs May 5, 2015 May 10, 2015
3 Dicuss Prototypes Discuss about Features May 11, 2015 May 15, 2015
4 Build Prototype Build Google Maps View and D3 Charts May 16, 2015 May 29, 2015
5 Presentation - May 30, 2015 June 01, 2015
6 Implement Prototype Finisg Maps and D3 Charts June 02, 2015 June 07, 2015
7 Tests Application Test and User Test June 08, 2015 June 12, 2015
8 Bugfixing / Improvements - June 13, 2015 June 17, 2015
9 Final Report - June 18, 2015 June 29, 2015