Sri Mittapalli College of Engineering

Department of Computer Science and Engineering g

A SHINY INTERFACE IN EXPLORING THE TAXI
TRIPS DATA

Present by
Batch A6
B.Mounika(15U91A0511)
M. Maneesha (15U91A0576)
G.Jeevana Jyothi(15U91A0532)
A.Durga Tirumala Rayudu(15U91A0503)
B.Vijay Sai(15U91A0512)
Under the guidance of
Mr.G.Dilip Kumar M.Tech.,
Assistant professor
 Contents
• Abstract
• Introduction
• Existing System
• Proposed System
• Modules
• Architecture
• System Design
• Implementation
• Code
• System Requirement Specifications
* Functional Requirements
* Non Functional Requirements
 ->Software Requirements
->Hardware Requirements
• Conclusion
• Future Enhancement
ABSTRACT
Our project aimed at performing an analysis of
commuting patterns, neighbourhoods, traffic, tipping patterns,
taxi fares (and more) in urban communities. The purpose is to
extract useful insights so that any solutions that we derive can
be mapped to other large cities. This dataset includes trip
records from all trips completed in green taxis in NYC in
2015.Records include fields capturing pick-up and drop-off
dates/times, pick-up and drop-off locations, trip distances,
itemized fares, rate types, payment types, and driver-reported
passenger counts.
 INTRODUCTION
• The dataset contains close to 200 Gigabytes of New York City
Yellow Cab and Green Taxi trips.
• The dataset contains detailed records of over 1.1 billion
individual taxi trips in the city from January 2009 through
December 2016[2].
• Each record includes pick-up and drop-off dates/times, pick-
up and drop-off precise location coordinates, trip distances,
itemized fares, and payment method Figure [1],depicts a heat
map of the NYC taxi trips[1].
Figure 1: NYC taxi trips heat map
 EXISTING SYSTEM
• The existing system or the application or the people used to
analyse the data based on worksheets, which doest fetch
enough results.
• This makes the company not to predict the actual information
and peak details and earnings of the company.
• Every detail are stored in a perfect database which in turn
creates a lot of data mess, which deals with difficult in the
analysis of the drives made by the people and the number of
drives made by the people.
 DISADVANTAGE
The designed application is not so user friendly and
doesn’t have a better user interface which led the users with a
bad perspective over the application.
• Daily updates to be loaded into the dataset and process the
data.
• No proper methods were used in the application.
• No logical packages for filtering the text.
• Libraries are not efficient in analysis user data is never
considered in the enhancement of the product.
 PROPOSED SYSTEM
• In our proposed system we are trying to create an interface
such that a dynamic interface can be explored on the data.
• To find out the peak hours in the trips data.
• The R program has many in built methods and a library to
work.
• We are using R programming to analyse the log files. The R
program has many in built methods and libraries to work.
Programming is easy.
• In our proposed system we are using new technologies for
developing the application and using some specific methods in
the library.
 ADVANTAGES
• R has a huge packages which are more efficient to work on
heavy data and any kind of data format
• R can also be connected to Hadoop to work on the big data.
• User friendly programming language.
• Has a CRAN Library.
• It has package as inbuilt libraries are used at most to analysis .
MODULES:

• Creating shiny interface

• Processing of the data
• Forecasting the results
ARCHITECTURE:
 SYSTEM DESIGN
USE CASE DIAGRAM:
Exx
Epp
oo
rtrt
ddaa
ta
ta

MaM ain
inta ta
in in
d data
ata

Client U u
pdp
adad
te te data
ata

Install shiny
Install shiny

LoadLs
oh
ain
dyshiny

LL
oo
aa
dddd
aa
ta
tato
tobb
uu
ffe
ffe
rr

Analyze the data User

System Analyze the data

G
Gee
nn
ee
rate
raterese
thults
results

Proce
P s
ros
ceth
sseth
da
eta
data

Crea
Ctes
re U
atesU
er
seIn
rterte
Infac
rfe
ace

T
Taa
kk
ee d
thata
e dafta
romfroR
mbufb
R fe
urffer

Serves UI.R
Serves UI.R

Shiny
ServS
eer
s v
s s
ervs
eerv
.R e.R

P
Procer
soce
s s
thsr
e th
eqeur
eeq
stuest

Ge
Gne
en
ra
ete
rate
ins
In
ta
sn
ta
tnre
ts
Rue
lts
sults

Storere
Sto data
data
server

MM
ana
an
ga
ege
dadata
ta

Sto
Srerr
to eesu
relts
sults
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
STATE CHART DIAGRAM:
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
 IMPLEMENTATION
• R is a programming dialect and programming condition and
designed by the R Foundation for Statistical Computing.
• The R dialect is generally utilized among analysts and
information mineworkers for creating factual programming and
information analysis.
• R was created by Ross Ihaka and Robert Gentleman at the
university of Auckland and is developed by the R development
core Team.
• R can deal with date factors in a few ways. There are worked in
R capacities accessible to manage date factors, and there are
additionally some helpful contributed bundles accessible.
• In any case, there is another R bundle, lubridate, contributed by
Grolemund that gives a great deal more easy to use usefulness
to manage date and time with time zone bolster.
Cont..

Here we are using some libraries:

 dplyr
 lubridate
 BH
SAMPLE CODE
library(dplyr)
library(lubridate)
library(BH)
taxiData<- read.csv ('D: /R Project/NYC/ tripData.csv', stringsAsFactors = FALSE)
View(taxiData)
vendorid_catageory<- table(taxiData$VendorID)
View(vendorid_catageory)
barplot (vendorid_catageory, main="Vendors Categeory", xlab="Yellow and Green Taxies”, lab =
"Count", col = topo.colors(10))
passenger_count<- table(taxiData$passenger_count)
View (passenger_count)
barplot (passenger_count, main="Passenger count", xlab="Passengers”, lab = "Count", col =
topo.colors(10))
fare<- subset (taxiData, taxiData$total_amount>10)
View(fare)
UI.R
shinyUI(pageWithSidebar(
headerPanel('A Shiny Interface in Exploring the newYork Taxis'),sidebarPanel(
selectInput('day','Choose the day',choices = c( 'Sunday' = 1,'Monday' = 2,'Tuesday' =
3,'Wednesday' = 4,'Thursday' = 5,'Friday' = 6,'Saturday' = 7) ),
SliderInput ( 'StartHour','Choose the starting hour',min = 0,max = 23,value = 3),
SliderInput ('endHour','Choose the ending hour',min = 0,max = 23,value = 7)),
mainPanel(
p('The analysis will show you the number of taxi trips that occurred on a particular day between
the selected hours.'),
h4('The day you chose:'),
verbatimTextOutput('day'),
h4('The starting hour you chose:'),
s verbatimTextOutput('startHour'),
h4('The ending hour you chose:'),
verbatimTextOutput('endHour'),
h4('The number of yellow taxi trips in the selected time period'),
plotOutput('taxiPlot')
)
))
SERVER.R
library(dplyr)
library(lubridate)
library(BH)
taxiData<- read.csv('D:/R Project/NYC/tripData.csv', stringsAsFactors = FALSE)
taxiData$tpep_pickup_datetime<- ymd_hms(taxiData$tpep_pickup_datetime)
taxiData$Day<- wday(taxiData$tpep_pickup_datetime)
tripsPlot<- function(day, startHour, endHour) {
tripsData<- subset(taxiData, Day == day)
tripsTable<- table(hour(tripsData$tpep_pickup_datetime))
tripsTable<- tripsTable[startHour + 1:endHour + 1]
taxiPlot<- plot(tripsTable, type = 'o', xlab = 'Hour', xlim = c(startHour, endHour))
return(taxiPlot)
}
shinyServer(
function(input, output) {
output$day<- renderPrint({input$day})
output$startHour<- renderPrint({input$startHour})
output$endHour<- renderPrint({input$endHour})
output$taxiPlot<- renderPlot({tripsPlot(input$day, input$startHour, input$endHour)})
}
)
OUTPUT
VALIDATION
The system has been tested and implemented successfully and
thus ensured that all the requirements as listed in the software
requirements specification are completely fulfilled.
TEST CASES

Test id Test case Output Result Priority Error result

1. Load libraries Loaded Loaded None None

Cant open the

2. Load data Loaded High Check the path
connection

3. Loading libraries Loaded dplyr missing High Install dplyr

4. Run App Execution No shiny found High Install shiny

TEST CASE 1:
TEST CASE 2:
TEST CASE 3:
TEST CASE 4:
 SYSTEM REQUIREMENT
SPECIFICATION
FUNCTIONAL REQUIREMENTS:
• Collect and transmit trip data, authenticate drivers, and accept
credit card payment
• Accept and display E-Hail requests from licensed E-Hail
Providers
• Accessibility to all approved E-Hail Providers via an open
application programming interface (“API”)

E-hail: “E-hail is an app that connects you to get safe, reliable

rides from licensed professional taxi drivers on demand.”
NON-FUNCTIONAL REQUIREMENTS:
SOFTWARE REQUIREMENTS:
• Operating System : Windows 7, Windows 8,
(or higher versions)
• Frame work : Twitter
• Language : R 3.2.5 version
• R Studio (IDE) : It is a powerful and productive user
interface for R
• Browser : Mozilla Firefox (or)any browser.
• Office Application: Microsoft Excel(or)open office
HARDWARE REQUIREMENTS:
• Processor : Pentium 3, Pentium 4 and higher
• RAM : 256MB/4GB RAM and higher
• Hard disk : 40GB and higher
 CONCLUSION
In this we conducted classification model for
analyzing the data of taxis which found to be more effective
than the statistical models, creating the subsets for
required data based on the probability models. The results
obtained are pretty much helpful for the organization in
arranging the cabs in peak hours at different location
which in return provides enough profits for the company
and the analysis that helps in identifying the better
locations for the cabs to be maintained.
 FUTURE ENHANCEMENT
The analysis is done for only the data available online. The
same can be implemented to the data of national and taxis like
OLA Cabs, Radio cabs etc..This will result in economic growth of
the company and also improve the financial value of the cabs. The
application seems to be work with almost 200000 lines of the data.
The same can be implemented with Hadoop and R. This can be
applied using the R Statistics which works well in the Hadoop and
R framework. This produces a huge amount of data analytical
platform with the best use of all available resources. Finally
implementing the analysis with shiny makes ease of analyzing the
data and improved the economic value of the products.
 References
1. www.nyc.gov/html/tlc/html/about/trip_record_data.shtml
2. pdfs.semanticscholar.org
3. S. Agarwal, B. Mozafari, A. Panda, H. Milner, S. Madden, and I.Stoica
Blinkdb: EuroSys, pages 29–42, 2013
4. NYC Taxi & Limousine Comission.
http://www.nyc.gov/html/tlc/html/about/about.shtml.
hhhgjgfg